You are not logged in.
The Freia version of openvpn is already backported to Excalibur-backports:
https://backports.debian.org/trixie-backports/overview/
To add the backports repository:
https://www.devuan.org/os/packages#add- … default-no
And to install the package:
The quickest way to get security fixes is to track Ceres (unstable).
Of course that is also the quickest way to get bugs!
Excalibur has runit integration for power-profiles-daemon via runit-services: https://pkginfo.devuan.org/cgi-bin/pack … .1+deb13u1
Devarch,
the keyword is "Ceres" smile
True, but I have now backported runit-services to Debian trixie, meaning the Devuan excalibur-backports repository gives access to the version of runit-services which is in Devuan Freia, as of today (0.12.0~bpo13+1).
That covers services which got added in Freia's version of runit-services; it does not cover the tiny number of packages which obtained their own native runit scripts in Freia as they would need to have their own individual backports, too.
I don't _think_ this can be your problem because you have reconfigured the timezone based on the files you _do_ have, but one differnce between Daedalus and Excalibur is that a lot of non-canonical timezone forms were - with doubtful justification - split off into a new package, tzdata-legacy. More likely to affect people upgrading I should think, but might be worth installing it anyway.
polkitd already works fine for me, probably launched by dbus. Same with accountsservice.
I'd also advise against patching the DEBAIN/postinst etc. maintscripts - these are _outputs_ of the package build process and this is just asking for trouble over time. Better to patch the source packages in the proper way and let the debhelpers set up the maintscripts. Better still, try to do it in Debian first and then in Devuan if a maintainer absolutely refuses to co-operate with a polite attempt to contribute.
A lot of work is being done on user services for different init systems for Debian. The runit packages are getting a solution soon that has been long in development, I think there's an openrc solution AND at least one generic solution, and that's just the ones going into standard packages. And on the specifics of pipewire integration for existing Devuan releases there's a huge thread for that already.
I am not convinced it is worth copying runit service directories or initscripts from other distros: almost always the required work is minimal but there's often a lot of legacy crud (especially in Debian initscripts) that was perceived to be important once but isn't anymore.
It's better to write from scratch.
The challenging parts, such as they are, often relate to system integration considerations that are distro-specific, how to ensure consistent behaviour across init systems and how to make sure upgrades work well.
Honestly, the systemd service units are a better source of ideas but even they often cargo-cult from what has gone before (including otiose initscripts).
Devuan only supports SysVinit, and OpenRC is considered a fake init in this context, similar to runit (frankeninits). This means that even if I choose OpenRC during installation, the boot process will still be managed by SysVinit.
I don't think that's fair about runit. In ceres now 21 packages have native runit integration for their daemons and the runit-services package adds 55 additional services (of which 2 were added today). Most of the services on my laptop are now covered in stage 2.
The single-shot/startup actions (stage 1) are not so well covered but I think some commonality with other inits makes sense for these things.
OpenRC I think is held back by not having a second directory where openrc's own interpreter can be used to override the initscript fallbacks. I suspect that would be a useful improvement for the debian package, although this is guesswork as I don't use OpenRC and don't plan to.
Hi Altoid, I also only learned about it because of the warning, and it didn't escape my realisation that this was a blessing! However, it is a newish feature really something of value to packaging developers and it will now be covered by the man page, which I think is appropriate. Any package that wants a drop-in for this directory will implicitly create it, which is the normal way for directories in Debian, so I agree with the accepted resolution.
Altoid wrote:
And lo, it was done.
Oh ye of little faith!
The message will be removed and documentation added in the next upstream release. Expect in Freia. :-)
Hi Altoid,
You could try filing a bug against INIT: no inittab.d directory found with the Debian devs.
But you will not like the reply.
I would not be so sure!
Watch this space: https://bugs.debian.org/1131137
It has probably been removed from the Debian installation process because systemd does not need it.
This functionality got added in 2020 so it probably never was used in Debian as standard!
https://github.com/slicer69/sysvinit/co … fcf8740c49
I had been wondering if we should get it added (via Debian) by default to encourage its use for drop-ins rather than maintscripts editing /etc/inittab.
People running Ceres/Freia helps make Freia good!
One thing to bear in mind is that the baseline of required x86 extensions is raised on 6.0 so some userspace packages that worked on 5.0 may be incompatible with 6.0. In my case that includes Firefox on one PC.
Well your fix is released already... that's what I call service! https://tracker.debian.org/news/1712683 … -unstable/
I would expect the package to be available within about 3 hours plus whatever the delay to devuan replication is.
Consider this a bug report.
I'm out, and still angry.
There's no justification for anger. Runit has a diligent maintainer who is extremely attentive to actual bug reports - which this isn't - as you can see from his fast resolution of the bug report I posted above. Use 'reportbug runit-init'. You should include your analysis of the problem and suggested solution.
I don't know why you seem to have to different slim startup scripts in parallel.
But it won't be helped by the existence of this bug, which has a simple fix/workaround: https://bugs.debian.org/cgi-bin/bugrepo … ug=1121099
Good news: we've worked out (on the bug) why this happens and are discussing the most appropriate patch to the elogind source which lets us benefit from the intended changes in the latest package.
This looks like https://bugs.devuan.org/cgi/bugreport.cgi?bug=937 - for which I must take blame as it was an enactment of my suggestion, but it is really not clear how it can be causing these problems. If anyone is handy with dbus logs there are some to decode there.
The reason I asked wasn't as a workaround but to try to diagnose the underlying problem but thanks!
There is an official initscript (by me) for stubby in ceres. So far no one has committed to wanting to install it from excalibur/trixie-backports but that could be an option if there were demand.
Here it is: https://sources.debian.org/src/getdns/1 … tubby.init
Have you tried killing slim and restarting it, or not letting it start and then manually starting it? Could be a startup ordering and synchronization issue. Are you using sysvinit?
The initscript for stubby didn't make it in before the Debian Trixie freeze: https://tracker.debian.org/news/1650899 … erimental/
If anyone wants the current version in Excalibur it might be worth politely indicating on the Debian BTS that there would be demand for a stable backport.
@tux_99 thanks for your comments! Not the original author, no, but it was abandoned for 20 years. I fixed a bug earlier in the year and before you know it I had forked it and fixed a ton more - the changelogs are under /usr/share/doc/sysv-rc-conf. The Debian trixie freeze had already started so this was too late for excalibur.