In Fedora 20, if you update your system with yum then the yum plugin
auto-update-debuginfo will enable the debuginfo repository, update the
debuginfo packages you have installed, then disable the debuginfo
repository. If you update with GNOME Software or Apper, this doesn't
happen and you wind up with debuginfo packages that don't match the
packages you have installed. They update your debuginfo just fine if you
enable the debuginfo repository manually by modifying /etc/yum.repos.d.
I think it's really time to fix this. Is there any reason we don't
simply have the debuginfo repository enabled by default? Alternatively,
it could be enabled the first time debuginfo-install is run.
-----BEGIN PGP SIGNED MESSAGE-----
there was a new build of libunistring today  which braought along
with it a soname bump from libunistring.so.0 to libunistring.so.2
On a f21 box repoquery tells me that
use libunistring.so.0 I have sent a build for gettext as its has broken
things, It will need extra care and a buildroot override on f21 to be
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
Recently I have noticed that systemd package dependency is creeping into
some packages where it is not necessary. subversion  or rsync  are
good examples. Please consider moving daemon parts into independent
subpackages. When I install rsync/subversion, I am typically interested
just in client side.
Just to be clear, systemd-libs is in minimal build root already, so I am
not complaining about systemd-libs package, but about systemd package.
Hi working groups members,
since we have learned on Flock that new Fedora working groups do not
communicate with each other much (or enough), I'd like to propose the
Every working group will time to time (e.g. weekly) send short summary
about what they did / were talking about directly to mailing lists of
other working groups + to devel(a)fp.o. Really only a short summary with
links where one can find details.
I tried to collect such info from the meeting logs and mailing lists for
the last few weeks for Env and Stacks WG:
I found many notes are really worth spreading beyond groups' borders,
but it takes too much time for one person to collect all the
information. Thus, proposing to "do a summary once per group and share
with other groups".
Another benefit would be that Matt would have better content for his 5tiftw.
I don't think we need to sync about date or frequency, just remembering
to send a direct mail if anything interesting is done/discussed should
List of proposed MLs to send this summary to:
Comments, ideas or better solutions are welcome as usually, but I might
be offline until Sunday, so do not expect any answers from me in that