On Thu, Mar 29, 2018 at 11:00 AM, Michael Schroeder <m...@suse.de> wrote: > 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. ;) >
I certainly don't mind it either! It'll be nice having the feature in Mageia 6's RPM package. :) -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
