Processed: Re: Bug#939898: fixed in nftables 0.9.2-2

2019-10-10 Thread Debian Bug Tracking System
Processing control commands:

> notfixed -1 nftables/0.9.2-2
Bug #939898 {Done: Arturo Borrero Gonzalez } [src:glibc] 
glibc: new getegid, geteuid and getppid syscalls used unconditionally on alpha
No longer marked as fixed in versions nftables/0.9.2-2.

-- 
939898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#939898: marked as done (glibc: new getegid, geteuid and getppid syscalls used unconditionally on alpha)

2019-10-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Oct 2019 18:04:35 +
with message-id 
and subject line Bug#939898: fixed in nftables 0.9.2-2
has caused the Debian Bug report #939898,
regarding glibc: new getegid, geteuid and getppid syscalls used unconditionally 
on alpha
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.)


-- 
939898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.29-1
Severity: important
User: debian-al...@lists.debian.org
Usertags: alpha

Hello!

Both on my Alpha XP-1000 as well as inside a qemu-user chroot, upgrading glibc
to version 2.29-1 resulted in setuid/getuid breaking in a weird way:

(sid-alpha-sbuild)root@epyc:/# apt -y upgrade  
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  bsd-mailx cron exim4-base exim4-config exim4-daemon-light groff-base 
libevent-2.1-6 libgnutls-dane0 liblockfile-bin liblockfile1 libpipeline1 
libreadline7 libtext-iconv-perl
  libuchardet0 libunbound8 man-db psmisc
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
  cpp g++ gcc libc-bin libc-dev-bin libc6.1 libc6.1-dev
7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 6329 kB/6355 kB of archives.
After this operation, 34.8 kB disk space will be freed.
Get:1 http://incoming.ports.debian.org/buildd unstable/main alpha libc6.1-dev 
alpha 2.29-1 [2586 kB]
Get:2 http://incoming.ports.debian.org/buildd unstable/main alpha libc-dev-bin 
alpha 2.29-1 [277 kB]
Get:3 http://incoming.ports.debian.org/buildd unstable/main alpha libc6.1 alpha 
2.29-1 [2677 kB]
Get:4 http://incoming.ports.debian.org/buildd unstable/main alpha libc-bin 
alpha 2.29-1 [788 kB]
Fetched 6329 kB in 3s (2509 kB/s) 
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = "en_US.UTF-8",
LC_CTYPE = "en_US.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
/usr/bin/locale: Cannot set LC_CTYPE to default locale: No such file or 
directory
/usr/bin/locale: Cannot set LC_MESSAGES to default locale: No such file or 
directory
/usr/bin/locale: Cannot set LC_ALL to default locale: No such file or directory
debconf: delaying package configuration, since apt-utils is not installed
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
(Reading database ... 13696 files and directories currently installed.)
Preparing to unpack .../libc6.1-dev_2.29-1_alpha.deb ...
Unpacking libc6.1-dev:alpha (2.29-1) over (2.28-4) ...
Preparing to unpack .../libc-dev-bin_2.29-1_alpha.deb ...
Unpacking libc-dev-bin (2.29-1) over (2.28-4) ...
Preparing to unpack .../libc6.1_2.29-1_alpha.deb ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
Unpacking libc6.1:alpha (2.29-1) over (2.28-4) ...
dpkg: error: requested operation requires superuser privilege
E: Sub-process /usr/bin/dpkg returned an error code (2)
(sid-alpha-sbuild)root@epyc:/#

After that, logging in through SSH no longer works. Running "dpkg --configure 
-a" always
results in the same error as shown above. Logging in through serial console 
aborts
immediately after typing the username, e.g. "root" and the login prompt is 
shown again.

Shortly after typing "root" and pressing enter, the following message is 
printed to the
console which seems to be an alpha-specific syscall:

[  195.414939] do_entUnaUser: 7 callbacks suppressed

I can fix the problem with the chroot, by simply downloading the 2.28-4 version 
of the
libc6.1 package and extracting it into the system root:

root@epyc:/local_scratch/sid-alpha-sbuild> wget 
http://snapshot.debian.org/archive/debian-ports/20190111T160151Z/pool-alpha/main/g/glibc/libc6.1_2.28-4_alpha.deb
--2019-09-09 22:55:02--  
http://snapshot.debian.org/archive/debian-ports/20190111T160151Z/pool-alpha/main/g/glibc/libc6.1_2.28-4_alpha.deb
Resolving snapshot.debian.org (snapshot.debian.org)... 193.62.202.27, 
185.17.185.185, 2001:630:206:4000:1a1a:0:c13e:ca1b, ...
Connecting to snapshot.debian.org

Processed: merging 403124 497525

2019-10-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> merge 403124 497525
Bug #403124 [libc6] fgetws chokes on input chars > 0x80 in C locale
Bug #403124 [libc6] fgetws chokes on input chars > 0x80 in C locale
Marked as found in versions glibc/2.3.6.ds1-13etch7.
Bug #497525 [libc6] libc6: fgetws treats C locale wrongly
Merged 403124 497525
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
403124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=403124
497525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#940852: marked as done (tzdata should install tzdata.zi file)

2019-09-28 Thread Debian Bug Tracking System
Your message dated Sat, 28 Sep 2019 23:21:16 +
with message-id 
and subject line Bug#940852: fixed in tzdata 2019c-2
has caused the Debian Bug report #940852,
regarding tzdata should install tzdata.zi file
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.)


-- 
940852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: tzdata
Version: 2019c-1

The upstream tzdata by default installs a file /usr/share/zoneinfo/tzdata.zi 
that contains version info along with the exact source used to generate the TZif 
binary files. This file was introduced in tzdb 2017c but apparently Debian 
hasn't picked it up yet. It is installed by Fedora, and I assume by other 
distributions. Please add it to Debian too. Proposed patch attached.
diff -pru src-1/debian/rules src-2/debian/rules
--- src-1/debian/rules	2019-09-11 14:01:07.0 -0700
+++ src-2/debian/rules	2019-09-20 13:19:23.657688442 -0700
@@ -47,6 +47,9 @@ override_dh_auto_build-indep:
 	# Generate a posixrules file
 	/usr/sbin/zic -d $(TZGEN) -p America/New_York

+	# Generate a tzdata.zi file
+	$(MAKE) VERSION_DEPS= tzdata.zi
+
 	# Replace hardlinks by symlinks
 	rdfind -outputname /dev/null -makesymlinks true -removeidentinode false $(TZGEN)
 	symlinks -r -s -c $(TZGEN)
diff -pru src-1/debian/tzdata.install src-2/debian/tzdata.install
--- src-1/debian/tzdata.install	2018-07-09 15:46:15.0 -0700
+++ src-2/debian/tzdata.install	2019-09-20 13:16:09.977451131 -0700
@@ -1,6 +1,7 @@
 debian/tzconfig /usr/sbin
 tzgen/* usr/share/zoneinfo/
 iso3166.tab usr/share/zoneinfo/
+tzdata.zi usr/share/zoneinfo/
 zone.tab usr/share/zoneinfo/
 zone1970.tab usr/share/zoneinfo/
 leap-seconds.list usr/share/zoneinfo/
--- End Message ---
--- Begin Message ---
Source: tzdata
Source-Version: 2019c-2

We believe that the bug you reported is fixed in the latest version of
tzdata, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 940...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated tzdata package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 29 Sep 2019 00:56:50 +0200
Source: tzdata
Architecture: source
Version: 2019c-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 940852
Changes:
 tzdata (2019c-2) unstable; urgency=medium
 .
   [ Paul Eggert ]
   * Install tzdata.zi file in /usr/share/zoneinfo.  Closes: #940852.
 .
   [ Aurelien Jarno ]
   * Use tzdata.zi to change hardlinks into symlinks.
   * Bump debhelper compatibility to 12.
   * Bump Standards-Version to 4.4.0 (no changes).
   * Drop Replaces on libc6, it is not needed anymore since Lenny.
   * Depends on gawk and use it instead of mawk which crashes with a memory
 corruption.
Checksums-Sha1:
 4a947ba08f193167cd6f1ce8d1e99aaed691709e 2237 tzdata_2019c-2.dsc
 512b97c2e86d258142cbb00c0b93b9361768f5a2 105048 tzdata_2019c-2.debian.tar.xz
 3ef3b9df462d6f7c20b34be78c8fb292824cdd55 5207 tzdata_2019c-2_source.buildinfo
Checksums-Sha256:
 ce1f585933eab45d1eedb964220519127fa0170406f633e08bd12120d164ef0d 2237 
tzdata_2019c-2.dsc
 d400e81ab0b91ccd28d5ad020a9283e8c75d76b995f1c5d7af3227946425bd26 105048 
tzdata_2019c-2.debian.tar.xz
 b0ab0c7569f5d9c89a8ad2a84d75b3ef6d2377a581612ee4b0e6e8dba79ed512 5207 
tzdata_2019c-2_source.buildinfo
Files:
 7effb0bcc0e161ceb6f3e80d70c0de5f 2237 localization required tzdata_2019c-2.dsc
 e16f7905066eb58da0ccfafb87cb6281 105048 localization required 
tzdata_2019c-2.debian.tar.xz
 fb2e7848de687305d13b60a7fcafd863 5207 localization required 
tzdata_2019c-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl2P5WAACgkQE4jA+Jno
M2tEcQ/8CNPq51YjLBpU9hBFeiszJ32S3Y5IshCJI91hU/L4E1r4/pwess3WAvwn
sPbJl70uJq9nEy6QFf9Ac1yZAKM0HSiV+g/VNmgm7iS65RZ/3cOF4c1/8GbJhO4D
v3u5nj7+MKEkmqXtsH4WNIAeaf3rANxR52tFxqOHVGqQIy3K4O8MNbUGE8FxbYq6
6Xt1Ly71XGFdSipl7YHHbW73Ulft3LyhQg6n1fo3/EaVAe8sMa9SVIvg3W3T+ECi
EuMx9zaqRti/uIAeNVZTe65gOlt7KWW0cPSFQ2qXChSBHAv6vy9SGZOECFGc7+Hd
nVkpMm2LzSRGl2Lqsuu1OYBHtvlnvrP6BR6a

Processed: Bug#940852 marked as pending in tzdata

2019-09-28 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #940852 [tzdata] tzdata should install tzdata.zi file
Added tag(s) pending.

-- 
940852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: bug 941174 is forwarded to https://sourceware.org/bugzilla/show_bug.cgi?id=23296

2019-09-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 941174 https://sourceware.org/bugzilla/show_bug.cgi?id=23296
Bug #941174 [src:glibc] glibc: FTBFS on hppa - new test failures
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=23296'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
941174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#939898: marked as done (glibc: new getegid, geteuid and getppid syscalls used unconditionally on alpha)

2019-09-21 Thread Debian Bug Tracking System
Your message dated Sat, 21 Sep 2019 07:49:50 +
with message-id 
and subject line Bug#939898: fixed in glibc 2.29-2
has caused the Debian Bug report #939898,
regarding glibc: new getegid, geteuid and getppid syscalls used unconditionally 
on alpha
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.)


-- 
939898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.29-1
Severity: important
User: debian-al...@lists.debian.org
Usertags: alpha

Hello!

Both on my Alpha XP-1000 as well as inside a qemu-user chroot, upgrading glibc
to version 2.29-1 resulted in setuid/getuid breaking in a weird way:

(sid-alpha-sbuild)root@epyc:/# apt -y upgrade  
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  bsd-mailx cron exim4-base exim4-config exim4-daemon-light groff-base 
libevent-2.1-6 libgnutls-dane0 liblockfile-bin liblockfile1 libpipeline1 
libreadline7 libtext-iconv-perl
  libuchardet0 libunbound8 man-db psmisc
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
  cpp g++ gcc libc-bin libc-dev-bin libc6.1 libc6.1-dev
7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 6329 kB/6355 kB of archives.
After this operation, 34.8 kB disk space will be freed.
Get:1 http://incoming.ports.debian.org/buildd unstable/main alpha libc6.1-dev 
alpha 2.29-1 [2586 kB]
Get:2 http://incoming.ports.debian.org/buildd unstable/main alpha libc-dev-bin 
alpha 2.29-1 [277 kB]
Get:3 http://incoming.ports.debian.org/buildd unstable/main alpha libc6.1 alpha 
2.29-1 [2677 kB]
Get:4 http://incoming.ports.debian.org/buildd unstable/main alpha libc-bin 
alpha 2.29-1 [788 kB]
Fetched 6329 kB in 3s (2509 kB/s) 
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = "en_US.UTF-8",
LC_CTYPE = "en_US.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
/usr/bin/locale: Cannot set LC_CTYPE to default locale: No such file or 
directory
/usr/bin/locale: Cannot set LC_MESSAGES to default locale: No such file or 
directory
/usr/bin/locale: Cannot set LC_ALL to default locale: No such file or directory
debconf: delaying package configuration, since apt-utils is not installed
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
(Reading database ... 13696 files and directories currently installed.)
Preparing to unpack .../libc6.1-dev_2.29-1_alpha.deb ...
Unpacking libc6.1-dev:alpha (2.29-1) over (2.28-4) ...
Preparing to unpack .../libc-dev-bin_2.29-1_alpha.deb ...
Unpacking libc-dev-bin (2.29-1) over (2.28-4) ...
Preparing to unpack .../libc6.1_2.29-1_alpha.deb ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
debconf: falling back to frontend: Readline
Unpacking libc6.1:alpha (2.29-1) over (2.28-4) ...
dpkg: error: requested operation requires superuser privilege
E: Sub-process /usr/bin/dpkg returned an error code (2)
(sid-alpha-sbuild)root@epyc:/#

After that, logging in through SSH no longer works. Running "dpkg --configure 
-a" always
results in the same error as shown above. Logging in through serial console 
aborts
immediately after typing the username, e.g. "root" and the login prompt is 
shown again.

Shortly after typing "root" and pressing enter, the following message is 
printed to the
console which seems to be an alpha-specific syscall:

[  195.414939] do_entUnaUser: 7 callbacks suppressed

I can fix the problem with the chroot, by simply downloading the 2.28-4 version 
of the
libc6.1 package and extracting it into the system root:

root@epyc:/local_scratch/sid-alpha-sbuild> wget 
http://snapshot.debian.org/archive/debian-ports/20190111T160151Z/pool-alpha/main/g/glibc/libc6.1_2.28-4_alpha.deb
--2019-09-09 22:55:02--  
http://snapshot.debian.org/archive/debian-ports/20190111T160151Z/pool-alpha/main/g/glibc/libc6.1_2.28-4_alpha.deb
Resolving snapshot.debian.org (snapshot.debian.org)... 193.62.202.27, 
185.17.185.185, 2001:630:206:4000:1a1a:0:c13e:ca1b, ...
Connecting to snapshot.debian.org (snapsho

Bug#752527: marked as done (Upgrading libc6:i386 on amd64 restarts services)

2019-09-21 Thread Debian Bug Tracking System
Your message dated Sat, 21 Sep 2019 07:49:50 +
with message-id 
and subject line Bug#700472: fixed in glibc 2.29-2
has caused the Debian Bug report #700472,
regarding Upgrading libc6:i386 on amd64 restarts services
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.)


-- 
700472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.19-1
Severity: normal

The check for services affected by an upgrade does not consider the package
architecture. So it restarts the 64bit sshd for a 32bit libc upgrade. This
is uneccessarily disruptive to the system.

MfG
Goswin

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc6:i386 depends on:
ii  libgcc1  1:4.9.0-1

Versions of packages libc6:i386 recommends:
pn  libc6-i686  

Versions of packages libc6:i386 suggests:
ii  debconf [debconf-2.0]  1.5.53
pn  glibc-doc  
ii  locales2.19-1
ii  locales-all [locales]  2.19-1

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.29-2

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 700...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 20 Sep 2019 21:39:03 +0200
Source: glibc
Architecture: source
Version: 2.29-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 700472 939871 939898
Changes:
 glibc (2.29-2) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/control.in/main: drop the  profile from the
 python3:native build-depends.  Closes: #939871.
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix getegid, geteuid and getppid on alpha with < 5.1 kernels.
   Closes: #939898.
 .
   [ Sven Joachim ]
   * debian/script.in/nsscheck.sh: Do not restart services of different
 architecture than libc.  Closes: #700472.
 .
   [ Samuel Thibault ]
   * patches/hurd-i386/submitted-anon-mmap-shared.diff: Re-disable, actually
 makes some tests fail.
Checksums-Sha1:
 35b34de4e427dc22ba597e5b432fca121db50918 8735 glibc_2.29-2.dsc
 973296e15df00f4adead5d19cf3e5a9d8efad4c3 854928 glibc_2.29-2.debian.tar.xz
 938eb756e710ef792c59ab3e61aee1e20d69fc9b 7457 glibc_2.29-2_source.buildinfo
Checksums-Sha256:
 f510055121cba83afe31fa4ad3d447663ef5081bf4f06f20728ad731ba391168 8735 
glibc_2.29-2.dsc
 886b5638571863452b5861b1ec0b012a3e0c882b46f0094427123ed82d6577d5 854928 
glibc_2.29-2.debian.tar.xz
 e743cceef3988a1595e7b94f1a2393c4d56851d952da3f5359cdb85b9560ea2e 7457 
glibc_2.29-2_source.buildinfo
Files:
 9341cc28bbb9b1c6131097e80ada2442 8735 libs required glibc_2.29-2.dsc
 aa813ad47b772ced0bc18ac5a4cd2d1f 854928 libs required 
glibc_2.29-2.debian.tar.xz
 0dccbf7f2cb2a47684c263672a9aa575 7457 libs required 
glibc_2.29-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl2FLEgACgkQE4jA+Jno
M2tizQ/+L6W3GSSvW293bCjiG7tPwfuvNif9KnUQUr7QzsrKYPmV3gXiEez7G6t9
UccBVJ3c37LU3RxmWlHlqyMx0w3KC5lWLwD3uT47oKPHpKRxDnpKCEMjfDArF7+u
jbDkS02nR+FENSUat0Xc5oUO3yLfvi1uhFIZF34AuL68RhAcHV/l9mgwlPtCByZw
8CL6hTr4u9H63MAX4BOzTiKLjtNA14wvneR3RrCCkW4y7juCZ2WqrhuY6tu3/TNM
I6D7sAXxz8auyZTCZFTmhar7/AeyCCiiI0jLYgP8cjl8BHpllS6yf0LLzlimhrhN
D2ZCqJnt0a4rz5mxWztAt7V3YuRLMXXrfsTRgGalDUuULd1TqAMajcDfRgklX6fi
O6dHln5TDAQuYNEYiy3QG+PJExWo0Hj1moInOGniFbyfCOq8antwzz6q8S53e+Dg
mHaOi3QZvrq9YG/7FjerpUFnHRm4aV8ImdzBym+FwiMEdImof2r2aqog5gIb/04G
Urg/+f/D6Bg3MaBvY2Oy+4ixKv6aZfGaYZ//mKI5VcpQJBgjGI8fKC+pUyKbg/sa
XxyeRKurJYTqmGg0EkK32+zxkV447/6pM/u7Uq9EApm1sbK2ibPDiOm/cxy9ciQe
QVDAx6O3TIQKpmOfKWUQtTML6U/yiThtxR9

Bug#700472: marked as done (Upgrade of the foreign arch libc6 causes service restart)

2019-09-21 Thread Debian Bug Tracking System
Your message dated Sat, 21 Sep 2019 07:49:50 +
with message-id 
and subject line Bug#700472: fixed in glibc 2.29-2
has caused the Debian Bug report #700472,
regarding Upgrade of the foreign arch libc6 causes service restart
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.)


-- 
700472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.17-0experimental2
Severity: wishlist

Filing as wishlist, maybe it's minor or even worse for some people.

The postinst script of libc6 checks services that need to be restarted not
taking into account that those services may be of a different arch and so not
using the libc6 being upgraded. That also means when you upgrade both
libc6:amd64 and libc6:i386 you get double restart of all those services.



-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.8.0-rc3-wrar-1+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc6:i386 depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  libgcc11:4.7.2-5

Versions of packages libc6:i386 recommends:
pn  libc6-i686  

Versions of packages libc6:i386 suggests:
pn  glibc-doc  
ii  locales-all [locales]  2.17-0experimental2

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.29-2

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 700...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 20 Sep 2019 21:39:03 +0200
Source: glibc
Architecture: source
Version: 2.29-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 700472 939871 939898
Changes:
 glibc (2.29-2) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/control.in/main: drop the  profile from the
 python3:native build-depends.  Closes: #939871.
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix getegid, geteuid and getppid on alpha with < 5.1 kernels.
   Closes: #939898.
 .
   [ Sven Joachim ]
   * debian/script.in/nsscheck.sh: Do not restart services of different
 architecture than libc.  Closes: #700472.
 .
   [ Samuel Thibault ]
   * patches/hurd-i386/submitted-anon-mmap-shared.diff: Re-disable, actually
 makes some tests fail.
Checksums-Sha1:
 35b34de4e427dc22ba597e5b432fca121db50918 8735 glibc_2.29-2.dsc
 973296e15df00f4adead5d19cf3e5a9d8efad4c3 854928 glibc_2.29-2.debian.tar.xz
 938eb756e710ef792c59ab3e61aee1e20d69fc9b 7457 glibc_2.29-2_source.buildinfo
Checksums-Sha256:
 f510055121cba83afe31fa4ad3d447663ef5081bf4f06f20728ad731ba391168 8735 
glibc_2.29-2.dsc
 886b5638571863452b5861b1ec0b012a3e0c882b46f0094427123ed82d6577d5 854928 
glibc_2.29-2.debian.tar.xz
 e743cceef3988a1595e7b94f1a2393c4d56851d952da3f5359cdb85b9560ea2e 7457 
glibc_2.29-2_source.buildinfo
Files:
 9341cc28bbb9b1c6131097e80ada2442 8735 libs required glibc_2.29-2.dsc
 aa813ad47b772ced0bc18ac5a4cd2d1f 854928 libs required 
glibc_2.29-2.debian.tar.xz
 0dccbf7f2cb2a47684c263672a9aa575 7457 libs required 
glibc_2.29-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl2FLEgACgkQE4jA+Jno
M2tizQ/+L6W3GSSvW293bCjiG7tPwfuvNif9KnUQUr7QzsrKYPmV3gXiEez7G6t9
UccBVJ3c37LU3RxmWlHlqyMx0w3KC5lWLwD3uT47oKPHpKRxDnpKCEMjfDArF7+u
jbDkS02nR+FENSUat0Xc5oUO3yLfvi1uhFIZF34AuL68RhAcHV/l9mgwlPtCByZw
8CL6hTr4u9H63MAX4BOzTiKLjtNA14wvneR3RrCCkW4y7juCZ2WqrhuY6tu3/TNM
I6D7sAXxz8auyZTCZFTmhar7/AeyCCiiI0jLYgP8cjl8BHpllS6yf0LLzlimhrhN
D2ZCqJnt0a4rz5mxWztAt7V3YuRLMXXrfsTRgGalDUuULd1TqAMajcDfRgklX6fi
O6dHln5TDAQuYNEYiy3QG+PJExWo0Hj1moInOGniFbyfCOq8antwzz6q8S53e+Dg
mHaOi3QZvrq9YG/7FjerpUFnHRm4aV8Imdz

Bug#939871: marked as done (glibc: python3:native build dependency incorrectly marked as )

2019-09-21 Thread Debian Bug Tracking System
Your message dated Sat, 21 Sep 2019 07:49:50 +
with message-id 
and subject line Bug#939871: fixed in glibc 2.29-2
has caused the Debian Bug report #939871,
regarding glibc: python3:native build dependency incorrectly marked as 

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.)


-- 
939871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.29-1
Severity: normal

According to the INSTALL file, Python is now required to build glibc:

,
|* Python 3.4 or later
|
|  Python is required to build the GNU C Library.  As of release time,
|  Python 3.7.1 is the newest verified to work for building and
|  testing the GNU C Library.
`

Indeed, building with the nocheck profile in a python-less chroot fails:

,
| $ sbuild --no-arch-all --arch=i386 --profiles=nocheck
| [...]
| checking if i686-linux-gnu-gcc-9 is sufficient to build libc... yes
| checking for i686-linux-gnu-nm... i686-linux-gnu-nm
| checking for python3... no
| checking for python... no
| configure: error:
| *** These critical programs are missing or too old: python
| *** Check the INSTALL file for required versions.
| make: *** [debian/rules.d/build.mk:66: 
/<>/stamp-dir/configure_libc] Error 1
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
`


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0-rc8-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.29-2

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 939...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 20 Sep 2019 21:39:03 +0200
Source: glibc
Architecture: source
Version: 2.29-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 700472 939871 939898
Changes:
 glibc (2.29-2) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/control.in/main: drop the  profile from the
 python3:native build-depends.  Closes: #939871.
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix getegid, geteuid and getppid on alpha with < 5.1 kernels.
   Closes: #939898.
 .
   [ Sven Joachim ]
   * debian/script.in/nsscheck.sh: Do not restart services of different
 architecture than libc.  Closes: #700472.
 .
   [ Samuel Thibault ]
   * patches/hurd-i386/submitted-anon-mmap-shared.diff: Re-disable, actually
 makes some tests fail.
Checksums-Sha1:
 35b34de4e427dc22ba597e5b432fca121db50918 8735 glibc_2.29-2.dsc
 973296e15df00f4adead5d19cf3e5a9d8efad4c3 854928 glibc_2.29-2.debian.tar.xz
 938eb756e710ef792c59ab3e61aee1e20d69fc9b 7457 glibc_2.29-2_source.buildinfo
Checksums-Sha256:
 f510055121cba83afe31fa4ad3d447663ef5081bf4f06f20728ad731ba391168 8735 
glibc_2.29-2.dsc
 886b5638571863452b5861b1ec0b012a3e0c882b46f0094427123ed82d6577d5 854928 
glibc_2.29-2.debian.tar.xz
 e743cceef3988a1595e7b94f1a2393c4d56851d952da3f5359cdb85b9560ea2e 7457 
glibc_2.29-2_source.buildinfo
Files:
 9341cc28bbb9b1c6131097e80ada2442 8735 libs required glibc_2.29-2.dsc
 aa813ad47b772ced0bc18ac5a4cd2d1f 854928 libs required 
glibc_2.29-2.debian.tar.xz
 0dccbf7f2cb2a47684c263672a9aa575 7457 libs required 
glibc_2.29-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl2FLEgACgkQE4jA+Jno
M2tizQ/+L6W3GSSvW293bCjiG7tPwfuvNif9KnUQUr7QzsrKYPmV3gXiEez7G6t9
UccBVJ3c37LU3RxmWlHlqyMx0w3KC5lWLwD3uT47oKPHpKRxDnpKCEMjfDArF7+u
jbDkS02nR+FENSUat0Xc5oUO3yLfvi1uhFIZF34AuL68RhAcHV/l9mg

Processed: Re: Bug#888073: glibc: Support amd64 systems without /lib64

2019-09-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> unarchive 888073
Bug #888073 {Done: Aurelien Jarno } [src:glibc] glibc: 
Support amd64 systems without /lib64
Unarchived Bug 888073
> submitter 888073 !
Bug #888073 {Done: Aurelien Jarno } [src:glibc] glibc: 
Support amd64 systems without /lib64
Changed Bug submitter to 'javier--j3tyas0zmadh4isvtuv7artbn2z...@jasp.net' from 
'javier--ryqcowxjkcug7xjmmivj70vapc5...@jasp.net'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
888073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: [bts-link] source package src:glibc

2019-09-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src: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 #939898 (http://bugs.debian.org/939898)
> # Bug title: glibc: new getegid, geteuid and getppid syscalls used 
> unconditionally on alpha
> #  * http://sourceware.org/bugzilla/show_bug.cgi?id=24986
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 939898 + fixed-upstream
Bug #939898 [src:glibc] glibc: new getegid, geteuid and getppid syscalls used 
unconditionally on alpha
Added tag(s) fixed-upstream.
> usertags 939898 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
939898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Bug#939898 marked as pending in glibc

2019-09-14 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #939898 [src:glibc] glibc: new getegid, geteuid and getppid syscalls used 
unconditionally on alpha
Added tag(s) pending.

-- 
939898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#935153: marked as done (tzdata: debconf french translation)

2019-09-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 21:51:24 +
with message-id 
and subject line Bug#935153: fixed in tzdata 2019c-1
has caused the Debian Bug report #935153,
regarding tzdata: debconf french translation
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.)


-- 
935153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tzdata
Version: N/A
Severity: wishlist
Tags: patch l10n

Dear Maintainer,

Please find attached the updated french translation
of debconf templates for tzdata 2019b,
proofread by the debian-l10n-french mailing list contributors.

This file should be put as debian/po/fr.po in your package build tree.

Thanks for maintaining tzdata.

Baptiste


-- System Information:
Debian Release: 9.9
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-9-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
# Translation of tzdata debconf templates to French
# Copyright (C) 2008 Christian Perrier 
# This file is distributed under the same license as the tzdata package.
#
# Several translations merged with translations from debian-installer's tzsetup 
package
#
# Christian Perrier , 2002-2004.
# Pierre Machard , 2002-2004.
# Denis Barbier , 2002-2004.
# Philippe Batailler , 2002-2004.
# Michel Grentzinger , 2003-2004.
# Christian Perrier , 2005, 2006, 2007, 2008, 2011, 2013, 
2016.
# Baptiste Jammet , 2016-2019.
msgid ""
msgstr ""
"Project-Id-Version: \n"
"Report-Msgid-Bugs-To: tzd...@packages.debian.org\n"
"POT-Creation-Date: 2018-12-29 23:10+\n"
"PO-Revision-Date: 2019-07-31 14:06+0200\n"
"Last-Translator: Baptiste Jammet \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=n>1;\n"
"X-Generator: Poedit 1.5.7\n"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of "GMT+xx" or "GMT-xx" timezones
#. - SystemV will give the choice between zone named as per SystemV conventions:
#. EST5, MST7, etc.
#: ../tzdata.templates:1001
msgid "Africa"
msgstr "Afrique"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of "GMT+xx" or "GMT-xx" timezones
#. - SystemV will give the choice between zone named as per SystemV conventions:
#. EST5, MST7, etc.
#: ../tzdata.templates:1001
msgid "America"
msgstr "Amérique"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of "GMT+xx" or "GMT-xx" timezones
#. - SystemV will give the choice between zone named as per SystemV conventions:
#. EST5, MST7, etc.
#: ../tzdata.templates:1001
msgid "Antarctica"
msgstr "Antarctique"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of "GMT+xx" or "GMT-xx" timezones
#. - SystemV will give the choice between zone named as per SystemV conventions:
#. EST5, MST7, etc.
#: ../tzdata.templates:1001
msgid "Australia"
msgstr "Australie"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of "GMT+xx" or "GMT-xx" timezones
#. - SystemV will give the choice between zone named as per SystemV conventions:
#. EST5, MST7, etc.
#: ../tzdata.templates:1001
msgid "Arctic"
msgstr "Arctique"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of "GMT+xx" or "GMT-xx" timezones
#. - SystemV will give the choice between zone named as per SystemV conventions:
#. EST5, MST7, etc.
#: ../tzdata.templates:1001
msgid "Asia"
msgstr "Asie"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of "GMT+xx" or "GMT-xx" timezones
#. - SystemV will give the choice between zone named as per SystemV conventions:
#. EST5, MST7, etc.
#: ../tzdata.templates:1001
msgid &q

Processed: Re: Bug#939898: glibc: new getegid, geteuid and getppid syscalls used unconditionally on alpha

2019-09-10 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 glibc: new getegid, geteuid and getppid syscalls used 
> unconditionally on alpha
Bug #939898 [src:glibc] glibc: setuid/getuid broken on alpha with 2.29-1
Changed Bug title to 'glibc: new getegid, geteuid and getppid syscalls used 
unconditionally on alpha' from 'glibc: setuid/getuid broken on alpha with 
2.29-1'.

-- 
939898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: bug 939898 is forwarded to https://sourceware.org/bugzilla/show_bug.cgi?id=24986

2019-09-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 939898 https://sourceware.org/bugzilla/show_bug.cgi?id=24986
Bug #939898 [src:glibc] glibc: setuid/getuid broken on alpha with 2.29-1
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=24986'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
939898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Bug#939871 marked as pending in glibc

2019-09-09 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #939871 [src:glibc] glibc: python3:native build dependency incorrectly 
marked as 
Added tag(s) pending.

-- 
939871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#700472: Upgrade of the foreign arch libc6 causes service restart

2019-09-09 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch
Bug #700472 [libc6] Upgrade of the foreign arch libc6 causes service restart
Bug #752527 [libc6] Upgrading libc6:i386 on amd64 restarts services
Added tag(s) patch.
Added tag(s) patch.

-- 
700472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700472
752527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#935507: marked as done (message should say how to enable not seeing this message anymore)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 15:17:26 +0200
with message-id <20190831131726.gb31...@aurel32.net>
and subject line Re: Bug#935507: message should say how to enable not seeing 
this message anymore
has caused the Debian Bug report #935507,
regarding message should say how to enable not seeing this message anymore
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.)


-- 
935507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.29-0experimental1

The message seen in the image
https://i.stack.imgur.com/UmlmT.png
seen in
https://serverfault.com/questions/238679/unable-to-force-debian-to-do-unattended-install-libc6-wants-interactive-confi
should also mention how to make it not ask ever again.

That way people wouldn't need to search Google for the answer.
--- End Message ---
--- Begin Message ---
control: found -1 glibc/2.13-20 

On 2019-08-23 20:43, 積丹尼 Dan Jacobson wrote:
> Package: libc6
> Version: 2.29-0experimental1
> 
> The message seen in the image
> https://i.stack.imgur.com/UmlmT.png
> seen in
> https://serverfault.com/questions/238679/unable-to-force-debian-to-do-unattended-install-libc6-wants-interactive-confi
> should also mention how to make it not ask ever again.
> 
> That way people wouldn't need to search Google for the answer.

The question "Restart services during package upgrades without asking?"
is shown by debconf with priority critical the first time a restart is
needed. If it is not presented to you, it's because "no" has been
answered in the past.

The way to manage debconf has no place in the questions asked by glibc.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net--- End Message ---


Bug#924712: marked as done (crypt() not available _XOPEN_SOURCE is defined)

2019-08-31 Thread Debian Bug Tracking System
Your message dated Sat, 31 Aug 2019 15:04:06 +0200
with message-id <20190831130406.ga31...@aurel32.net>
and subject line Re: Bug#924712: crypt() not available _XOPEN_SOURCE is defined
has caused the Debian Bug report #924712,
regarding crypt() not available _XOPEN_SOURCE is defined
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.)


-- 
924712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-dev
Version: 2.28-8
Severity: serious

Hi,

The crypt.3 manpage, state that _XOPEN_SOURCE should be define for
crypt() to be available.

But it looks that it's currently the opposite, if _XOPEN_SOURCE is
defined, the function cannot be found.

This actually looks like a regression compared to stretch.

Regards,
Laurent Bigonville

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages manpages-dev depends on:
ii  manpages  4.16-1

manpages-dev recommends no packages.

Versions of packages manpages-dev suggests:
ii  man-db [man-browser]  2.8.5-2

-- no debconf information
--- End Message ---
--- Begin Message ---
On 2019-08-25 15:51, Francesco Poli wrote:
> On Sun, 25 Aug 2019 13:46:36 +0200 Florian Weimer wrote:
> 
> > * Francesco Poli:
> > 
> > > Hello everyone,
> > > I am sorry to ask, but... I cannot understand what's the status of
> > > [this bug report].
> > >
> > > [this bug report]: <https://bugs.debian.org/924712>
> > >
> > > A serious bug for libc6-dev without any apparent activity since last
> > > March?  Sure there must have been some hidden progress that I cannot
> > > see.
> > 
> > We provided a solution acceptable to the reporter.  I do not think
> > further action is needed on the glibc side.  The manual page needs to
> > be updated to reflect the change, but that's not part of glibc.
> 
> OK, good.
> Thanks for your prompt reply!
> 
> Why is the bug report being kept open, though?
> Should it be reassigned to package manpages-dev and fixed there?

manpages-dev doesn't provide the manpage for crypt(3) anymore. It is now
provided by libcrypt2-dev. The crypt functions are getting removed from
the glibc and will be provided by this external library. I guess we'll
do the transition after getting glibc 2.29 into unstable.

As the version provided by libcrypt2-dev doesn't have the reported
issue, I am closing the bug.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature
--- End Message ---


Processed: bug 931456 is forwarded to https://sourceware.org/bugzilla/show_bug.cgi?id=24936

2019-08-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 931456 https://sourceware.org/bugzilla/show_bug.cgi?id=24936
Bug #931456 [libc6] libc6: uselocale(3) does not invalidate gettext translation 
cache
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=24936'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
931456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#926906: marked as done (libc6: range of cyrillic lowercase letters matches also uppercase)

2019-08-20 Thread Debian Bug Tracking System
Your message dated Tue, 20 Aug 2019 14:37:00 +0200
with message-id <20190820123700.ga23...@aurel32.net>
and subject line Re: Bug#926906: libc6: range of cyrillic lowercase letters 
matches also uppercase
has caused the Debian Bug report #926906,
regarding libc6: range of cyrillic lowercase letters matches also uppercase
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.)


-- 
926906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.28-8
Severity: normal

Dear Maintainer, new version (2.28) of libc6 contains collation error.

expected behaviour:
$ echo АБВабв | grep -o '[а-в]'
а
б
в
$ echo АБВабв | sed 's/[а-в]/-/g'
АБВ---

observed behaviour:
$ echo АБВабв | grep -o '[а-в]'
А
Б
а
б
в
$ echo АБВабв | sed 's/[а-в]/-/g'
--В---

this error is also observed in archlinux (libc-2.28) (see discussion in
russian: https://ru.stackoverflow.com/q/968618/178576)

additional info:
$ locale
LANG=
LANGUAGE=ru
LC_CTYPE="ru_RU.UTF-8"
LC_NUMERIC="ru_RU.UTF-8"
LC_TIME="ru_RU.UTF-8"
LC_COLLATE="ru_RU.UTF-8"
LC_MONETARY="ru_RU.UTF-8"
LC_MESSAGES="ru_RU.UTF-8"
LC_PAPER="ru_RU.UTF-8"
LC_NAME="ru_RU.UTF-8"
LC_ADDRESS="ru_RU.UTF-8"
LC_TELEPHONE="ru_RU.UTF-8"
LC_MEASUREMENT="ru_RU.UTF-8"
LC_IDENTIFICATION="ru_RU.UTF-8"
LC_ALL=ru_RU.UTF-8

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to 
ru_RU.UTF-8), LANGUAGE=C (charmap=UTF-8) (ignored: LC_ALL set to ru_RU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages libc6 depends on:
ii  libgcc1  1:8.3.0-5

Versions of packages libc6 recommends:
ii  libidn2-0  2.0.5-1

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.71
pn  glibc-doc  
ii  libc-l10n  2.28-8
ii  locales2.28-8

-- debconf information excluded
--- End Message ---
--- Begin Message ---
On 2019-04-12 03:45, aleksandr barakin wrote:
> Package: libc6
> Version: 2.28-8
> Severity: normal
> 
> Dear Maintainer, new version (2.28) of libc6 contains collation error.
> 
> expected behaviour:
> $ echo АБВабв | grep -o '[а-в]'
> а
> б
> в
> $ echo АБВабв | sed 's/[а-в]/-/g'
> АБВ---
> 
> observed behaviour:
> $ echo АБВабв | grep -o '[а-в]'
> А
> Б
> а
> б
> в
> $ echo АБВабв | sed 's/[а-в]/-/g'
> --В---
> 
> this error is also observed in archlinux (libc-2.28) (see discussion in
> russian: https://ru.stackoverflow.com/q/968618/178576)

Please see the answer from upstream there:
https://sourceware.org/bugzilla/show_bug.cgi?id=23393#c41

In short the range in any non-POSIX/C locale is undefined, so there is
no bug. I am therefore closing it.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net--- End Message ---


Processed: Bug#935153 marked as pending in tzdata

2019-08-20 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #935153 [tzdata] tzdata: debconf french translation
Added tag(s) pending.

-- 
935153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#922213: locales-all: Doesn't provide en_DE.UTF-8

2019-08-17 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 plasma-desktop
Bug #922213 [locales-all] locales-all: Doesn't provide en_DE.UTF-8
Bug reassigned from package 'locales-all' to 'plasma-desktop'.
No longer marked as found in versions glibc/2.28-6.
Ignoring request to alter fixed versions of bug #922213 to the same values 
previously set

-- 
922213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: reassign 926699 to debootstrap,usrmerge

2019-08-17 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 926699 debootstrap,usrmerge
Bug #926699 [libc6-x32,libc6-i386] libc6-{i386,x32}: installing, removing, 
reinstalling in a --merged-usr system results in unmerged /lib{32,x32}
Bug reassigned from package 'libc6-x32,libc6-i386' to 'debootstrap,usrmerge'.
No longer marked as found in versions 2.28-8.
Ignoring request to alter fixed versions of bug #926699 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
926699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#861238: marked as done (libc-bin: prompting due to modified conffiles which were not modified by the user: /etc/ld.so.conf)

2019-08-17 Thread Debian Bug Tracking System
Your message dated Sat, 17 Aug 2019 21:43:42 +0200
with message-id <20190817194342.ga17...@aurel32.net>
and subject line Re: Bug#861238: libc-bin: prompting due to modified conffiles 
which were not modified by the user: /etc/ld.so.conf
has caused the Debian Bug report #861238,
regarding libc-bin: prompting due to modified conffiles which were not modified 
by the user: /etc/ld.so.conf
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.)


-- 
861238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc-bin
Version: 2.19-18+deb8u7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is no user input, this fails.
But this is not the real problem, the real problem is that this prompt
shows up in the first place, as there was nobody modifying this conffile
at all, the package has just been installed and upgraded...

This is a violation of policy 10.7.3, see
https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."

https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.

In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

>From the attached log (scroll to the bottom...):

  Setting up libc-bin (2.19-18+deb8u7) ...
  Installing new version of config file /etc/bindresvport.blacklist ...
  Installing new version of config file /etc/gai.conf ...
  
  Configuration file `/etc/ld.so.conf'
   ==> File on system created by you or by a script.
   ==> File also in package provided by package maintainer.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** ld.so.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing libc-bin 
(--configure):
   EOF on stdin at conffile prompt
  Errors were encountered while processing:
   libc-bin

This was found on i386 with amd64-libs installed on the upgrade path

  squeeze -> wheezy -> jessie -> stretch

while upgrading to jessie.

In my piuparts scripts I have the following exception for cleaning
this up before purge, but that doesn't apply in this case, since it
is not yet purge time:

# amd64-libs leaves a superfluous line there ...
sed -i '3{/^$/d}' /etc/ld.so.conf

amd64-libs wasn't seen any more after squeeze :-)

Maybe it is sufficient for libc-bin in jessie to
a) add Breaks: amd64-libs and
b) put the sed magic into the preinst


cheers,

Andreas


amd64-libs_None.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
On 2017-04-27 09:46, Aurelien Jarno wrote:
> On 2017-04-26 14:18, Andreas Beckmann wrote:
> > Package: libc-bin
> > Version: 2.19-18+deb8u7
> > Severity: serious
> > User: debian...@lists.debian.org
> > Usertags: piuparts
> > 
> > Hi,
> > 
> > during a test with piuparts I noticed your package failed the piuparts
> > upgrade test because dpkg detected a conffile as being modified and then
> > prompted the user for an action. As there is no user input, this fails.
> > But this is not the real problem, the real problem is that this prompt
> > shows up in the first place, as there was nobody modifying this conffile
> > at all, the package has just been installed and upgraded...
> > 
> > This is a violation of policy 10.7.3, see
> > https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3,
> > which says "[These scripts handling conffiles] must not ask unnecessary
> > questions (particularly during upgrades), and must otherwise be good
> > citizens."
> > 
> > https://wiki.debian.org/DpkgConffileHandling should help with figuring
> > out how to do this properly.
> > 
> > In https://lists.debian.org/debian-devel/2009/08/msg00675.html and
> > followups it has been ag

Bug#934823: marked as done (glibc needs an update for linux-5.2 kernel headers (alpha))

2019-08-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Aug 2019 11:05:31 +
with message-id 
and subject line Bug#934823: fixed in glibc 2.29-0experimental0
has caused the Debian Bug report #934823,
regarding glibc needs an update for linux-5.2 kernel headers (alpha)
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.)


-- 
934823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:glibc
Version: 2.28-10
Severity: sersious
Tags: sid bullseye patch

currently c-t-b-p ftbfs on alpha. A patch needs to be backported.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836064

the c-t-b-ports package ftbfs:

/bin/bash ../scripts/move-if-change
/<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.T
/<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.h
touch /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.stmp
if test -r /<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new;
then mv -f /<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new
/<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h; \
else echo >&2 'This configuration not matched in ../abi-tags'; exit 1; fi
In file included from :1:
../sysdeps/unix/sysv/linux/alpha/sysdep.h:54: error: "__NR_osf_shmat" redefined
[-Werror]
 #define __NR_osf_shmat 209

In file included from ../sysdeps/unix/sysv/linux/sys/syscall.h:24,
 from ../sysdeps/unix/sysdep.h:20,
 from ../sysdeps/unix/alpha/sysdep.h:19,
 from ../sysdeps/unix/sysv/linux/alpha/sysdep.h:29,
 from :1:
/<>/glibc-2.29/debian/include/asm/unistd.h:8: note: this is the
location of the previous definition
 #define __NR_osf_shmat __NR_shmat

cc1: all warnings being treated as errors

a definition of __NR_osf_shmat was added during the 5.1 cycle:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=12b57c5c70f397a9410411d4e348096edada20f9

Looks like a fix has been applied to upstream glibc:

https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=d5ecee822e72a2fd156338ab2be2f2e70a1da55a
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.29-0experimental0

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 934...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 16 Aug 2019 12:42:42 +0200
Source: glibc
Architecture: source
Version: 2.29-0experimental0
Distribution: experimental
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 908946 910669 933513 933800 934823
Changes:
 glibc (2.29-0experimental0) experimental; urgency=medium
 .
   [ Adam Conrad ]
   * New upstream release 2.29, with git updates up to 2019-02-20:
 - Add PF_XDP, AF_XDP and SOL_XDP to bits/socket.h.  Closes: #933800.
 - debian/symbols.wildcard: Add 2.29, and debian/control: Regenrate.
 - debian/patches/localedata/locales_CH.diff: Applied upstream.
 - debian/patches/localedata/submitted-it_IT-thousands_sep.diff: Upstreamed.
 - debian/patches/localedata/git-en_US-date_fmt.diff: Applied upstream.
 - debian/patches/hurd-i386/git-magic-pid.diff: Applied upstream.
 - debian/patches/hurd-i386/git-interrupt_timeout_EIO.diff: Upstreamed.
 - debian/patches/hurd-i386/git-interrupt_timeout.diff: Applied upstream.
 - debian/patches/hurd-i386/git-intr-msg.diff: Applied upstream.
 - debian/patches/hurd-i386/git-pci.diff: Applied upstream.
 - debian/patches/hurd-i386/git-msync.diff: Applied upstream.
 - debian/patches/hurd-i386/git-spawn-open.diff: Applied upstream.
 - debian/patches/hurd-i386/git-tst-preadvwritev2-common.c.diff: Upstreamed.
 - debian/patches/hurd-i386/git-fcntl64.diff: Applied upstream.
 - debian/patches/hurd-i386/git-lockf-0.diff: Applied upstream.
 - debian/patches/hurd-i386/git-libpthread_setpshared.diff: Upstreamed.
 - debian/patches/hurd-i386/git-AT_EM

Bug#933513: marked as done (glibc: mips{64,n32}r6{,el} ln wrong ld.so filename)

2019-08-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Aug 2019 11:05:31 +
with message-id 
and subject line Bug#933513: fixed in glibc 2.29-0experimental0
has caused the Debian Bug report #933513,
regarding glibc: mips{64,n32}r6{,el} ln wrong ld.so filename
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.)


-- 
933513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:glibc
Version: 2.28-10

diff -Nru glibc-2.28/debian/sysdeps/mips64r6el.mk
glibc-2.28/debian/sysdeps/mips64r6el.mk
--- glibc-2.28/debian/sysdeps/mips64r6el.mk 2019-02-10
16:13:53.0 +
+++ glibc-2.28/debian/sysdeps/mips64r6el.mk 2019-05-01
17:24:19.0 +
@@ -60,7 +60,7 @@
 # create a symlink for the 32 bit dynamic linker in /lib
 define libc6-mips32_extra_pkg_install
 mkdir -p debian/libc6-mips32/lib
-ln -sf /libo32/ld.so.1 debian/libc6-mips32/lib
+ln -sf /libo32/ld-linux-mipsn8.so.1 debian/libc6-mips32/lib
 endef

 endif # multilib
diff -Nru glibc-2.28/debian/sysdeps/mips64r6.mk
glibc-2.28/debian/sysdeps/mips64r6.mk
--- glibc-2.28/debian/sysdeps/mips64r6.mk   2019-02-10
16:13:53.0 +
+++ glibc-2.28/debian/sysdeps/mips64r6.mk   2019-05-01
17:24:19.0 +
@@ -60,7 +60,7 @@
 # create a symlink for the 32 bit dynamic linker in /lib
 define libc6-mips32_extra_pkg_install
 mkdir -p debian/libc6-mips32/lib
-ln -sf /libo32/ld.so.1 debian/libc6-mips32/lib
+ln -sf /libo32/ld-linux-mipsn8.so.1 debian/libc6-mips32/lib
 endef

 endif # multilib
diff -Nru glibc-2.28/debian/sysdeps/mipsn32r6el.mk
glibc-2.28/debian/sysdeps/mipsn32r6el.mk
--- glibc-2.28/debian/sysdeps/mipsn32r6el.mk2019-02-10
16:13:53.0 +
+++ glibc-2.28/debian/sysdeps/mipsn32r6el.mk2019-05-01
17:24:19.0 +
@@ -60,7 +60,7 @@
 # create a symlink for the 32 bit dynamic linker in /lib
 define libc6-mips32_extra_pkg_install
 mkdir -p debian/libc6-mips32/lib
-ln -sf /libo32/ld.so.1 debian/libc6-mips32/lib
+ln -sf /libo32/ld-linux-mipsn8.so.1 debian/libc6-mips32/lib
 endef

 endif # multilib
diff -Nru glibc-2.28/debian/sysdeps/mipsn32r6.mk
glibc-2.28/debian/sysdeps/mipsn32r6.mk
--- glibc-2.28/debian/sysdeps/mipsn32r6.mk  2019-02-10
16:13:53.0 +
+++ glibc-2.28/debian/sysdeps/mipsn32r6.mk  2019-05-01
17:24:19.0 +
@@ -62,7 +62,7 @@
 # create a symlink for the 32 bit dynamic linker in /lib
 define libc6-mips32_extra_pkg_install
 mkdir -p debian/libc6-mips32/lib
-ln -sf /libo32/ld.so.1 debian/libc6-mips32/lib
+ln -sf /libo32/ld-linux-mipsn8.so.1 debian/libc6-mips32/lib
 endef

 endif # multilib

-- 
YunQiang Su
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.29-0experimental0

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 933...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 16 Aug 2019 12:42:42 +0200
Source: glibc
Architecture: source
Version: 2.29-0experimental0
Distribution: experimental
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 908946 910669 933513 933800 934823
Changes:
 glibc (2.29-0experimental0) experimental; urgency=medium
 .
   [ Adam Conrad ]
   * New upstream release 2.29, with git updates up to 2019-02-20:
 - Add PF_XDP, AF_XDP and SOL_XDP to bits/socket.h.  Closes: #933800.
 - debian/symbols.wildcard: Add 2.29, and debian/control: Regenrate.
 - debian/patches/localedata/locales_CH.diff: Applied upstream.
 - debian/patches/localedata/submitted-it_IT-thousands_sep.diff: Upstreamed.
 - debian/patches/localedata/git-en_US-date_fmt.diff: Applied upstream.
 - debian/patches/hurd-i386/git-magic-pid.diff: Applied upstream.
 - debian/patches/hurd-i386/git-interrupt_timeout_EIO.diff: Upstreamed.
 - debian/patches/hurd-i386/git-interrupt_timeout.diff: Applied upstream.
 - debian/patches/hurd-i386/git-intr-msg.diff: Applied upstream.
 - debian/patches

Bug#933800: marked as done (AF_XDP missing in libc6-dev)

2019-08-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Aug 2019 11:05:31 +
with message-id 
and subject line Bug#933800: fixed in glibc 2.29-0experimental0
has caused the Debian Bug report #933800,
regarding AF_XDP missing in libc6-dev
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.)


-- 
933800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-dev
Version: 2.28-10

There is currently a mismatch between libc6 on Debian stable and the
underlying kernel with respect to XDP. The kernel has support for XDP
sockets, but the libc6 library does not have the associated macro
AF_XDP, to specify the address family.

The addition of the AF_XDP macro to glibc is here:

https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=38b0593e9a862c3b35392a0f5b202696b8116aa3;hp=5cd7dbdea13eb302620491ef44837b17e9d39c5a

So it would seem that this does not show up until glibc version 2.29.
However, since the Debian stable kernel has this functionality,
perhaps this is worth patching in?

I am currently running Debian stable with kernel 4.19.0-5 Debian
4.19.37-5+deb10u1 (2019-07-19) and have the latest libc6-dev 2.28-10
package installed.

-- 
~ ry
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.29-0experimental0

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 933...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 16 Aug 2019 12:42:42 +0200
Source: glibc
Architecture: source
Version: 2.29-0experimental0
Distribution: experimental
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 908946 910669 933513 933800 934823
Changes:
 glibc (2.29-0experimental0) experimental; urgency=medium
 .
   [ Adam Conrad ]
   * New upstream release 2.29, with git updates up to 2019-02-20:
 - Add PF_XDP, AF_XDP and SOL_XDP to bits/socket.h.  Closes: #933800.
 - debian/symbols.wildcard: Add 2.29, and debian/control: Regenrate.
 - debian/patches/localedata/locales_CH.diff: Applied upstream.
 - debian/patches/localedata/submitted-it_IT-thousands_sep.diff: Upstreamed.
 - debian/patches/localedata/git-en_US-date_fmt.diff: Applied upstream.
 - debian/patches/hurd-i386/git-magic-pid.diff: Applied upstream.
 - debian/patches/hurd-i386/git-interrupt_timeout_EIO.diff: Upstreamed.
 - debian/patches/hurd-i386/git-interrupt_timeout.diff: Applied upstream.
 - debian/patches/hurd-i386/git-intr-msg.diff: Applied upstream.
 - debian/patches/hurd-i386/git-pci.diff: Applied upstream.
 - debian/patches/hurd-i386/git-msync.diff: Applied upstream.
 - debian/patches/hurd-i386/git-spawn-open.diff: Applied upstream.
 - debian/patches/hurd-i386/git-tst-preadvwritev2-common.c.diff: Upstreamed.
 - debian/patches/hurd-i386/git-fcntl64.diff: Applied upstream.
 - debian/patches/hurd-i386/git-lockf-0.diff: Applied upstream.
 - debian/patches/hurd-i386/git-libpthread_setpshared.diff: Upstreamed.
 - debian/patches/hurd-i386/git-AT_EMPTY_PATH.diff: Applied upstream.
 - debian/patches/hurd-i386/git-altstack.diff: Applied upstream.
 - debian/patches/riscv64/git-thread-debugging.diff: Applied upstream.
 - debian/patches/sparc/submitted-sparc64-socketcall.diff: Applied upstream.
 - debian/patches/any/local-tst-mktime2.diff: Applied upstream.
 - debian/patches/all/local-remove-manual.diff: Rebased.
 - debian/patches/alpha/local-string-functions.diff: Rebased.
 - debian/patches/any/git-libio-stdout-putc.diff: Rebased.
 - debian/patches/hurd-i386/local-exec_filename.diff: Rebased.
 - debian/patches/hurd-i386/local-hurdsig-globaldisp-version.diff: Rebased.
 - debian/patches/hurd-i386/submitted-anon-mmap-shared.diff: Rebased.
 - debian/patches/hurd-i386/tg-EGREGIOUS-fr.diff: Rebased.
 - debian/patches/hurd-i386/tg-EIEIO-fr.diff: Rebased.
 - debian/patches/hurd-i386/tg-hurdsig-global

Bug#910669: marked as done (glibc: Please remove transitional package multiarch-support)

2019-08-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Aug 2019 11:05:31 +
with message-id 
and subject line Bug#910669: fixed in glibc 2.29-0experimental0
has caused the Debian Bug report #910669,
regarding glibc: Please remove transitional package multiarch-support
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.)


-- 
910669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.27-6
X-Debbugs-CC: aure...@debian.org d...@debian.org
Severity: normal

Hi Aurelien, Matthias and Debian glibc maintainers,

As previously discussed in
https://lists.debian.org/debian-science/2018/08/msg00050.html ,
I think it's time to completely remove multiarch-support from Sid (and
thus Buster).

There's already no package in Sid (on amd64 platform) that depends on
multiarch-support. There is still one left in experimental
(openjdk-7-jre-headless) however it was due to its FTBFS in
experimental. Openjdk-7's source package has already removed it.
Please see https://bugs.debian.org/906117 for its details.

I do hope we could get rid of multiarch-support before Buster freeze.

P.S. doko: is it possible that #906117 eventually gets solved? That
would undoubtedly be helpful.

--
Regards,
Boyuan Yang
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.29-0experimental0

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 910...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 16 Aug 2019 12:42:42 +0200
Source: glibc
Architecture: source
Version: 2.29-0experimental0
Distribution: experimental
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 908946 910669 933513 933800 934823
Changes:
 glibc (2.29-0experimental0) experimental; urgency=medium
 .
   [ Adam Conrad ]
   * New upstream release 2.29, with git updates up to 2019-02-20:
 - Add PF_XDP, AF_XDP and SOL_XDP to bits/socket.h.  Closes: #933800.
 - debian/symbols.wildcard: Add 2.29, and debian/control: Regenrate.
 - debian/patches/localedata/locales_CH.diff: Applied upstream.
 - debian/patches/localedata/submitted-it_IT-thousands_sep.diff: Upstreamed.
 - debian/patches/localedata/git-en_US-date_fmt.diff: Applied upstream.
 - debian/patches/hurd-i386/git-magic-pid.diff: Applied upstream.
 - debian/patches/hurd-i386/git-interrupt_timeout_EIO.diff: Upstreamed.
 - debian/patches/hurd-i386/git-interrupt_timeout.diff: Applied upstream.
 - debian/patches/hurd-i386/git-intr-msg.diff: Applied upstream.
 - debian/patches/hurd-i386/git-pci.diff: Applied upstream.
 - debian/patches/hurd-i386/git-msync.diff: Applied upstream.
 - debian/patches/hurd-i386/git-spawn-open.diff: Applied upstream.
 - debian/patches/hurd-i386/git-tst-preadvwritev2-common.c.diff: Upstreamed.
 - debian/patches/hurd-i386/git-fcntl64.diff: Applied upstream.
 - debian/patches/hurd-i386/git-lockf-0.diff: Applied upstream.
 - debian/patches/hurd-i386/git-libpthread_setpshared.diff: Upstreamed.
 - debian/patches/hurd-i386/git-AT_EMPTY_PATH.diff: Applied upstream.
 - debian/patches/hurd-i386/git-altstack.diff: Applied upstream.
 - debian/patches/riscv64/git-thread-debugging.diff: Applied upstream.
 - debian/patches/sparc/submitted-sparc64-socketcall.diff: Applied upstream.
 - debian/patches/any/local-tst-mktime2.diff: Applied upstream.
 - debian/patches/all/local-remove-manual.diff: Rebased.
 - debian/patches/alpha/local-string-functions.diff: Rebased.
 - debian/patches/any/git-libio-stdout-putc.diff: Rebased.
 - debian/patches/hurd-i386/local-exec_filename.diff: Rebased.
 - debian/patches/hurd-i386/local-hurdsig-globaldisp-version.diff: Rebased.
 - debian/patches/hurd-i386/submitted-anon-mmap-shared.diff: Rebased.
 - debian/patches/hurd-i386/tg-EGREGIOUS-fr.diff: Rebased.
 - debian/patches/hurd-i386/tg-EIEIO-fr.diff: Rebased

Bug#908946: marked as done (ldconfig: Default to the new format for ld.so.cache)

2019-08-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Aug 2019 11:05:31 +
with message-id 
and subject line Bug#908946: fixed in glibc 2.29-0experimental0
has caused the Debian Bug report #908946,
regarding ldconfig: Default to the new format for ld.so.cache
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.)


-- 
908946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glibc
Version: 2.27-6
Tags: patch

glibc has supported the new ld.so.cache format for 18+ years, and the
old/compat versions date back to around the libc5 era. Switching to the
new format makes the cache smaller, and slightly faster to load.

The attached patch switches to the new format by default. I've also
submitted this patch upstream at
https://sourceware.org/bugzilla/show_bug.cgi?id=23668 .
diff --git a/debian/local/manpages/ldconfig.8 b/debian/local/manpages/ldconfig.8
index 505a1c84..d6722bc0 100644
--- a/debian/local/manpages/ldconfig.8
+++ b/debian/local/manpages/ldconfig.8
@@ -112,7 +112,7 @@ the current cache.
 .B \-c\ \-\-format=FORMAT
 Use
 .B FORMAT
-for the cache file. Choices are old, new and compat (the default).
+for the cache file. Choices are old, compat, and new (the default).
 .TP
 .B \-i \-\-ignore-aux-cache
 Ignore auxiliary cache file.
diff --git a/debian/patches/any/ldconfig-new-format.diff b/debian/patches/any/ldconfig-new-format.diff
new file mode 100644
index ..b0f4126e
--- /dev/null
+++ b/debian/patches/any/ldconfig-new-format.diff
@@ -0,0 +1,74 @@
+From 1183d8acf478e36b7e427db295b9763859822c79 Mon Sep 17 00:00:00 2001
+From: Josh Triplett 
+Date: Sun, 16 Sep 2018 04:20:34 -0700
+Subject: [PATCH] Default to the new format for ld.so.cache
+
+glibc has supported this format for 18+ years.
+
+Reorder conditionals to look for the new format first.
+
+* elf/ldconfig.c: Default to the new format for ld.so.cache. glibc has
+supported this format for 18+ years.
+* elf/dl-cache.c (_dl_load_cache_lookup): Reorder conditionals to look
+for the new format first.
+---
+ elf/dl-cache.c | 16 
+ elf/ldconfig.c |  4 ++--
+ 4 files changed, 20 insertions(+), 10 deletions(-)
+
+diff --git a/elf/dl-cache.c b/elf/dl-cache.c
+index 6ee5153ff9..75bd9d9536 100644
+--- a/elf/dl-cache.c
 b/elf/dl-cache.c
+@@ -203,7 +203,14 @@ _dl_load_cache_lookup (const char *name)
+ 	 - the old format with the new format in it
+ 	 - only the new format
+ 	 The following checks if the cache contains any of these formats.  */
+-  if (file != MAP_FAILED && cachesize > sizeof *cache
++  if (file != MAP_FAILED && cachesize > sizeof *cache_new
++	   && memcmp (file, CACHEMAGIC_VERSION_NEW,
++			  sizeof CACHEMAGIC_VERSION_NEW - 1) == 0)
++	{
++	  cache_new = file;
++	  cache = file;
++	}
++  else if (file != MAP_FAILED && cachesize > sizeof *cache
+ 	  && memcmp (file, CACHEMAGIC, sizeof CACHEMAGIC - 1) == 0)
+ 	{
+ 	  size_t offset;
+@@ -220,13 +227,6 @@ _dl_load_cache_lookup (const char *name)
+ 			 sizeof CACHEMAGIC_VERSION_NEW - 1) != 0)
+ 	cache_new = (void *) -1;
+ 	}
+-  else if (file != MAP_FAILED && cachesize > sizeof *cache_new
+-	   && memcmp (file, CACHEMAGIC_VERSION_NEW,
+-			  sizeof CACHEMAGIC_VERSION_NEW - 1) == 0)
+-	{
+-	  cache_new = file;
+-	  cache = file;
+-	}
+   else
+ 	{
+ 	  if (file != MAP_FAILED)
+diff --git a/elf/ldconfig.c b/elf/ldconfig.c
+index fbdd814edf..1ce4a29566 100644
+--- a/elf/ldconfig.c
 b/elf/ldconfig.c
+@@ -95,7 +95,7 @@ int opt_verbose;
+
+ /* Format to support.  */
+ /* 0: only libc5/glibc2; 1: both; 2: only glibc 2.2.  */
+-int opt_format = 1;
++int opt_format = 2;
+
+ /* Build cache.  */
+ static int opt_build_cache = 1;
+@@ -148,7 +148,7 @@ static const struct argp_option options[] =
+   { NULL, 'f', N_("CONF"), 0, N_("Use CONF as configuration file"), 0},
+   { NULL, 'n', NULL, 0, N_("Only process directories specified on the command line.  Don't build cache."), 0},
+   { NULL, 'l', NULL, 0, N_("Manually link individual libraries."), 0},
+-  { "format", 'c', N_("FORMAT"), 0, N_("Format to use: new, old or compat (default)"), 0},
++  { "format", 'c', N_("FORMAT"), 0, N_("Format to use: new (default), old, or compat"), 0},
+   { "ignore-aux-cache", 'i', NULL, 0, N_("Ignore auxiliary cache file"), 0},
+   { NULL, 0, NULL, 0, NULL, 0 }
+ };
diff --git a/debian/patches/series

Processed: Bug#908946 marked as pending in glibc

2019-08-15 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #908946 [glibc] ldconfig: Default to the new format for ld.so.cache
Added tag(s) pending.

-- 
908946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Bug#934823 marked as pending in glibc

2019-08-15 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #934823 [src:glibc] glibc needs an update for linux-5.2 kernel headers 
(alpha)
Added tag(s) pending.

-- 
934823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Bug#933513 marked as pending in glibc

2019-08-15 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #933513 [src:glibc] glibc: mips{64,n32}r6{,el} ln wrong ld.so filename
Added tag(s) pending.

-- 
933513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: bug 908946 is forwarded to https://sourceware.org/bugzilla/show_bug.cgi?id=23668

2019-08-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 908946 https://sourceware.org/bugzilla/show_bug.cgi?id=23668
Bug #908946 [glibc] ldconfig: Default to the new format for ld.so.cache
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=23668'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
908946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908946
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#934080: marked as done ([libc6] Significant degradation in the memory effectivity of the memory allocator)

2019-08-08 Thread Debian Bug Tracking System
Your message dated Thu, 8 Aug 2019 19:00:38 +0200
with message-id <20190808170038.gb26...@aurel32.net>
and subject line Re: Bug#934080: [libc6] Significant degradation in the memory 
effectivity of the memory allocator
has caused the Debian Bug report #934080,
regarding [libc6] Significant degradation in the memory effectivity of the 
memory allocator
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.)


-- 
934080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: libc6
Version: 2.19, 2.24, 2.28
Severity: normal

--- Please enter the report below this line. ---
Initial condition of the problem representing is a program in the single 
source code, built on-and for Debian 7, 8, 9, 10 with a result in the 
Live disks.


The program represents a web-interface of several pages, where here used 
only the first page.


In building the first page there used wide range of memory chunks: small 
objects of the C++ classes (~100 bytes), resources of the image files 
(~10 kbytes), GD memory blocks (~1 kbytes), so on


The live disks were started under VirtualBox 5.2, where the got data was 
measured by *top*.


The data measuring under VirtualBox performed into the next stages:
1. Start the program and set the initial state, fixing the memory 
allocation — *measuring the initial memory consumption value*

2. Perform the allocation-freeing iteration
2.1. Open the first Web-interface page from a Web-browser of the host system
2.2. Close the page on the Web-browser
2.3. Wait to close-freeing session of the first Web-interface page on 
the program side, 1 minute — *measuring the iteration **memory 
consumption value*

3. Return to the stage 2 and repeating 5 iterations

The stage 2.3 tested to real freeing all the allocated memory blocks 
both by the objects counters and by *valgrind*!


In the result we have next data:

Environment 	Initially, MB 	Iter. 1, MB 	Iter. 2, MB 	Iter. 3, MB 	Iter. 
4, MB 	Iter. 5, MB 	Resume
Debian 10 amd64, GLibC 2.28, GCC 8.3.0 	182 	191.5 	199 	206 	212 	212 
Satiated on the iteration*4*, base consumption 9.5 MB, extra consumption 
20 MB (*200* %), liboscada.so 3.5 MB, ui_WebVision.so 0.74 MB
Debian 9 amd64, GLibC 2.24, GCC 6.3.0 	160 	170 	178 	179 	183 	185 
Satiated on the iteration*5*, base consumption 10 MB, extra consumption 
15 MB (*150* %), liboscada.so 3.5 MB, ui_WebVision.so 0.72 MB
Debian 8 amd64, GLibC 2.19, GCC 4.9.2 	125.5 	133 	139 	139 	139 	139 
Satiated on the iteration*2*, base consumption 7.5 MB, extra consumption 
6 MB (*80* %), liboscada.so 3.8 MB, ui_WebVision.so 0.79 MB
Debian 7 amd64, GLibC 2.13, GCC 4.7.2 	101 	108 	111 	112 	112 	112 
Satiated on the iteration*2*, base consumption 7 MB, extra consumption 4 
MB (*57* %), liboscada.so 3.4 MB, ui_WebVision.so 0.85 MB
Debian 10 i386, GLibC 2.28, GCC 8.3.0 	151 	158 	162.5 	166 	166 	166 
Satiated on the iteration*3*, base consumption 7 MB, extra consumption 8 
MB (*114* %), liboscada.so 3.7 MB, ui_WebVision.so 0.9 MB
Debian 9 i386, GLibC 2.24, GCC 6.3.0 	125 	131 	132 	136 	136 	139 
Satiated on the iteration*5*, base consumption 6 MB, extra consumption 8 
MB (*133* %), liboscada.so 3.7 MB, ui_WebVision.so 0.9 MB
Debian 8 i386, GLibC 2.19, GCC 4.9.2 	92.5 	99 	101.5 	103 	103.5 	103.5 
	Satiated on the iteration*2*, base consumption 6.5 MB, extra 
consumption 4.5 (*69* %), liboscada.so 3.6 MB, ui_WebVision.so 0.94 MB
Debian 7 i386, GLibC 2.13, GCC 4.7.2 	70 	76 	76 	76 	77 	77 	Satiated 
on the iteration*2*, base consumption 6 MB, extra consumption 1 MB 
(*16* %), liboscada.so 3.6 MB, ui_WebVision.so 0.9 MB
ALTLinux 6 i386, GLibC 2.11.3, GCC 4.5.4 	69 	74 	75 	75 	75 	75 
Satiated on the iteration*2*, base consumption 5 MB, extra consumption 1 
MB (*20* %), liboscada.so 2.3 MB, ui_WebVision.so 0.9 MB


From the data we have the memory effectivity on AMD64 and I386 platform:

and the absolute initial size for the both platform:



I know about "the Memory Allocation Tunables" 
(https://www.gnu.org/software/libc/manual/html_node/Memory-Allocation-Tunables.html) 
and have tried them but:
- I have not got any effect from environments like to 
"GLIBC_TUNABLES=glibc.malloc.trim_threshold=128" on Debian 10
- If the tunables real work, why their do not apply globally (on the 
system level) to return the memory effectivity to the level of the 
Debian 7 (GLibC 2.13)?
- If the new memory allocator (into GLibC 2.28) is so good, how can I 
return its memory effectivity to the level of the Debian 7 (GLibC 2.13)?


The tested pr

Processed: reassign 705056 to libc6, fixed 705056 in 2.21-4, affects 705056, reassign 930003 to src:symfony ...

2019-07-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 705056 libc6
Bug #705056 {Done: Jakub Wilk } [initscripts,libc6] 
/etc/default/devpts instructions to set "mesg n" by default don't work
Bug reassigned from package 'initscripts,libc6' to 'libc6'.
Ignoring request to alter found versions of bug #705056 to the same values 
previously set
No longer marked as fixed in versions glibc/2.21-4.
> fixed 705056 2.21-4
Bug #705056 {Done: Jakub Wilk } [libc6] /etc/default/devpts 
instructions to set "mesg n" by default don't work
Marked as fixed in versions glibc/2.21-4.
> affects 705056 + initscripts
Bug #705056 {Done: Jakub Wilk } [libc6] /etc/default/devpts 
instructions to set "mesg n" by default don't work
Added indication that 705056 affects initscripts
> reassign 930003 src:symfony 3.4.22+dfsg-2
Bug #930003 {Done: David Prévot } [src:php7.3, src:symfony] 
php7.3 breaks symfony autopkgtest (maybe only deprecation warnings?)
Bug reassigned from package 'src:php7.3, src:symfony' to 'src:symfony'.
No longer marked as found in versions symfony/3.4.22+dfsg-2 and php7.3/7.3.6-1.
No longer marked as fixed in versions symfony/4.3.1+dfsg-1.
Bug #930003 {Done: David Prévot } [src:symfony] php7.3 
breaks symfony autopkgtest (maybe only deprecation warnings?)
Marked as found in versions symfony/3.4.22+dfsg-2.
> fixed 930003 4.3.1+dfsg-1
Bug #930003 {Done: David Prévot } [src:symfony] php7.3 
breaks symfony autopkgtest (maybe only deprecation warnings?)
Marked as fixed in versions symfony/4.3.1+dfsg-1.
> affects 930003 src:php7.3
Bug #930003 {Done: David Prévot } [src:symfony] php7.3 
breaks symfony autopkgtest (maybe only deprecation warnings?)
Added indication that 930003 affects src:php7.3
> notfound 731656 1:4.7-1
Bug #731656 {Done: Balint Reczey } [login] Please disable 
securetty by default
No longer marked as found in versions shadow/1:4.7-1.
> # do not close invalid bugs with the found version
> notfixed 896748 5.2.1-1
Bug #896748 {Done: Stig Sandbeck Mathisen } [varnish] systemd 
type should be set to forking?
No longer marked as fixed in versions varnish/5.2.1-1.
> notfixed 928680 1.8.1-1
Bug #928680 {Done: Daniel Echeverry } [openfortivpn] 
[openfortivpn] Since switching to buster openfortivpn can't connect to vpn 
anymore
No longer marked as fixed in versions openfortivpn/1.8.1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
705056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705056
731656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
896748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896748
928680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928680
930003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: severity of 930734 is wishlist

2019-07-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 930734 wishlist
Bug #930734 [glibc] glibc: Doesn't honor noudeb build profile
Severity set to 'wishlist' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
930734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930734
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Bug#910669 marked as pending in glibc

2019-07-26 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #910669 [src:glibc] glibc: Please remove transitional package 
multiarch-support
Added tag(s) pending.

-- 
910669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#705056: marked as done (/etc/default/devpts instructions to set "mesg n" by default don't work)

2019-07-26 Thread Debian Bug Tracking System
Your message dated Fri, 26 Jul 2019 16:39:41 +0200
with message-id <20190726143941.padkhqxgwo7dd...@jwilk.net>
and subject line Re: Bug#705056: /etc/default/devpts instructions to set "mesg 
n" by default don't work
has caused the Debian Bug report #705056,
regarding /etc/default/devpts instructions to set "mesg n" by default don't work
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.)


-- 
705056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: initscripts,libc6

/etc/default/devpts reads:
# Set to 600 to have `mesg n' be the default
TTYMODE=620

But this doesn't really work. Even if you mount /dev/pts with mode=600, 
your pty devices will end up with 620 permissions. This is because 
well-behaved software calls grantpt(), which changes the device 
permissions.


Either grantpt() should be fixed not to touch permissions if /dev/pts is 
a devpts fs (as it did in the past[0]) or initscripts should be fixed 
not to claim you can have "mesg n" by default.



[0] 
http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=292e3abebff9f94ca47c1a725a691cb6ed6cff5f

--
Jakub Wilk
--- End Message ---
--- Begin Message ---

Source: glibc
Source-Version: 2.21-4


[2013-04-09 17:13] Jakub Wilk 

/etc/default/devpts reads:
# Set to 600 to have `mesg n' be the default
TTYMODE=620

But this doesn't really work. Even if you mount /dev/pts with 
mode=600, your pty devices will end up with 620 permissions. This is 
because well-behaved software calls grantpt(), which changes the 
device permissions.

[...]
* Dmitry Bogatov , 2019-07-25, 19:07:
I just tried this -- remounted /dev/pts with mode=600 and started 
dvtm(1) and stterm(1). This resulted in /dev/pts/{0,1} with $USER:tty, 
600. So to be `TTYMODE' seems to work.


This has been fixed in glibc; see bug #806882.

--
Jakub Wilk--- End Message ---


Processed: Re: Bug#705056: /etc/default/devpts instructions to set "mesg n" by default don't work

2019-07-25 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 +moreinfo +unreproducible
Bug #705056 [initscripts,libc6] /etc/default/devpts instructions to set "mesg 
n" by default don't work
Added tag(s) moreinfo.
Bug #705056 [initscripts,libc6] /etc/default/devpts instructions to set "mesg 
n" by default don't work
Added tag(s) unreproducible.

-- 
705056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#910669: glibc: Please remove transitional package multiarch-support

2019-07-24 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #910669 [src:glibc] glibc: Please remove transitional package 
multiarch-support
Ignoring request to change severity of Bug 910669 to the same value.
> tag -1 - wontfix
Bug #910669 [src:glibc] glibc: Please remove transitional package 
multiarch-support
Removed tag(s) wontfix.

-- 
910669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#932384: marked as done (libc6: utmp broken)

2019-07-19 Thread Debian Bug Tracking System
Your message dated Fri, 19 Jul 2019 14:44:53 +0200
with message-id <20190719124453.gb2...@aurel32.net>
and subject line Re: Bug#932384: libc6: utmp broken
has caused the Debian Bug report #932384,
regarding libc6: utmp broken
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.)


-- 
932384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.28-10
Severity: important

After hitting #932380 I looked at the source code of GNU screen,
saw it uses the getutline(3) function, and compiled the example
from its manpage.

The output is not what I expected:

tglase@tglase:~ $ ./a.out
before adding entry:
tglase   :0   2019-07-18 16:07
after adding entry:
tglase   :0   2019-07-18 16:07
after removing entry:
tglase   :0   2019-07-18 16:07

This is the same, no matter whether I’m in GNU screen in xterm,
or just in xterm, or even on the Linux text console:

tglase@tglase:~ $ ./a.out
before adding entry:
tglase   tty2 2019-07-18 17:25
tglase   :0   2019-07-18 16:07
after adding entry:
tglase   tty2 2019-07-18 17:25
tglase   :0   2019-07-18 16:07
after removing entry:
tglase   tty2 2019-07-18 17:25
tglase   :0   2019-07-18 16:07

utmp entries cannot be added (and the GNU screen source code contains
curse^Wcomplaints about the GNU API for utmp lacking the ability to
return success/error information, so the applications cannot even de‐
tect this!), while the file is set up correctly:

tglase@tglase:~ $ ll /var/run/utmp
-rw-r--r-- 1 root utmp 4608 Jul 18 17:26 /var/run/utmp
tglase@tglase:~ $ w | cat
 17:27:33 up  1:21,  1 user,  load average: 1.35, 1.68, 2.12
USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
tglase   :0   -16:07   ?xdm?  14:24   0.03s 
/usr/bin/ck-launch-session /usr/bin/monkeysphere-validation-agent /bin/mksh 
/usr/share/tarent/autokde.d/loadenv.sh icewm-session


-- System Information:
Debian Release: bullseye/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), 
(100, 'experimental')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
control: severity 932384 important

On 2019-07-18 17:28, Thorsten Glaser wrote:
> Package: libc6
> Version: 2.28-10
> Severity: important

I fail to see how this bug has a major effect on the usability of the
glibc.

> After hitting #932380 I looked at the source code of GNU screen,
> saw it uses the getutline(3) function, and compiled the example
> from its manpage.

No it doesn't. It uses libutempter, which provides a setgid utmp binary
do to the job.

> The output is not what I expected:
> 
> tglase@tglase:~ $ ./a.out
> before adding entry:
> tglase   :0   2019-07-18 16:07
> after adding entry:
> tglase   :0   2019-07-18 16:07
> after removing entry:
> tglase   :0   2019-07-18 16:07
> 
> This is the same, no matter whether I’m in GNU screen in xterm,
> or just in xterm, or even on the Linux text console:
> 
> tglase@tglase:~ $ ./a.out
> before adding entry:
> tglase   tty2 2019-07-18 17:25
> tglase   :0   2019-07-18 16:07
> after adding entry:
> tglase   tty2 2019-07-18 17:25
> tglase   :0   2019-07-18 16:07
> after removing entry:
> tglase   tty2 2019-07-18 17:25
> tglase   :0   2019-07-18 16:07
> 
> utmp entries cannot be added (and the GNU screen source code contains
> curse^Wcomplaints about the GNU API for utmp lacking the ability to
> return success/error information, so the applications cannot even de‐
> tect this!), while the file is set up correctly:
> 
> tglase@tglase:~ $ ll /var/run/utmp
> -rw-r--r-- 1 root utmp 4608 Jul 18 17:26 /var/run/utmp

That's the issue, you need to have write access to the utmp file to be
able to update it (and also read access to read it). There is no magic
involved, the file and the function obey to the standard unix
permissions.

Therefore there is no bug, neither in glibc nor in the manpage. Closing
it.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net--- End Message ---


Processed: Re: Bug#932384: libc6: utmp broken

2019-07-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 932380 initscripts
Bug #932380 [screen] screen: Utmp slot not found -> not removed
Bug reassigned from package 'screen' to 'initscripts'.
No longer marked as found in versions screen/4.6.2-3.
Ignoring request to alter fixed versions of bug #932380 to the same values 
previously set
> found 932380 2.95-1
Bug #932380 [initscripts] screen: Utmp slot not found -> not removed
Marked as found in versions sysvinit/2.95-1.
> notfound 932380 2.93-8
Bug #932380 [initscripts] screen: Utmp slot not found -> not removed
Ignoring request to alter found versions of bug #932380 to the same values 
previously set
> retitle 932380 initscripts: /etc/init.d/bootmisc.sh: wrong /var/run/utmp 
> permissions
Bug #932380 [initscripts] screen: Utmp slot not found -> not removed
Changed Bug title to 'initscripts: /etc/init.d/bootmisc.sh: wrong /var/run/utmp 
permissions' from 'screen: Utmp slot not found -> not removed'.
> severity 932380 important
Bug #932380 [initscripts] initscripts: /etc/init.d/bootmisc.sh: wrong 
/var/run/utmp permissions
Severity set to 'important' from 'normal'
> unblock 932380 by 932384
Bug #932380 [initscripts] initscripts: /etc/init.d/bootmisc.sh: wrong 
/var/run/utmp permissions
932380 was blocked by: 932384
932380 was not blocking any bugs.
Removed blocking bug(s) of 932380: 932384
> block 932384 by 932380
Bug #932384 [libc6] libc6: utmp broken
932384 was not blocked by any bugs.
932384 was not blocking any bugs.
Added blocking bug(s) of 932384: 932380
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
932380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932380
932384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#932380: screen: Utmp slot not found -> not removed

2019-07-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 932380 by 932384
Bug #932380 [screen] screen: Utmp slot not found -> not removed
932380 was not blocked by any bugs.
932380 was not blocking any bugs.
Added blocking bug(s) of 932380: 932384
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
932380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#930884: marked as done (feature request: with Windows and FreeBSD and MacOS desktop, you can ship the libraries together with your application. With Linux desktop: still not :-(.)

2019-06-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Jun 2019 10:15:15 +0200
with message-id <20190627081515.ga11...@aurel32.net>
and subject line Bug#930884: feature request: with Windows and FreeBSD and 
MacOS desktop, you can ship the libraries together with your application. With 
Linux desktop: still not :-(.
has caused the Debian Bug report #930884,
regarding feature request: with Windows and FreeBSD and MacOS desktop, you can 
ship the libraries together with your application. With Linux desktop: still 
not :-(.
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.)


-- 
930884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: ld-linux.so.X

When we, I, write an application on Linux, we do installation from the 
repositories (or even the installation of "-dev" packages in addition if "soft 
symlink" is missing) for the needed shared libraries (fore exeample: Firebird, 
...).
But, once the application is finished, I will uninstall everything about 
Firebird, and from the content of the download of its *.tar.gz, I must create a 
client installation with AppImage + its yaml scripts (my choice). It's not so 
easy.
The problem is that on *nix the escape like on Window or MacOS ( putting dlls 
together with the application !!!) doesn't work, making versioning issues more 
complex, specially when using official packaging systems ==> "DLL-hell" now 
only exists under *nix \ Linux.

Can Linux improve its binary compatibility and be less forced in its package 
management (specially: versioning on Desktop. It's really always "DLL-hell": if 
you want to start distributing the libraries\packages and resulting files 
apart, on Linux Desktop, then you get into the dependency problems).

Honestly, I think that the Linux ELF's program loader ( ld-linux.so.X ), on 
Linux idiosyncrasy directories, would require an evolution that would make 
Linux as convenient as Windows or MacOS  from the point of view of desktop 
developments, i. e. starting by ***first*** looking in the same directory as 
the loaded application, if the NEEDED library would not be there, by the best 
of luck.

-- 
Best regards
--- End Message ---
--- Begin Message ---
Hi,

On 2019-06-21 22:37, eric.mou...@laposte.net wrote:
> 
> Package: ld-linux.so.X
> 
> When we, I, write an application on Linux, we do installation from the 
> repositories (or even the installation of "-dev" packages in addition if 
> "soft symlink" is missing) for the needed shared libraries (fore exeample: 
> Firebird, ...).
> But, once the application is finished, I will uninstall everything about 
> Firebird, and from the content of the download of its *.tar.gz, I must create 
> a client installation with AppImage + its yaml scripts (my choice). It's not 
> so easy.
> The problem is that on *nix the escape like on Window or MacOS ( putting dlls 
> together with the application !!!) doesn't work, making versioning issues 
> more complex, specially when using official packaging systems ==> "DLL-hell" 
> now only exists under *nix \ Linux.
> 
> Can Linux improve its binary compatibility and be less forced in its package 
> management (specially: versioning on Desktop. It's really always "DLL-hell": 
> if you want to start distributing the libraries\packages and resulting files 
> apart, on Linux Desktop, then you get into the dependency problems).
> 
> Honestly, I think that the Linux ELF's program loader ( ld-linux.so.X ), on 
> Linux idiosyncrasy directories, would require an evolution that would make 
> Linux as convenient as Windows or MacOS  from the point of view of desktop 
> developments, i. e. starting by ***first*** looking in the same directory as 
> the loaded application, if the NEEDED library would not be there, by the best 
> of luck.

While I think it's a bad idea, especially from security point of view,
what you ask is already implemented on GNU/Linux for many years. This
feature is called rpath, and allows one to provide a list of paths where
to look for the NEEDED libraries. You can use the $ORIGIN keyword to
specify a path relative to the binary, which is exactly what you want.

For example:

$ gcc -o main ./main.c -lz
$ ldd ./main 
linux-vdso.so.1 (0x7ffda8dd7000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fda95b4f000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fda9598e000)
/li

Processed: severity of 930884 is wishlist

2019-06-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 930884 wishlist
Bug #930884 [src:glibc] feature request: with Windows and FreeBSD and MacOS 
desktop, you can ship the libraries together with your application. With Linux 
desktop: still not :-(.
Severity set to 'wishlist' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
930884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: notfound 930808 in 2.28-10

2019-06-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfound 930808 2.28-10
Bug #930808 {Done: Vincent Hobeïka } [libc6] libc6: 
${PLATFORM} is expanded as haswell instead of x86_64
No longer marked as found in versions glibc/2.28-10.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
930808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: reassign 930884 to src:glibc, reassign 930914 to sponsorship-requests, reassign 931080 to wnpp ...

2019-06-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 930884 src:glibc
Bug #930884 [ld-linux.so.x] feature request: with Windows and FreeBSD and MacOS 
desktop, you can ship the libraries together with your application. With Linux 
desktop: still not :-(.
Warning: Unknown package 'ld-linux.so.x'
Bug reassigned from package 'ld-linux.so.x' to 'src:glibc'.
Ignoring request to alter found versions of bug #930884 to the same values 
previously set
Ignoring request to alter fixed versions of bug #930884 to the same values 
previously set
> reassign 930914 sponsorship-requests
Bug #930914 {Done: Stephan Lachnit } 
[pseudo-package] RFS: psu-targets/1-1 [ITP]
Warning: Unknown package 'pseudo-package'
Bug reassigned from package 'pseudo-package' to 'sponsorship-requests'.
Ignoring request to alter found versions of bug #930914 to the same values 
previously set
Ignoring request to alter fixed versions of bug #930914 to the same values 
previously set
> reassign 931080 wnpp
Bug #931080 [asciiflowqt] asciiflowqt: Wish for new package: asciiflowqt
Warning: Unknown package 'asciiflowqt'
Bug reassigned from package 'asciiflowqt' to 'wnpp'.
No longer marked as found in versions v0.3.3.
Ignoring request to alter fixed versions of bug #931080 to the same values 
previously set
> reassign 929112 src:rustc 1.32.0+dfsg1-3
Bug #929112 [libstd-rust-1.32] libstd-rust-1.32: Packaging a more recent rust 
version
Warning: Unknown package 'libstd-rust-1.32'
Bug reassigned from package 'libstd-rust-1.32' to 'src:rustc'.
No longer marked as found in versions rustc/1.32.0+dfsg1-3.
Ignoring request to alter fixed versions of bug #929112 to the same values 
previously set
Bug #929112 [src:rustc] libstd-rust-1.32: Packaging a more recent rust version
Marked as found in versions rustc/1.32.0+dfsg1-3.
> reassign 930737 src:linux
Bug #930737 [hibernation] hibernation: keyboard inactive after hibernation mode
Warning: Unknown package 'hibernation'
Bug reassigned from package 'hibernation' to 'src:linux'.
No longer marked as found in versions hibernate.
Ignoring request to alter fixed versions of bug #930737 to the same values 
previously set
> reassign 931066 xserver-xorg-core 2:1.20.4-1
Bug #931066 [server-xorg-core] xserver-xorg-core:  X crash - libfb
Warning: Unknown package 'server-xorg-core'
Bug reassigned from package 'server-xorg-core' to 'xserver-xorg-core'.
No longer marked as found in versions 2:1.20.4-1.
Ignoring request to alter fixed versions of bug #931066 to the same values 
previously set
Bug #931066 [xserver-xorg-core] xserver-xorg-core:  X crash - libfb
Marked as found in versions xorg-server/2:1.20.4-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
929112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929112
930737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930737
930884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930884
930914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930914
931066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931066
931080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: notfixed 930808 in 2.28-10

2019-06-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # unconfuse the bts
> notfixed 930808 2.28-10
Bug #930808 {Done: Vincent Hobeïka } [libc6] libc6: 
${PLATFORM} is expanded as haswell instead of x86_64
No longer marked as fixed in versions libc6/2.28-10.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
930808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#930808: marked as done (libc6: ${PLATFORM} is expanded as haswell instead of x86_64)

2019-06-21 Thread Debian Bug Tracking System
Your message dated Sat, 22 Jun 2019 01:32:36 +0200
with message-id 

and subject line Re: Bug#930808: libc6: ${PLATFORM} is expanded as haswell 
instead of x86_64
has caused the Debian Bug report #930808,
regarding libc6: ${PLATFORM} is expanded as haswell instead of x86_64
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.)


-- 
930808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.28-10
Severity: important

Dear Maintainer,

It seems ${PLATFORM} is wrongly expanded on x86_64 architectures with
libc6 2.28. This leads to troubles while referencing libraries.

This doesn't seem related to the usage of curly braces.

You can find the reproductions steps below:

$ arch
x86_64

$ strace -ELD_PRELOAD='/sss/$PLATFORM/'  -s300  /bin/cat
execve("/bin/cat", ["/bin/cat"], 0x5607e51d5490 /* 62 vars */) = 0
brk(NULL)   = 0x560cc39d5000
readlink("/proc/self/exe", "/bin/cat", 4096) = 8
openat(AT_FDCWD, "/sss/haswell/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)

$ strace -ELD_PRELOAD='/sss/${PLATFORM}/'  -s300  /bin/cat
execve("/bin/cat", ["/bin/cat"], 0x563dc5b51490 /* 62 vars */) = 0
brk(NULL)   = 0x55f8d420d000
readlink("/proc/self/exe", "/bin/cat", 4096) = 8
openat(AT_FDCWD, "/sss/haswell/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)

Feel free to ask me any additionnal information.

Best regards,

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (900, 'testing'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libc6 depends on:
ii  libgcc1  1:8.3.0-6

Versions of packages libc6 recommends:
ii  libidn2-0  2.0.5-1

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.71
pn  glibc-doc  
ii  libc-l10n  2.28-10
ii  locales2.28-10

-- debconf information:
  glibc/disable-screensaver:
  glibc/kernel-too-old:
  glibc/restart-failed:
  glibc/upgrade: true
* libraries/restart-without-asking: false
  glibc/kernel-not-supported:
* glibc/restart-services: cups cron
--- End Message ---
--- Begin Message ---
Package: libc6
Version: 2.28-10

Thanks for your thorough explanation.

After reading more the documentation regarding the $PLATFORM token I
fully agree with you. There is no bug here.
I'll head up to the writers of the library to fix the problem there.
Thanks a lot for your time and precious feedback.

-- 
Vincent Hobeïka--- End Message ---


Processed: reassign 761509 to src:glibc, reassign 607573 to src:glibc, reassign 696785 to src:glibc ...

2019-06-09 Thread Debian Bug Tracking System
 values 
previously set
Ignoring request to alter fixed versions of bug #47896 to the same values 
previously set
Bug #47896 [src:glibc] MS_SYNC Macros Missing from Hurd development environment
The source 'glibc' and version '2.1.2-0pre12' do not appear to match any binary 
packages
Marked as found in versions glibc/2.1.2-0pre12.
> reassign 666454 src:glibc 2.11.3-2
Bug #666454 [libc0.1-dev] sizeof(struct sigevent) is smaller than the kernel 
definition
Warning: Unknown package 'libc0.1-dev'
Bug reassigned from package 'libc0.1-dev' to 'src:glibc'.
No longer marked as found in versions eglibc/2.11.3-2.
Ignoring request to alter fixed versions of bug #666454 to the same values 
previously set
Bug #666454 [src:glibc] sizeof(struct sigevent) is smaller than the kernel 
definition
The source 'glibc' and version '2.11.3-2' do not appear to match any binary 
packages
Marked as found in versions glibc/2.11.3-2.
> reassign 739281 src:glibc
Bug #739281 [libc0.1-dev] provides sendfile() prototype (in ) 
but no sendfile symbol
Warning: Unknown package 'libc0.1-dev'
Bug reassigned from package 'libc0.1-dev' to 'src:glibc'.
Ignoring request to alter found versions of bug #739281 to the same values 
previously set
Ignoring request to alter fixed versions of bug #739281 to the same values 
previously set
> reassign 629556 src:glibc 2.13-4
Bug #629556 [libc0.1-dev] please provide getvfsbyname() and getosreldate()
Warning: Unknown package 'libc0.1-dev'
Bug reassigned from package 'libc0.1-dev' to 'src:glibc'.
No longer marked as found in versions eglibc/2.13-4.
Ignoring request to alter fixed versions of bug #629556 to the same values 
previously set
Bug #629556 [src:glibc] please provide getvfsbyname() and getosreldate()
The source 'glibc' and version '2.13-4' do not appear to match any binary 
packages
Marked as found in versions glibc/2.13-4.
> reassign 630843 src:glibc 2.13-4
Bug #630843 [libc0.1-dev] missing nfssvc() and nlm_syscall()
Warning: Unknown package 'libc0.1-dev'
Bug reassigned from package 'libc0.1-dev' to 'src:glibc'.
No longer marked as found in versions eglibc/2.13-4.
Ignoring request to alter fixed versions of bug #630843 to the same values 
previously set
Bug #630843 [src:glibc] missing nfssvc() and nlm_syscall()
The source 'glibc' and version '2.13-4' do not appear to match any binary 
packages
Marked as found in versions glibc/2.13-4.
> reassign 762677 src:glibc 2.19-11
Bug #762677 [libc0.3] libc0.3: Hurd futimens does not support UTIME_NOW
Warning: Unknown package 'libc0.3'
Bug reassigned from package 'libc0.3' to 'src:glibc'.
No longer marked as found in versions glibc/2.19-11.
Ignoring request to alter fixed versions of bug #762677 to the same values 
previously set
Bug #762677 [src:glibc] libc0.3: Hurd futimens does not support UTIME_NOW
Marked as found in versions glibc/2.19-11.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
187391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=187391
288105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=288105
413734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413734
47896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=47896
607573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607573
629556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629556
630843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630843
666454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666454
696785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696785
739281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739281
753223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753223
761509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761509
762677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762677
897335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897335
923067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: user release.debian....@packages.debian.org, usertagging 926699, tagging 926699

2019-06-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 926699 buster-can-defer
There were no usertags set.
Usertags are now: buster-can-defer.
> tags 926699 + buster-ignore
Bug #926699 [libc6-x32,libc6-i386] libc6-{i386,x32}: installing, removing, 
reinstalling in a --merged-usr system results in unmerged /lib{32,x32}
Added tag(s) buster-ignore.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
926699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: notfound 928405 in 2.28-10

2019-05-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfound 928405 2.28-10
Bug #928405 {Done: Aurelien Jarno } [src:glibc] Package: 
 Version: <2.28-10>
No longer marked as found in versions glibc/2.28-10.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
928405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: reassign 928405 to src:glibc, notfixed 926215 in 2.6~20180302-1, tagging 926215

2019-05-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 928405 src:glibc 2.28-10
Bug #928405 {Done: Aurelien Jarno } [] 
Package:  Version: <2.28-10>
Warning: Unknown package ''
Bug reassigned from package '' to 'src:glibc'.
Ignoring request to alter found versions of bug #928405 to the same values 
previously set
Ignoring request to alter fixed versions of bug #928405 to the same values 
previously set
Bug #928405 {Done: Aurelien Jarno } [src:glibc] Package: 
 Version: <2.28-10>
Marked as found in versions glibc/2.28-10.
> notfixed 926215 2.6~20180302-1
Bug #926215 {Done: Santiago Vila } [src:dune-pdelab] 
dune-pdelab: testpk fails with assertion failure
No longer marked as fixed in versions 2.6~20180302-1.
> tags 926215 + unreproducible
Bug #926215 {Done: Santiago Vila } [src:dune-pdelab] 
dune-pdelab: testpk fails with assertion failure
Added tag(s) unreproducible.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
926215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926215
928405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#928405: marked as done (Package: Version: <2.28-10>)

2019-05-04 Thread Debian Bug Tracking System
Your message dated Sat, 4 May 2019 21:16:30 +0200
with message-id <20190504191630.gb3...@aurel32.net>
and subject line Re: Bug#928405: Package:  Version: <2.28-10>
has caused the Debian Bug report #928405,
regarding Package:  Version: <2.28-10>
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.)


-- 
928405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: 
Version: <2.28-10>

Wysłane z aplikacji Poczta dla Windows 10



pl.po
Description: Binary data
--- End Message ---
--- Begin Message ---
On 2019-05-03 22:44, N wrote:
> Package: 
> Version: <2.28-10>
> 
> Wysłane z aplikacji Poczta dla Windows 10
> 



-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net--- End Message ---


Bug#913929: marked as done (pldd never stops)

2019-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 01 May 2019 17:49:10 +
with message-id 
and subject line Bug#913929: fixed in glibc 2.28-10
has caused the Debian Bug report #913929,
regarding pldd never stops
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.)


-- 
913929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc-bin
Version: 2.27-8
Severity: normal

Hi,

I've ran `pldd $$`, but it never comes to an end. I've killed the process
with SIGQUIT and got this backtrace:

```
   PID: 10556 (pldd)
   UID: 1000 (joerg)
   GID: 1000 (joerg)
Signal: 3 (QUIT)
 Timestamp: Sat 2018-11-17 08:33:56 CET (5min ago)
  Command Line: pldd 953
Executable: /usr/bin/pldd
 Control Group: /user.slice/user-1000.slice/session-1.scope
  Unit: session-1.scope
 Slice: user-1000.slice
   Session: 1
 Owner UID: 1000 (joerg)
   Boot ID: 87a38c39c06e4c36b4eebb33c4e3e2ac
Machine ID: 523cb54753234ed08c13ec497d0d3b64
  Hostname: zenbook
   Storage: 
/var/lib/systemd/coredump/core.pldd.1000.87a38c39c06e4c36b4eebb33c4e3e2ac.10556.154244003600.lz4
   Message: Process 10556 (pldd) of user 1000 dumped core.

Stack trace of thread 10556:
#0  0x7f81a7d6a7a7 __libc_pread64 (libc.so.6)
#1  0x557c5866224d n/a (pldd)
#2  0x557c58661792 n/a (pldd)
#3  0x7f81a7ca5b17 __libc_start_main (libc.so.6)
#4  0x557c5866184a n/a (pldd)

[New LWP 10556]
Core was generated by `pldd 953'.
Program terminated with signal SIGQUIT, Quit.
#0  0x7f81a7d6a7a7 in __libc_pread64 (fd=4, buf=0x7ffebbcd5900, count=16, 
offset=140221672822504) at ../sysdeps/unix/sysv/linux/pread64.c:29
29  ../sysdeps/unix/sysv/linux/pread64.c: Datei oder Verzeichnis nicht 
gefunden.
#0  0x7f81a7d6a7a7 in __libc_pread64 (fd=4, buf=0x7ffebbcd5900, count=16, 
offset=140221672822504) at ../sysdeps/unix/sysv/linux/pread64.c:29
resultvar = 16
sc_ret = 
sc_ret = 
resultvar = 
resultvar = 
__arg4 = 
__arg3 = 
__arg2 = 
__arg1 = 
_a4 = 
_a3 = 
_a2 = 
_a1 = 
sc_cancel_oldtype = 
resultvar = 
resultvar = 
__arg4 = 
__arg3 = 
__arg2 = 
__arg1 = 
_a4 = 
_a3 = 
_a2 = 
_a1 = 
#1  0x557c5866224d in find_maps64 (pid=, auxv=, auxv_size=) at pldd-xx.c:230
ln = {name = 140221672822528, next = 0}
m = {l_addr = 93944802607104, l_name = 140221672822528, l_ld = 
93944803440424, l_next = 140221672822544, l_prev = 0, l_real = 140221672821104, 
l_ns = 0, l_libname = 140221672822504}
name_offset = 140221672822528
phdr = 
phnum = 
phent = 
auxvXX = 
p = 
offset = 
list = 
interp = 
tmpbuf = {data = 0x7ffebbcd5960, length = 1024, __space = {__align = 
{__max_align_ll = 0, __max_align_ld = }, __c = '\000' 
, 
"\360\231\220\377\177\000\000\260\233\377\346\207\177\000\000H\363\231\220\377\177\000\000\000\260\372\346\207\177\000\000p\221\377\346\207\177\000\000\020\227\377\346\207\177\000\000\000\000\000\000\000\000\000\000\210\233\377\346\207\177",
 '\000' , 
"\240v\377\346\207\177\000\000\260v\377\346\207\177\000\000\300v\377\346\207\177",
 '\000' , 
"\250\363\231\220\377\177\000\000\270\363\231\220\377\177", '\000' , "H\363\231\220\377\177\000\000\000\000\000\000\000\000\000\000"...}}
status = 0
#2  0x557c58661792 in get_process_info (pid=953, dfd=3) at pldd.c:338
fd = 5
auxv = 0x557c59f6b480
retval = 
e_ident = "\177ELF\002\001\001\000\000\000\000\000\000\000\000"
auxv_size = 320
fd = 
e_ident = 
auxv_size = 
auxv = 
retval = 
n = 
#3  main (argc=, argv=) at pldd.c:193
remaining = 1
__PRETTY_FUNCTION__ = "main"
endp = 0x557c59f6b4f6 ""
pid = 953
buf = 
"/proc/953\000ͻ\376\177\000\000\001\000\000\000\000\000\000\000\265Iҧ\201\177"
dfd = 
exebuf = {data = 0x7ffebbcd5e20, length = 1024, __space = {__align = 
{__max_align_ll = 7526493746400682543, __max_align_ld = }, 
__c = 
"/bin/zsh\000_ͻ\376\177\000\000\210\t䧁\177\000\000\360\331见\177\000\000\000\000\000\000\000\000\000\000\027\362槁\177\000\000\001\000\000\

Bug#576484: marked as done (libc6-prof: segmentation fault when using profiling with pthread.)

2019-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 1 May 2019 13:42:33 +0200
with message-id <20190501114233.ga10...@aurel32.net>
and subject line libc6-prof has been removed in glibc 2.19-12
has caused the Debian Bug report #576484,
regarding libc6-prof: segmentation fault when using profiling with pthread.
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.)


-- 
576484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-prof
Version: 2.10.2-6
Severity: important

# cat a.c  int main() { return 0; } # gcc -g -pg a.c -o a  -static-libgcc -lc_p
# ./a Exit code 0 # gcc -g -pg a.c -o a  -static-libgcc -lc_p -pthread  # ./a
Segmentation fault (core dumped) # gdb ./a ./core  [New Thread 9335]
warning: Can't read pathname for load map: Input/output error. Reading symbols
from /lib/i686/cmov/libpthread.so.0...Reading symbols from
/usr/lib/debug/lib/i686/cmov/libpthread-2.10.2.so...done. done. Loaded symbols
for /lib/i686/cmov/libpthread.so.0 Reading symbols from
/lib/i686/cmov/libc.so.6...Reading symbols from
/usr/lib/debug/lib/i686/cmov/libc-2.10.2.so...done. done. Loaded symbols for
/lib/i686/cmov/libc.so.6 Reading symbols from /lib/ld-linux.so.2...Reading
symbols from /usr/lib/debug/lib/ld-2.10.2.so...done. done. Loaded symbols for
/lib/ld-linux.so.2 Core was generated by `./a'. Program terminated with signal
11, Segmentation fault. #0  0x0807fed1 in _dl_get_tls_static_info () (gdb) bt
#0  0x0807fed1 in _dl_get_tls_static_info () #1  0x400425ff in
__pthread_initialize_minimal_internal () at nptl-init.c:387 #2  0x40041df8 in
_init () at /build/buildd-eglibc_2.10.2-6-i386-fHPOAN/eglibc-2.10.2/build-
tree/i386-i686/nptl/crti.S:24 #3  0x4000e554 in call_init (l=0x40020858,
argc=1, argv=0xbfaa6734,  env=0xbfaa673c) at dl-init.c:70 #4  0x4000e6e6 in
_dl_init (main_map=0x4001d670, argc=1, argv=0xbfaa6734,  env=0xbfaa673c) at
dl-init.c:100 #5  0x488f in _dl_start_user () from /lib/ld-linux.so.2 (gdb)
Using -lpthread also gives this error. Removing -pthread from gcc command line
resolves problem in test program.   Unfortunetly in my program i'm using
threads, and after removing -pthread, i have linking error.  recursive.o: In
function `launch_thread': /maradns-1.4.03/server/recursive.c:3544: undefined
reference to `pthread_create'   I found that using -lpthread_p resolves problem
in my test program (it links and runs correctly), but then in my main program i
got on linking this:  /usr/lib/gcc/i486-linux-
gnu/4.4.3/../../../../lib/libpthread_p.a(lowlevellock.op): In function
`__lll_lock_wait_private': /build/buildd-eglibc_2.10.2-6-i386-fHPOAN/eglibc-2.1
0.2/nptl/../nptl/sysdeps/unix/sysv/linux/i386/i486/lowlevellock.S:76: multiple
definition of `__lll_lock_wait_private' /usr/lib/gcc/i486-linux-
gnu/4.4.3/../../../../lib/libc_p.a(libc-lowlevellock.op):(.text+0x0): first
defined here /usr/lib/gcc/i486-linux-
gnu/4.4.3/../../../../lib/libpthread_p.a(lowlevellock.op): In function
`__lll_unlock_wake_private': /build/buildd-eglibc_2.10.2-6-i386-fHPOAN/eglibc-2
..10.2/nptl/../nptl/sysdeps/unix/sysv/linux/i386/i486/lowlevellock.S:326:
multiple definition of `__lll_unlock_wake_private' /usr/lib/gcc/i486-linux-
gnu/4.4.3/../../../../lib/libc_p.a(libc-lowlevellock.op):(.text+0x30): first
defined hereCould you add this information to
/usr/share/doc/libc6-prof/README.Debian , and solve problem with multiple
definitions?   I also found that executable is probably not linked (compiler
done something wrong) correctly:  # ldd ./a linux-gate.so.1 =>
(0x4001e000) libpthread.so.0 => /lib/i686/cmov/libpthread.so.0
(0x4003e000) libc.so.6 => /lib/i686/cmov/libc.so.6 (0x40057000)
/lib/ld-linux.so.2 (0x4000) #  Thanks.


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.34-rc2-sredniczarny-00184-g01e7770 (PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to pl_PL.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc6-prof depends on:
ii  libc6 2.10.2-6   Embedded GNU C Library: Shared lib

libc6-prof recommends no packages.

libc6-prof suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 2.19-12

libc6-prof has been removed in glibc 2.19-12, closing the corresponding
bugs.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net--- End Message ---


Bug#551154: marked as done (libc6-prof: undefined reference to `_dl_prof_resolve')

2019-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 1 May 2019 13:42:33 +0200
with message-id <20190501114233.ga10...@aurel32.net>
and subject line libc6-prof has been removed in glibc 2.19-12
has caused the Debian Bug report #551154,
regarding libc6-prof: undefined reference to `_dl_prof_resolve'
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.)


-- 
551154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-prof
Version: 2.7-18
Severity: important


$ cat myprog.c
int main(void)
{
  return 0;
}
$ gcc -g -pg -o myprog myprog.c -static-libgcc -lc_p
/usr/lib/gcc/powerpc-linux-gnu/4.3.2/../../../../lib/libc_p.a(dl-machine.op): 
In function `__elf_machine_runtime_setup':
(.text+0xd56): undefined reference to `_dl_prof_resolve'
/usr/lib/gcc/powerpc-linux-gnu/4.3.2/../../../../lib/libc_p.a(dl-machine.op): 
In function `__elf_machine_runtime_setup':
(.text+0xd5a): undefined reference to `_dl_prof_resolve'
collect2: ld returned 1 exit status
$

Note the gcc command line above is an exact copy of the example in
README.Debian, but it doesn't work. I can't find a way to get this
_dl_prof_resolve linked in. nm /lib/lib* /usr/lib/lib* finds it only in
/usr/lib/libc.a

I haven't made much of an effort to find out what _dl_prof_resolve is
supposed to do, but I did notice that it's defined in
sysdeps/powerpc/powerpc32/dl-trampoline.S, inside #ifndef PROF, which makes
me wonder, is that backwards? A function with "prof" in its name, that's
defined everywhere but the profiling library? Could I fix this by taking the
'n' out of #ifndef?

-- System Information:
Debian Release: 5.0.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: powerpc (ppc)

Kernel: Linux 2.6.31.2
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc6-prof depends on:
ii  libc6 2.7-18 GNU C Library: Shared libraries

libc6-prof recommends no packages.

libc6-prof suggests no packages.

-- debconf-show failed


--- End Message ---
--- Begin Message ---
Version: 2.19-12

libc6-prof has been removed in glibc 2.19-12, closing the corresponding
bugs.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net--- End Message ---


Bug#589755: marked as done (Segfaults/FPEs using -lc_p)

2019-05-01 Thread Debian Bug Tracking System
Your message dated Wed, 1 May 2019 13:42:33 +0200
with message-id <20190501114233.ga10...@aurel32.net>
and subject line libc6-prof has been removed in glibc 2.19-12
has caused the Debian Bug report #589755,
regarding Segfaults/FPEs using -lc_p
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.)


-- 
589755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-prof
Version: 2.7-18lenny4

Take the example program (example1) at

http://www.ibm.com/developerworks/library/l-gnuprof.html

(source appended at end for ease of reference).

ed@sagittarius:~/tmp$ gcc example.c -pg -o example -static-libgcc -lc_p
example.c: In function ‘main’:
example.c:27: warning: incompatible implicit declaration of built-in
function ‘exit’
ed@sagittarius:~/tmp$ ./example
Usage ./example 
ed@sagittarius:~/tmp$ ./example 100
No of iterations = 100
ed@sagittarius:~/tmp$

Now try linking any other library, e.g. zlib (4 places in link order shown):

ed@sagittarius:~/tmp$ gcc example.c -pg -o example -static-libgcc -lc_p -lz
example.c: In function ‘main’:
example.c:27: warning: incompatible implicit declaration of built-in
function ‘exit’
ed@sagittarius:~/tmp$ ./example 100
Floating point exception
ed@sagittarius:~/tmp$

ed@sagittarius:~/tmp$ gcc example.c -pg -o example -lz -static-libgcc -lc_p
example.c: In function ‘main’:
example.c:27: warning: incompatible implicit declaration of built-in
function ‘exit’
ed@sagittarius:~/tmp$ ./example 100
Floating point exception
ed@sagittarius:~/tmp$

ed@sagittarius:~/tmp$ gcc example.c -pg -o example  -static-libgcc -lz -lc_p
example.c: In function ‘main’:
example.c:27: warning: incompatible implicit declaration of built-in
function ‘exit’
ed@sagittarius:~/tmp$ ./example 100
Floating point exception
ed@sagittarius:~/tmp$

ed@sagittarius:~/tmp$ gcc example.c -lz -pg -o example  -static-libgcc -lc_p
example.c: In function ‘main’:
example.c:27: warning: incompatible implicit declaration of built-in
function ‘exit’
ed@sagittarius:~/tmp$ ./example 100
Floating point exception

Now try specifying -static (e.g. there are many libraries in your program)

ed@sagittarius:~/tmp$ gcc example.c -pg -o example -static -static-libgcc -lc_p
example.c: In function ‘main’:
example.c:27: warning: incompatible implicit declaration of built-in
function ‘exit’
ed@sagittarius:~/tmp$ ./example 100
Segmentation fault

ed@sagittarius:~/tmp$ gcc example.c -pg -o example -static-libgcc -lc_p -static
example.c: In function ‘main’:
example.c:27: warning: incompatible implicit declaration of built-in
function ‘exit’
ed@sagittarius:~/tmp$ ./example 100
Segmentation fault

Thus it appears with this version you can only use -lc_p to debug
programs with no external dependencies, because you can't link other
libraries, and if you could, you still couldn't link them statically
to get proper gprof output.

I can't find any other reference to this behaviour; if it's just a
documentation problem, I'm happy to write the documentation if someone
tells me what the actual correct behaviour is (or necessary
limitations are).

Example program:

#include 

int a(void) {
  int i=0,g=0;
  while(i++<10)
  {
 g+=i;
  }
  return g;
}
int b(void) {
  int i=0,g=0;
  while(i++<40)
  {
g+=i;
  }
  return g;
}

int main(int argc, char** argv)
{
   int iterations;

   if(argc != 2)
   {
  printf("Usage %s \n", argv[0]);
  exit(-1);
   }
   else
  iterations = atoi(argv[1]);

   printf("No of iterations = %d\n", iterations);

   while(iterations--)
   {
  a();
  b();
   }
}


--- End Message ---
--- Begin Message ---
Version: 2.19-12

libc6-prof has been removed in glibc 2.19-12, closing the corresponding
bugs.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net--- End Message ---


Processed: Bug #913929 in glibc marked as pending

2019-04-30 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #913929 [libc-bin] pldd never stops
Added tag(s) pending.

-- 
913929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: reassign 776994 to src:glibc, reassign 784171 to src:glibc, reassign 814078 to src:glibc ...

2019-04-30 Thread Debian Bug Tracking System
.org/cgi-bin/bugreport.cgi?bug=91815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#927914: marked as done (glibc: deal with Japanese new era "令和 (Reiwa)")

2019-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2019 22:49:48 +
with message-id 
and subject line Bug#927914: fixed in glibc 2.28-9
has caused the Debian Bug report #927914,
regarding glibc: deal with Japanese new era "令和 (Reiwa)"
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.)


-- 
927914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: glibc
tags: l10n, patch

Hi,

 To deal with Japanese new era "令和 (Reiwa)" (from 1st May), please
 add attached patch that is taken from upstream(*)

 It should be applied to stretch as well.

 (*) 
https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=7423da211d1490d9fc76c2f0ce49e5dd90ea9bcc;hp=4aeff335ca19286ee2382d8eba794ae5fd49281a


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp
>From 3a660291290fd6e65db1f17fbfff67fa4ef2bc99 Mon Sep 17 00:00:00 2001
From: Hideki Yamane 
Date: Thu, 25 Apr 2019 10:33:00 +0900
Subject: [PATCH] add localedata/locale-ja_JP-reiwa_era.diff

---
 .../localedata/locale-ja_JP-reiwa_era.diff| 30 +++
 debian/patches/series |  1 +
 2 files changed, 31 insertions(+)
 create mode 100644 debian/patches/localedata/locale-ja_JP-reiwa_era.diff

diff --git a/debian/patches/localedata/locale-ja_JP-reiwa_era.diff b/debian/patches/localedata/locale-ja_JP-reiwa_era.diff
new file mode 100644
index ..141ee8a4
--- /dev/null
+++ b/debian/patches/localedata/locale-ja_JP-reiwa_era.diff
@@ -0,0 +1,30 @@
+Index: glibc/NEWS
+===
+--- glibc.orig/NEWS
 glibc/NEWS
+@@ -7,6 +7,10 @@ using `glibc' in the "product" field.
+ 
+ Version 2.28.1
+ 
++Major new features:
++
++* The entry for the new Japanese era has been added for ja_JP locale.
++
+ Deprecated and removed features, and other changes affecting compatibility:
+ 
+ * For powercp64le ABI, Transactional Lock Elision is now enabled iff kernel
+Index: glibc/localedata/locales/ja_JP
+===
+--- glibc.orig/localedata/locales/ja_JP
 glibc/localedata/locales/ja_JP
+@@ -14946,7 +14946,9 @@ am_pm	"";""
+ 
+ t_fmt_ampm "%p%I%M%S"
+ 
+-era	"+:2:1990//01//01:+*::%EC%Ey";/
++era	"+:2:2020//01//01:+*::%EC%Ey";/
++	"+:1:2019//05//01:2019//12//31::%EC";/
++	"+:2:1990//01//01:2019//04//30::%EC%Ey";/
+ 	"+:1:1989//01//08:1989//12//31::%EC";/
+ 	"+:2:1927//01//01:1989//01//07::%EC%Ey";/
+ 	"+:1:1926//12//25:1926//12//31::%EC";/
diff --git a/debian/patches/series b/debian/patches/series
index 461d8245..d75630cb 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -20,6 +20,7 @@ localedata/submitted-en_AU-date_fmt.diff
 localedata/submitted-es_MX-decimal_point.diff
 localedata/submitted-it_IT-thousands_sep.diff
 localedata/git-en_US-date_fmt.diff
+localedata/locale-ja_JP-reiwa_era.diff
 
 alpha/local-gcc4.1.diff
 alpha/submitted-dl-support.diff
-- 
2.20.1

--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.28-9

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 927...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 25 Apr 2019 21:12:03 +0200
Source: glibc
Architecture: source
Version: 2.28-9
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 924612 927914
Changes:
 glibc (2.28-9) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix heap-based buffer over-read in regular-expression matching
   (CVE-2019-9169).  Closes: #924612.
 - Add entry for the new Japanese era to the ja_JP locale.  Closes:
   #927914.
 .
   [ Adam Conrad ]
   * debian/patches/arm/unsu

Bug#924612: marked as done (CVE-2019-9169)

2019-04-25 Thread Debian Bug Tracking System
Your message dated Thu, 25 Apr 2019 22:49:47 +
with message-id 
and subject line Bug#924612: fixed in glibc 2.28-9
has caused the Debian Bug report #924612,
regarding CVE-2019-9169
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.)


-- 
924612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Severity: important
Tags: security

Please see
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34140
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34142
https://sourceware.org/bugzilla/show_bug.cgi?id=24114
https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commit;h=583dd860d5b833037175247230a328f0050dbfe9

Cheers,
Moritz

--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.28-9

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 25 Apr 2019 21:12:03 +0200
Source: glibc
Architecture: source
Version: 2.28-9
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 924612 927914
Changes:
 glibc (2.28-9) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix heap-based buffer over-read in regular-expression matching
   (CVE-2019-9169).  Closes: #924612.
 - Add entry for the new Japanese era to the ja_JP locale.  Closes:
   #927914.
 .
   [ Adam Conrad ]
   * debian/patches/arm/unsubmitted-ldso-abi-check.diff: Fix rtld segv in
 dl_open() introduced via merge with upstream at 2.28 (LP: #1821677)
Checksums-Sha1:
 7833db1fb71e76fca664ab85378d3782ecdfb5a1 8885 glibc_2.28-9.dsc
 a79f40a76ee667d33d972884341b90ca75b8116e 882956 glibc_2.28-9.debian.tar.xz
 475f4fd5058d96c297e2ead57c9d42acd20f30ba 7241 glibc_2.28-9_source.buildinfo
Checksums-Sha256:
 e8abfd8e99890e93324c6c0ec1b4a093b0bde628151848bf5d26114eb1f11376 8885 
glibc_2.28-9.dsc
 59908f806fe0eddd6929705d3a493e6b96aa5dcb2f0e6e824aae57040adafbd8 882956 
glibc_2.28-9.debian.tar.xz
 bc2668920175c17ccc0daf7039a06c2e44942f5fd2fc4eaf97a741e7140b5829 7241 
glibc_2.28-9_source.buildinfo
Files:
 b6a4f9e6e8a061fc45c63dae4ff296f2 8885 libs required glibc_2.28-9.dsc
 ab58421e5d02853af6901659a921d808 882956 libs required 
glibc_2.28-9.debian.tar.xz
 af3dd21b0d7110f77ed3501f89d92c5f 7241 libs required 
glibc_2.28-9_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAlzCMggACgkQE4jA+Jno
M2su0g//eQz8QjgERLm0617Q06rvoTTtQz03UKdCw8ebhSIXoliW7TOe+OFGwn9/
Kq6cm/rZXETDApIDQs0eegBT5CrlmvWPPLjgTwscJks8azddY6EL5qr/jo9G155Y
7nuv90WRUbbIrcPx9aTpzk2vBhUKYfxDKug5ORdRg18d6NIg+Dp4/bpUPhewB5in
WDaQ8pEWK8vK1wZiHnijAlAsX8erJCcVFyb1hUpBfTeE7B9L/7CSrR3fxwXMq/Xx
14F6kiGBohwmhgGIOviiMfapFq94K9c57MtTK67uRIsiZ5FGPddgW5f9j4pBujFK
TZEFjk9J8bg0C3vm8FDnoFCSIbf8BX40FYPaT5PZznErHq2X7U+CFFSZk9jqcFCC
AeSMCWBbydhGzh1UKTGnw/L0Zd82GDYr/1JvFEJ6u4g3lFBo0bFDZ18UZGz4jGk5
HYv3WgCAZMwWXN4XV95T/QA+g9pl1rQb05ORTQ3w5QHp9cDrESu87vx2ycDdg9Ar
xfdeepw+vDIcIZFULUGCoLkx465idJHPT3ccEpXqagC5qtqvJYc13C/XB4OqdROD
a7ErW/x5ZOvFyY+ngG5eCyL0Ts62IJzBqBSe+ze32ZooML0LS7nGFTBaLv3Luoyi
axSyZYu7JyMjpWPdmRlWO2+xJ1aejNeAs8X5GOENfeBeWaKXAOU=
=vSUV
-END PGP SIGNATURE End Message ---


Processed: [bts-link] source package glibc

2019-04-25 Thread Debian Bug Tracking System
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 #913929 (http://bugs.debian.org/913929)
> # Bug title: pldd never stops
> #  * http://sourceware.org/bugzilla/show_bug.cgi?id=18035
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 913929 + fixed-upstream
Bug #913929 [libc-bin] pldd never stops
Added tag(s) fixed-upstream.
> usertags 913929 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 913929 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
913929: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Bug #927914 in glibc marked as pending

2019-04-25 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #927914 [glibc] glibc: deal with Japanese new era "令和 (Reiwa)"
Added tag(s) pending.

-- 
927914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: your mail

2019-04-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 927914 glibc: deal with Japanese new era "令和 (Reiwa)"
Bug #927914 [glibc] gblic: deal with Japanese new era "令和 (Reiwa)"
Changed Bug title to 'glibc: deal with Japanese new era "令和 (Reiwa)"' from 
'gblic: deal with Japanese new era "令和 (Reiwa)"'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
927914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: [stunnel4] still random segfaults - gdb backtrace

2019-04-24 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 stunnel4
Bug #880659 [libc6] sigill - xend opcode in libpthread on non hle/tsx cpu
Bug reassigned from package 'libc6' to 'stunnel4'.
No longer marked as found in versions 2.24-11+deb9.
Ignoring request to alter fixed versions of bug #880659 to the same values 
previously set
> retitle -1 stunnel4 calls pthread_rwlock_unlock on an rwlock which is not 
> locked
Bug #880659 [stunnel4] sigill - xend opcode in libpthread on non hle/tsx cpu
Changed Bug title to 'stunnel4 calls pthread_rwlock_unlock on an rwlock which 
is not locked' from 'sigill - xend opcode in libpthread on non hle/tsx cpu'.

-- 
880659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed (with 1 error): xend opcode in libpthread on non hle cpu

2019-04-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 880659 libc6 2.24-11+deb9
Bug #880659 [stunnel4] [stunnel4] random segfaults in libcrypto.so.1.1 / 
libpthread-2.24.so
Bug reassigned from package 'stunnel4' to 'libc6'.
No longer marked as found in versions stunnel4/3:5.39-2.
Ignoring request to alter fixed versions of bug #880659 to the same values 
previously set
Bug #880659 [libc6] [stunnel4] random segfaults in libcrypto.so.1.1 / 
libpthread-2.24.so
There is no source info for the package 'libc6' at version '2.24-11+deb9' with 
architecture ''
Unable to make a source version for version '2.24-11+deb9'
Marked as found in versions 2.24-11+deb9.
> retitle 880659 sigill - xend opcode in libpthread on non hle/tsx cpu
Bug #880659 [libc6] [stunnel4] random segfaults in libcrypto.so.1.1 / 
libpthread-2.24.so
Changed Bug title to 'sigill - xend opcode in libpthread on non hle/tsx cpu' 
from '[stunnel4] random segfaults in libcrypto.so.1.1 / libpthread-2.24.so'.
> end
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
880659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#926751: gcc-riscv64-linux-gnu: Doesn't work with all valid abi combinations.

2019-04-10 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 + wontfix
Bug #926751 [src:glibc] gcc-riscv64-linux-gnu: Doesn't work with all valid abi 
combinations.
Added tag(s) wontfix.

-- 
926751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#926751: gcc-riscv64-linux-gnu: Doesn't work with all valid abi combinations.

2019-04-09 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 src:glibc
Bug #926751 [gcc-riscv64-linux-gnu] gcc-riscv64-linux-gnu: Doesn't work with 
all valid abi combinations.
Bug reassigned from package 'gcc-riscv64-linux-gnu' to 'src:glibc'.
No longer marked as found in versions gcc-defaults-ports/1.182.
Ignoring request to alter fixed versions of bug #926751 to the same values 
previously set

-- 
926751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: tagging 924891

2019-04-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # bug is in stretch kernel, not in buster/sid
> tags 924891 = stretch
Bug #924891 [src:glibc] glibc: misc/tst-pkey fails due to cleared PKRU register 
after signal in amd64 32-bit compat mode
Added tag(s) stretch; removed tag(s) sid and buster.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
924891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Found in glibc 2.28-5

2019-03-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 903514 2.28-5
Bug #903514 [src:glibc] Deadlock in _dl_close join-ing threads accessing TLS
Bug #904544 [src:glibc] gimp hangs on startup if libopenblas-base is installed
Bug #906152 [src:glibc] libopenblas-base: version 0.3.2+ds-1 makes gimp hang 
indefinitely
Bug #906516 [src:glibc] gimp: Segfault with libopenblas-base
Marked as found in versions glibc/2.28-5.
Marked as found in versions glibc/2.28-5.
Marked as found in versions glibc/2.28-5.
Marked as found in versions glibc/2.28-5.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903514
904544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904544
906152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906152
906516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#914999: [libc6] Locking problems into libc6

2019-03-31 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #914999 [libc6] [libc6] Locking problems into libc6
Severity set to 'important' from 'critical'

-- 
914999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#582698: marked as done (libc6-dev: INTMAX_MAX definition yields build failure in 32-bit C90 mode though intmax_t is supported)

2019-03-29 Thread Debian Bug Tracking System
Your message dated Fri, 29 Mar 2019 12:28:08 +0100
with message-id <20190329112808.ga8...@cventin.lip.ens-lyon.fr>
and subject line Re: libc6-dev: INTMAX_MAX definition yields build failure in 
32-bit C90 mode though intmax_t is supported
has caused the Debian Bug report #582698,
regarding libc6-dev: INTMAX_MAX definition yields build failure in 32-bit C90 
mode though intmax_t is supported
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.)


-- 
582698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-dev
Version: 2.10.2-8
Severity: minor

The INTMAX_MAX definition in /usr/include/stdint.h yields build
failure in 32-bit C90 mode (x86_64 machines with the -m32 gcc
switch and x86 machines).

$ cat intmax-test.c
#include 
int main (void)
{
  intmax_t x;
  x = INTMAX_MAX;
  return 0;
}
$ gcc -m32 -ansi -pedantic-errors intmax-test.c
intmax-test.c:5:1: error: use of C99 long long integer constant

Support for intmax_t is not expected to work in C90 mode, but in
such a case, the failure should probably occur on the 
inclusion or "intmax_t x;" line. Otherwise I wonder whether the
failure on INTMAX_MAX is intended and/or fixable.

The consequence of this inconsistency is the following: for a
software that uses intmax_t optionally (such as MPFR), as intmax_t
works fine, autoconf detects that intmax_t is supported, but then
the build of the software fails if it uses INTMAX_MAX.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc6-dev depends on:
ii  libc-dev-bin  2.10.2-8   Embedded GNU C Library: Developmen
ii  libc6 2.10.2-8   Embedded GNU C Library: Shared lib
ii  linux-libc-dev2.6.32-12  Linux support headers for userspac

Versions of packages libc6-dev recommends:
ii  gcc [c-compiler]  4:4.4.3-1  The GNU C compiler
ii  gcc-4.1 [c-compiler]  4.1.2-29   The GNU C compiler
ii  gcc-4.3 [c-compiler]  4.3.4-10   The GNU C compiler
ii  gcc-4.4 [c-compiler]  4.4.4-1The GNU C compiler

Versions of packages libc6-dev suggests:
ii  glibc-doc 2.10.2-8   Embedded GNU C Library: Documentat
ii  manpages-dev  3.24-1 Manual pages about using GNU/Linux

-- no debconf information


--- End Message ---
--- Begin Message ---
On 2010-05-22 22:49:51 +0200, Vincent Lefevre wrote:
> The INTMAX_MAX definition in /usr/include/stdint.h yields build
> failure in 32-bit C90 mode (x86_64 machines with the -m32 gcc
> switch and x86 machines).
> 
> $ cat intmax-test.c
> #include 
> int main (void)
> {
>   intmax_t x;
>   x = INTMAX_MAX;
>   return 0;
> }
> $ gcc -m32 -ansi -pedantic-errors intmax-test.c
> intmax-test.c:5:1: error: use of C99 long long integer constant

Closing this old bug since the issue was eventually fixed in GCC 4.8:

ypig% gcc-4.7 -m32 -ansi -pedantic-errors intmax-test.c
intmax-test.c: In function ‘main’:
intmax-test.c:5:1: error: use of C99 long long integer constant [-Wlong-long]
ypig% gcc-4.8 -m32 -ansi -pedantic-errors intmax-test.c
ypig% 

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)--- End Message ---


Processed: Re: Bug#924891: glibc: FTBFS: /<>/build-tree/amd64-libc/conform/UNIX98/ndbm.h/scratch/ndbm.h-test.c:1:10: fatal error: ndbm.h: No such file or directory

2019-03-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 924891 glibc: misc/tst-pkey fails due to cleared PKRU register after 
> signal in amd64 32-bit compat mode
Bug #924891 [src:glibc] glibc: FTBFS: tst-pkey fails for 32-bit processes on 
Xeon SP
Changed Bug title to 'glibc: misc/tst-pkey fails due to cleared PKRU register 
after signal in amd64 32-bit compat mode' from 'glibc: FTBFS: tst-pkey fails 
for 32-bit processes on Xeon SP'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
924891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: retitle 924891 to glibc: FTBFS: tst-pkey fails for 32-bit processes on Xeon SP

2019-03-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 924891 glibc: FTBFS: tst-pkey fails for 32-bit processes on Xeon SP
Bug #924891 [src:glibc] glibc: FTBFS: 
/<>/build-tree/amd64-libc/conform/UNIX98/ndbm.h/scratch/ndbm.h-test.c:1:10:
 fatal error: ndbm.h: No such file or directory
Changed Bug title to 'glibc: FTBFS: tst-pkey fails for 32-bit processes on Xeon 
SP' from 'glibc: FTBFS: 
/<>/build-tree/amd64-libc/conform/UNIX98/ndbm.h/scratch/ndbm.h-test.c:1:10:
 fatal error: ndbm.h: No such file or directory'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
924891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: [bts-link] source package src:glibc

2019-03-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src: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 #924612 (http://bugs.debian.org/924612)
> # Bug title: CVE-2019-9169
> #  * http://sourceware.org/bugzilla/show_bug.cgi?id=24114
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 924612 + fixed-upstream
Bug #924612 [src:glibc] CVE-2019-9169
Added tag(s) fixed-upstream.
> usertags 924612 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
924612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Bug #924612 in glibc marked as pending

2019-03-17 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #924612 [src:glibc] CVE-2019-9169
Added tag(s) pending.

-- 
924612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: found 924612 in 2.28-8

2019-03-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 924612 2.28-8
Bug #924612 [src:glibc] CVE-2019-9169
Marked as found in versions glibc/2.28-8.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
924612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: tagging 924612

2019-03-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 924612 + upstream
Bug #924612 [src:glibc] CVE-2019-9169
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
924612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: bug 924612 is forwarded to https://sourceware.org/bugzilla/show_bug.cgi?id=24114

2019-03-14 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 924612 https://sourceware.org/bugzilla/show_bug.cgi?id=24114
Bug #924612 [src:glibc] CVE-2019-9169
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=24114'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
924612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#923802: marked as done (pthread: dead-lock while pthread_cond_destroy())

2019-03-06 Thread Debian Bug Tracking System
Your message dated Wed, 06 Mar 2019 13:13:36 +0100
with message-id <877edccia7@oldenburg2.str.redhat.com>
and subject line Re: Bug#923802: Acknowledgement (pthread: dead-lock while 
pthread_cond_destroy())
has caused the Debian Bug report #923802,
regarding pthread: dead-lock while pthread_cond_destroy()
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.)


-- 
923802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923802
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc0.1-dev
Version: 2.25-2
Severity: normal
File: pthread

Dear Maintainer,

As checking why GSequencer's test didn't continue, I have discovered a dead-lock
as calling pthread_cond_destroy()

http://salsa.debian.org/multimedia-team/gsequencer

Here is the command to reproduce:

joel@kbsd:~/gsequencer-2.1.64$ libtool --mode=execute gdb 
ags_condition_manager_test 
GNU gdb (Debian 8.2.1-2) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-kfreebsd-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from 
/home/joel/gsequencer-2.1.64/.libs/ags_condition_manager_test...done.
(gdb) r
Starting program: /home/joel/gsequencer-2.1.64/.libs/ags_condition_manager_test 


 CUnit - A unit testing framework for C - Version 2.1-3
 http://cunit.sourceforge.net/


Suite: AgsConditionManagerTest
  Test: test of AgsConditionManager insert ...passed
  Test: test of AgsConditionManager remove ...^Z
Program received signal SIGTSTP, Stopped (user).
__syscall__umtx_op () at ../sysdeps/unix/syscall-template.S:76
76  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) bt
#0  0x00080360f1da in __syscall__umtx_op () at 
../sysdeps/unix/syscall-template.S:76
#1  0x00080360d8cc in __lll_lock_wait_private (futex=0x12479a0) at 
../sysdeps/unix/bsd/bsd4.4/kfreebsd/fbtl/lowlevellock.c:31
#2  0x00080360aa9b in __pthread_cond_destroy (cond=cond@entry=0x12479a0) at 
pthread_cond_destroy.c:34
#3  0x0008018982f2 in ags_condition_manager_remove 
(condition_manager=0x12410a0, lock_object=0x12444d0)
at ags/thread/ags_condition_manager.c:176
#4  0x0102229e in ags_condition_manager_test_remove () at 
ags/test/thread/ags_condition_manager_test.c:136
#5  0x000801ab130f in  () at /usr/lib/x86_64-kfreebsd-gnu/libcunit.so.1
#6  0x000801ab154d in  () at /usr/lib/x86_64-kfreebsd-gnu/libcunit.so.1
#7  0x000801ab19be in CU_run_all_tests () at 
/usr/lib/x86_64-kfreebsd-gnu/libcunit.so.1
#8  0x01021fc0 in main (argc=, argv=) at 
ags/test/thread/ags_condition_manager_test.c:218


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: kfreebsd-amd64 (x86_64)

Kernel: kFreeBSD 10.3-0-amd64
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libc0.1-dev:kfreebsd-amd64 depends on:
ii  kfreebsd-kernel-headers  10.3~8
ii  libc-dev-bin 2.25-2
ii  libc0.1  2.25-2

libc0.1-dev:kfreebsd-amd64 recommends no packages.

Versions of packages libc0.1-dev:kfreebsd-amd64 suggests:
pn  glibc-doc 
ii  manpages-dev  4.16-1

-- no debconf information
--- End Message ---
--- Begin Message ---
* Joël Krähemann:

> Yes, it is an application bug. So, I fixed my upstream source. Just recognized
> calling pthread_cond_destroy() twice, later.

Okay, closing.

Thanks,
Florian--- End Message ---


Bug#918823: marked as done (libc6: [24945.428485] libvirtd[12553]: segfault at 8 ip 00007fb0f515ba63 sp 00007fff86e08370 error 4 in ld-2.24.so[7fb0f514b000+23000])

2019-03-04 Thread Debian Bug Tracking System
Your message dated Mon, 4 Mar 2019 22:48:33 +0100
with message-id <20190304214833.vcmbqznywkhdf...@aurel32.net>
and subject line Re: Bug#918823: Update on your bug report
has caused the Debian Bug report #918823,
regarding libc6: [24945.428485] libvirtd[12553]: segfault at 8 ip 
7fb0f515ba63 sp 7fff86e08370 error 4 in ld-2.24.so[7fb0f514b000+23000]
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.)


-- 
918823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: libc6
Version: 2.24-11+deb9u3
Severity: critical
Tags: d-i
Justification: breaks unrelated software

Dear Maintainer,

I can not work libvirtd ?-:-(


Reading symbols from virsh...(no debugging symbols found)...done.
(gdb) set pagination 8
"on" or "off" expected.
(gdb) run
Starting program: /usr/bin/virsh

Program received signal SIGSEGV, Segmentation fault.
match_symbol (name=0x7fffe89d "/usr/bin/virsh", ns=0,
hash=160186580, string=0xaf0b "LIBVIRT_QEMU_0.9.4",
map=0x77ff69a8,
verbose=verbose@entry=1, weak=0) at dl-version.c:77
77dl-version.c: File o directory non esistente.

> 
--- End Message ---
--- Begin Message ---
On 2019-02-16 16:03, Aurelien Jarno wrote:
> Hi Richard,
> 
> On 2019-02-15 17:03, Richard Hartmann wrote:
> > Hi Leopold,
> > 
> > did you have a chance to run the commands requested by Aurelien? This
> > bug is marked critical, but has been stale for more than a month, now.
> 
> Leopold answered me privately, I am sorry to not have provided a summary
> to the bug log earlier. There was an issue on the system with a
> /usr/local/lib/libvirt-lxc.so.0 symlink but it turned out to not be the
> issue.
> 
> I am personally out of ideas, if someone is able to reproduce the issue
> or have ideas about what causes the issue, please don't hesitate to tell

He answered me privately that the issue went away after upgrading other
packages than libc6. I am therefore closing the bug.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net--- End Message ---


Processed: forcibly merging 585737 923505

2019-03-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forcemerge 585737 923505
Bug #585737 [locales] locales: upgrade not atomic
Bug #586489 [locales] locales needs higher dpkg priority
Bug #588180 [locales] dist-upgrade from lenny to squeeze with tons of warning 
messages
Bug #660669 [locales] lenny->squeeze: Upgrading locales causes broken 
en_US.utf8 locale during upgrade
Bug #923505 [locales] Be sure locales are available even during updates
Severity set to 'minor' from 'wishlist'
Added indication that 923505 affects upgrade-reports
Marked as found in versions eglibc/2.11.3-3, eglibc/2.11.1-3, and 
eglibc/2.11.2-1.
Bug #588180 [locales] dist-upgrade from lenny to squeeze with tons of warning 
messages
Marked as found in versions glibc/2.28-8.
Marked as found in versions glibc/2.28-8.
Marked as found in versions glibc/2.28-8.
Marked as found in versions glibc/2.28-8.
Bug #586489 [locales] locales needs higher dpkg priority
Bug #660669 [locales] lenny->squeeze: Upgrading locales causes broken 
en_US.utf8 locale during upgrade
Merged 585737 586489 588180 660669 923505
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
585737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585737
586489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586489
588180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588180
660669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660669
923505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#920598: marked as done (tzdata: [INTL:ru] Russian translation of debconf template)

2019-02-28 Thread Debian Bug Tracking System
Your message dated Thu, 28 Feb 2019 22:40:52 +
with message-id 
and subject line Bug#920598: fixed in tzdata 2018i-2
has caused the Debian Bug report #920598,
regarding tzdata: [INTL:ru] Russian translation of debconf template
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.)


-- 
920598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tzdata
Version: 2018i-1
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

please find the updated Russian translation of debconf tempalte for tzdata 
attached.

With regards,
Lev Lamberov


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tzdata depends on:
ii  debconf [debconf-2.0]  1.5.70

tzdata recommends no packages.

tzdata suggests no packages.

-- debconf information excluded
# translation of ru.po to Russian
#
# Copyright (C) 2003 Software in the Public Interest, Inc.
# Russian L10N Team , 2004.
# Dmitry Beloglazov , 2005.
# Sergey Alyoshin , 2007.
# Stepan Golosunov , 2007.
# Yuri Kozlov , 2004, 2005, 2006, 2007, 2008.
# Yuri Kozlov , 2009, 2011, 2013.
# Lev Lamberov , 2017, 2019
msgid ""
msgstr ""
"Project-Id-Version: tzdata 2013b-2\n"
"Report-Msgid-Bugs-To: tzd...@packages.debian.org\n"
"POT-Creation-Date: 2018-12-29 23:10+\n"
"PO-Revision-Date: 2019-01-27 14:44+0500\n"
"Last-Translator: Lev Lamberov \n"
"Language-Team: Russian \n"
"Language: ru\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
"X-Generator: Poedit 2.2.1\n"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of "GMT+xx" or "GMT-xx" timezones
#. - SystemV will give the choice between zone named as per SystemV conventions:
#. EST5, MST7, etc.
#: ../tzdata.templates:1001
msgid "Africa"
msgstr "Африка"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of "GMT+xx" or "GMT-xx" timezones
#. - SystemV will give the choice between zone named as per SystemV conventions:
#. EST5, MST7, etc.
#: ../tzdata.templates:1001
msgid "America"
msgstr "Америка"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of "GMT+xx" or "GMT-xx" timezones
#. - SystemV will give the choice between zone named as per SystemV conventions:
#. EST5, MST7, etc.
#: ../tzdata.templates:1001
msgid "Antarctica"
msgstr "Антарктида"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of "GMT+xx" or "GMT-xx" timezones
#. - SystemV will give the choice between zone named as per SystemV conventions:
#. EST5, MST7, etc.
#: ../tzdata.templates:1001
msgid "Australia"
msgstr "Австралия"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of "GMT+xx" or "GMT-xx" timezones
#. - SystemV will give the choice between zone named as per SystemV conventions:
#. EST5, MST7, etc.
#: ../tzdata.templates:1001
msgid "Arctic"
msgstr "Арктика"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of "GMT+xx" or "GMT-xx" timezones
#. - SystemV will give the choice between zone named as per SystemV conventions:
#. EST5, MST7, etc.
#: ../tzdata.templates:1001
msgid "Asia"
msgstr "Азия"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of "GMT+xx" or "GMT-xx" timezones
#. - SystemV will give the choice between zone named as per SystemV conventions:
#. EST5, MST

Bug#923061: marked as done ([INTL:da] Danish translation of the debconf templates tzdata)

2019-02-28 Thread Debian Bug Tracking System
Your message dated Thu, 28 Feb 2019 22:40:52 +
with message-id 
and subject line Bug#923061: fixed in tzdata 2018i-2
has caused the Debian Bug report #923061,
regarding [INTL:da] Danish translation of the debconf templates tzdata
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.)


-- 
923061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tzdata
Severity: wishlist
Tags: l10n patch

Please include the attached Danish tzdata debconf po file.

joe@debianbuster:~/over/debian/tzdata$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 476 oversatte tekster.

bye
Joe

da.po.tar.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: tzdata
Source-Version: 2018i-2

We believe that the bug you reported is fixed in the latest version of
tzdata, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 923...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated tzdata package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 28 Feb 2019 22:56:09 +0100
Source: tzdata
Binary: tzdata
Architecture: source
Version: 2018i-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Description:
 tzdata - time zone and daylight-saving time data
Closes: 918455 920427 920598 923061
Changes:
 tzdata (2018i-2) unstable; urgency=medium
 .
   * Update German debconf translation, by Holger Wansing.  Closes:
 #918455.
   * Update Dutch debconf translation, by Frans Spiesschaert.  Closes:
 #920427.
   * Update Russian debconf translation, by Lev Lamberov.  Closes:
 #920598.
   * Update Danish debconf translation, by Joe Hansen.  Closes:
 #923061.
Checksums-Sha1:
 137e51a6011a6ecd3fd91451ce2bba51a3b58557 2232 tzdata_2018i-2.dsc
 b1daf6e97e7c28618c59dd6e059756ebaa2ddb1b 104648 tzdata_2018i-2.debian.tar.xz
 8f58ce9f30446d610a6707de9818dab52904 5292 tzdata_2018i-2_source.buildinfo
Checksums-Sha256:
 79bda2830db31bd1668c623f468112006a76f2b3d99738982f9a592dcffb0aaa 2232 
tzdata_2018i-2.dsc
 f98af5cdf2b8cc54323d8d88a6cff071dde66a02bbb00dd0cff3c7a091d89fa0 104648 
tzdata_2018i-2.debian.tar.xz
 a2ab77a7155eb89e7ad68f60fc6bd7de2c7f08c09641f2887782a45561c966ad 5292 
tzdata_2018i-2_source.buildinfo
Files:
 00081c47f8380b849a274633f840c81b 2232 localization required tzdata_2018i-2.dsc
 d12ad1a5f3eafcc5c889807d097de02e 104648 localization required 
tzdata_2018i-2.debian.tar.xz
 c45c033ae261a04fd7c83bff44eae8c6 5292 localization required 
tzdata_2018i-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAlx4WT0ACgkQE4jA+Jno
M2vJqw/9GnB+rnU7qk73vN0wDmgPJhPqAYiZ1Mizjl0w3Uzj7Aayr4KN7+92BfxI
SAwNvvIAVnLf+zdy+kcMTjxR1ssABjNmUVBxNjnTbVWGsHoF86XXkIykuUFbS2Wf
+2JrcrK7Bh36pcmK39dKsSr4keg4timLXgHae/zU7bRfbnnIGTngnvElU4Sj0N8o
6zQn7CJ5kQPQezNgxdgkU2KSNmNMiE5ONrSv4bzw+u/hp9dsGeuDXdHQk2qlWYYY
PlbdNpoghGAJFZAYYA8khgR0+tdHlK/dyPQZNZGh88Y/wRQv7lKuoqh8rKS5Snja
sx5gMB3R+tQEh9l71oAPZykj9RhriKcSFXL5O2Cb8Y4UmZN7KQGtxxdOrh2mOMLv
eSiYs/umECvPdgx8SajonJtD+oedVc+gNHZ6MvcVMGQxuXNi1a2NGkCYdEXTCwx+
KE5qK1XK34TwUXWxzz21cyUgBK6BEYSlgzgGesgDM5sxIkYIarlBJZS/HbaRUuVI
pQoTUPr9QWow0CyNC8cbznT3gAuI/fnabD7hxmNp7BM8g7+caTGMMwiBtOW7c9Qm
ABBMp25ycJ3OXtQ65g5fhSVe/QZIh+7pqo3b1RGADf3Bqqq7Bhx3vp1LlWpWaJ3h
zwx0N5q8QVbRNZJ0J2EMtrjcytv4K8zySFl3hpT/qW+NP84neM8=
=f2ZP
-END PGP SIGNATURE End Message ---


Bug#920427: marked as done (tzdata: [INTL:nl] Dutch translation of debconf messages)

2019-02-28 Thread Debian Bug Tracking System
Your message dated Thu, 28 Feb 2019 22:40:52 +
with message-id 
and subject line Bug#920427: fixed in tzdata 2018i-2
has caused the Debian Bug report #920427,
regarding tzdata: [INTL:nl] Dutch translation of debconf messages
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.)


-- 
920427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
 
 
Package: tzdata 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch translation of tzdata debconf
messages. 
It has been submitted for review to the debian-l10n-dutch mailing
list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
 

-- 
Met vriendelijke groet,
Frans Spiesschaert


nl.po.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: tzdata
Source-Version: 2018i-2

We believe that the bug you reported is fixed in the latest version of
tzdata, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated tzdata package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 28 Feb 2019 22:56:09 +0100
Source: tzdata
Binary: tzdata
Architecture: source
Version: 2018i-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Description:
 tzdata - time zone and daylight-saving time data
Closes: 918455 920427 920598 923061
Changes:
 tzdata (2018i-2) unstable; urgency=medium
 .
   * Update German debconf translation, by Holger Wansing.  Closes:
 #918455.
   * Update Dutch debconf translation, by Frans Spiesschaert.  Closes:
 #920427.
   * Update Russian debconf translation, by Lev Lamberov.  Closes:
 #920598.
   * Update Danish debconf translation, by Joe Hansen.  Closes:
 #923061.
Checksums-Sha1:
 137e51a6011a6ecd3fd91451ce2bba51a3b58557 2232 tzdata_2018i-2.dsc
 b1daf6e97e7c28618c59dd6e059756ebaa2ddb1b 104648 tzdata_2018i-2.debian.tar.xz
 8f58ce9f30446d610a6707de9818dab52904 5292 tzdata_2018i-2_source.buildinfo
Checksums-Sha256:
 79bda2830db31bd1668c623f468112006a76f2b3d99738982f9a592dcffb0aaa 2232 
tzdata_2018i-2.dsc
 f98af5cdf2b8cc54323d8d88a6cff071dde66a02bbb00dd0cff3c7a091d89fa0 104648 
tzdata_2018i-2.debian.tar.xz
 a2ab77a7155eb89e7ad68f60fc6bd7de2c7f08c09641f2887782a45561c966ad 5292 
tzdata_2018i-2_source.buildinfo
Files:
 00081c47f8380b849a274633f840c81b 2232 localization required tzdata_2018i-2.dsc
 d12ad1a5f3eafcc5c889807d097de02e 104648 localization required 
tzdata_2018i-2.debian.tar.xz
 c45c033ae261a04fd7c83bff44eae8c6 5292 localization required 
tzdata_2018i-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAlx4WT0ACgkQE4jA+Jno
M2vJqw/9GnB+rnU7qk73vN0wDmgPJhPqAYiZ1Mizjl0w3Uzj7Aayr4KN7+92BfxI
SAwNvvIAVnLf+zdy+kcMTjxR1ssABjNmUVBxNjnTbVWGsHoF86XXkIykuUFbS2Wf
+2JrcrK7Bh36pcmK39dKsSr4keg4timLXgHae/zU7bRfbnnIGTngnvElU4Sj0N8o
6zQn7CJ5kQPQezNgxdgkU2KSNmNMiE5ONrSv4bzw+u/hp9dsGeuDXdHQk2qlWYYY
PlbdNpoghGAJFZAYYA8khgR0+tdHlK/dyPQZNZGh88Y/wRQv7lKuoqh8rKS5Snja
sx5gMB3R+tQEh9l71oAPZykj9RhriKcSFXL5O2Cb8Y4UmZN7KQGtxxdOrh2mOMLv
eSiYs/umECvPdgx8SajonJtD+oedVc+gNHZ6MvcVMGQxuXNi1a2NGkCYdEXTCwx+
KE5qK1XK34TwUXWxzz21cyUgBK6BEYSlgzgGesgDM5sxIkYIarlBJZS/HbaRUuVI
pQoTUPr9QWow0CyNC8cbznT3gAuI/fnabD7hxmNp7BM8g7+caTGMMwiBtOW7c9Qm
ABBMp25ycJ3OXtQ65g5fhSVe/QZIh+7pqo3b1RGADf3Bqqq7Bhx3vp1LlWpWaJ3h
zwx0N5q8QVbRNZJ0J2EMtrjcytv4K8zySFl3hpT/qW+NP84neM8=
=f2ZP
-END PGP SIGNATURE End Message ---


Bug#918455: marked as done ([L10N,DE] tzdata: updated german debconf translation)

2019-02-28 Thread Debian Bug Tracking System
Your message dated Thu, 28 Feb 2019 22:40:52 +
with message-id 
and subject line Bug#918455: fixed in tzdata 2018i-2
has caused the Debian Bug report #918455,
regarding [L10N,DE] tzdata: updated german debconf translation
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.)


-- 
918455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tzdata
Severity: wishlist
Tags: patch,l10n


Hi,
attached is the updated german debconf translation for tzdata, version 2018i.
Please include it in your package.

Thanks for your i18n efforts.


So long
Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076


tzdata_2018i-1_de.po.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: tzdata
Source-Version: 2018i-2

We believe that the bug you reported is fixed in the latest version of
tzdata, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 918...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated tzdata package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 28 Feb 2019 22:56:09 +0100
Source: tzdata
Binary: tzdata
Architecture: source
Version: 2018i-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Description:
 tzdata - time zone and daylight-saving time data
Closes: 918455 920427 920598 923061
Changes:
 tzdata (2018i-2) unstable; urgency=medium
 .
   * Update German debconf translation, by Holger Wansing.  Closes:
 #918455.
   * Update Dutch debconf translation, by Frans Spiesschaert.  Closes:
 #920427.
   * Update Russian debconf translation, by Lev Lamberov.  Closes:
 #920598.
   * Update Danish debconf translation, by Joe Hansen.  Closes:
 #923061.
Checksums-Sha1:
 137e51a6011a6ecd3fd91451ce2bba51a3b58557 2232 tzdata_2018i-2.dsc
 b1daf6e97e7c28618c59dd6e059756ebaa2ddb1b 104648 tzdata_2018i-2.debian.tar.xz
 8f58ce9f30446d610a6707de9818dab52904 5292 tzdata_2018i-2_source.buildinfo
Checksums-Sha256:
 79bda2830db31bd1668c623f468112006a76f2b3d99738982f9a592dcffb0aaa 2232 
tzdata_2018i-2.dsc
 f98af5cdf2b8cc54323d8d88a6cff071dde66a02bbb00dd0cff3c7a091d89fa0 104648 
tzdata_2018i-2.debian.tar.xz
 a2ab77a7155eb89e7ad68f60fc6bd7de2c7f08c09641f2887782a45561c966ad 5292 
tzdata_2018i-2_source.buildinfo
Files:
 00081c47f8380b849a274633f840c81b 2232 localization required tzdata_2018i-2.dsc
 d12ad1a5f3eafcc5c889807d097de02e 104648 localization required 
tzdata_2018i-2.debian.tar.xz
 c45c033ae261a04fd7c83bff44eae8c6 5292 localization required 
tzdata_2018i-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAlx4WT0ACgkQE4jA+Jno
M2vJqw/9GnB+rnU7qk73vN0wDmgPJhPqAYiZ1Mizjl0w3Uzj7Aayr4KN7+92BfxI
SAwNvvIAVnLf+zdy+kcMTjxR1ssABjNmUVBxNjnTbVWGsHoF86XXkIykuUFbS2Wf
+2JrcrK7Bh36pcmK39dKsSr4keg4timLXgHae/zU7bRfbnnIGTngnvElU4Sj0N8o
6zQn7CJ5kQPQezNgxdgkU2KSNmNMiE5ONrSv4bzw+u/hp9dsGeuDXdHQk2qlWYYY
PlbdNpoghGAJFZAYYA8khgR0+tdHlK/dyPQZNZGh88Y/wRQv7lKuoqh8rKS5Snja
sx5gMB3R+tQEh9l71oAPZykj9RhriKcSFXL5O2Cb8Y4UmZN7KQGtxxdOrh2mOMLv
eSiYs/umECvPdgx8SajonJtD+oedVc+gNHZ6MvcVMGQxuXNi1a2NGkCYdEXTCwx+
KE5qK1XK34TwUXWxzz21cyUgBK6BEYSlgzgGesgDM5sxIkYIarlBJZS/HbaRUuVI
pQoTUPr9QWow0CyNC8cbznT3gAuI/fnabD7hxmNp7BM8g7+caTGMMwiBtOW7c9Qm
ABBMp25ycJ3OXtQ65g5fhSVe/QZIh+7pqo3b1RGADf3Bqqq7Bhx3vp1LlWpWaJ3h
zwx0N5q8QVbRNZJ0J2EMtrjcytv4K8zySFl3hpT/qW+NP84neM8=
=f2ZP
-END PGP SIGNATURE End Message ---


Bug#923055: marked as done ([INTL:da] Danish translation of the debconf templates glibc)

2019-02-28 Thread Debian Bug Tracking System
Your message dated Thu, 28 Feb 2019 14:53:11 +
with message-id 
and subject line Bug#923055: fixed in glibc 2.28-8
has caused the Debian Bug report #923055,
regarding [INTL:da] Danish translation of the debconf templates glibc
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.)


-- 
923055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glibc
Severity: wishlist
Tags: l10n patch

Please include the attached Danish glibc debconf po file.

joe@debianbuster:~/over/debian/glibc$ msgfmt --statistics -c -v -o /dev/null 
da.po
da.po: 26 oversatte tekster.


bye
Joe

da.po.tar.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.28-8

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 923...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Feb 2019 21:56:01 -0800
Source: glibc
Binary: glibc-doc glibc-source libc-bin libc-bin-dbgsym libc-dev-bin 
libc-dev-bin-dbgsym libc-l10n libc6 libc6-dbg libc6-dev libc6-dev-i386 
libc6-dev-x32 libc6-i386 libc6-i386-dbgsym libc6-pic libc6-udeb libc6-x32 
libc6-x32-dbgsym locales locales-all multiarch-support nscd nscd-dbgsym
Architecture: source
Version: 2.28-8
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Samuel Thibault 
Description:
 glibc-doc  - GNU C Library: Documentation
 glibc-source - GNU C Library: sources
 libc-bin   - GNU C Library: Binaries
 libc-dev-bin - GNU C Library: Development binaries
 libc-l10n  - GNU C Library: localization files
 libc6  - GNU C Library: Shared libraries
 libc6-dbg  - GNU C Library: detached debugging symbols
 libc6-dev  - GNU C Library: Development Libraries and Header Files
 libc6-dev-i386 - GNU C Library: 32-bit development libraries for AMD64
 libc6-dev-x32 - GNU C Library: X32 ABI Development Libraries for AMD64
 libc6-i386 - GNU C Library: 32-bit shared libraries for AMD64
 libc6-pic  - GNU C Library: PIC archive library
 libc6-udeb - GNU C Library: Shared libraries - udeb (udeb)
 libc6-x32  - GNU C Library: X32 ABI Shared libraries for AMD64
 locales- GNU C Library: National Language (locale) data [support]
 locales-all - GNU C Library: Precompiled locale data
 multiarch-support - Transitional package to ensure multiarch compatibility
 nscd   - GNU C Library: Name Service Cache Daemon
Closes: 923055
Changes:
 glibc (2.28-8) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch.
   * Update Danish debconf translation, by Joe Hansen.  Closes: #923055.
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/libpthread_sigs.diff: Enable patch to restore
 per-thread signal distribution, lost on upgrading to 2.28. Fixes go.
   * debian/patches/hurd-i386/git-renameat2.diff: New patch, fixes renameat2,
 now used by coreutils.
Checksums-Sha1:
 7aea3761fddcd8fb4c834901b162e9fa8637e437 8885 glibc_2.28-8.dsc
 e3a044799c1bba6cfd5af1592e68b291325857f7 881916 glibc_2.28-8.debian.tar.xz
Checksums-Sha256:
 761cdb28592f2c805fdc580c66753c90e9118b8631e0c738b283c77a9120ff3c 8885 
glibc_2.28-8.dsc
 fac6b18552dbd2271e6db03c5a91b01b072f91f5b64ee782c874d0f0ea9d9d2f 881916 
glibc_2.28-8.debian.tar.xz
Files:
 e26fdd586ba6bf40a4e0bf6c336c7699 8885 libs required glibc_2.28-8.dsc
 aba162114e4e7e362e7f15f89b4ce4ec 881916 libs required 
glibc_2.28-8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEM/p7ZGGVAfjOnI+X4/ZanpVg20wFAlx350QACgkQ4/ZanpVg
20yb+xAAtfnh79ib2cddPqPLB1abxRy6arc0eWIVhy/Vo77TESmzIsuGWVMybR/L
QTrJa2hZpW7Gdnyj2l6OtaHc0KGhSAc4I2AiqWWIyr8YvSU0+1veOic4zoiappq1
l5C5k3D4MSzdP4eVeQiaOiCLz3zqqBfCzxNSU1/S/Hq7ZKXubZXA2xQCEcfNAJbU
KZlr7LD1BGKlQF8Q1yDEbYdOM/eCTyygX/tUtCb7Tgh417kcRy/8dmu/egPt01Cg
F9865Pn8E7x6TuH7CfUTt3RrK7G/ajvXXXPffSaAq0BE5bMqQ0x3y5Dg1N1hS13u
utaiHIh9i+tvSs2VRrXHq8hZnQWBg2f3/eyZiX2/m15wN7+3CEWlQs6pC7ANg5JT

Processed: Bug #923061 in tzdata marked as pending

2019-02-24 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #923061 [tzdata] [INTL:da] Danish translation of the debconf templates 
tzdata
Added tag(s) pending.

-- 
923061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Bug #923055 in glibc marked as pending

2019-02-24 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #923055 [glibc] [INTL:da] Danish translation of the debconf templates glibc
Added tag(s) pending.

-- 
923055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: fixed 736479 in 1.18.0-1, fixed 768915 in 2.2.1-1, fixed 859499 in 3.0.2+ds-1~exp1 ...

2019-02-10 Thread Debian Bug Tracking System
M
Bug reassigned from package 'libc6-armhf-cross' to 'src:glibc'.
No longer marked as found in versions cross-toolchain-base/30.
No longer marked as fixed in versions glibc/2.28-4.
Bug #916779 {Done: Aurelien Jarno } [src:glibc] 
libc6-armhf-cross: strerror(-3) sets errno to ENOMEM
Marked as found in versions glibc/2.28-2.
> fixed 916779 2.28-4
Bug #916779 {Done: Aurelien Jarno } [src:glibc] 
libc6-armhf-cross: strerror(-3) sets errno to ENOMEM
Marked as fixed in versions glibc/2.28-4.
> affects 916779 + libc6-armhf-cross
Bug #916779 {Done: Aurelien Jarno } [src:glibc] 
libc6-armhf-cross: strerror(-3) sets errno to ENOMEM
Added indication that 916779 affects libc6-armhf-cross
> reassign 915785 rakudo
Bug #915785 {Done: Robert Lemmen } [perl6-zef] 
perl6-zef: unowned directory after purge: /usr/lib/perl6/vendor/resources/
Bug reassigned from package 'perl6-zef' to 'rakudo'.
No longer marked as found in versions perl6-zef/0.5.3-1.
No longer marked as fixed in versions rakudo/2018.12-2.
> fixed 915785 2018.12-2
Bug #915785 {Done: Robert Lemmen } [rakudo] perl6-zef: 
unowned directory after purge: /usr/lib/perl6/vendor/resources/
Marked as fixed in versions rakudo/2018.12-2.
> affects 915785 + perl6-zef
Bug #915785 {Done: Robert Lemmen } [rakudo] perl6-zef: 
unowned directory after purge: /usr/lib/perl6/vendor/resources/
Added indication that 915785 affects perl6-zef
> tags 917801 + sid
Bug #917801 {Done: Aurelien Jarno } [src:pacemaker] 
pacemaker is linked to both libcfg6 and libcfg7 causing it to fail to start
Added tag(s) sid.
> tags 903878 + sid buster
Bug #903878 {Done: Aleksey Kravchenko } [rhash] rhash: 
unsatisfiable recommends: libssl1.0.0 (>= 1.0.0)
Added tag(s) sid and buster.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
609959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609959
629650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629650
678251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678251
690816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690816
736479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736479
768915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768915
774333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774333
787601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787601
795620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795620
810605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810605
812826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812826
834131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834131
838318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838318
838503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838503
847099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847099
851924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851924
855810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855810
859499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859499
863451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863451
867237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867237
874675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874675
875977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875977
876794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876794
884586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884586
885908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885908
891432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891432
899302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899302
901430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901430
903878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903878
905055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905055
905826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905826
906855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906855
910713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910713
914530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914530
914927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914927
915136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915136
915785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915785
916480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916480
916620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916620
916779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916779
917801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: breaks when #included after

2019-02-09 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 libc6-dev
Bug #898743 [linux-libc-dev,libc6-dev]  breaks when #included 
after 
Bug reassigned from package 'linux-libc-dev,libc6-dev' to 'libc6-dev'.
Ignoring request to alter found versions of bug #898743 to the same values 
previously set
Ignoring request to alter fixed versions of bug #898743 to the same values 
previously set
> severity -1 normal
Bug #898743 [libc6-dev]  breaks when #included after 
Severity set to 'normal' from 'serious'

-- 
898743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#904158: marked as done (glibc: pthread_cond_wait() is broken in the pshared case)

2019-02-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 21:47:22 +
with message-id 
and subject line Bug#904158: fixed in glibc 2.24-11+deb9u4
has caused the Debian Bug report #904158,
regarding glibc: pthread_cond_wait() is broken in the pshared case
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.)


-- 
904158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glibc
Version: 2.24-11+deb9u3
Severity: important

The short version is that pthread_cond_wait() is broken in the pshared
case in glibc in Stretch. The version in Sid is not affected because
that part received a large rewrite (that is why I use explicit the
version Stretch for the report).

