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
[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. - - - - - 498e8d11 by Aurelien Jarno at 2021-12-20T21:40:34+01:00 debian/testsuite-xfail-debian.mk: whitelist dirent/tst-readdir64-compat and signal/tst-minsigstksz-5. Closes: #1002041. - - - - - 2 changed files: - debian/changelog - debian/testsuite-xfail-debian.mk View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/compare/42770b2d9500403d344045d4f06531ac8ad090ca...498e8d11b42743d3d305869c80b31fb0a2dffbb3 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/compare/42770b2d9500403d344045d4f06531ac8ad090ca...498e8d11b42743d3d305869c80b31fb0a2dffbb3 You're receiving this email because of your account on salsa.debian.org.
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” allows > for a passing workflow. A link to the pass, with contextual information, can > be found here (note, this is under a fork of CPython where this behavior was > being investigated): > > https://github.com/wasade/cpython/runs/4584894670?check_suite_focus=true#step:17:76 > > While this is reassuring, it seems the behavior is qualitatively different > across operating systems (or glibc versions). I’m unsure if that is expected. > As an example, we pass on Ubuntu 18.04 without changing the timezone: > > https://github.com/wasade/cpython/runs/4585124128?check_suite_focus=true#step:14:43 Ubuntu 18.04 seems to run glibc 2.27. Versions of glibc older than 2.29 are affected by bug #23789 [1], and do not report any error if the date is not representable. This is arguably a bug in Ubuntu 18.04, but this behaviour is expected. Regards, Aurelien [1] https://sourceware.org/bugzilla/show_bug.cgi?id=23789 -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
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. | +-+ FAIL: dirent/tst-readdir64-compat FAIL: signal/tst-minsigstksz-5 touch /<>/stamp-dir/check_libc CHECK SUMMARY check for check_libc failed make: *** [debian/rules.d/build.mk:187: build-arch-post-check] Error 1 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 The dirent/tst-readdir64-compat failure is libc/27654. This is apparently a test issue. The signal/tst-minsigstksz-5 failure is a known issue with the signal trampoline which should be fixed when the kernel implements a vdso: https://www.spinics.net/lists/linux-parisc/msg15397.html Regards, Dave Anglin -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 5.14.21+ (SMP w/4 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
[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) # Bug title: src:glibc: default locale to C.UTF-8 # * http://sourceware.org/bugzilla/show_bug.cgi?id=17318 # * remote status changed: NEW -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 874160 + fixed-upstream usertags 874160 - status-NEW usertags 874160 + status-RESOLVED resolution-FIXED # remote status report for #874160 (http://bugs.debian.org/874160) # Bug title: src:glibc: default locale to C.UTF-8 # * http://sourceware.org/bugzilla/show_bug.cgi?id=17318 # * remote status changed: NEW -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 874160 + fixed-upstream usertags 874160 - status-NEW usertags 874160 + status-RESOLVED resolution-FIXED # remote status report for #874160 (http://bugs.debian.org/874160) # Bug title: src:glibc: default locale to C.UTF-8 # * http://sourceware.org/bugzilla/show_bug.cgi?id=17318 # * remote status changed: NEW -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 874160 + fixed-upstream usertags 874160 - status-NEW usertags 874160 + status-RESOLVED resolution-FIXED thanks
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 user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #874160 (http://bugs.debian.org/874160) > # Bug title: src:glibc: default locale to C.UTF-8 > # * http://sourceware.org/bugzilla/show_bug.cgi?id=17318 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 874160 + fixed-upstream Bug #874160 [libc6] src:glibc: default locale to C.UTF-8 Bug #719590 [libc6] Provide a C.UTF-8 locale by default Bug #748215 [libc6] Provide a C.UTF-8 locale by default Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > usertags 874160 - status-NEW Usertags were: status-NEW. There are now no usertags set. > usertags 874160 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. > # remote status report for #874160 (http://bugs.debian.org/874160) > # Bug title: src:glibc: default locale to C.UTF-8 > # * http://sourceware.org/bugzilla/show_bug.cgi?id=17318 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 874160 + fixed-upstream Bug #874160 [libc6] src:glibc: default locale to C.UTF-8 Bug #719590 [libc6] Provide a C.UTF-8 locale by default Bug #748215 [libc6] Provide a C.UTF-8 locale by default Ignoring request to alter tags of bug #874160 to the same tags previously set Ignoring request to alter tags of bug #719590 to the same tags previously set Ignoring request to alter tags of bug #748215 to the same tags previously set > usertags 874160 - status-NEW Usertags were: status-RESOLVED resolution-FIXED. Usertags are now: status-RESOLVED resolution-FIXED. > usertags 874160 + status-RESOLVED resolution-FIXED Usertags were: status-RESOLVED resolution-FIXED. Usertags are now: status-RESOLVED resolution-FIXED. > # remote status report for #874160 (http://bugs.debian.org/874160) > # Bug title: src:glibc: default locale to C.UTF-8 > # * http://sourceware.org/bugzilla/show_bug.cgi?id=17318 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 874160 + fixed-upstream Bug #874160 [libc6] src:glibc: default locale to C.UTF-8 Bug #719590 [libc6] Provide a C.UTF-8 locale by default Bug #748215 [libc6] Provide a C.UTF-8 locale by default Ignoring request to alter tags of bug #874160 to the same tags previously set Ignoring request to alter tags of bug #719590 to the same tags previously set Ignoring request to alter tags of bug #748215 to the same tags previously set > usertags 874160 - status-NEW Usertags were: status-RESOLVED resolution-FIXED. Usertags are now: status-RESOLVED resolution-FIXED. > usertags 874160 + status-RESOLVED resolution-FIXED Usertags were: status-RESOLVED resolution-FIXED. Usertags are now: status-RESOLVED resolution-FIXED. > thanks Stopping processing here. Please contact me if you need assistance. -- 719590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719590 748215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748215 874160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems