[opensuse-project] systemd 234? what the literal eff you cee kay?
OK, who decided to stick with a THREE YEAR OLD systemd in Leap 15.2, and why? There are open bugs in that version that have been fixed TWO YEARS AGO. Asking for advice about that kind of stuff upstream is just plain old embarrassing! Can I safely replace that with the up to date systemd from factory? Cheers Mathias -- Mathias Homann Mathias.Homann@openSUSE.org Jabber (XMPP): lemmy@tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
Hi Mathias, Mathias Homann <Mathias.Homann@opensuse.org> writes:
OK, who decided to stick with a THREE YEAR OLD systemd in Leap 15.2, and why?
There are open bugs in that version that have been fixed TWO YEARS AGO.
Asking for advice about that kind of stuff upstream is just plain old embarrassing!
I would like to give you a "good" reason, but it boils down to systemd coming from SLE and that there probably wasn't the time and/or manpower to update it for SLE 15 SP2. However, I would kindly ask you to consider using a different tone in the future. The currently very negative tone on the mailinglists is actively detracting community members (see for instance: https://lists.opensuse.org/opensuse-project/2020-07/msg00116.html).
Can I safely replace that with the up to date systemd from factory?
Yes, if you feel confident with dealing the unpredictable and potentially catastrophic fallout. So the answer is rather: no, don't do it, things will probably break.
Cheers Mathias
-- Mathias Homann Mathias.Homann@openSUSE.org Jabber (XMPP): lemmy@tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
-- Dan Čermák <dcermak@suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer
Am Montag, 20. Juli 2020, 10:58:22 CEST schrieb Dan Čermák:
Hi Mathias,
Mathias Homann <Mathias.Homann@opensuse.org> writes:
OK, who decided to stick with a THREE YEAR OLD systemd in Leap 15.2, and why?
There are open bugs in that version that have been fixed TWO YEARS AGO.
Asking for advice about that kind of stuff upstream is just plain old embarrassing!
I would like to give you a "good" reason, but it boils down to systemd coming from SLE and that there probably wasn't the time and/or manpower to update it for SLE 15 SP2.
However, I would kindly ask you to consider using a different tone in the future. The currently very negative tone on the mailinglists is actively detracting community members (see for instance: https://lists.opensuse.org/opensuse-project/2020-07/msg00116.html).
@all: sorry for that.
Can I safely replace that with the up to date systemd from factory?
Yes, if you feel confident with dealing the unpredictable and potentially catastrophic fallout. So the answer is rather: no, don't do it, things will probably break.
Here comes ye olde VM ... XD Cheers Mathias -- Mathias Homann Mathias.Homann@openSUSE.org Jabber (XMPP): lemmy@tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
Hi Mathias, On 7/20/20 10:58 AM, Dan Čermák wrote:
Hi Mathias,
Mathias Homann <Mathias.Homann@opensuse.org> writes:
OK, who decided to stick with a THREE YEAR OLD systemd in Leap 15.2, and why?
There are open bugs in that version that have been fixed TWO YEARS AGO.
Asking for advice about that kind of stuff upstream is just plain old embarrassing!
I would like to give you a "good" reason, but it boils down to systemd coming from SLE and that there probably wasn't the time and/or manpower to update it for SLE 15 SP2.
That's one part of the reason, the other is that the risk of introducing regressions and incompatibilities is very high with systemd and we try to avoid that during SP releases (for SLE) or minor releases (for Leap). Therefore, we are doing a more cautious approach and backport fixes and features from upstream to our systemd v234, where possible. (unfortunately, not always possible after some features and fixes are quite intrusive, but we are doing our best ;) ) And, as opposed to Tumbleweed, where we are very close to upstream, if you encounter any issues with systemd v234, we usually don't refer to upstream, but try to help as good as possible. I hope that makes things more clear? Regards, Benjamin
However, I would kindly ask you to consider using a different tone in the future. The currently very negative tone on the mailinglists is actively detracting community members (see for instance: https://lists.opensuse.org/opensuse-project/2020-07/msg00116.html).
Can I safely replace that with the up to date systemd from factory?
Yes, if you feel confident with dealing the unpredictable and potentially catastrophic fallout. So the answer is rather: no, don't do it, things will probably break.
Cheers Mathias
-- Mathias Homann Mathias.Homann@openSUSE.org Jabber (XMPP): lemmy@tuxonline.tech IRC: [Lemmy] on freenode and ircnet (bouncer active) telegram: https://telegram.me/lemmy98 keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
-- Benjamin Brunner <bbrunner@suse.de>, Engineering Manager System Boot and Init SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nürnberg Germany HRB 36809, AG Nürnberg Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
On 7/20/20 6:15 PM, Mathias Homann wrote:
OK, who decided to stick with a THREE YEAR OLD systemd in Leap 15.2, and why?
Because it is the newest version that SUSE Engineers are providing enterprise support for.
There are open bugs in that version that have been fixed TWO YEARS AGO.
As mentioned elsewhere in this thread most of those bugfixes should have made there way into Leap either as part of the latest release or maintenance updates. If you are encountering a bug in Leap 15.2 that has been fixed upstream please open a bug in openSUSE's bugtracker and the team will try there best to backport it.
Asking for advice about that kind of stuff upstream is just plain old embarrassing!
It shouldn't be, many of the people working on upstream systemd work for Enterprise Linux Distro's be it SUSE, Redhat or Debian and are well aware of how enterprise / LTSS distro's work.
Can I safely replace that with the up to date systemd from factory?
No I imagine that will probably break something horribly if not right now probably sometime in the future. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
Am 2020-07-22 03:27, schrieb Simon Lees:
On 7/20/20 6:15 PM, Mathias Homann wrote:
OK, who decided to stick with a THREE YEAR OLD systemd in Leap 15.2, and why?
Because it is the newest version that SUSE Engineers are providing enterprise support for.
There are open bugs in that version that have been fixed TWO YEARS AGO.
As mentioned elsewhere in this thread most of those bugfixes should have made there way into Leap either as part of the latest release or maintenance updates. If you are encountering a bug in Leap 15.2 that has been fixed upstream please open a bug in openSUSE's bugtracker and the team will try there best to backport it.
While doing that just now i noticed that backporting that fix was already requested and had been denied, see https://bugzilla.opensuse.org/show_bug.cgi?id=1136674 Cheers Mathias -- Mathias Homann Mathias.Homann@openSUSE.org telegram: https://telegram.me/lemmy98 irc: [lemmy] on freenode and ircnet obs: lemmy04 gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
On 7/22/20 5:24 PM, Mathias Homann wrote:
Am 2020-07-22 03:27, schrieb Simon Lees:
On 7/20/20 6:15 PM, Mathias Homann wrote:
OK, who decided to stick with a THREE YEAR OLD systemd in Leap 15.2, and why?
Because it is the newest version that SUSE Engineers are providing enterprise support for.
There are open bugs in that version that have been fixed TWO YEARS AGO.
As mentioned elsewhere in this thread most of those bugfixes should have made there way into Leap either as part of the latest release or maintenance updates. If you are encountering a bug in Leap 15.2 that has been fixed upstream please open a bug in openSUSE's bugtracker and the team will try there best to backport it.
While doing that just now i noticed that backporting that fix was already requested and had been denied, see https://bugzilla.opensuse.org/show_bug.cgi?id=1136674
It seems there is an alternate workaround available which sometimes makes it less likely to backport a fix, especially a complex set of changes such as this which involves changing a large number of things. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
participants (6)
-
Benjamin Brunner -
Carlos E. R. -
Dan Čermák -
Mathias Homann -
Mathias Homann
-
Simon Lees