21.02.2017 12:12, Christian Ehrhardt пишет: > On Tue, Feb 21, 2017 at 9:46 AM, Michael Tokarev <m...@tls.msk.ru > <mailto:m...@tls.msk.ru>> wrote: > > Hello Christian! > > Thank you for doing this. > > 17.02.2017 13:48, Christian Ehrhardt wrote: > > > case sha1 summary > > a 84dc4d05d3 ubuntu acl fix dependencies changed > > This really should be fixed in acl package, not in qemu. I > filed a bugreport about this quite some time ago, and actually > forgot about it. > > > I agree that a correct long term solution would be better. > Yet this change is only modifying the current "workaround" to be slightly > more modern. > And it all is behind an :ubuntu: mask anyway. > So if you could consider to pick it still that would be very kind.
Yes, I surely can pick it up, that was the intention anyway, to keep the same d/control to avoid editing it for ubuntu. With any strange or ugly thing in there which is needed for ubuntu ;) > If not I think that is fine as well - as this really isn't the most complex > delta :-) > > Do you happen to know/find the bug number you filed on acl? yes, #762339, http://bugs.debian.org/762339 > > a 0d52ac1285 Make qemu-system-common depend on qemu-block-extra > > a b24146b825 Make qemu-utils depend on qemu-block-extra > > This is something I really don't want to do. This completely > defeats the purpose of qemu-block-extra package. [] > I think a recommend would be just as fine for us bug I need to know the > history to really decide. > *digging* Imagine a spinning progress bad | / - \ ... > Ah I found it https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1495895 Oh, rados is DEFINITELY an "extra" dependency, especially with their history of issues with packaging :) > Reading that I think we would be fine with a recommends as well. > On installing by default recommended packages would be co-installed. > But one "could" install without them via the man apt ways of not installing > recommends. Or one can remove them without removing the rest of the packages. > What do you think now knowing the history of this? > Should we just together go with a recommends in the git for now. I'd say definitely :) Thanks, /mjt
