On 09/13/2011 09:28 PM, Reindl Harald wrote:
Am 13.09.2011 23:25, schrieb Sérgio Basto:
On Tue, 2011-09-13 at 23:15 +0200, Reindl Harald wrote:
Am 13.09.2011 21:41, schrieb Sérgio Basto:
thanks for this information , could I update systemd to systemd-35 in
Fedora 15 with rebuilding the src.rpm , I don't get in trouble ? or we
have some restrictions ?
I we don't have restriction why systemd Fedora packager don't update
them on Fedora 15?
because they tend to throw out a dist-upgrade with unfinished replacements
and do not care about bring improvements to the users because they can
jump to the next dist-upgrade and hope that no other subsystem is
replaced with a public beta
systemd-26-9.fc15
systemd-35-1.fc16
this is a bad joke in the middle of life-cycle and would be only acceptable if
F15 and it's version of sytemd would have been perfect but it was not
I know examples of jumps in middle of a life-cycle like kernel 38 -> 40
Networkmanager to 0.9 and we leave happy with it. I will give more
examples to not personalize the issue, kde for example and many others
(hopefully).
Mirco Tischler said "I used the systemd packages from f16 on a f15
system and they worked just fine for me."
So Fedora guys what you are waiting for ? update systemd please , should
I open a report in bugzilla ?
please open a bugreport - maybe they would hear if i am not would be the
only person who is unhappy about what was done with F15 but all others
out there are silent and hoping for wonders
This is rather interesting the person that has been the nosiest the most
about systemd breaking his system, disrupting his workflow and what not,
is now advocating that we potentially disrupt all deployments by
bringing in a newer release of systemd which means bringing in updates
to surrounding components as well to accommodating the changes that have
been made not only in systemd but the surrounding components so as well.
What is this the twilight zone?
How about you stop wasting people mail storage spaces and channel that
energy in actually helping out in the migration to systemd to aid in
preventing users from experiencing the same unfortunate experience you
seemed to have had.
How about you actually for once provide a migrated legacy sysv init
script to a native systemd unit in a bug report in bugzilla instead of
demanding one from the maintainer or help maintainers updating
documentation surrounding their component or bring a patch upstream that
fixes the brokenness you seem to be experiencing.
Yeah how about that...
If you are incabable of doing the above I suggest you stop wasting
people times with this noise.
I can tell you one thing here and now that with my QA hat on I nack this
proposal in an instance and I'm pretty sure the rest of the QA community
is on the same opinion.
JBG
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
