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 >

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

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

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

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

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

[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:

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

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

[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

[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.

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

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)

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

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

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

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

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:

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;

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

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)