Re: dpkg upgrade/downgrade dependency problem
On Mon, Apr 13, 1998 at 07:16:41PM -0600, Jason Gunthorpe wrote:
>
> On Mon, 13 Apr 1998, Juan Cespedes wrote:
>
> > I'm trying to fix Bug#1797,#5639,#6842... (i.e., the famous
> > dependencies problems in dpkg)
> >
> > Is anyone else working on this?
>
> If you do make any changes please consider applying them only to the
> configuration stage - for instance aborting a configuration if other
> dependencies are broken?
No, that won't work. The problem is that dpkg allows you to
upgrade or downgrade a package without checking if the new installed
package has any dependency problems which weren't there in the
previously-installed one.
> If I read the bug reports correctly, dpkg allows you to configure things
> when other packages dependencies on those things is unmet.. Which means it
> does not inspect reverse dependancies and reverse provide dependancies.
Hmm... no, not exactly.
(ie, if you have a lot of packages which depend on
"libc6 (>= 2.0.92)", and you have libc6_2.0.92 installed, and try to
install libc6_2.0.91, it will let you do it without even a warning.
See the following examples:
----------------------------------------------
# dpkg -l test-a
Package: test-a
Version: 1.0
# dpkg -l test-b
Package: test-b
Version: 1.0
Dependens: test-a (= 1.0)
# dpkg -i test-a_2.0.deb
(Reading database ... 27151 files and directories currently installed.)
Unpacking test-a (from test-a_2.0.deb) ...
Setting up test-a (2.0) ...
# dpkg -l test-a
Package: test-a
Version: 2.0
----------------------------------------------
# dpkg -l test-1
Package: test-1
Version: 1.0
Provides: test-2 /* No other package provides test-2 */
# dpkg -l test-3
Package: test-3
Version: 1.0
Dependens: test-2
# dpkg -i test-1_2.0.deb
(Reading database ... 27151 files and directories currently installed.)
Unpacking test-1 (from test-1_2.0.deb) ...
Setting up test-1 (2.0) ...
# dpkg -l test-1
Package: test-1
Version: 2.0
----------------------------------------------
IMHO, the correct way to handle this (and the only way to meet
all the dependencies) is to forbid that installation, ie, not even
unpack the new version, unless option "--auto-deconfigure" is given,
in which case the package should be installed and all the other
packages with broken dependencies will have to be deconfigured.
Am I correct?
Thanks.
--
Juan Cespedes
--
To UNSUBSCRIBE, email to debian-dpkg-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: