Control: tags -1 + moreinfo
Hi Christian,
On Tue, Mar 19, 2024 at 10:11:53AM +0100, Christian Marillat wrote:
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.
`----
I fear this is not enough information to diagnose the problem. I'm
giving you some context to better understand what we need here.
e2fsprogs was identified as one of the packages whose ABI is affected by time64. That analsys did not discriminate between individual shared
libraries built from e2fsprogs and hence all libraries including
libcom-err2 were bumped. It turned out that libss2 and libcom-err2
really were not affected and libss2t64 and libcom-err2t64 did not
transition to trixie. Hence, I reverted the transition for these to ease upgrades knowing that I'd be making upgrades in unstable slightly harder
though those are difficult at best.
So we need to know which libcom-err2 and libcom-err2t64 packages are
installed for which architectures on your system. If there is any libcom-err2t64, please "upgrade" to libcom-err2. Then retry your
original apt. I fear this is going to be manual in unstable as there is
no sane way to make apt understand that we really don't need
libco-err2t64. I expect that upgrades from bookworm and trixie are
unaffected by this issue. Unless this expectation is wrong, I suggest
that we close this bug as wontfix.
Helmut
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)