On Thu, Mar 22, 2018 at 11:18:17AM +0100, Andrea Bolognani wrote:
On Wed, 2018-03-21 at 16:11 +0100, Pavel Hrdina wrote:
> > +++ b/guests/vars/projects/blacklist.yml
> > @@ -0,0 +1,3 @@
> > +---
> > +packages:
> > + - nano
>
> In the past we've installed some packages, that were removed from
> ansible and it would make sense to list them in the blacklist in order
> to cleanup existing installations that someone can already have.
>
> The list of the removed packages is:
>
> polkit-devel
> glibc-rpcgen on Fedora > 27 (it was glibc-common)
>
> Anyway, this can be a followup patch.
The rpcgen stuff is pretty confusing, even though I'm the one who
made the change :) Anyway, glibc-rpcgen no longer seems to exist in
rawhide, while glibc-common can't be removed because packages depend
on it, so I guess there's no cleaning up required there.
Nothing should have depended on glibc-rpcgen at all - it was just a
temporary hack - any dep should have been on "rpcgen" (glibc-rpcgen
provided that as a virutal Provides), and the new RPM has that correct
name. Prior to F27 just glibc-common is right.
As for polkit-devel, I'm trying to figure out a nice way to add it
to the blacklist... The current naming convention is along the
lines of
foo:
deb: libfoo-dev
rpm: foo-devel
so it doesn't fit neatly in there, because we want to blacklist
polkit-devel but still install polkit itself. Maybe we could have
blacklist-polkit:
rpm: polkit-devel
or something similar as a workaround? Does that look reasonable?
Alternatively we can just leave the package installed, of course :)
--
Andrea Bolognani / Red Hat / Virtualization
--
libvir-list mailing list
libvir-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Regards,
Daniel
--
|:
https://berrange.com -o-
https://www.flickr.com/photos/dberrange :|
|:
https://libvirt.org -o-
https://fstop138.berrange.com :|
|:
https://entangle-photo.org -o-
https://www.instagram.com/dberrange :|