On Tue, May 25, 2021 at 10:00:48PM +0200, Paul Gevers wrote: > See below. > The following additional packages will be installed: > libgc1 libobjc4 > The following packages will be REMOVED: > libgc1c2 > The following NEW packages will be installed: > libgc1 > The following packages will be upgraded: > guile-2.2-libs libobjc4 > 2 upgraded, 1 newly installed, 1 to remove and 5 not upgraded.
Thanks a lot! This seems the crux of the problem: In buster: libgc1c2: Conflicts/Replace libgc1 while in bulleyes libgc1: Conflicts/Replace libgc1c2 This is unusual. Independently they are correct and quite usual, but not both at the same time. They means that libgc1c2 supersed libgc1, while at the same time libgc1 supersed libgc1c2. This is probably confusing apt. This comes from old package name reuse. There was an older libgc1 in 2005 which was superseded by libgc2 which is now superseded by a new libgc1. The package name libgc1 should not have been reused before all reference to it have been removed from stable. This is why removing outdated Conflicts is important. One way to fix that is to update libgc1c2 in stable to not Conflict/Replaces with libgc1. At this point could you send the message of apt-get install libobjc4 just to be sure. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here.
