Your message dated Sat, 24 Mar 2012 18:24:49 +0100
with message-id <[email protected]>
and subject line Re: Bug#652063: When installing Multi-Arch: same
(meta-)package for two architectures, dpkg considers one arch as completely
disappeared
has caused the Debian Bug report #652063,
regarding When installing Multi-Arch: same (meta-)package for two
architectures, dpkg considers one arch as completely disappeared
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
652063: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652063
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.16.1.2
Note that this is not actually in Debian yet, it's for
git://git.debian.org/users/hertzog/dpkg.git pu/multiarch/full.
But I'm filing it here because
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632555#20 referred to
it and to have an early warning before that dpkg branch lands in
Debian. If you consider that inappropriate, then please just close the
bug and sorry for the unnecessary noise then.
If you install the i386 and amd64 variant of a Multi-Arch: same
package which just has identical files on both architectures, dpkg
considers one architecture as completely replacing the other, marking
the package as uninstalled:
$ LANG= sudo apt-get install --reinstall libpthread-stubs0{,:i386}
libpthread-stubs0-dev
[...]
Preparing to replace libpthread-stubs0 0.3-2.1ubuntu1 (using
.../libpthread-stubs0_0.3-2.1ubuntu1_amd64.deb) ...
Unpacking replacement libpthread-stubs0 ...
(Noting disappearance of libpthread-stubs0:i386, which has been completely
replaced.)
Selecting previously unselected package libpthread-stubs0:i386.
Unpacking libpthread-stubs0:i386 (from
.../libpthread-stubs0_0.3-2.1ubuntu1_i386.deb) ...
Preparing to replace libpthread-stubs0-dev 0.3-2.1ubuntu1 (using
.../libpthread-stubs0-dev_0.3-2.1ubuntu1_amd64.deb) ...
Unpacking replacement libpthread-stubs0-dev ...
dpkg: dependency problems prevent configuration of libpthread-stubs0-dev:
libpthread-stubs0-dev depends on libpthread-stubs0 (= 0.3-2.1ubuntu1); however:
Package libpthread-stubs0 is not configured yet.
dpkg: error processing libpthread-stubs0-dev (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup
error from a previous failure.
Errors were encountered while processing:
libpthread-stubs0-dev
E: Sub-process /usr/bin/dpkg returned an error code (1)
Note that I sometimes have to run the command twice for it to appear.
The multi-arch patch was applied in Debian's libpthread-stubs in
0.3-3, so that reproducer should work in sid just as well.
This happens for packages which are metapackages for others (like
libtag1c2a), or just empty on most architectures (like
libpthread-stubs0), so they can't be M-A: foreign as they have M-A:
same dependencies.
I think the "completely disappeared" logic should not apply in this
case.
Thanks,
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1.16.2
On Wed, 2011-12-14 at 16:07:30 +0100, Martin Pitt wrote:
> Package: dpkg
> Version: 1.16.1.2
>
> Note that this is not actually in Debian yet, it's for
> git://git.debian.org/users/hertzog/dpkg.git pu/multiarch/full.
> But I'm filing it here because
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632555#20 referred to
> it and to have an early warning before that dpkg branch lands in
> Debian. If you consider that inappropriate, then please just close the
> bug and sorry for the unnecessary noise then.
>
> If you install the i386 and amd64 variant of a Multi-Arch: same
> package which just has identical files on both architectures, dpkg
> considers one architecture as completely replacing the other, marking
> the package as uninstalled:
>
> $ LANG= sudo apt-get install --reinstall libpthread-stubs0{,:i386}
> libpthread-stubs0-dev
> [...]
> Preparing to replace libpthread-stubs0 0.3-2.1ubuntu1 (using
> .../libpthread-stubs0_0.3-2.1ubuntu1_amd64.deb) ...
> Unpacking replacement libpthread-stubs0 ...
> (Noting disappearance of libpthread-stubs0:i386, which has been completely
> replaced.)
> Selecting previously unselected package libpthread-stubs0:i386.
> Unpacking libpthread-stubs0:i386 (from
> .../libpthread-stubs0_0.3-2.1ubuntu1_i386.deb) ...
> Preparing to replace libpthread-stubs0-dev 0.3-2.1ubuntu1 (using
> .../libpthread-stubs0-dev_0.3-2.1ubuntu1_amd64.deb) ...
> Unpacking replacement libpthread-stubs0-dev ...
> dpkg: dependency problems prevent configuration of libpthread-stubs0-dev:
> libpthread-stubs0-dev depends on libpthread-stubs0 (= 0.3-2.1ubuntu1);
> however:
> Package libpthread-stubs0 is not configured yet.
> dpkg: error processing libpthread-stubs0-dev (--configure):
> dependency problems - leaving unconfigured
> No apport report written because the error message indicates its a followup
> error from a previous failure.
> Errors were encountered while processing:
> libpthread-stubs0-dev
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Note that I sometimes have to run the command twice for it to appear.
>
> The multi-arch patch was applied in Debian's libpthread-stubs in
> 0.3-3, so that reproducer should work in sid just as well.
>
> This happens for packages which are metapackages for others (like
> libtag1c2a), or just empty on most architectures (like
> libpthread-stubs0), so they can't be M-A: foreign as they have M-A:
> same dependencies.
>
> I think the "completely disappeared" logic should not apply in this
> case.
This does not affect 1.16.2, closing.
thanks,
guillem
--- End Message ---
