tzdata_2020b-0+deb10u1_source.changes ACCEPTED into proposed-updates->stable-new
Mapping buster to stable. Mapping stable to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 11 Oct 2020 15:36:25 +0200 Source: tzdata Architecture: source Version: 2020b-0+deb10u1 Distribution: buster Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Changes: tzdata (2020b-0+deb10u1) buster; urgency=medium . * New upstream version, affecting the following past and future timestamps: - Revised predictions for Morocco's changes starting in 2023. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. * Restore the pacificnew and systemv files that have been removed upstream. The corresponding timezones have been removed from the bullseye/sid package, with the switch to the new names handle by the maintainer scripts. However we do not want to transition to the new names in a stable release. * Update debian/upstream/signing-key.asc. Checksums-Sha1: 0e9ca510a59fbe9c7ef2b2353c35a3884eedeb63 2264 tzdata_2020b-0+deb10u1.dsc 89f5295b0bdbc8315f97fd8f7f5ed035f238a1e7 400017 tzdata_2020b.orig.tar.gz c9327c81eecf9d2804902bfac4d1d8f70ba82941 833 tzdata_2020b.orig.tar.gz.asc ab8475d95793eba962c6d1121a26d1be1ff823db 106144 tzdata_2020b-0+deb10u1.debian.tar.xz d14b33e91309c59f5cbb9d877757052930bfbe3a 5156 tzdata_2020b-0+deb10u1_source.buildinfo Checksums-Sha256: 5cccba401fea5768afff28dcd423a7f7b08ea525c51e3ab03029dd3529ebacf6 2264 tzdata_2020b-0+deb10u1.dsc 9b053f951d245ce89d850b96ee4711d82d833559b1fc96ba19f90bc4d745e809 400017 tzdata_2020b.orig.tar.gz 2e9e0492e556500d9f6d33b4290667d53d85af37f14929371f56c147354157ce 833 tzdata_2020b.orig.tar.gz.asc 071756485a2a549ef9130cfd1f7a79f28d163bd254f5b2ea5ce593745c90 106144 tzdata_2020b-0+deb10u1.debian.tar.xz bd4af4dc6fa44c703a03d47687bbf1505d6b35bd63a3d8bb23dea602cd88d150 5156 tzdata_2020b-0+deb10u1_source.buildinfo Files: 630ec22f7bcdb81b4d1204037a59da76 2264 localization required tzdata_2020b-0+deb10u1.dsc 8902c580f7042c0ce94a6b05b0798ec9 400017 localization required tzdata_2020b.orig.tar.gz 17ec06854d8f0e7ac4ea9e3a1c192733 833 localization required tzdata_2020b.orig.tar.gz.asc 662139fbd96f6389d02290f0b1d6ee50 106144 localization required tzdata_2020b-0+deb10u1.debian.tar.xz 78768a8913374e9048f46839494f3b06 5156 localization required tzdata_2020b-0+deb10u1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl+DDFAACgkQE4jA+Jno M2tKhA/9FZBDHArWo7OedyDwrDRqdBlEt1UA+K+Q5OT9NO7r30MfWZK7wK32cw3d o8B8tcEJQM8QQwcV0D3l+J/xkTk3D/r0BTmViFCyVkJAnOwb2rx6QhJyiMBieffy CLLOonjvv5Qo/KYqYNr1N4u/HXvgWo3+3c9pYVcovl4EVso5dapgg1ymgE3zX+Yy xU8Akt4CSDYXFJNtU4J6Iazcw2kYRSz5LVAJZPLxsy0rarT362mzHJqhdOujIpdX 3U6p154hMRemC/nXeKnmCOzp8keBi2rIgDMJ9F3jw2Tj1WbAvGANa9Romboml+96 ScenGmu04D5fkUsNwfhmzC2MLStDU0AGhlrBWnJRZbcANdSGut+Q/6hlWqIreW3B mGf00OhOM56is3SPj71PnW0xW3QUv2HnKwweHzc4WG6bJz28fYmPlrY/cuWFkho6 K0N21UDPvpdvkaXwr/shdmCI0S/t2D9KxhjN1HqD13udzP5LvU9AXMCGzDs2mRBU uMTFltKbElS5ZfZac9d15IHsB/LZNPpP0YzUPl8WqXkqbf+yL5o3h8EPXtxbkif4 wJaj9ELKY/gRQXSptATDhvq8l7e2eeNbX7KZW3Lr+Mu7CB8bMBtl6EJ+86AG00V9 OUnvsULX+z0M3WFZ/1Fy4n3wVIaLWbfYQzQyT5nNYsmFSR3+Xic= =brD6 -END PGP SIGNATURE- Thank you for your contribution to Debian.
[Git][glibc-team/glibc][sid] hurd: Add support for clock_gettime(CPUTIME)
Samuel Thibault pushed to branch sid at GNU Libc Maintainers / glibc Commits: 813a0006 by Samuel Thibault at 2020-10-11T16:06:10+02:00 hurd: Add support for clock_gettime(CPUTIME) * debian/patches/hurd-i386/git-clock-cputime.diff: New patch to support clock_gettime(CPUTIME). * debian/patches/hurd-i386/local-clock_gettime_MONOTONIC.diff: Refresh. * debian/patches/hurd-i386/local-posix_cputime.diff: Remove. - - - - - 5 changed files: - debian/changelog - + debian/patches/hurd-i386/git-clock-cputime.diff - debian/patches/hurd-i386/local-clock_gettime_MONOTONIC.diff - − debian/patches/hurd-i386/local-posix_cputime.diff - debian/patches/series View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/813a00066cc7c2a2c55e9df54e1777d4e76822a1 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/813a00066cc7c2a2c55e9df54e1777d4e76822a1 You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/glibc] Pushed new branch disable-obsolete-rpc
Aurelien Jarno pushed new branch disable-obsolete-rpc at GNU Libc Maintainers / glibc -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/tree/disable-obsolete-rpc You're receiving this email because of your account on salsa.debian.org.
Bug#971537: Impossible to run /sbin/ldconfig on buster using qemu-i386-static
control: reassign -1 qemu-user-static control: found -1 qemu-user-static/1:3.1+dfsg-8 control: fixed -1 qemu-user-static/1:5.0-1 control: affect -1 libc-bin Hi, On 2020-10-01 18:11, Rudra Saraswat wrote: > Package: libc-bin > Version: 2.28-10 > > It impossible to run /sbin/ldconfig using qemu-i386-static (debootstrap > --foreign chroot) on a Raspberry Pi 4B with libc-bin at 2.28-10 (on Debian > Buster in the debootstrap chroot). However, it does work on a stretch > debootstrap chroot, without any errors. > > Here is the error encountered with Buster: > > qemu: uncaught target signal 11 (Segmentation fault) - core dumped This is an issue that is not specific to the Raspberry Pi 4B or even arm64, but can be reproduced on amd64. It affects all 32-bit emulated target when running PIE binaries. This has been fixed in qemu 5.0 by the following upstream commit: https://git.qemu.org/?p=qemu.git;a=commit;h=6fd5944980f4ccee728ce34bdaffc117db50b34d > Multiple people have faced this issue, which is why I'm reporting it as a > bug. > > On all setups, Debian Buster/Raspbian Buster is used as the operating > system. This is definitely not a glibc bug. I am therefore reassigning the bug to QEMU. Note that you might fix the issue by installing a recent version of qemu-user-static in your chroot. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Processed: Re: Bug#971537: Impossible to run /sbin/ldconfig on buster using qemu-i386-static
Processing control commands: > reassign -1 qemu-user-static Bug #971537 [libc-bin] Impossible to run /sbin/ldconfig on buster using qemu-i386-static Bug reassigned from package 'libc-bin' to 'qemu-user-static'. No longer marked as found in versions glibc/2.28-10. Ignoring request to alter fixed versions of bug #971537 to the same values previously set > found -1 qemu-user-static/1:3.1+dfsg-8 Bug #971537 [qemu-user-static] Impossible to run /sbin/ldconfig on buster using qemu-i386-static The source qemu-user-static and version 1:3.1+dfsg-8 do not appear to match any binary packages Marked as found in versions qemu-user-static/1:3.1+dfsg-8. > fixed -1 qemu-user-static/1:5.0-1 Bug #971537 [qemu-user-static] Impossible to run /sbin/ldconfig on buster using qemu-i386-static The source qemu-user-static and version 1:5.0-1 do not appear to match any binary packages Marked as fixed in versions qemu-user-static/1:5.0-1. > affect -1 libc-bin Bug #971537 [qemu-user-static] Impossible to run /sbin/ldconfig on buster using qemu-i386-static Added indication that 971537 affects libc-bin -- 971537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971537 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of tzdata_2020b-0+deb10u1_source.changes
tzdata_2020b-0+deb10u1_source.changes uploaded successfully to localhost along with the files: tzdata_2020b-0+deb10u1.dsc tzdata_2020b.orig.tar.gz tzdata_2020b.orig.tar.gz.asc tzdata_2020b-0+deb10u1.debian.tar.xz tzdata_2020b-0+deb10u1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#972001: buster-pu: package tzdata/2020b-0+deb10u1
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: debian-glibc@lists.debian.org Dear stable release team, I've uploaded tzdata/2020b-0+deb10u1 to buster. There is no urgency to get it through stable-updates and it can wait for the next stable point release. Here is the corresponding changelog: tzdata (2020b-0+deb10u1) buster; urgency=medium * New upstream version, affecting the following past and future timestamps: - Revised predictions for Morocco's changes starting in 2023. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. * Restore the pacificnew and systemv files that have been removed upstream. The corresponding timezones have been removed from the bullseye/sid package, with the switch to the new names handle by the maintainer scripts. However we do not want to transition to the new names in a stable release. * Update debian/upstream/signing-key.asc. -- Aurelien Jarno Sun, 11 Oct 2020 15:36:25 +0200 Thanks for considering. Regards, Aurelien
[Git][glibc-team/tzdata][buster] releasing package tzdata version 2020b-0+deb10u1
Aurelien Jarno pushed to branch buster at GNU Libc Maintainers / tzdata Commits: d201851e by Aurelien Jarno at 2020-10-11T15:36:31+02:00 releasing package tzdata version 2020b-0+deb10u1 - - - - - 1 changed file: - debian/changelog View it on GitLab: https://salsa.debian.org/glibc-team/tzdata/-/commit/d201851ef752a6b42901d68eabf187f64cbd6453 -- View it on GitLab: https://salsa.debian.org/glibc-team/tzdata/-/commit/d201851ef752a6b42901d68eabf187f64cbd6453 You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/tzdata] Pushed new tag debian/2020b-0+deb10u1
Aurelien Jarno pushed new tag debian/2020b-0+deb10u1 at GNU Libc Maintainers / tzdata -- View it on GitLab: https://salsa.debian.org/glibc-team/tzdata/-/tree/debian/2020b-0+deb10u1 You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/tzdata][buster] 3 commits: New upstream version, affecting the following past and future timestamps:
Aurelien Jarno pushed to branch buster at GNU Libc Maintainers / tzdata Commits: 686dcbf6 by Aurelien Jarno at 2020-10-11T15:17:42+02:00 New upstream version, affecting the following past and future timestamps: * New upstream version, affecting the following past and future timestamps: - Revised predictions for Morocco's changes starting in 2023. - Macquarie Island has stayed in sync with Tasmania since 2011. - Casey, Antarctica is at +08 in winter and +11 in summer since 2018. - - - - - 4e40dc39 by Aurelien Jarno at 2020-10-11T15:32:05+02:00 Restore the pacificnew and systemv files that have been removed upstream. The corresponding timezones have been removed from the bullseye/sid package, with the switch to the new names handle by the maintainer scripts. However we do not want to transition to the new names in a stable release. - - - - - 70a0e92d by Aurelien Jarno at 2020-10-11T15:32:05+02:00 Update debian/upstream/signing-key.asc. - - - - - 5 changed files: - debian/changelog - + debian/patches/pacificnew.diff - debian/patches/series - debian/patches/systemv.diff - debian/upstream/signing-key.asc View it on GitLab: https://salsa.debian.org/glibc-team/tzdata/-/compare/6f8a93bb28555910a1bbc27560eae59e0d6e110b...70a0e92d673e9eaf298d95d6f7bcbb3a27312eab -- View it on GitLab: https://salsa.debian.org/glibc-team/tzdata/-/compare/6f8a93bb28555910a1bbc27560eae59e0d6e110b...70a0e92d673e9eaf298d95d6f7bcbb3a27312eab You're receiving this email because of your account on salsa.debian.org.
Bug#969618: marked as done (getopt: optarg is NULL outside of loop)
Your message dated Sun, 11 Oct 2020 13:11:57 +0200
with message-id <2020101157.ga1454...@aurel32.net>
and subject line Re: Bug#969618: getopt: optarg is NULL outside of loop
has caused the Debian Bug report #969618,
regarding getopt: optarg is NULL outside of loop
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
969618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.31-3
Severity: normal
X-Debbugs-Cc:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I suspect this is an upstream problem but I'm reporting it here
first per their policy [1] since I'm unsure.
Both POSIX (including the Issue 8 draft) and the GNU C Library
manual say that when an argument is provided for an option, a
pointer to it is provided as optarg.
It seems like after leaving the while() loop getopt is usually
used in, optarg points to NULL instead, even if no other options,
bearing arguments or not, are used. It's a little grey but POSIX
doesn't seem to permit this, and the (non-DFSG) glibc manual could
be construed as saying it should work fine this way:
> If the option has an argument, getopt returns the argument by storing
> it in the variable optarg. You don’t ordinarily need to copy the optarg
> string, since it is a pointer into the original argv array, not into a
> static area that might be overwritten.
Everything works fine with Musl libc which can be tried with musl-gcc.
Consider this example program:
#define _POSIX_C_SOURCE 200809L
#include
#include
#include
#include
int main(int argc, char *argv[]) {
int opt;
while((opt = getopt(argc, argv, "a:")) != -1) {}
assert(optarg != NULL);
}
If this is invoked as './a.out -afoo', the inner assertion will
the last assertion will fail with glibc. In the absence of
a compelling reason (such as if I were using the GNU extension of
having an optional argument via '::'), standards aside, it would
be helpful for me if the variable could be left alone.
[1] https://sourceware.org/glibc/wiki/FilingBugs
[2] https://www.gnu.org/software/libc/manual/html_node/Using-Getopt.html
- -- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (2, 'unstable'), (1, 'testing-debug'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.7.0-3-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libc6 depends on:
ii libcrypt1 1:4.4.17-1
ii libgcc-s1 10.2.0-5
Versions of packages libc6 recommends:
ii libidn2-0 2.3.0-1
Versions of packages libc6 suggests:
ii debconf [debconf-2.0] 1.5.74
ii glibc-doc 2.31-3
ii libc-l10n 2.31-3
ii locales2.31-3
- -- debconf information:
glibc/restart-failed:
glibc/upgrade: true
glibc/kernel-too-old:
glibc/kernel-not-supported:
* libraries/restart-without-asking: true
glibc/disable-screensaver:
glibc/restart-services:
-BEGIN PGP SIGNATURE-
iHUEARYIAB0WIQT287WtmxUhmhucNnhyvHFIwKstpwUCX1Q6TgAKCRByvHFIwKst
p+D0AQDqLFwxGh/oTV+13E5stB3WvG9zD0tpMiol/xHW0QuERgEAsPKsGbQBW2nG
VFzkfExA5cGyGj0GW7IyKg42+wLaZgI=
=WQf5
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
On 2020-09-06 21:47, Aurelien Jarno wrote:
> Hi,
>
> On 2020-09-06 09:25, Florian Weimer wrote:
> > * John Scott:
> >
> > > #define _POSIX_C_SOURCE 200809L
> > > #include
> > > #include
> > > #include
> > > #include
> > > int main(int argc, char *argv[]) {
> > > int opt;
> > > while((opt = getopt(argc, argv, "a:")) != -1) {}
> > > assert(optarg != NULL);
> > > }
> > >
> > > If this is invoked as './a.out -afoo', the inner assertion will
> > > the last assertion will fail with glibc.
> >
> > POSIX leaves it unspecified if optarg is changed if getopt returns -1.
> > Only optind must be left unchanged. I do not think this is a glibc
> > bug (or a musl bug).
>
> Thanks Florian for the explanations. This can be confirmed that optarg
> is not NULL by moving the assert in the while loop. So it doesn't seems
> like a bug to me.
I am therefore closing it.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net--- End Message ---
[Git][glibc-team/rpcsvc-proto][master] Add bug number
Aurelien Jarno pushed to branch master at GNU Libc Maintainers / rpcsvc-proto Commits: c758a791 by Aurelien Jarno at 2020-10-11T13:00:29+02:00 Add bug number - - - - - 1 changed file: - debian/changelog View it on GitLab: https://salsa.debian.org/glibc-team/rpcsvc-proto/-/commit/c758a791232db522f894f2aa9bb828746a8a1624 -- View it on GitLab: https://salsa.debian.org/glibc-team/rpcsvc-proto/-/commit/c758a791232db522f894f2aa9bb828746a8a1624 You're receiving this email because of your account on salsa.debian.org.
Bug#971990: ITP: rpcsvc-proto -- RPC protocol compiler and definitions
Package: wnpp Severity: wishlist Owner: Aurelien Jarno X-Debbugs-Cc: debian-de...@lists.debian.org, debian-glibc@lists.debian.org * Package name: rpcsvc-proto Version : 1.4.2 Upstream Author : Thorsten Kukuk * URL : https://github.com/thkukuk/rpcsvc-proto * License : BSD-3-clause Programming Lang: C Description : RPC protocol compiler and definitions rpcgen is a tool that generates C code to implement an RPC protocol. The input to rpcgen is a language similar to C known as RPC Language (Remote Procedure Call Language). This package also includes several rpcsvc header files and RPC protocol definitions from SunRPC sources that were previously shipped by glibc. The glibc SunRPC implementation has been removed in glibc version 2.32. It is replaced by rpcsvc-proto and libtirpc, which also brings new features (IPv6, Kerberos support, etc.). This package will be maintained within the glibc team.
