systemd-219 issues with 22 and Rawhide composes

Lennart Poettering mzerqung at
Fri Feb 20 16:11:58 UTC 2015

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?

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.

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

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

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

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?


Lennart Poettering, Red Hat

More information about the devel mailing list