You are not logged in.
or at least one version behind?
I believe many of us out there are running arch on servers like me. I love arch running on servers but just need the core packages to be more LTS-ish.
eg. v260 is coming but it deprecates sysv scripts. I have UPS monitor service written in sysv.
Offline
make a feature request https://gitlab.archlinux.org/archlinux/ … d/-/issues
I Have Linux Perl Can i Download Gnome???
Offline
Everyone has known that was coming, really ever since systemd started getting adopted. If you've put off migrating this long, it's not systemd's issue. Arch already uses the stable releases, which is currently 260.
but just need the core packages to be more LTS-ish.
That's a very non-rolling-release attitude. That's not Arch at all.
Last edited by Scimmia (2026-03-19 01:26:14)
Offline
What difference does it make to have the same work but half a year later? You'll need to migrate away from that anyways ![]()
Offline
I have UPS monitor service written in sysv.
There is a big chance that sysv service can be easily ported to systemd.
Online
The idea for dropping support of sysv scripts is ten years old. In December 2025, they announced that it will be finally removed from systemd.
Offline
Maintaining a PKGBUILD fo systemd-stable in AUR would be the first step. That would show if the idea flies and make it visible to package maintainers. I believe this is in line with the guidelines: systemd-stable is a separate line officially maintained by the upstream.
As noted by others, however, keeping old versions as a systematic behavior has never seen endorsement from Arch. There are exceptional situations, like dependencies⁽¹⁾ or delays due to unexpected, serious breaking changes.⁽²⁾ There are also packages with version that are ahead of stable.⁽³⁾ LTS versions are not about keeping things old. They’re both about freezing API for developers and about guaranteeing updates for time much longer than the standard release cycle. LTS versions will often outlive multiple releases in the non-LTS line(s). Systemd-stable is not an LTS release.
____
⁽¹⁾ For example electron, currently from 31 to 39, or JRE from 8 to 25, or GTK or Qt libraries.
⁽²⁾ E.g. dovecot 2.3, because 2.4 suddenly introduced configuration changes that both require a major, complicated rewrite of configs and block access to some features.
⁽³⁾ nginx-mainline vs stable nginx.
Last edited by mpan (2026-03-19 13:49:33)
Paperclips in avatars? | Sometimes I seem a bit harsh — don’t get offended too easily!
Offline
Maintaining a PKGBUILD fo systemd-stable in AUR would be the first step. That would show if the idea flies and make it visible to package maintainers. I believe this is in line with the guidelines: systemd-stable is a separate line officially maintained by the upstream.
That would be a terrible name, though, as the current stable branch is what Arch already packages.
Offline
I agree, but that’s how the upstream calls it.
Paperclips in avatars? | Sometimes I seem a bit harsh — don’t get offended too easily!
Offline
No, they don't
Offline
yes they do...
Offline
That repo:
A. Has multiple branches for each version, it's not it's own thing.
B. Is semi-abandoned as newer versions are branches in the main systemd repo.
Offline
I edited my post while your replied to link to the currently maintained "systemd-stable" branches in the systemd repo.
Offline
Branches which are called v260-stable, v259-stable, etc, not 'systemd-stable'. And which Arch is already packaging from.
Last edited by Scimmia (2026-03-19 14:19:29)
Offline
Offline
Which is the link I was replying to in https://bbs.archlinux.org/viewtopic.php … 7#p2291247. That repo is no longer relevant.
Offline
"systemd-yore", but this really doesn't address https://bbs.archlinux.org/viewtopic.php … 6#p2291226
stall systemd locally, migrate your sysv scripts and then update.
Postponing the changes will not prevent them and you'd at worst face the a shitload of incompatibilities and headaches when jumping from systemd-256 to systemd-384, especially because "systemd" is more like "lennarts grabbag" and the update covers a wide array of functions.
Not (effectively) re-installing or setting aside a week(end) for a major version upgrade is kinda the point of a RR distro, so you probably didn't want to?
Offline
That repo:
A. Has multiple branches for each version, it's not it's own thing.
B. Is semi-abandoned as newer versions are branches in the main systemd repo.
To reinforce Scimmia here see the announcement from almost 2yrs ago:
• https://github.com/systemd/systemd/blob … table/NEWS
* Stable releases for version v256 and newer will now be pushed in the
main repository. The systemd-stable repository will be used for existing
stable branches (v255-stable and lower), and when they reach EOL it will
be archived.
Coincidentally, and for the OP, in the same release notes:
* Support for System V service scripts is deprecated and will be
removed in a future release. Please make sure to update your software
*now* to include a native systemd unit file instead of a legacy
System V script to retain compatibility with future systemd releases.
As others have noted... a decade of heads-up, and repeated reminders should have sufficiently weened folks off their archaic scripts.
Offline