systemd-219 issues with 22 and Rawhide composes

Simo Sorce simo at
Mon Feb 23 13:52:36 UTC 2015

On Mon, 2015-02-23 at 14:40 +0100, drago01 wrote:
> On Mon, Feb 23, 2015 at 2:17 PM, David Cantrell <dcantrell at> wrote:
> >  That is, and I am trying to
> > be specific here, changes that impact other components in the distribution
> > need to be coordinated in Fedora among the affected components.
> Almost every change might "affect other components" ... it might be
> obvious to a maintainer of an affected component but not necessarily
> for the maintainer / developer of the component that got changed.

Which is why you should send a message to a general development list for
changes that change the semantics of a well established mechanism.

If you are changing something internal to your software then the burden
of keeping up is with the downstream people that may decide to depend on
internal features (assuming private/public interfaces are clearly

If you are changing something in the system public interfaces, instead a
bit more general and advance notice is necessary.

This is a general rule, not specific to systemd, and I am guilty of
having changed stuff without a direct message to devel@ in the past.

We all need to get better at communicating changes that may affect
others, it buys goodwill and understanding, and perhaps the occasional
flame, but what was the saying ? Flame early, flame often ? :)


Simo Sorce * Red Hat, Inc * New York

More information about the devel mailing list