On Wed, Mar 28, 2018 at 04:02:16PM +0300, Panu Matilainen wrote: > The reason for the "unexpected" rich dependency backport is that we failed > to add a new rpmlib() dependency tracker when adding these new dependencies, > and thus rpm 4.13.0* wont refuse to touch packages using them as it should.
Hmm, I wonder why that is so. It shouldn't be able to parse the new rich dependencies and thus fail in the dependency check. I don't mind them being backported, though. ;) Cheers, Michael. -- Michael Schroeder [email protected] SUSE LINUX GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} _______________________________________________ Rpm-maint mailing list [email protected] http://lists.rpm.org/mailman/listinfo/rpm-maint
