Bug#810164: perl-modules-5.22: Unversioned Breaks against perl-modules should be a Conflict

[Niko Tyni]

Control: tag -1 pending

On Fri, Jan 08, 2016 at 02:07:10PM -0700, Adam Conrad wrote:
> On Fri, Jan 08, 2016 at 12:22:50PM +0200, Niko Tyni wrote:

> Given the above, I think the only reasonable solution right now is to
> move your Breaks to a Conflicts.

I've done this in git, and test upgrades seem to work as expected,
so it should be in the next upload.

 http://anonscm.debian.org/cgit/perl/perl.git/commit/?id=c4dd2a49267344ddac688b43c87e78b533f2ce01

> As a side note, you may also want to make your Provides versioned, as
> having it unversioned has suddenly swapped meaning for dependencies
> such as:
> 
>  Depends: perl-modules (>= 5.10) | libcgi-pm-perl (>= 3.35)
> 
> An unversioned Provides is evaluated as version 0:0.0, which means an
> upgrade that's removing perl-modules will pull in libcgi-pm-perl, even
> though that shouldn't be necessary.  A versioned Provides would fix
> that.

I believe the Debian archive isn't ready for versioned Provides yet;
at least testing migration still needs changes. See #786803.

Your example is apparently from the sympa package, and it's the only
versioned dependency on perl-modules that's left in sid as we went
to some trouble to get rid of those. In this case it actually works,
because perl 5.22 dropped CGI.pm so the separate package is now actually
needed. Anyway, the dependency should be cleaned, and I've filed #811194
about this.

Thanks again,
-- 
Niko Tyni   ntyni at debian.org