Hi! On Mon, 2017-11-13 at 17:35:06 +0900, Norbert Preining wrote: > severity 881582 wishlist > retitle 881582 allow conflict against actual package even if provided by > different one > thanks
I don't think this is needed. Even less so now that we have versioned provides. Ideally perl would switch to use those for the modules it provides as part of the perl distribution. > > $ dpkg -l libunicode-collate-perl > > .... > > un libunicode-collate-perl <none> <none> (no > > description available) > > $ grep Conflicts debian/control > > Build-Conflicts: libunicode-collate-perl > > $ dpkg-checkbuilddeps > > dpkg-checkbuilddeps: error: Build conflicts: libunicode-collate-perl > > $ > > perl provides libunicode-collate-perl, but unfortunately they are not > binary compatible and hash tests differ when using the one or the other. > > Downgraded to wishlist, I would like to conflict against some > libunicode-collate-perl actual package instead of the provided one. Doesn't depending on at least the version that provides the required interface, fix this problem in a cleaner way? Both now and in the future. Now because the versioned dependency will not even be fullfilled by the unversioned perl-modules-5.26 Provides. And in the future, because even if perl-modules-5.NM starts having a versioned provides, it will only be fullfilled if the version complies with the restriction. So I'd say, you just need to do that, and we'd reassign or close this report. Thanks, Guillem
