[Git][glibc-team/glibc][sid] hurd: fix default character for termio cc[VSTATE]

2022-01-06 Thread Samuel Thibault (@sthibault)
Samuel Thibault pushed to branch sid at GNU Libc Maintainers / glibc Commits: 9bb7cc7e by Samuel Thibault at 2022-01-07T00:25:56+01:00 hurd: fix default character for termio cc[VSTATE] * debian/patches/hurd-i386/git-ttydefaults.diff - - - - - 3 changed files: - debian/changelog - +

glibc_2.33-2_source.changes ACCEPTED into unstable

2022-01-06 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 06 Jan 2022 22:32:53 +0100 Source: glibc Architecture: source Version: 2.33-2 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 1003201 Changes: glibc

Processing of glibc_2.33-2_source.changes

2022-01-06 Thread Debian FTP Masters
glibc_2.33-2_source.changes uploaded successfully to localhost along with the files: glibc_2.33-2.dsc glibc_2.33-2.debian.tar.xz glibc_2.33-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1003201: marked as done (libc6: Upgrading to libc 2.33-1 causes lots of strange crashes)

2022-01-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Jan 2022 22:03:45 + with message-id and subject line Bug#1003201: fixed in glibc 2.33-2 has caused the Debian Bug report #1003201, regarding libc6: Upgrading to libc 2.33-1 causes lots of strange crashes to be marked as done. This means that you claim that the

Processed: Bug#1003201 marked as pending in glibc

2022-01-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1003201 [libc6] libc6: Upgrading to libc 2.33-1 causes lots of strange crashes Ignoring request to alter tags of bug #1003201 to the same tags previously set -- 1003201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003201 Debian Bug

[Git][glibc-team/glibc][glibc-2.34] 4 commits: Note upstream commit ids

2022-01-06 Thread Aurelien Jarno (@aurel32)
Aurelien Jarno pushed to branch glibc-2.34 at GNU Libc Maintainers / glibc Commits: 6c5717f3 by Samuel Thibault at 2022-01-06T15:53:33+01:00 Note upstream commit ids - - - - - 8de2e937 by Aurelien Jarno at 2022-01-06T22:30:11+01:00 debian/patches/git-updates.diff: update from upstream stable

[Git][glibc-team/glibc] Pushed new tag debian/2.33-2

2022-01-06 Thread Aurelien Jarno (@aurel32)
Aurelien Jarno pushed new tag debian/2.33-2 at GNU Libc Maintainers / glibc -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.33-2 You're receiving this email because of your account on salsa.debian.org.

[Git][glibc-team/glibc][sid] releasing package glibc version 2.33-2

2022-01-06 Thread Aurelien Jarno (@aurel32)
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc Commits: 9e66c645 by Aurelien Jarno at 2022-01-06T22:32:59+01:00 releasing package glibc version 2.33-2 - - - - - 1 changed file: - debian/changelog View it on GitLab:

Processed: Bug#1003201 marked as pending in glibc

2022-01-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1003201 [libc6] libc6: Upgrading to libc 2.33-1 causes lots of strange crashes Added tag(s) pending. -- 1003201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes

2022-01-06 Thread Aurelien Jarno
On 2022-01-06 05:36, Rich wrote: > On Thu, Jan 6, 2022 at 5:22 AM Aurelien Jarno wrote: > > > On 2022-01-06 03:36, Rich wrote: > > > Hi Aurelien, > > > It's a VM running in qemu on an amd64 Debian bullseye system, no KVM > > > acceleration to be found here. > > > > Ok, that might be a QEMU issue

[Git][glibc-team/glibc][sid] debian/patches/git-updates.diff: update from upstream stable branch:

2022-01-06 Thread Aurelien Jarno (@aurel32)
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc Commits: 8de2e937 by Aurelien Jarno at 2022-01-06T22:30:11+01:00 debian/patches/git-updates.diff: update from upstream stable branch: * debian/patches/git-updates.diff: update from upstream stable branch: - Fix syscall() on

[Git][glibc-team/glibc][sid] Note upstream commit ids

2022-01-06 Thread Samuel Thibault (@sthibault)
Samuel Thibault pushed to branch sid at GNU Libc Maintainers / glibc Commits: 6c5717f3 by Samuel Thibault at 2022-01-06T15:53:33+01:00 Note upstream commit ids - - - - - 6 changed files: - debian/patches/hurd-i386/git-auth-leak.diff - debian/patches/hurd-i386/git-get_dtable.diff -

Bug#1003213: locales-all: introduce locales-utf8 package?

2022-01-06 Thread Simon McVittie
Package: locales-all Version: 2.33-1 Severity: wishlist As discussed recently on -devel and previously in #701585, at the moment Debian users have a choice between two non-ideal locale setups: * install locales and generate a subset of locale files with locale-gen (this is optimal for small

Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes

2022-01-06 Thread Rich
On Thu, Jan 6, 2022 at 5:22 AM Aurelien Jarno wrote: > On 2022-01-06 03:36, Rich wrote: > > Hi Aurelien, > > It's a VM running in qemu on an amd64 Debian bullseye system, no KVM > > acceleration to be found here. > > Ok, that might be a QEMU issue then. Which CPU do you emulate with QEMU? > I

Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes

2022-01-06 Thread Aurelien Jarno
On 2022-01-06 03:36, Rich wrote: > Hi Aurelien, > It's a VM running in qemu on an amd64 Debian bullseye system, no KVM > acceleration to be found here. Ok, that might be a QEMU issue then. Which CPU do you emulate with QEMU? Regards, Aurelien -- Aurelien Jarno GPG:

Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes

2022-01-06 Thread Rich
https://www.dropbox.com/s/k117zefr83k6b11/ppc64%20bt.png?dl=0 is the backtrace gdb reports from that core, helpful as it is. I actually originally had this happen on qemu 5.2, then I upgraded to 6.1 to see if it went away (it does not, and it happily reproduces on fresh upgrade each time). -

Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes

2022-01-06 Thread John Paul Adrian Glaubitz
Hello! On 1/6/22 09:13, Aurelien Jarno wrote: >> (I marked this as serious because it's "just" ppc64, but the system is >> permaneantly unusable if this upgrade is installed.) > > I have added the powerpc list in Cc: as the ppc64 porters are the people > who can help you there. > >> I booted my

Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes

2022-01-06 Thread Rich
Hi Aurelien, It's a VM running in qemu on an amd64 Debian bullseye system, no KVM acceleration to be found here. dmesg doesn't have any backtraces - the two messages that show up are py3compile segfaulting with all the addresses printed as instead, and a couple of programs (like mandb)

Processed (with 2 errors): Re: Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes

2022-01-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + help Bug #1003201 [libc6] libc6: Upgrading to libc 2.33-1 causes lots of strange crashes Added tag(s) help. > user debian-powe...@lists.debian.org Unknown command or malformed arguments to command. > usertag -1 ppc64 Unknown command or malformed arguments

Bug#1003201: libc6: Upgrading to libc 2.33-1 causes lots of strange crashes

2022-01-06 Thread Aurelien Jarno
control: tag -1 + help control: user debian-powe...@lists.debian.org control: usertag -1 ppc64 On 2022-01-06 01:45, Rich Ercolani wrote: > Package: libc6 > Version: 2.33-1 > Severity: important > X-Debbugs-Cc: rincebr...@gmail.com > > Dear Maintainer, > > (I marked this as serious because it's