systemd-219 issues with 22 and Rawhide composes

Peter Robinson pbrobinson at
Fri Feb 20 16:24:36 UTC 2015

On Fri, Feb 20, 2015 at 4:11 PM, Lennart Poettering
<mzerqung at> wrote:
> On Fri, 20.02.15 16:03, Peter Robinson (pbrobinson at wrote:
>> On Fri, Feb 20, 2015 at 3:47 PM, Harald Hoyer <harald at> wrote:
>> > To prevent surprises on the next systemd updates like in
>> > <>, we will not apply
>> > workarounds anymore in rawhide and track the issues on
>> > <> so, that
>> > they are not forgotten.
>> >
>> > We removed the change for /etc/resolv.conf in F22 again (like in F21), but this
>> > time we keep the change for rawhide.
>> >
>> > Sorry for the inconvenience and feel free to add bugs to the tracker, which are
>> > caused by systemd changes and have to be fixed in other components.
>> Are you going to start notifying deve@ of upcoming changes that may
>> impact other areas of the distro too rather than just land them
>> without notification or discussion?
> Oh god, stop this, will you?

No, I mean the above in general for general changes you make that
affect the distro as a whole. You generally land them without

> The folks in question knew I would drop the patch. In the original bug
> I even said I would remove the work-around from systemd.rpm after TC1
> of the last cycle. I was nice, left it in for the whole cycle, only
> dropped it now.

Yes, and it looks like it affects dhcpd too... just because you
notified one dev team on a single bug it's not the same as a wider
announcement to the wider community. There's all sorts of things that
this can affect, and while yes it may be a bug in their software, it
should be as widely notified as possible. People have priorities that
may not be the same as yours.

> There is no news in all of this, I just removed the work-around now, as
> indicated back then.

Again, I'm not just referring to this single incident, it would be
nice if you notified people widely of changes. It's a community,
people don't all follow closely the upstream development of all
upstream components.

> How many months would you like me to notify people in advance of a
> simple change like this? Isn't 6 month *ample* time?

Likely not, not everyone has the same schedule as upstream systemd, in
a lot of cases they don't know it's broken until things land and teams
have other priorities.

> How much time do you think is appropriate for fixing a file copy
> routine in anaconda? 12 months? 18 months? 2 years?

I'm not just referring to *just* anaconda. This is *one* thing,
there's other things that might be broken by this. How long has
/etc/resolv.conf been a file in that location? How many things across
the distro expect it to be like it is? It's legacy and while I'm not
against changing it there may be impact that isn't take into account.
Bullying people/process/team just because "you've waited 6 months
already" isn't an appropriate response just because you're impatient
and want to move on. We're a community that doesn't revolved around
systemd... sorry!

> Also, NM fixed a similar issue with /etc/resolve.conf in their code a
> long time ago, to my knowledge. Am I so misguided to assume that
> Anaconda can fix a fricking file copy too, in all those months?

To my knowledge there also looks to be issues with dhcp due to this
change as of yesterday.... so maybe you don't have all the knowledge.
What else might be affected in the distro according "to your


More information about the devel mailing list