Bug#171101: unreproducible
tags 171101 unreproducible
thanks
I have made some efforts to try to reproduce this bug with equivs packages
using apt 0.5.4 and 0.5.8 and have had no success. In every situation I tried
(including requesting installation of both packages when one was already
installed, with each package first), apt refused to install the new package
without removing the existing one.
there:[/tmp/test] dpkg -I foo_1.0_all.deb
new debian package, version 2.0.
size 2382 bytes: control archive= 801 bytes.
915 bytes, 23 lines control
193 bytes, 3 lines md5sums
Package: foo
Version: 1.0
Section: misc
Priority: optional
Architecture: all
Conflicts: foobar
Provides: foobar
Installed-Size: 12
Maintainer: Your Name <yourname@foo.com>
Description: Dummy package to fulfil package dependencies
This is a dummy package that makes Debian's package management
system believe that equivalents to packages on which other
packages do depend on are actually installed.
.
Deinstallation of this package is only possible when all pending
dependency issues are properly resolved in some other way. A more
brutal approach for it's deinstallation is to create and install
this package configured using an empty control file.
.
Please note that this is a crude hack and if thoughtlessly used
might possibly do damage to your packaging system. And please
note as well that using it is not the recommended way of dealing
with broken dependencies. Better file a bug report instead.
there:[/tmp/test] dpkg -I bar_1.0_all.deb
new debian package, version 2.0.
size 2392 bytes: control archive= 804 bytes.
915 bytes, 23 lines control
193 bytes, 3 lines md5sums
Package: bar
Version: 1.0
Section: misc
Priority: optional
Architecture: all
Conflicts: foobar
Provides: foobar
Installed-Size: 12
Maintainer: Your Name <yourname@foo.com>
Description: Dummy package to fulfil package dependencies
This is a dummy package that makes Debian's package management
system believe that equivalents to packages on which other
packages do depend on are actually installed.
.
Deinstallation of this package is only possible when all pending
dependency issues are properly resolved in some other way. A more
brutal approach for it's deinstallation is to create and install
this package configured using an empty control file.
.
Please note that this is a crude hack and if thoughtlessly used
might possibly do damage to your packaging system. And please
note as well that using it is not the recommended way of dealing
with broken dependencies. Better file a bug report instead.
--
- mdz
Reply to: