Your message dated Tue, 19 Mar 2024 15:45:40 +0100
with message-id <20240319144540.ga2975...@subdivi.de>
and subject line Re: Bug#1067134: Try to remove i386 packages
has caused the Debian Bug report #1067134,
regarding Try to remove i386 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 ow...@bugs.debian.org
immediately.)
--
1067134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: comerr-dev
Version: 2.1-1.47.0-2.4
Severity: serious
Dear Maintainer,
I'm unable to install comerr-dev under a multiarch amd64/i386
machine.
Here is a simple example :
,----
| $ sudo apt-get install comerr-dev
| Reading package lists... Done
| Building dependency tree... Done
| Reading state information... Done
|
| [...]
|
| The following additional packages will be installed:
| libcom-err2
| Suggested packages:
| doc-base
| The following packages will be REMOVED:
| inetutils-telnet:i386
| The following NEW packages will be installed:
| comerr-dev libcom-err2
| 0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
`----
Christian
-- System Information:
Debian Release: trixie/sid
APT prefers buildd-unstable
APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.8.1-1-custom (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Control: tags -1 - moreinfo + wontfix
On Tue, Mar 19, 2024 at 02:21:59PM +0100, Christian Marillat wrote:
> On 19 mars 2024 13:28, Helmut Grohne <hel...@subdivi.de> wrote:
>
>
> [...]
>
> > I agree that the experience is a little messed up, but this is
> > resolvable with apt and it only affects unstable users. Do you agree
> > with closing this bug with no action?
>
> Yes, if you think that this bug is only related to unstable...
Yes. libcom-err2t64 (which is what is require to experience the problem)
has never gotten beyond unstable and experimental. Thus closing the bug.
Helmut
--- End Message ---
