Bug#790509: libmpfi-dev: transitional package uninstallable
On 2015-07-02 12:42:32 +0200, Andreas Beckmann wrote: I think the general consensus is to have more unversioned -dev packages to ease transitions, since in most cases a binNMU will be sufficient to pick up the dependency on the new SONAME. Even historically versioned ones have transitioned to unversioned ones (e.g. tiff3, tiff4 - tiff). Also -dev package versioning (if needed) is usually by project version, not by SOVERSION (the two tiffs have/had SOVERSIONS 4 and 5, respectively, which may be a bit confusing: you built against libtiff3-dev and got a dependency on libtiff4). I suppose that the different versions on the -dev is to differentiate the API, while the SONAME is to differentiate the ABI. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#790509: libmpfi-dev: transitional package uninstallable
On 2015-06-30 01:31:38 +0200, Jerome BENOIT wrote: On 30/06/15 00:38, Andreas Beckmann wrote: PS: Is it really necessary to switch from an unversioned -dev package to a versioned one? For consistency ? I'm not sure, but this will have the drawback that packages which depend or build-depend on the -dev package will have to be updated if its name changes (due to a backward incompatible change in the libmpfi ABI). -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#790509: libmpfi-dev: transitional package uninstallable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Andreas,
thanks for your report and your fix.
On 30/06/15 00:38, Andreas Beckmann wrote:
Package: libmpfi-dev
Version: 1.5.1+ds-1
Severity: grave
Tags: sid
Justification: renders package unusable
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
The following packages have unmet dependencies:
libmpfi-dev : Depends: libmpfi0-dev (= 1.5.1+ds-1) but it is not going to
be installed
This is caused by the Conflicts in libmpfi0-dev:
Package: libmpfi0-dev
Source: mpfi
Version: 1.5.1+ds-1
Replaces: libmpfi-dev (= 1.5.1-3)
Provides: libmpfi-dev
Depends: libmpfi0 (= 1.5.1+ds-1), libmpfi0-dev-common (= 1.5.1+ds-1),
libmpfr-dev, libgmp-dev
Conflicts: libmpfi-dev
Breaks: libmpfi-dev (= 1.5.1-3)
The transitional package being uninstallable will prevent migration
to testing. Please don't drop the transitional package (because
upgrades won't automatically switch from a real package to a
virtual one) but drop the Conflicts for now.
For stretch+1 you can drop the transitional package and switch to
unversioned Breaks+Replaces (or Conflicts+Replaces) to ensure the
old transitional one gets removed upon upgrades.
Let be specific. The current d/control metadata for libmpfi0-dev are:
Package: libmpfi0-dev
Provides: libmpfi-dev
Section: libdevel
Architecture: any
Replaces: libmpfi-dev (= 1.5.1-3)
Breaks: libmpfi-dev (= 1.5.1-3)
Depends:
libmpfi0 (= ${binary:Version}), libmpfi0-dev-common (= ${source:Version}),
libmpfr-dev, libgmp-dev, ${misc:Depends}
Conflicts: libmpfi-dev
Multi-Arch: same
Description: multiple precision floating-point interval computation library --
libdev
[[LONG DESCRIPTION]]
May I replace them by:
Package: libmpfi0-dev
Provides: libmpfi-dev
Section: libdevel
Architecture: any
Replaces: libmpfi-dev (= 1.5.1-3)
Breaks: libmpfi-dev (= 1.5.1-3)
Depends:
libmpfi0 (= ${binary:Version}), libmpfi0-dev-common (= ${source:Version}),
libmpfr-dev, libgmp-dev, ${misc:Depends}
Multi-Arch: same
Description: multiple precision floating-point interval computation library --
libdev
[[LONG DESCRIPTION]]
Namely, removing the Conflicts: entry.
Cheers,
Andreas
PS: Is it really necessary to switch from an unversioned -dev package
to a versioned one?
For consistency ?
Best wishes,
Jerome
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBAgAGBQJVkdUoAAoJEIC/w4IMSybjltsH/RWaOTW8Hy5q4YL100sUNnKY
Q0spSuFleAtlizziWARSXGBD8qQQTVfmRvzkKLXy7oovQajr1U1w/j8RAJKqTkym
ztSPgorbGhkWo/+Gd+M5llwmheEO4Jq9FLQZ15ZFibwHxK0AyPmZR2UjEjrgG41M
nZUNdWUZBnLauCCAmBpQjWtLRl+HiumhhjAlTWVoeB8wk7awUvjgeM0QN39su5wS
TKhP2T/mwm368OrYC6GISMybTpEC9j1YZDz6EMMdl//lRd2L3I5pz6j+wNm0Q2rf
/YHGypFlzpdr1pH6mAF6djKc8qJLzV8tKv2U3qsLXN7Mthfz/zvcNMfnW5NJ+DI=
=8uzq
-END PGP SIGNATURE-
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#790509: libmpfi-dev: transitional package uninstallable
Package: libmpfi-dev Version: 1.5.1+ds-1 Severity: grave Tags: sid Justification: renders package unusable User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package is no longer installable in sid: The following packages have unmet dependencies: libmpfi-dev : Depends: libmpfi0-dev (= 1.5.1+ds-1) but it is not going to be installed This is caused by the Conflicts in libmpfi0-dev: Package: libmpfi0-dev Source: mpfi Version: 1.5.1+ds-1 Replaces: libmpfi-dev (= 1.5.1-3) Provides: libmpfi-dev Depends: libmpfi0 (= 1.5.1+ds-1), libmpfi0-dev-common (= 1.5.1+ds-1), libmpfr-dev, libgmp-dev Conflicts: libmpfi-dev Breaks: libmpfi-dev (= 1.5.1-3) The transitional package being uninstallable will prevent migration to testing. Please don't drop the transitional package (because upgrades won't automatically switch from a real package to a virtual one) but drop the Conflicts for now. For stretch+1 you can drop the transitional package and switch to unversioned Breaks+Replaces (or Conflicts+Replaces) to ensure the old transitional one gets removed upon upgrades. Cheers, Andreas PS: Is it really necessary to switch from an unversioned -dev package to a versioned one? -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
