Your message dated Tue, 7 Apr 2020 14:59:40 +0200 with message-id <20200407125940.GF2857@aurel32.net> and subject line Re: Bug#955818: libc6: Invalid symbolic link directory x86_64-linux-gnu has caused the Debian Bug report #955818, regarding libc6: Invalid symbolic link directory x86_64-linux-gnu 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 owner@bugs.debian.org immediately.) -- 955818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955818 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libc6: Invalid symbolic link directory x86_64-linux-gnu
- From: Santiago José López Borrazás <sjlopezb@gmx.es>
- Date: Sun, 05 Apr 2020 12:34:28 +0200
- Message-id: <[🔎] 158608286802.222178.15884087092826734257.reportbug@local.sjlopezb.es>
Package: libc6 Version: 2.30-4 Severity: normal Dear Maintainer, This little mistake, which brings me upside down. It may be a symbolic link problem, but... Resolve that, every time I install a new package, it appears at the end of everything: ldconfig: /lib/x86_64-linux-gnu/ is not a symbolic link I see everything correctly, but there is a but. And that but it is, that every time I install a new package I get that. The /etc/ld.so.conf.d/x86_64-linux-gnu.conf file is correct, I see no problem. This is kind of weird. Thanks. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_USER Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libc6 depends on: ii libcrypt1 1:4.4.16-1 ii libgcc-s1 [libgcc-s1] 10-20200402-1 Versions of packages libc6 recommends: ii libidn2-0 2.3.0-1 Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.73 pn glibc-doc <none> ii libc-l10n 2.30-4 ii locales 2.30-4 -- debconf information excluded
--- End Message ---
--- Begin Message ---
- To: Santiago José López Borrazás <sjlopezb@gmx.es>, 955818-done@bugs.debian.org
- Subject: Re: Bug#955818: libc6: Invalid symbolic link directory x86_64-linux-gnu
- From: Aurelien Jarno <aurelien@aurel32.net>
- Date: Tue, 7 Apr 2020 14:59:40 +0200
- Message-id: <20200407125940.GF2857@aurel32.net>
- In-reply-to: <[🔎] 70a0f4a8-03cd-7dcf-b450-79f5f845e076@local.sjlopezb.es>
- References: <[🔎] 158608286802.222178.15884087092826734257.reportbug@local.sjlopezb.es> <[🔎] 20200407095407.GE2857@aurel32.net> <[🔎] 158608286802.222178.15884087092826734257.reportbug@local.sjlopezb.es> <[🔎] 70a0f4a8-03cd-7dcf-b450-79f5f845e076@local.sjlopezb.es>
On 2020-04-07 12:00, Santiago José López Borrazás wrote: > El 7/4/20 a las 11:54, Aurelien Jarno escribió: > > I agree it is kind of weird. Could you please try to run ldconfig in > > verbose mode and send the output? That should be 'ldconfig -v' as root > > or through sudo. > > > > Thanks, > > Aurelien > Thanks, is SOLVED. > > Not problem the information. A package resolve after 2 days. Ok, it might have been a package that installed a wrong symlink and that has been fixed in the meantime. I am closing the bug for now. Feel free to reopen with the output of 'ldconfig -v' if it happens again. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://www.aurel32.net
--- End Message ---