Processed: [bts-link] source package glibc

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package glibc > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting

[bts-link] source package glibc

# # bts-link upstream status pull for source package glibc # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #874160 (http://bugs.debian.org/874160) #

[Git][glibc-team/glibc][glibc-2.34] 2 commits: debian/testsuite-xfail-debian.mk: whitelist again test-xfail-tst-pkey on...

Aurelien Jarno pushed to branch glibc-2.34 at GNU Libc Maintainers / glibc Commits: 01351dd9 by Aurelien Jarno at 2021-12-20T21:37:35+01:00 debian/testsuite-xfail-debian.mk: whitelist again test-xfail-tst-pkey on powerpc, as 32-bit protection key support on powerpc is unclear. - - - - -

Bug#1002041: glibc: rc

Source: glibc Version: 2.34-0experimental2 Severity: normal Dear Maintainer, There are two new regressions in glibc 2.34 that need to be xfailed on hppa: +-+ | Encountered regressions that don't match expected failures.

Bug#1001774: tm_isdst=1 with mktime produces unexpected output

On 2021-12-20 09:06, Daniel McDonald wrote: > Dear Aurelian, > > I can confirm that changing the timezone within Ubuntu 20.04 through Github > Actions resolves the bug. The default set timezone is “Etc/UTC” as reported > by “timedatectl”. Setting to “America/Los_Angeles” with “timedatectl”

Processed: Bug#1002041 marked as pending in glibc

Processing control commands: > tag -1 pending Bug #1002041 [src:glibc] glibc: rc Added tag(s) pending. -- 1002041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems