Debian Bug report logs - #17655
dpkg: dependency problem when upgrading splitted package

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Michael Meskes <meskes@topsystem.de>

To: submit@bugs.debian.org

Subject: e2fsprogs: package should depend on ss2g

Date: Fri, 30 Jan 1998 12:03:48 +0100

Package: e2fsprogs
Version: 1.10-11

Otherwise this can happen:

gate# dpkg -i e2fsprogs_1.10-11_i386.deb 
(Reading database ... 6187 files and directories currently installed.)
Preparing to replace e2fsprogs 1.10-10 (using e2fsprogs_1.10-11_i386.deb) ...
Unpacking replacement e2fsprogs ...
Setting up e2fsprogs (1.10-11) ...
gate# dpkg -i e2fslibsg_1.10-11_i386.deb comerr2g_2.0-1.10-11_i386.deb 
(Reading database ... 6188 files and directories currently installed.)
Preparing to replace e2fslibsg 1.10-10 (using e2fslibsg_1.10-11_i386.deb) ...
Unpacking replacement e2fslibsg ...
Preparing to replace comerr2g 1.10-10 (using comerr2g_2.0-1.10-11_i386.deb)...
Unpacking replacement comerr2g ...
Setting up comerr2g (2.0-1.10-11) ...
Setting up e2fslibsg (1.10-11) ...
gate# ldd /usr/sbin/debugfs 
        libext2fs.so.2 => /lib/libext2fs.so.2 (0x4000d000)
        libss.so.2 => not found
        libcom_err.so.2 => /lib/libcom_err.so.2 (0x4001d000)
        libuuid.so.1 => /lib/libuuid.so.1 (0x4001f000)
        libc.so.6 => /lib/libc.so.6 (0x40022000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)


Michael

-- System Information
Debian Release: 1.3
Kernel Version: Linux gauss 2.0.33 #2 Wed Dec 17 09:14:18 MEZ 1997 i686 unknown

Versions of the packages e2fsprogs depends on:
comerr2g	Version: 2.0-1.10-11
e2fslibsg	Version: 1.10-11
libc6	Version: 2.0.6-3
ss2g	Version: 2.0-1.10-11

Message #10 received at 17655@bugs.debian.org (full text, mbox, reply):

From: Yann Dirson <ydirson@a2points.com>

To: Michael Meskes <meskes@topsystem.de>, 17655@bugs.debian.org

Subject: Bug#17655: another dpkg dependency bug ?

Date: Fri, 30 Jan 1998 19:45:52 +0100

Michael Meskes writes:
 > Package: e2fsprogs
 > Version: 1.10-11

???
$ dpkg-deb -I  e2fsprogs_1.10-11_i386.deb | grep Depends
 Depends: comerr2g, e2fslibsg, libc6, ss2g

It does already !

When I ask dselect "remove" to ss2g, it flags e2fsprogs for removal as
well in the conflict-resolution dialog.  So I guess it's all right
with my packages.

 > Otherwise this can happen:
 > 
 > gate# dpkg -i e2fsprogs_1.10-11_i386.deb 
 > (Reading database ... 6187 files and directories currently installed.)
 > Preparing to replace e2fsprogs 1.10-10 (using e2fsprogs_1.10-11_i386.deb) ...
 > Unpacking replacement e2fsprogs ...
 > Setting up e2fsprogs (1.10-11) ...

This one works, because e2fslibsg_1.10-10 Provides ss2g.

 > gate# dpkg -i e2fslibsg_1.10-11_i386.deb comerr2g_2.0-1.10-11_i386.deb 
 > (Reading database ... 6188 files and directories currently installed.)
 > Preparing to replace e2fslibsg 1.10-10 (using e2fslibsg_1.10-11_i386.deb) ...
 > Unpacking replacement e2fslibsg ...
 > Preparing to replace comerr2g 1.10-10 (using comerr2g_2.0-1.10-11_i386.deb)...
 > Unpacking replacement comerr2g ...
 > Setting up comerr2g (2.0-1.10-11) ...
 > Setting up e2fslibsg (1.10-11) ...

This one giving no error seems much like another dpkg bug !!

I would have advised you to use dselect to install the whole, if only
all packages had been installed. But I guess it will take some time
for ss2g to be installed, being a new package.

I'd advise for:

reassign 17655 dpkg
severity 17655 grave
--
I though of critical, but it won't affect normal users using dselect...

-- 
Yann Dirson  <ydirson@a2points.com>      | Stop making M$-Bill richer & richer,
alt-email:     <dirson@univ-mlv.fr>      |     support Debian GNU/Linux:
debian-email:   <dirson@debian.org>      |         more powerful, more stable !
http://www.a2points.com/homepage/3475232 | Check <http://www.debian.org/>

Message #19 received at 17655-done@bugs.debian.org (full text, mbox, reply):

From: Wichert Akkerman <wichert@cistron.nl>

To: 17655-done@bugs.debian.org

Subject: Can't reproduce

Date: Mon, 25 Dec 2000 17:01:55 +0100

I can't reproduce this one, and countless other packages have
handled similar upgrades without such problems which makes me
suspect it never was a dpkg or dselect problem. Closing this
bugreport.

Wichert.

Send a report that this bug log contains spam.