Bug#954915: [libc6] upgrade fail: A copy of the C library was found in an unexpected directory

2020-03-25 Thread Stephan Skrodzki
On Wed, 25 Mar 2020 10:54:22 +0100 =?utf-8?B?SsO2cmc=?= Sommer
 wrote:
> 
> A quick and dirty workaround is:
> 
> ```
> # egrep '/(ld|lib(d|c|m|pthread|rt|dl))-2.*.so' $I/libc6:amd64.list |sed 
> 's,^,/usr,' |tee -a $I/libc6:amd64.list
> /usr/lib/x86_64-linux-gnu/ld-2.30.so
> /usr/lib/x86_64-linux-gnu/libc-2.30.so
> /usr/lib/x86_64-linux-gnu/libdl-2.30.so
> /usr/lib/x86_64-linux-gnu/libm-2.30.so
> /usr/lib/x86_64-linux-gnu/libpthread-2.30.so
> /usr/lib/x86_64-linux-gnu/librt-2.30.so
> # dpkg --unpack $A/libc6_2.30-3_amd64.deb
> (Lese Datenbank ... 452795 Dateien und Verzeichnisse sind derzeit 
> installiert.)
> Vorbereitung zum Entpacken von .../libc6_2.30-3_amd64.deb ...
> libc6:i386 (2.30-2) wird de-konfiguriert ...
> Entpacken von libc6:amd64 (2.30-3) über (2.30-2) ...

Hmm... strange, why does this not work for me? Although libc6:amd64.list
is expanded with these lines, dkpg --unpack still fails with the same
error message from the bug report...



glibc_2.30-4_source.changes ACCEPTED into unstable

2020-03-25 Thread Debian FTP Masters



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 25 Mar 2020 13:56:56 +0100
Source: glibc
Architecture: source
Version: 2.30-4
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 954915
Changes:
 glibc (2.30-4) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/debhelper.in/libc.preinst, debian/rules.d/debhelper.mk: there
 is no easy way to check if a file belongs to a package with usrmerge.
 Just drop all safety checks...  Closes: #954915.
   * debian/patches/any/local-tst-system-disable-shell-tests.diff: disable
 tests that rely on a particular shell until a fix is found upstream.
 .
   [ John Paul Adrian Glaubitz ]
   * debian/testsuite-xfail-debian.mk: mark nptl/tst-cond8-static and
 nptl/tst-mutex{,pi}8-static as XFAIL on sparc64.
Checksums-Sha1:
 9270975bdfd83e676bc1efc4c59be0cb966c9c22 8731 glibc_2.30-4.dsc
 3d6d0acbc4a4f998ae95425b53e55bd779c0a35f 843820 glibc_2.30-4.debian.tar.xz
 a4d077fb683b1951b60fa4dc8c21fbad287a1acb 7589 glibc_2.30-4_source.buildinfo
Checksums-Sha256:
 84c8d7c231ba1f683023391f794e9dc39710af1e3ae70b15dee73453cb9b7d9f 8731 
glibc_2.30-4.dsc
 d223a88aff38b11c414b17f8e1be6a0a392115fb5451c7e9f5bf6c12955c4275 843820 
glibc_2.30-4.debian.tar.xz
 28e660a2c6729827e53e86cca11340f7d015711c65db108f3f9808fefaa1370b 7589 
glibc_2.30-4_source.buildinfo
Files:
 930de8f673f1ae03a5f4f1ff8152fec9 8731 libs required glibc_2.30-4.dsc
 48419cf9436a0c326076375b4cc5a658 843820 libs required 
glibc_2.30-4.debian.tar.xz
 6bea50637c4cea30bd6828dd25ba2de5 7589 libs required 
glibc_2.30-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl57WgkACgkQE4jA+Jno
M2vNQBAAhw6GHStKsu2QVUTXGf+Lgyu+QbxJRaR1Im6woTZCZdKorXiv8QCbVE6j
kQ5yDYjxYM+jXzetfHHL3cVGps1fVdc4Cd/zelY4RM1dWxRzJsE9tNaYoHc6AOeH
hOqI6mxxEg9phDntNcz8jX55DsMTE1i/klbj4NbW93E98FVZzLhxuuHf0JTgxd9N
CMZX2MBxGrK3zKFdRdX7kaIOGo0nP4fu+b+L/CuMvW7/Wle1daDgLX21Zjb/Fa4s
Gq/jWUu/PfiECksAn/7EDI9pMsFrv8TEk/EypUNjXNNQNgevDJuZcuy/jYUB6RKH
BtCRJR4cG4PIR/bL2lCkCfpxVT0x6APVbhh2EGY72ZDE+BTdZIvOnJMK/Z1SuYy+
Ihb+4+SgFCGLgWlRMOQ2SPL+CrwzfkQZstRbLjwXNzzODsb+WQG96vqg3R0Npn5u
qli1GhllDA+e/yqRZUDGwKsjzrtfDskpiwr+aajYI//WCwO5Si51rQCYhQkBQEE5
WxL2DDegoYLkH0fuboJnM//g/qjwePNsXitAf13tNGNAUxIfN0/M/AEeVUqJ0IXu
6jq+3q0+jl86KMwZ6kV7Y8vQOWHXHX+IoDShY8aReoZj14R1u/K5GHEQU31NAoiv
Z99ogoT8oi2RFYmeZFWaYA3+4RPyCFXEnzVx9BNbuRdmwcr1ta8=
=TwfF
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



Bug#953869: marked as done (glibc: Please disable nptl/tst-cond8-static and nptl/tst-mutex{,pi}8-static on sparc64)

2020-03-25 Thread Debian Bug Tracking System
Your message dated Wed, 25 Mar 2020 14:44:46 +0100
with message-id <20200325134446.gd2...@aurel32.net>
and subject line Re: Bug#953869: glibc: Please disable nptl/tst-cond8-static 
and nptl/tst-mutex{,pi}8-static on sparc64
has caused the Debian Bug report #953869,
regarding glibc: Please disable nptl/tst-cond8-static and 
nptl/tst-mutex{,pi}8-static on sparc64
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.)


-- 
953869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.31-0experimental0
Severity: normal
User: debian-sp...@lists.debian.org
Usertags: sparc64

Hello!

With glibc 2.31, the number of testsuite failures has dropped to just three
failures on sparc64:

FAIL: nptl/tst-cond8-static
FAIL: nptl/tst-mutex8-static
FAIL: nptl/tst-mutexpi8-static

I have reported these failures upstream [1, 2].

Since 2.31 seems to be a big improvement on sparc64, can you disable these
three tests so that we can quickly enable 2.31 on sparc64? 2.30 seems to be
broken on sparc64, unfortunately, as it already causes segfaults during
installation:

Setting up libc6:sparc64 (2.30-2) ...
dpkg: error processing package libc6:sparc64 (--configure):
 installed libc6:sparc64 package post-installation script subprocess was killed 
by signal (Segmentation fault)
Errors were encountered while processing:
 libc6:sparc64
E: Sub-process /usr/bin/dpkg returned an error code (1)
apt-get failed.
E: Package installation failed

Thanks,
Adrian

> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=25671
> [2] https://sourceware.org/bugzilla/show_bug.cgi?id=25672

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Version: 2.30-4

On 2020-03-15 12:50, John Paul Adrian Glaubitz wrote:
> On 3/14/20 11:26 AM, John Paul Adrian Glaubitz wrote:
> > With glibc 2.31, the number of testsuite failures has dropped to just three
> > failures on sparc64:
> > 
> > FAIL: nptl/tst-cond8-static
> > FAIL: nptl/tst-mutex8-static
> > FAIL: nptl/tst-mutexpi8-static
> > 
> > I have reported these failures upstream [1, 2].
> > 
> > Since 2.31 seems to be a big improvement on sparc64, can you disable these
> > three tests so that we can quickly enable 2.31 on sparc64?
> 
> I have rebuild glibc_2.31 with these tests marked as XFAIL multiple times
> and the number of failures is reproducible for me.
> 
> So, can we get this change included?
> 

This has been done in version 2.30-4, but I forgot to close the bug in
the changelog. Closing it now.

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


Bug#954915: marked as pending in glibc

2020-03-25 Thread Simon McVittie
On Wed, 25 Mar 2020 at 13:15:03 +, Aurelien Jarno wrote:
> debian/debhelper.in/libc.preinst, debian/rules.d/debhelper.mk: there is no 
> easy way to check if a file belongs to a package with usrmerge. Just drop all 
> safety checks...  Closes: #954915.

The /usr merge merges /foo with /usr/foo (for some values of foo) and
nothing else, so if you would prefer to keep those checks, you could do
something like this:

if dpkg-query -S "${lib#/usr}" >/dev/null 2>&1 ; then
continue
fi

if dpkg-query -S "/usr${lib#/usr}" >/dev/null 2>&1 ; then
continue
fi

which will in particular treat /usr/lib/whatever as equivalent to
/lib/whatever.

(And the same for the quicker check involving libcfiles - but I don't
understand how or whether that one works, because it seems to be telling
grep to look for ^ and $ as literals rather than as anchors, which seems
wrong to me. But perhaps I'm missing something there.)

smcv



[Git][glibc-team/glibc][sid] Add bug number

2020-03-25 Thread Aurelien Jarno


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
68a644fc by Aurelien Jarno at 2020-03-25T14:44:13+01:00
Add bug number

- - - - -


1 changed file:

- debian/changelog


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/68a644fc87cceeda4c1f4b3631cbcff6c02bac28

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/68a644fc87cceeda4c1f4b3631cbcff6c02bac28
You're receiving this email because of your account on salsa.debian.org.




Bug#954915: marked as done ([libc6] upgrade fail: A copy of the C library was found in an unexpected directory)

2020-03-25 Thread Debian Bug Tracking System
Your message dated Wed, 25 Mar 2020 13:35:22 +
with message-id 
and subject line Bug#954915: fixed in glibc 2.30-4
has caused the Debian Bug report #954915,
regarding [libc6] upgrade fail: A copy of the C library was found in an 
unexpected directory
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.)


-- 
954915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.30-3

sudo aptitude upgrade just now:

```
Preparing to unpack .../libc6-dev_2.30-3_amd64.deb ...
Unpacking libc6-dev:amd64 (2.30-3) over (2.30-2) ...
Preparing to unpack .../libc-dev-bin_2.30-3_amd64.deb ...
Unpacking libc-dev-bin (2.30-3) over (2.30-2) ...
Preparing to unpack .../libc6-dbg_2.30-3_amd64.deb ...
Unpacking libc6-dbg:amd64 (2.30-3) over (2.30-2) ...
Preparing to unpack .../libc6_2.30-3_amd64.deb ...

A copy of the C library was found in an unexpected directory:
  '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
It is not safe to upgrade the C library in this situation;
please remove that copy of the C library or get it out of
'/usr/lib/x86_64-linux-gnu' and try again.

dpkg: error processing archive /var/cache/apt/archives/libc6_2.30-
3_amd64.deb (--unpack):
 new libc6:amd64 package pre-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.30-3_amd64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
dpkg: dependency problems prevent configuration of libc6-dbg:amd64:
 libc6-dbg:amd64 depends on libc6 (= 2.30-3); however:
  Version of libc6:amd64 on system is 2.30-2.

dpkg: error processing package libc6-dbg:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libc6-dev:amd64:
 libc6-dev:amd64 depends on libc6 (= 2.30-3); however:
  Version of libc6:amd64 on system is 2.30-2.

dpkg: error processing package libc6-dev:amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up libc-dev-bin (2.30-3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.30-2) ...
Errors were encountered while processing:
 libc6-dbg:amd64
 libc6-dev:amd64
```
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.30-4
Done: Aurelien Jarno 

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 25 Mar 2020 13:56:56 +0100
Source: glibc
Architecture: source
Version: 2.30-4
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 954915
Changes:
 glibc (2.30-4) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/debhelper.in/libc.preinst, debian/rules.d/debhelper.mk: there
 is no easy way to check if a file belongs to a package with usrmerge.
 Just drop all safety checks...  Closes: #954915.
   * debian/patches/any/local-tst-system-disable-shell-tests.diff: disable
 tests that rely on a particular shell until a fix is found upstream.
 .
   [ John Paul Adrian Glaubitz ]
   * debian/testsuite-xfail-debian.mk: mark nptl/tst-cond8-static and
 nptl/tst-mutex{,pi}8-static as XFAIL on sparc64.
Checksums-Sha1:
 9270975bdfd83e676bc1efc4c59be0cb966c9c22 8731 glibc_2.30-4.dsc
 3d6d0acbc4a4f998ae95425b53e55bd779c0a35f 843820 glibc_2.30-4.debian.tar.xz
 a4d077fb683b1951b60fa4dc8c21fbad287a1acb 7589 glibc_2.30-4_source.buildinfo
Checksums-Sha256:
 84c8d7c231ba1f683023391f794e9dc39710af1e3ae70b15dee73453cb9b7d9f 8731 
glibc_2.30-4.dsc
 d223a88aff38b11c414b17f8e1be6a0a392115fb5451c7e9f5bf6c12955c4275 843820 
glibc_2.30-4.debian.tar.xz
 28e660a2c6729827e53e86cca11340f7d015711c65db108f3f9808fefaa1370b 7589 
glibc_2.30-4_source.buildinfo
Files:
 930de8f673f1ae03a5f4f1ff8152fec9 8731 libs required glibc_2.30-4.dsc
 48419cf9436a0c326076375b

Bug#954933: marked as done (libc6: Not installing package libc6. Problem script.)

2020-03-25 Thread Debian Bug Tracking System
Your message dated Wed, 25 Mar 2020 13:35:22 +
with message-id 
and subject line Bug#954915: fixed in glibc 2.30-4
has caused the Debian Bug report #954915,
regarding libc6: Not installing package libc6. Problem script.
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.)


-- 
954915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.30-2
Severity: important

Dear Maintainer,

Only fail this package, and returnet fail:

A copy of the C library was found in an unexpected directory:
  '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
It is not safe to upgrade the C library in this situation;
please remove that copy of the C library or get it out of
'/usr/lib/x86_64-linux-gnu' and try again.

dpkg: error al procesar el archivo 
/var/cache/apt/archives/libc6_2.30-3_amd64.deb (--unpack):
 el subproceso nuevo paquete libc6:amd64 script pre-installation devolvió el 
código de salida de error 1
Se encontraron errores al procesar:
 /var/cache/apt/archives/libc6_2.30-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Others packages is installed, only this package fail.

This package is problem in update. No fail others packages. Only this.

In this moment in the version 2.30-2 of libc6.

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)
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.15-1
ii  libgcc-s1  10-20200324-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  
ii  libc-l10n  2.30-3
ii  locales2.30-3

-- debconf information:
* glibc/upgrade: true
  glibc/kernel-too-old:
* libraries/restart-without-asking: true
  glibc/restart-services:
  glibc/disable-screensaver:
  glibc/restart-failed:
  glibc/kernel-not-supported:
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.30-4
Done: Aurelien Jarno 

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 954...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 25 Mar 2020 13:56:56 +0100
Source: glibc
Architecture: source
Version: 2.30-4
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 954915
Changes:
 glibc (2.30-4) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/debhelper.in/libc.preinst, debian/rules.d/debhelper.mk: there
 is no easy way to check if a file belongs to a package with usrmerge.
 Just drop all safety checks...  Closes: #954915.
   * debian/patches/any/local-tst-system-disable-shell-tests.diff: disable
 tests that rely on a particular shell until a fix is found upstream.
 .
   [ John Paul Adrian Glaubitz ]
   * debian/testsuite-xfail-debian.mk: mark nptl/tst-cond8-static and
 nptl/tst-mutex{,pi}8-static as XFAIL on sparc64.
Checksums-Sha1:
 9270975bdfd83e676bc1efc4c59be0cb966c9c22 8731 glibc_2.30-4.dsc
 3d6d0acbc4a4f998ae95425b53e55bd779c0a35f 843820 glibc_2.30-4.debian.tar.xz
 a4d077fb683b1951b60fa4dc8c21fbad287a1acb 7589 glibc_2.30-4_source.buildinfo
Checksums-Sha256:
 84c8d7c231ba1f683023391f794e9dc39710af1e3ae70b15dee73453cb9b7d9f 8731 
glibc_2.30-4.dsc
 d223a88aff38b11c414b17f8e1be6a0a392115fb5451c7e9f5bf6c12955c4275 843820 
glibc_2.30-4.debian.tar.xz
 28e660a2c6729827e53e86cca11340f7d015711c65db108f3f9808fefaa1370b 7589 
glibc_2.30-4_source.buildinfo
Files:
 930de8f673f1ae03a5f4f1ff8152fec9 8731 libs required glibc_2.30-4.dsc
 48419cf9436a0c326076375b4cc5a658 843820 libs required 
glibc_2.30-4.d

Processing of glibc_2.30-4_source.changes

2020-03-25 Thread Debian FTP Masters
glibc_2.30-4_source.changes uploaded successfully to localhost
along with the files:
  glibc_2.30-4.dsc
  glibc_2.30-4.debian.tar.xz
  glibc_2.30-4_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



Processed: forcibly merging 954915 954933

2020-03-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forcemerge 954915 954933
Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in 
an unexpected directory
Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in 
an unexpected directory
Marked as found in versions glibc/2.30-2.
Bug #954933 [libc6] libc6: Not installing package libc6. Problem script.
Severity set to 'serious' from 'important'
Marked as found in versions glibc/2.30-3.
Added tag(s) confirmed and pending.
Merged 954915 954933
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954915
954933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: notfound 954933 in libc6/2.30-2

2020-03-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfound 954933 libc6/2.30-2
Bug #954933 [libc6] libc6: Not installing package libc6. Problem script.
The source libc6 and version 2.30-2 do not appear to match any binary packages
Ignoring request to alter found versions of bug #954933 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Bug#954915 marked as pending in glibc

2020-03-25 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in 
an unexpected directory
Added tag(s) pending.

-- 
954915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



[Git][glibc-team/glibc][sid] 4 commits: debian/debhelper.in/libc.preinst, debian/rules.d/debhelper.mk: there is no...

2020-03-25 Thread Aurelien Jarno


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
49d137c4 by Aurelien Jarno at 2020-03-25T13:41:56+01:00
debian/debhelper.in/libc.preinst, debian/rules.d/debhelper.mk: there is no easy 
way to check if a file belongs to a package with usrmerge. Just drop all safety 
checks...  Closes: #954915.

- - - - -
4ac2ba5f by Aurelien Jarno at 2020-03-25T13:43:42+01:00
debian/testsuite-xfail-debian.mk: mark nptl/tst-cond8-static and 
nptl/tst-mutex{,pi}8-static as XFAIL on sparc64.

- - - - -
e109fbff by Aurelien Jarno at 2020-03-25T13:44:26+01:00
debian/patches/any/local-tst-system-disable-shell-tests.diff: disable tests 
that rely on a particular shell until a fix is found upstream.

- - - - -
581dcda6 by Aurelien Jarno at 2020-03-25T13:57:21+01:00
releasing package glibc version 2.30-4

- - - - -


6 changed files:

- debian/changelog
- debian/debhelper.in/libc.preinst
- + debian/patches/any/local-tst-system-disable-shell-tests.diff
- debian/patches/series
- debian/rules.d/debhelper.mk
- debian/testsuite-xfail-debian.mk


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/a4fd8e29defda0889722a8212b50cf1b2eb27b65...581dcda683bc1aca051adc43f449548ff62192d2

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/a4fd8e29defda0889722a8212b50cf1b2eb27b65...581dcda683bc1aca051adc43f449548ff62192d2
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc] Pushed new tag debian/2.30-4

2020-03-25 Thread Aurelien Jarno


Aurelien Jarno pushed new tag debian/2.30-4 at GNU Libc Maintainers / glibc

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.30-4
You're receiving this email because of your account on salsa.debian.org.




Bug#954933: libc6: Not installing package libc6. Problem script.

2020-03-25 Thread Santiago José López Borrazás
Package: libc6
Version: 2.30-2
Severity: important

Dear Maintainer,

Only fail this package, and returnet fail:

A copy of the C library was found in an unexpected directory:
  '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
It is not safe to upgrade the C library in this situation;
please remove that copy of the C library or get it out of
'/usr/lib/x86_64-linux-gnu' and try again.

dpkg: error al procesar el archivo 
/var/cache/apt/archives/libc6_2.30-3_amd64.deb (--unpack):
 el subproceso nuevo paquete libc6:amd64 script pre-installation devolvió el 
código de salida de error 1
Se encontraron errores al procesar:
 /var/cache/apt/archives/libc6_2.30-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Others packages is installed, only this package fail.

This package is problem in update. No fail others packages. Only this.

In this moment in the version 2.30-2 of libc6.

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)
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.15-1
ii  libgcc-s1  10-20200324-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  
ii  libc-l10n  2.30-3
ii  locales2.30-3

-- debconf information:
* glibc/upgrade: true
  glibc/kernel-too-old:
* libraries/restart-without-asking: true
  glibc/restart-services:
  glibc/disable-screensaver:
  glibc/restart-failed:
  glibc/kernel-not-supported:


Bug#954915: [libc6] upgrade fail: A copy of the C library was found in an unexpected directory

2020-03-25 Thread Aurelien Jarno
On 2020-03-25 10:21, Jörg Sommer wrote:
> jnq...@gmail.com hat am Mi 25. Mär, 09:03 (+) geschrieben:
> > Package: libc6
> > Version: 2.30-3
> > 
> > sudo aptitude upgrade just now:
> > 
> > ```
> > Preparing to unpack .../libc6-dev_2.30-3_amd64.deb ...
> > Unpacking libc6-dev:amd64 (2.30-3) over (2.30-2) ...
> > Preparing to unpack .../libc-dev-bin_2.30-3_amd64.deb ...
> > Unpacking libc-dev-bin (2.30-3) over (2.30-2) ...
> > Preparing to unpack .../libc6-dbg_2.30-3_amd64.deb ...
> > Unpacking libc6-dbg:amd64 (2.30-3) over (2.30-2) ...
> > Preparing to unpack .../libc6_2.30-3_amd64.deb ...
> > 
> > A copy of the C library was found in an unexpected directory:
> >   '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
> > It is not safe to upgrade the C library in this situation;
> > please remove that copy of the C library or get it out of
> > '/usr/lib/x86_64-linux-gnu' and try again.
> 
> I'm having the same problem. It's caused by the package *usrmerge*, that
> installed the symlinks:
> 
> ```
> % ls -l /*(@)
> lrwxrwxrwx 1 root root  7 Mär  7  2019 /bin -> usr/bin
> lrwxrwxrwx 1 root root  7 Mär  7  2019 /lib -> usr/lib
> lrwxrwxrwx 1 root root  9 Mär  7  2019 /lib32 -> usr/lib32
> lrwxrwxrwx 1 root root  9 Mär  7  2019 /lib64 -> usr/lib64
> lrwxrwxrwx 1 root root 10 Mär  7  2019 /libx32 -> usr/libx32
> lrwxrwxrwx 1 root root  8 Mär  7  2019 /sbin -> usr/sbin
> ```

It happens that the checks in the libc6.preinst were broken, and that
the fix for #954374 just fixed them. It also means that usrmerge broke
those checks but we didn't notice it until now...

I wonder if the best is to just remove all those checks in libc6.preinst.
After all they haven't been useful all those years, although we also got
a few bugs report about broken systems for which we don't know the cause
and that might have been prevented by working checks.

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


signature.asc
Description: PGP signature


Processed: tagging 954915

2020-03-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 954915 + confirmed
Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in 
an unexpected directory
Added tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#954915: [libc6] upgrade fail: A copy of the C library was found in an unexpected directory

2020-03-25 Thread Jörg Sommer
jnq...@gmail.com hat am Mi 25. Mär, 09:03 (+) geschrieben:
> Package: libc6
> Version: 2.30-3
> 
> sudo aptitude upgrade just now:
> 
> ```
> Preparing to unpack .../libc6-dev_2.30-3_amd64.deb ...
> Unpacking libc6-dev:amd64 (2.30-3) over (2.30-2) ...
> Preparing to unpack .../libc-dev-bin_2.30-3_amd64.deb ...
> Unpacking libc-dev-bin (2.30-3) over (2.30-2) ...
> Preparing to unpack .../libc6-dbg_2.30-3_amd64.deb ...
> Unpacking libc6-dbg:amd64 (2.30-3) over (2.30-2) ...
> Preparing to unpack .../libc6_2.30-3_amd64.deb ...
> 
> A copy of the C library was found in an unexpected directory:
>   '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
> It is not safe to upgrade the C library in this situation;
> please remove that copy of the C library or get it out of
> '/usr/lib/x86_64-linux-gnu' and try again.

A quick and dirty workaround is:

```
# egrep '/(ld|lib(d|c|m|pthread|rt|dl))-2.*.so' $I/libc6:amd64.list |sed 
's,^,/usr,' |tee -a $I/libc6:amd64.list
/usr/lib/x86_64-linux-gnu/ld-2.30.so
/usr/lib/x86_64-linux-gnu/libc-2.30.so
/usr/lib/x86_64-linux-gnu/libdl-2.30.so
/usr/lib/x86_64-linux-gnu/libm-2.30.so
/usr/lib/x86_64-linux-gnu/libpthread-2.30.so
/usr/lib/x86_64-linux-gnu/librt-2.30.so
# dpkg --unpack $A/libc6_2.30-3_amd64.deb
(Lese Datenbank ... 452795 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../libc6_2.30-3_amd64.deb ...
libc6:i386 (2.30-2) wird de-konfiguriert ...
Entpacken von libc6:amd64 (2.30-3) über (2.30-2) ...

# egrep '/(ld|lib(d|c|m|pthread|rt|dl))-2.*.so' $I/libc6:i386.list |sed 
's,^,/usr,; p; s,/i386-linux-gnu,32,' |tee -a $I/libc6:i386.list
/usr/lib/i386-linux-gnu/ld-2.30.so
/usr/lib32/ld-2.30.so
/usr/lib/i386-linux-gnu/libc-2.30.so
/usr/lib32/libc-2.30.so
/usr/lib/i386-linux-gnu/libdl-2.30.so
/usr/lib32/libdl-2.30.so
/usr/lib/i386-linux-gnu/libm-2.30.so
/usr/lib32/libm-2.30.so
/usr/lib/i386-linux-gnu/libpthread-2.30.so
/usr/lib32/libpthread-2.30.so
/usr/lib/i386-linux-gnu/librt-2.30.so
/usr/lib32/librt-2.30.so
# dpkg --unpack $A/libc6_2.30-3_i386.deb
(Lese Datenbank ... 452801 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../archives/libc6_2.30-3_i386.deb ...
Entpacken von libc6:i386 (2.30-3) über (2.30-2) ...
```

Pay attention: The command for sed for i386 is different from amd64!



-- 
The UNIX Guru's View of Sex:
# unzip ; strip ; touch ; finger ; mount ; fsck ; more ; yes ; umount ; sleep


signature.asc
Description: PGP signature


Bug#954374: Breaks on systems with /usr merge

2020-03-25 Thread Fiona Klute
This change appears to break systems with /usr merge [1], I get this
when trying to upgrade libc6 from 2.30-2 to 2.30-3 on amd64:

> A copy of the C library was found in an unexpected directory:
>   '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
> It is not safe to upgrade the C library in this situation;
> please remove that copy of the C library or get it out of
> '/usr/lib/x86_64-linux-gnu' and try again.

It seems like the preinst script is getting confused by /lib being a
symlink to /usr/lib:

$ dpkg -L libc6 | grep ld-2.30.so
/lib/x86_64-linux-gnu/ld-2.30.so
$ realpath /lib/x86_64-linux-gnu/ld-2.30.so
/usr/lib/x86_64-linux-gnu/ld-2.30.so

[1] https://wiki.debian.org/UsrMerge



Bug#954915: [libc6] upgrade fail: A copy of the C library was found in an unexpected directory

2020-03-25 Thread Jörg Sommer
jnq...@gmail.com hat am Mi 25. Mär, 09:03 (+) geschrieben:
> Package: libc6
> Version: 2.30-3
> 
> sudo aptitude upgrade just now:
> 
> ```
> Preparing to unpack .../libc6-dev_2.30-3_amd64.deb ...
> Unpacking libc6-dev:amd64 (2.30-3) over (2.30-2) ...
> Preparing to unpack .../libc-dev-bin_2.30-3_amd64.deb ...
> Unpacking libc-dev-bin (2.30-3) over (2.30-2) ...
> Preparing to unpack .../libc6-dbg_2.30-3_amd64.deb ...
> Unpacking libc6-dbg:amd64 (2.30-3) over (2.30-2) ...
> Preparing to unpack .../libc6_2.30-3_amd64.deb ...
> 
> A copy of the C library was found in an unexpected directory:
>   '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
> It is not safe to upgrade the C library in this situation;
> please remove that copy of the C library or get it out of
> '/usr/lib/x86_64-linux-gnu' and try again.

I'm having the same problem. It's caused by the package *usrmerge*, that
installed the symlinks:

```
% ls -l /*(@)
lrwxrwxrwx 1 root root  7 Mär  7  2019 /bin -> usr/bin
lrwxrwxrwx 1 root root  7 Mär  7  2019 /lib -> usr/lib
lrwxrwxrwx 1 root root  9 Mär  7  2019 /lib32 -> usr/lib32
lrwxrwxrwx 1 root root  9 Mär  7  2019 /lib64 -> usr/lib64
lrwxrwxrwx 1 root root 10 Mär  7  2019 /libx32 -> usr/libx32
lrwxrwxrwx 1 root root  8 Mär  7  2019 /sbin -> usr/sbin
```

Regards Jörg

-- 
Habe Mut, dich deines eigenen Verstandes zu bedienen! – Immanuel Kant


signature.asc
Description: PGP signature


Processed: your mail

2020-03-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 954915 serious
Bug #954915 [libc6] [libc6] upgrade fail: A copy of the C library was found in 
an unexpected directory
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
954915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#954915: [libc6] upgrade fail: A copy of the C library was found in an unexpected directory

2020-03-25 Thread jnqnfe
Package: libc6
Version: 2.30-3

sudo aptitude upgrade just now:

```
Preparing to unpack .../libc6-dev_2.30-3_amd64.deb ...
Unpacking libc6-dev:amd64 (2.30-3) over (2.30-2) ...
Preparing to unpack .../libc-dev-bin_2.30-3_amd64.deb ...
Unpacking libc-dev-bin (2.30-3) over (2.30-2) ...
Preparing to unpack .../libc6-dbg_2.30-3_amd64.deb ...
Unpacking libc6-dbg:amd64 (2.30-3) over (2.30-2) ...
Preparing to unpack .../libc6_2.30-3_amd64.deb ...

A copy of the C library was found in an unexpected directory:
  '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
It is not safe to upgrade the C library in this situation;
please remove that copy of the C library or get it out of
'/usr/lib/x86_64-linux-gnu' and try again.

dpkg: error processing archive /var/cache/apt/archives/libc6_2.30-
3_amd64.deb (--unpack):
 new libc6:amd64 package pre-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.30-3_amd64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
dpkg: dependency problems prevent configuration of libc6-dbg:amd64:
 libc6-dbg:amd64 depends on libc6 (= 2.30-3); however:
  Version of libc6:amd64 on system is 2.30-2.

dpkg: error processing package libc6-dbg:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libc6-dev:amd64:
 libc6-dev:amd64 depends on libc6 (= 2.30-3); however:
  Version of libc6:amd64 on system is 2.30-2.

dpkg: error processing package libc6-dev:amd64 (--configure):
 dependency problems - leaving unconfigured
Setting up libc-dev-bin (2.30-3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.30-2) ...
Errors were encountered while processing:
 libc6-dbg:amd64
 libc6-dev:amd64
```