Re: lib6-dev broken

[Marcelo Varanda <m@varanda.ca>]

Thanks a lot for your attention Aurelien.
Regards,
Marcelo



Hi,

On 2022-11-08 14:02, Marcelo Varanda wrote:
> According to the maintainer of that machine the installation was done using: debian-11.5.0-amd64-netinst.iso downloaded from the Debian website 
> 
> > On Nov 8, 2022, at 12:09 PM, Marcelo Varanda <m@varanda.ca> wrote:
> > 
> > Thanks for your reply Aurelian,
> > 
> > The machine that had this problem is gone (re-imaged). It was not setup by me.  All other Debian 11 machines I have are OK having lib6-dev depending on installed lib6 2.31-13+deb11u4 (not u5 like that odd machine).
> > I will ask which DVD image they use to install Debian 11 for the “odd” machine.
> > 
> > 
> > Following are some info I had captured and I hope it helps.
> > 
> > sources.list:
> > 
> > deb http://security.debian.org/debian-security <http://security.debian.org/debian-security> bullseye-security main contrib non-free
> > deb-src http://security.debian.org/debian-security <http://security.debian.org/debian-security> bullseye-security main contrib non-free
> > deb http://deb.debian.org/debian/ <http://deb.debian.org/debian/> bullseye main contrib non-free

Ok, so it does not have any entry for bullseye-updates that provides
non-security updates for stable. This is where glibc version
2.31-13+deb11u5 is hosted, as it was published after the released of
Debian 11.5 to fix regression issues on some CPUs.

Without this entry, it's normal that the newest glibc version is
2.31-13+deb11u4.

> > vigil@vigil:~$ apt show libc6-dev
> > Package: libc6-dev
> > Version: 2.31-13+deb11u4
> > Priority: optional
> > Build-Essential: yes
> > Section: libdevel
> > Source: glibc
> > Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org <mailto:debian-glibc@lists.debian.org>>
> > Installed-Size: 14.9 MB
> > Provides: libc-dev
> > Depends: libc6 (= 2.31-13+deb11u4), libc-dev-bin (= 2.31-13+deb11u4), linux-libc-dev, libcrypt-dev, libnsl-dev
> > Suggests: glibc-doc, manpages-dev
> > Conflicts: libc0.1-dev, libc0.3-dev, libc6.1-dev
> > Breaks: libc6-dev-amd64-cross (<< 2.31~), libgcc-10-dev (<< 10-20200321-1~), libgcc-7-dev (<< 7.5.0-6~), libgcc-8-dev (<< 8.4.0-2~), libgcc-9-dev (<< 9.3.0-5~), libperl5.26 (<< 5.26.1-3), python3.7 (<< 3.7.7-1+b1), python3.8 (<< 3.8.2-1+b1)
> > Homepage: https://www.gnu.org/software/libc/libc.html <https://www.gnu.org/software/libc/libc.html>
> > Tag: devel::lang:c, devel::library, implemented-in::c, role::devel-lib,
> >  suite::gnu
> > Download-Size: 2,360 kB
> > APT-Sources: http://deb.debian.org/debian <http://deb.debian.org/debian> bullseye/main amd64 Packages
> > Description: GNU C Library: Development Libraries and Header Files
> >  Contains the symlinks, headers, and object files needed to compile
> >  and link programs which use the standard C library.
> > 
> > 
> > vigil@vigil:~$ uname a
> > uname: extra operand ‘a’
> > Try 'uname --help' for more information.
> > vigil@vigil:~$ uname -a
> > Linux vigil 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21) x86_64 GNU/Linux
> > 
> > 
> > vigil@vigil:~$ apt policy libc6-dev
> > libc6-dev:
> >   Installed: (none)
> >   Candidate: 2.31-13+deb11u4
> >   Version table:
> >      2.31-13+deb11u4 500
> >         500 http://deb.debian.org/debian <http://deb.debian.org/debian> bullseye/main amd64 Packages
> > 
> > The following packages have unmet dependencies:
> >  libc6-dev : Depends: libc6 (= 2.31-13+deb11u4) but 2.31-13+deb11u5 is to be installed
> > E: Unable to correct problems, you have held broken packages.

My guess is that there has been an entry for bullseye-updates at some
point, the machine got upgraded (with libc6 2.31-13+deb11u5 among other
things) and that entry got removed.

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net