The full explanation is attached as a patch. I also attached a testcase
to verify. Please note that x86 has handwritten assembly code for the
function which does not have the problem. All other architectures are
using the generic C code and share the problem.
On amdahl.d.o:~bigeasy/glibc you can try the following:

|strace -f ../testcase 
|clone(child_stack=0x99483b10, 
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
 parent_tidptr=0x994842d0, tls=0x994848f0, child_tidptr=0x994842d0) 
= 26581
|[pid 26581] futex(0xda3d40fc, FUTEX_WAIT_REQUEUE_PI, 1, NULL, 
0xda3d40b8 
|[pid 26579] clone(child_stack=0x98c83b10, 
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
 parent_tidptr=0x98c842d0, tls=0x98c848f0, child_tidptr=0x98c842d0) 
= 26582
|[pid 26582] futex(0xda3d40fc, FUTEX_WAIT_REQUEUE_PI, 2, NULL, 
0xda3d40b8 
|[pid 26579] futex(0xda3d40fc, FUTEX_WAKE_OP, 1, 1, 0xda3d40f8, 
FUTEX_OP_SET<<28|0<<12|FUTEX_OP_CMP_GT<<24|0x1) = -1 EINVAL (Invalid argument)
|[pid 26579] futex(0xda3d40fc, FUTEX_WAKE, 1) = -1 EINVAL (Invalid argument)

As you see the two waiting threads do FUTEX_WAIT_REQUEUE_PI and the
waker does FUTEX_WAKE* which is not valid. The program hangs at this
point.
With the patch attached:
|LD_LIBRARY_PATH=x/lib/aarch64-linux-gnu/ strace -f ../testcase 
|child_stack=0x8edb6b10, 
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
 parent_tidptr=0x8edb72d0, tls=0x8edb78f0, child_tidptr=0x8edb72d0) 
= 26660
|[pid 26660] futex(0xe4e1c0fc, FUTEX_WAIT, 1, NULL 
|[pid 26659] clone(child_stack=0x8e5b6b10, 
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID,
 parent_tidptr=0x8e5b72d0, tls=0x8e5b78f0, child_tidptr=0x8e5b72d0) 
= 26661
|[pid 26661] futex(0xe4e1c0fc, FUTEX_WAIT, 2, NULL 
|[pid 26659] futex(0xe4e1c0fc, FUTEX_WAKE_OP, 1, 1, 0xe4e1c0f8, 
FUTEX_OP_SET<<28|0<<12|FUTEX_OP_CMP_GT<<24|0x1) = 1
and so on, the program finishes.

Sebastian
From: John Ogness 
Date: Wed, 16 May 2018 22:34:41 +0200
Subject: [PATCH] condvar: do not use requeue for pshared condvars

With commit e42a990eccb (Update.) condvars were changed to not
store the mutex address when pshared. Instead, ~0l is stored.
This value is checked for in USE_REQUEUE_PI() to determine if
requeue should be used.

pthread_cond_signal() and pthread_cond_broadcast() both use
USE_REQUEUE_PI() with the mutex address stored on the condvar.

However, pthread_cond_wait() and pthread_cond_timedwait() use
USE_REQUEUE_PI() on the mutex address passed in from the caller
(even though that address is *not* stored on the condvar in the
pshared case). The result is that in the pshared case, the
wait functions are using requeue and the wake functions are
not! This is not allowed by the kernel (the waking futex call
returns EINVAL).

Modify the wait functions to use USE_REQUEUE_PI() on the mutex
address stored on the condvar, thus mirroring the behavior of
the wake functions.

Signed-off-by: John Ogness 
Acked-by: Sebastian Andrzej Siewior 
Reviewed-by: Kurt Kanzenbach 
Signed-off-by: Kurt Kanzenbach 
---
 nptl/pthread_cond_timedwait.c | 4 +++-
 nptl/pthread_cond_wait.c  | 4 +++-
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/nptl/pthread_cond_timedwait.c b/nptl/pthread_cond_timedwait.c
index 711a51de20..9e6a393a43 100644
--- a/nptl/pthread_cond_timedwait.c
+++ b/nptl/pthread_cond_timedwait.c
@@ -163,6 +163,8 @@ __pthread_cond_timedwait (pthread_cond_t *cond, pthread_mutex_t 

Bug#916925: marked as done (Use after free on pthread_create (glibc))

2019-02-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 21:47:22 +
with message-id 
and subject line Bug#916925: fixed in glibc 2.24-11+deb9u4
has caused the Debian Bug report #916925,
regarding Use after free on pthread_create (glibc)
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.)


-- 
916925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: glibc-source
Version: 2.24-11+deb9u3

We are using slurm, which uses a lot of pthreads, and it keeps exercising this 
bug that has already
been reported upstream 
(https://sourceware.org/bugzilla/show_bug.cgi?id=20116#c5), which was introduced
after glibc 2.19 and has been fixed in glibc 2.25. Can this patch be merged in 
Debian while we wait for buster?

I am using Debian GNU/Linux 9.3, kernel 4.9.0-5-amd64, libc6 2.24-11+deb9u3

--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.24-11+deb9u4

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 916...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 06 Feb 2019 22:17:41 +0100
Source: glibc
Binary: libc-bin libc-dev-bin libc-l10n glibc-doc glibc-source locales 
locales-all nscd multiarch-support libc6 libc6-dev libc6-dbg libc6-pic 
libc6-udeb libc6.1 libc6.1-dev libc6.1-dbg libc6.1-pic libc6.1-udeb libc0.3 
libc0.3-dev libc0.3-dbg libc0.3-pic libc0.3-udeb libc0.1 libc0.1-dev 
libc0.1-dbg libc0.1-pic libc0.1-udeb libc6-i386 libc6-dev-i386 libc6-sparc 
libc6-dev-sparc libc6-sparc64 libc6-dev-sparc64 libc6-s390 libc6-dev-s390 
libc6-amd64 libc6-dev-amd64 libc6-powerpc libc6-dev-powerpc libc6-ppc64 
libc6-dev-ppc64 libc6-mips32 libc6-dev-mips32 libc6-mipsn32 libc6-dev-mipsn32 
libc6-mips64 libc6-dev-mips64 libc0.1-i386 libc0.1-dev-i386 libc6-x32 
libc6-dev-x32 libc6-xen libc0.3-xen libc6.1-alphaev67 libc0.1-i686 libc0.3-i686 
libc6-i686
Architecture: source
Version: 2.24-11+deb9u4
Distribution: stretch
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Description:
 glibc-doc  - GNU C Library: Documentation
 glibc-source - GNU C Library: sources
 libc-bin   - GNU C Library: Binaries
 libc-dev-bin - GNU C Library: Development binaries
 libc-l10n  - GNU C Library: localization files
 libc0.1- GNU C Library: Shared libraries
 libc0.1-dbg - GNU C Library: detached debugging symbols
 libc0.1-dev - GNU C Library: Development Libraries and Header Files
 libc0.1-dev-i386 - GNU C Library: 32bit development libraries for AMD64
 libc0.1-i386 - GNU C Library: 32bit shared libraries for AMD64
 libc0.1-i686 - transitional dummy package
 libc0.1-pic - GNU C Library: PIC archive library
 libc0.1-udeb - GNU C Library: Shared libraries - udeb (udeb)
 libc0.3- GNU C Library: Shared libraries
 libc0.3-dbg - GNU C Library: detached debugging symbols
 libc0.3-dev - GNU C Library: Development Libraries and Header Files
 libc0.3-i686 - transitional dummy package
 libc0.3-pic - GNU C Library: PIC archive library
 libc0.3-udeb - GNU C Library: Shared libraries - udeb (udeb)
 libc0.3-xen - GNU C Library: Shared libraries [Xen version]
 libc6  - GNU C Library: Shared libraries
 libc6-amd64 - GNU C Library: 64bit Shared libraries for AMD64
 libc6-dbg  - GNU C Library: detached debugging symbols
 libc6-dev  - GNU C Library: Development Libraries and Header Files
 libc6-dev-amd64 - GNU C Library: 64bit Development Libraries for AMD64
 libc6-dev-i386 - GNU C Library: 32-bit development libraries for AMD64
 libc6-dev-mips32 - GNU C Library: o32 Development Libraries for MIPS
 libc6-dev-mips64 - GNU C Library: 64bit Development Libraries for MIPS64
 libc6-dev-mipsn32 - GNU C Library: n32 Development Libraries for MIPS64
 libc6-dev-powerpc - GNU C Library: 32bit powerpc development libraries for 
ppc64
 libc6-dev-ppc64 - GNU C Library: 64bit Development Libraries for PowerPC64
 libc6-dev-s390 - GNU C Library: 32bit Development Libraries for IBM zSeries
 libc6-dev-sparc

Bug#903554: marked as done (libc6: segfault in ld-2.24.so when running 'xl' from Xen, only on Skylake CPUs (upstream bug BZ#22636))

2019-02-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 21:47:22 +
with message-id 
and subject line Bug#903554: fixed in glibc 2.24-11+deb9u4
has caused the Debian Bug report #903554,
regarding libc6: segfault in ld-2.24.so when running 'xl' from Xen, only on 
Skylake CPUs (upstream bug BZ#22636)
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.)


-- 
903554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.24-11+deb9u3
Severity: normal

Dear Maintainer,

When I use 'xl create' or 'xl destroy' to manage Xen domUs, xl segfaults
with:

(gdb) run create /etc/xen/domU.cfg
Starting program: /usr/lib/xen-4.8/bin/xl create /etc/xen/domU.cfg
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Parsing config from /etc/xen/domU.cfg
[New Thread 0x77ff4700 (LWP 3311)]

Thread 2 "xl" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x77ff4700 (LWP 3311)]
0x77de2ff5 in _dl_lookup_symbol_x (undef_name=0x75478c63 
"_Unwind_Find_FDE", undef_map=0x55788310, 
ref=ref@entry=0x77ff2128, symbol_scope=0x55788668, 
version=0x55788a50, type_class=type_class@entry=1, flags=5, 
skip_map=0x0) at dl-lookup.c:833

Despite the segfault, it seems that the domU is running fine, which
might explain why this wasn't reported yet AFAIK.

In the exact same software environment, I cannot reproduce this on
pre-Skylake CPUs.

I could confirm that:
- upgrading glibc to 2.26-5 fixes the problem.
- 2.26-4 is still affected.

I looked at the changes between 2.26-4 and 2.26-5.

My initial guess was that this was BZ#22715 due to the link with
AVX-512. But backporting the fix (which is already in
release/2.24/master but not in the stretch package) did not solve the
issue.

However, backporting the fix for BZ#22636 fixed the issue (specifically
I backported
771c846a71d9ee14aa3b91fd184026482da585d9..abf2e34ee6a9cf1b7e5afddd13971754e5c5fa82
, from the release/2.25/master branch).


Could you please backport this fix to the stretch package?

Thanks!

Lucas




-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/64 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libc6 depends on:
ii  libgcc1  1:6.3.0-18+deb9u1

libc6 recommends no packages.

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.61
pn  glibc-doc  
ii  libc-l10n  2.24-11+deb9u3
ii  locales2.24-11+deb9u3

-- debconf information:
  glibc/disable-screensaver:
  glibc/upgrade: true
  glibc/restart-failed:
  glibc/restart-services:
  glibc/kernel-not-supported:
  glibc/kernel-too-old:
  libraries/restart-without-asking: false
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.24-11+deb9u4

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 903...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 06 Feb 2019 22:17:41 +0100
Source: glibc
Binary: libc-bin libc-dev-bin libc-l10n glibc-doc glibc-source locales 
locales-all nscd multiarch-support libc6 libc6-dev libc6-dbg libc6-pic 
libc6-udeb libc6.1 libc6.1-dev libc6.1-dbg libc6.1-pic libc6.1-udeb libc0.3 
libc0.3-dev libc0.3-dbg libc0.3-pic libc0.3-udeb libc0.1 libc0.1-dev 
libc0.1-dbg libc0.1-pic libc0.1-udeb libc6-i386 libc6-dev-i386 libc6-sparc 
libc6-dev-sparc libc6-sparc64 libc6-dev-sparc64 libc6-s390 libc6-dev-s390 
libc6-amd64 libc6-dev-amd64 libc6-powerpc libc6-dev-powerpc libc6-ppc64 
libc6-dev-ppc64

Bug#921165: marked as done (glibc: [INTL:ru] Updated Russian translation of debconf template)

2019-02-05 Thread Debian Bug Tracking System
Your message dated Tue, 05 Feb 2019 19:37:58 +
with message-id 
and subject line Bug#921165: fixed in glibc 2.28-6
has caused the Debian Bug report #921165,
regarding glibc: [INTL:ru] Updated Russian translation of debconf template
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.)


-- 
921165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

please find attached the updated Russian translation of debconf template for 
glibc.

With regards,
Lev Lamberov


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
# translation of ru.po to Russian
# Translation of glibc debconf .po to Russian
# This file is distributed under the same license as the eglibc package.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER.
#
# Yuri Kozlov , 2006.
# Sergey Alyoshin , 2007, 2008.
# Yuri Kozlov , 2009, 2011.
# Lev Lamberov , 2019.
msgid ""
msgstr ""
"Project-Id-Version: eglibc 2.13-23\n"
"Report-Msgid-Bugs-To: gl...@packages.debian.org\n"
"POT-Creation-Date: 2017-08-26 13:35+0200\n"
"PO-Revision-Date: 2019-01-30 19:31+0500\n"
"Last-Translator: Lev Lamberov \n"
"Language-Team: Russian \n"
"Language: ru\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.2.1\n"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n"
"%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"

#. Type: multiselect
#. Choices
#: ../debhelper.in/locales.templates:1001
msgid "All locales"
msgstr "Все локали"

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid "Locales to be generated:"
msgstr "Локали, которые будут созданы:"

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid ""
"Locales are a framework to switch between multiple languages and allow users "
"to use their language, country, characters, collation order, etc."
msgstr ""
"Локаль — это инфраструктура для поддержки в системе нескольких языков; она "
"позволяет пользователю настроить язык сообщений, страну, алфавит, порядок "
"сортировки и т. п."

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid ""
"Please choose which locales to generate. UTF-8 locales should be chosen by "
"default, particularly for new installations. Other character sets may be "
"useful for backwards compatibility with older systems and software."
msgstr ""
"Выберите создаваемые локали. Кодировка локали UTF-8 должна быть выбрана по "
"умолчанию, особенно при новой установке. Другие кодировки локали могут быть "
"полезны для обратной совместимости со старыми системами и программами."

#. Type: select
#. Choices
#: ../debhelper.in/locales.templates:2001
msgid "None"
msgstr "Нет"

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid "Default locale for the system environment:"
msgstr "Локаль по умолчанию в системном окружении:"

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid ""
"Many packages in Debian use locales to display text in the correct language "
"for the user. You can choose a default locale for the system from the "
"generated locales."
msgstr ""
"Многие пакеты в Debian используют локали для отображения сообщений на языке "
"пользователя. Вы можете выбрать из созданных локалей системную локаль по "
"умолчанию."

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid ""
"This will select the default language for the entire system. If this system "
"is a multi-user system where not all users are able to

Bug#920047: marked as done (glibc: CVE-2016-10739: getaddrinfo should reject IP addresses with trailing characters)

2019-02-05 Thread Debian Bug Tracking System
Your message dated Tue, 05 Feb 2019 19:37:58 +
with message-id 
and subject line Bug#920047: fixed in glibc 2.28-6
has caused the Debian Bug report #920047,
regarding glibc: CVE-2016-10739: getaddrinfo should reject IP addresses with 
trailing characters
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.)


-- 
920047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glibc
Version: 2.28-5--src
Severity: normal
Tags: patch security upstream
Forwarded: https://sourceware.org/bugzilla/show_bug.cgi?id=20018
Control: found -1 2.24-11+deb9u3
Control: found -1 2.24-11

Hi,

The following vulnerability was published for glibc.

CVE-2016-10739[0]:
| In the GNU C Library (aka glibc or libc6) through 2.28, the getaddrinfo
| function would successfully parse a string that contained an IPv4
| address followed by whitespace and arbitrary characters, which could
| lead applications to incorrectly assume that it had parsed a valid
| string, without the possibility of embedded HTTP headers or other
| potentially dangerous substrings.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-10739
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10739
[1] https://sourceware.org/bugzilla/show_bug.cgi?id=20018

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.28-6

We believe that the bug you reported is fixed in the latest version of
glibc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 05 Feb 2019 19:55:42 +0100
Source: glibc
Architecture: source
Version: 2.28-6
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 761300 908928 920047 921165
Changes:
 glibc (2.28-6) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/git-AT_EMPTY_PATH.diff: New patch, fixes qt's
 file size query.
   * debian/patches/hurd-i386/git-altstack.diff: New patch, fixes altstack
 initial state.
 .
   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix a buffer overflow in string/memory functions on x32 (CVE-2019-6488).
 - Reject IP addresses with trailing characters (CVE-2016-10739).  Closes:
   #920047.
 - Fix wrong return value for memcmp on amd64 and x32 due to mishandling
   of most significant bit (CVE-2019-7309).
   * Update Russian debconf translation, by Lev Lamberov.  Closes:
 #921165.
   * debian/patches/any/local-ldso-disable-hwcap.diff: only check for
 /etc/ld.so.nohwcap on alpha, hurd-i386 and i386. Based on a patch from
 Josh Triplett.  Closes: #908928.
   * debian/patches/any/git-libio-stdout-putc.diff: fix puts and putchar output
 with change stdout pointer.  Closes: #761300.
   * debhelper.in/locales.bug-presubj: drop obsolete file, the dependency
 mechanism for locales has been changes a lot of time ago.
Checksums-Sha1:
 c09451059d222a7b4615af2f5547437d570f9025 8885 glibc_2.28-6.dsc
 e32156b4d0791ec0af883685e726f618160c1284 873424 glibc_2.28-6.debian.tar.xz
 455f82ecf3fe6c42c28048462e3ee74da2b2ed5c 7303 glibc_2.28-6_source.buildinfo
Checksums-Sha256:
 469d2e7c196f3be89ec55f8cf28a5d8d0ef276ac227be063f782d1b9f85a65a8 8885 
glibc_2.28-6.dsc
 e94e20f890cd3e1b3bcb9e5dc3cc4725b91e9101a8a93c2588b506f73b688924 873424 
glibc_2.28-6.debian.tar.xz
 a1dacf4de9985443c1e80d9332e2e8bea963abbfcffa1b30e33cf637c8b05bf3 7303 
glibc_2.28-6_source.buildinfo
Files:
 9ef64b9ffb224bb9f67441398348154b 8885 libs required glibc_2.28-6.dsc
 fea4aa332e15e9acbe37484470e9e47f 873424 libs required 
glibc_2.28-6.debian.tar.xz
 f219b499b86ca6b5dc46f30347b7f828 7303 libs required 
glibc_

Bug#908928: marked as done (Most architectures do not need to check /etc/ld.so.nohwcap)

2019-02-05 Thread Debian Bug Tracking System
Your message dated Tue, 05 Feb 2019 19:37:58 +
with message-id 
and subject line Bug#908928: fixed in glibc 2.28-6
has caused the Debian Bug report #908928,
regarding Most architectures do not need to check /etc/ld.so.nohwcap
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.)


-- 
908928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glibc
Version: 2.27-6
Tags: patch

Debian's glibc includes a Debian-specific patch that makes the dynamic
linker check for the existence of /etc/ld.so.nohwcap (multiple times)
before loading a shared library, and disable loading of libraries in
hwcap paths (optimized libraries) if found. This gets created in the
libc6 (or equivalent) package preinst, and removed by the various libc
packages' postinsts once all glibc packages have been upgraded to
identical versions.

However, only two architectures have hwcap-based libc packages: i386
(which has libc6-xen), and alpha (which has libc6.1-alphaev67). Other
architectures don't have any such packages, but still spend time
checking for /etc/ld.so.nohwcap on every dynamic library load.

I measured the impact of this, by running a defconfig kernel build under
strace. These access syscalls took an average of 17us per call, and
comprised 125453 (0.66%) of the 19069475 syscalls during the build.
Overall, they added an estimated 2.1s to the build.

The attached patch makes the check for /etc/ld.so.nohwcap conditional
based on architecture, and only includes it on i386 and alpha. This
removes the overhead from all other architectures.

Note that if any future architecture ever needed to add such libraries
(and we don't have a better mechanism to handle this at that time), we
can easily add the check on that architecture.

- Josh Triplett
diff --git a/debian/patches/any/local-ldso-disable-hwcap.diff b/debian/patches/any/local-ldso-disable-hwcap.diff
index 933032ec..dccbfe6a 100644
--- a/debian/patches/any/local-ldso-disable-hwcap.diff
+++ b/debian/patches/any/local-ldso-disable-hwcap.diff
@@ -24,7 +24,7 @@
 
  #include 
  #include 
-@@ -44,6 +46,7 @@
+@@ -43,6 +46,7 @@
size_t cnt = platform != NULL;
size_t n, m;
size_t total;
@@ -32,10 +32,11 @@
struct r_strlenpair *result;
struct r_strlenpair *rp;
char *cp;
-@@ -113,8 +116,22 @@
+@@ -124,8 +128,24 @@
/* For TLS enabled builds always add 'tls'.  */
++cnt;
  
++#ifdef NEED_LD_SO_NOHWCAP
 +  if (__access_noerrno ("/etc/ld.so.nohwcap", F_OK) == 0)
 +{
 +  /* If hwcap is disabled, we only have the base directory to search.  */
@@ -49,6 +50,7 @@
 +  *sz = 1;
 +  return result;
 +}
++#endif
 +
/* Create temporary data structure to generate result table.  */
 -  struct r_strlenpair temp[cnt];
@@ -56,14 +58,16 @@
m = 0;
  #ifdef NEED_DL_SYSINFO_DSO
if (dsocaps != NULL)
-@@ -199,8 +216,11 @@
+@@ -210,8 +230,13 @@
*sz = 1 << cnt;
result = (struct r_strlenpair *) malloc (*sz * sizeof (*result) + total);
if (result == NULL)
 -_dl_signal_error (ENOMEM, NULL, NULL,
 -		  N_("cannot create capability list"));
 +{
++#ifdef NEED_LD_SO_NOHWCAP
 +no_memory:
++#endif
 +  _dl_signal_error (ENOMEM, NULL, NULL,
 +		 	N_("cannot create capability list"));
 +}
@@ -82,7 +86,7 @@
  
  #ifndef _DL_PLATFORMS_COUNT
  # define _DL_PLATFORMS_COUNT 0
-@@ -248,6 +250,7 @@
+@@ -246,6 +249,7 @@
if (cache_new != (void *) -1)
  {
uint64_t platform;
@@ -90,17 +94,19 @@
  
/* This is where the strings start.  */
cache_data = (const char *) cache_new;
-@@ -261,6 +264,9 @@
+@@ -259,6 +263,11 @@
  
uint64_t hwcap_mask = GET_HWCAP_MASK();
  
++#ifdef NEED_LD_SO_NOHWCAP
 +  if (__access_noerrno ("/etc/ld.so.nohwcap", F_OK) == 0)
 +	disable_hwcap = 1;
++#endif
 +
  #define _DL_HWCAP_TLS_MASK (1LL << 63)
uint64_t hwcap_exclude = ~((GLRO(dl_hwcap) & hwcap_mask)
   | _DL_HWCAP_PLATFORM | _DL_HWCAP_TLS_MASK);
-@@ -271,6 +277,8 @@
+@@ -269,6 +278,8 @@
  	continue;			  \
if (GLRO(dl_osversion) && lib->osversion > GLRO(dl_osversion))	  \
  	continue;			  \
@@ -109,3 +115,25 @@
if (_DL_PLATFORMS_COUNT		  \
  	  && (lib->hwcap & _DL_HWCAP_PLATFORM) != 0			  \
  	  && (lib->hwcap & _DL_HWCAP_PLATFORM) != platform)		  \
+--- a/sysdeps/alpha/ldsodefs.h
 b/sysdeps/alpha/ldsodefs.h
+@@ -37,6 +37,8 @@ struct La_alpha_retval;
+   struct La_alpha_r

  1   2   3   4   5   6   7   8   9   10   >