Your message dated Wed, 9 Sep 2026 03:50:09 +0200
with message-id <[email protected]>
and subject line Re: Bug#71333: dpkg: dpkg ignores architecture while reading
Packages
has caused the Debian Bug report #71333,
regarding dpkg --merge-avail ignores architecture while reading Packages
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.)
--
71333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=71333
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.6.14
Severity: normal
When merging in Packages files with 'dpkg --merge-avail', dpkg
apparently doesn't care about the architecture of the package entries
it reads. If there is more than one entry for the same package (each
with a different architecture) it only keeps one of them, and this one
needn't be the right one.
I got a lot of dependency problems in dselect after merging the
Packages file from potato-proposed-updates, because there are a lot of
entries for traceroute and dpkg chose to keep the one for alpha
architecure instead of i386. That, in turn, depends on libc6.1 which
is only available for alpha and conflicts with libc6 ...
Regards, Daniel
-- System Information
Debian Release: 2.2
Kernel Version: Linux tpce14 2.2.17 #1 Mit Aug 23 17:38:47 CEST 2000 i686
unknown
Versions of the packages dpkg depends on:
ii libc6 2.1.3-13 GNU C Library: Shared libraries and Timezone
ii libncurses5 5.0-6 Shared libraries for terminal handling
ii libstdc++2.10 2.95.2-13 The GNU stdc++ library
--- End Message ---
--- Begin Message ---
Hi!
On Mon, 2000-09-11 at 07:47:18 +0200, Daniel Mueller wrote:
> Package: dpkg
> Version: 1.6.14
> Severity: normal
>
> When merging in Packages files with 'dpkg --merge-avail', dpkg
> apparently doesn't care about the architecture of the package entries
> it reads. If there is more than one entry for the same package (each
> with a different architecture) it only keeps one of them, and this one
> needn't be the right one.
>
> I got a lot of dependency problems in dselect after merging the
> Packages file from potato-proposed-updates, because there are a lot of
> entries for traceroute and dpkg chose to keep the one for alpha
> architecure instead of i386. That, in turn, depends on libc6.1 which
> is only available for alpha and conflicts with libc6 ...
This seems to be fixed now. I've not checked when, but I'm assuming it
got implemented when multiarch support got merged. As an example
session:
,---
# cat Packages.amd64
Package: test-arch-duped
Version: 1.0
Architecture: amd64
Maintainer: Some One <[email protected]>
Description: test package with duped arch entries
# cat Packages.alpha
Package: test-arch-duped
Version: 2.0
Architecture: alpha
Maintainer: Some One <[email protected]>
Description: test package with duped arch entries
# dpkg --clear-avail
# dpkg --merge-avail Packages.amd64
Updating available packages information from Packages.amd64.
Information about 1 package was updated.
# dpkg --merge-avail Packages.alpha
Updating available packages information from Packages.alpha.
Information about 1 package was updated.
# dpkg-query -p
Package: test-arch-duped
Maintainer: Some One <[email protected]>
Architecture: amd64
Version: 1.0
Description: test package with duped arch entries
Package: test-arch-duped
Maintainer: Some One <[email protected]>
Architecture: alpha
Version: 2.0
Description: test package with duped arch entries
`---
Thus closing.
Thanks,
Guillem
--- End Message ---
