Paul Gevers wrote:
> As part of the interim architecture qualification for bullseye, we
> request that DSA, the security team, Wanna build, and the toolchain
> maintainers review and update their list of known concerns for bullseye
> release architectures.
There's nothing really of concern from
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 13 Jul 2020 21:34:17 +0200
Source: glibc
Architecture: source
Version: 2.31-1
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers
Changed-By: Aurelien Jarno
Closes: 964141
Changes:
glibc
glibc_2.31-1_source.changes uploaded successfully to localhost
along with the files:
glibc_2.31-1.dsc
glibc_2.31-1.debian.tar.xz
glibc_2.31-1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Mon, 13 Jul 2020 19:49:11 +
with message-id
and subject line Bug#964141: fixed in glibc 2.31-1
has caused the Debian Bug report #964141,
regarding libc6: "cannot allocate memory in static TLS block" with some library
combinations on arm64
to be marked as done.
This means
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc
Commits:
2283c1ee by Aurelien Jarno at 2020-07-13T21:34:13+02:00
debian/control.in/main: update breaks on cross-toolchain-base* as they will
need changes to build with glibc 2.31.
- - - - -
b26cf134 by Aurelien Jarno at
Aurelien Jarno pushed new tag debian/2.31-1 at GNU Libc Maintainers / glibc
--
View it on GitLab:
https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.31-1
You're receiving this email because of your account on salsa.debian.org.
Processing control commands:
> tag -1 pending
Bug #964141 [libc6] libc6: "cannot allocate memory in static TLS block" with
some library combinations on arm64
Ignoring request to alter tags of bug #964141 to the same tags previously set
--
964141:
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc
Commits:
d3c5f0d5 by Aurelien Jarno at 2020-02-08T18:22:56+01:00
New upstream release:
* New upstream release:
- Adds GNU hash support on MIPS (closes: #943538).
- debian/symbols.wildcard: add 2.31.
-
Processing control commands:
> tag -1 pending
Bug #964141 [libc6] libc6: "cannot allocate memory in static TLS block" with
some library combinations on arm64
Added tag(s) pending.
--
964141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964141
Debian Bug Tracking System
Contact
Aurelien Jarno pushed to branch glibc-2.31 at GNU Libc Maintainers / glibc
Commits:
a7549bfa by Aurelien Jarno at 2020-07-12T23:45:20+02:00
debian/patches/any/git-surplus-tls-accounting.diff: backport TLS surplus
accounting from upstream. Closes: #964141.
- - - - -
3 changed files:
-
Control: tags -1 + fixed-upstream
On Fri, Jul 03, 2020 at 03:57:36PM +0200, Gianfranco Costamagna wrote:
> control: tags -1 patch
>
> Hello, the patch (v5) applied on top of 2.31 (build-tested in Ubuntu)
> seems to solve the issue
Thanks for testing it!
Dear glibc maintainers: the patchset was
Processing control commands:
> tags -1 + fixed-upstream
Bug #964141 [libc6] libc6: "cannot allocate memory in static TLS block" with
some library combinations on arm64
Added tag(s) fixed-upstream.
--
964141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964141
Debian Bug Tracking System
Your message dated Mon, 13 Jul 2020 12:13:22 +0200
with message-id <20200713101322.ge8...@aurel32.net>
and subject line Re: Bug#964948: tzdata: The leap-seconds.list file is expired
has caused the Debian Bug report #964948,
regarding tzdata: The leap-seconds.list file is expired
to be marked as
Package: tzdata
Version: 2019c-0+deb9u1
Severity: normal
Dear Maintainer,
It appears the leap-seconds.list file of tzdata in debian stable is now expired.
This is a potential issue if new leap seconds are introduced, and thus, as far
as I understand, deserve an upgrade even in debian oldstable.
14 matches
Mail list logo