Processed (with 2 errors): Re: Bug#972552: Buster->Sid upgrades fail with 'Could not perform immediate configuration on 'libnss-nis:amd64''

2020-10-20 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 apt
Bug #972552 [libnss-nis] Buster->Sid upgrades fail with 'Could not perform 
immediate configuration on 'libnss-nis:amd64''
Bug reassigned from package 'libnss-nis' to 'apt'.
No longer marked as found in versions libnss-nis/3.1-4.
Ignoring request to alter fixed versions of bug #972552 to the same values 
previously set
> forcemerge 953260 -1
Failed to forcibly merge 953260: Not altering archived bugs; see unarchive.

> affects 953260 libnss-nis
Failed to mark 953260 as affecting package(s): Not altering archived bugs; see 
unarchive.


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



Processed: Bug#972510 marked as pending in glibc

2020-10-19 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #972510 [src:glibc] glibc: Please ignore misc/tst-sbrk and/or 
misc/tst-sbrk-pie on all archs
Added tag(s) pending.

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



Processed: retitle 972510 to glibc: Please ignore misc/tst-sbrk and/or misc/tst-sbrk-pie on all archs

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

> retitle 972510 glibc: Please ignore misc/tst-sbrk and/or misc/tst-sbrk-pie on 
> all archs
Bug #972510 [src:glibc] (no subject)
Changed Bug title to 'glibc: Please ignore misc/tst-sbrk and/or 
misc/tst-sbrk-pie on all archs' from '(no subject)'.
> thanks
Stopping processing here.

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



Processed: Re: Bug#971537: Impossible to run /sbin/ldconfig on buster using qemu-i386-static

2020-10-11 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 qemu-user-static
Bug #971537 [libc-bin] Impossible to run /sbin/ldconfig on buster using 
qemu-i386-static
Bug reassigned from package 'libc-bin' to 'qemu-user-static'.
No longer marked as found in versions glibc/2.28-10.
Ignoring request to alter fixed versions of bug #971537 to the same values 
previously set
> found -1 qemu-user-static/1:3.1+dfsg-8
Bug #971537 [qemu-user-static] Impossible to run /sbin/ldconfig on buster using 
qemu-i386-static
The source qemu-user-static and version 1:3.1+dfsg-8 do not appear to match any 
binary packages
Marked as found in versions qemu-user-static/1:3.1+dfsg-8.
> fixed -1 qemu-user-static/1:5.0-1
Bug #971537 [qemu-user-static] Impossible to run /sbin/ldconfig on buster using 
qemu-i386-static
The source qemu-user-static and version 1:5.0-1 do not appear to match any 
binary packages
Marked as fixed in versions qemu-user-static/1:5.0-1.
> affect -1 libc-bin
Bug #971537 [qemu-user-static] Impossible to run /sbin/ldconfig on buster using 
qemu-i386-static
Added indication that 971537 affects libc-bin

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



Bug#969618: marked as done (getopt: optarg is NULL outside of loop)

2020-10-11 Thread Debian Bug Tracking System
Your message dated Sun, 11 Oct 2020 13:11:57 +0200
with message-id <2020101157.ga1454...@aurel32.net>
and subject line Re: Bug#969618: getopt: optarg is NULL outside of loop
has caused the Debian Bug report #969618,
regarding getopt: optarg is NULL outside of loop
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
969618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.31-3
Severity: normal
X-Debbugs-Cc: 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I suspect this is an upstream problem but I'm reporting it here
first per their policy [1] since I'm unsure.

Both POSIX (including the Issue 8 draft) and the GNU C Library
manual say that when an argument is provided for an option, a
pointer to it is provided as optarg.

It seems like after leaving the while() loop getopt is usually
used in, optarg points to NULL instead, even if no other options,
bearing arguments or not, are used. It's a little grey but POSIX
doesn't seem to permit this, and the (non-DFSG) glibc manual could
be construed as saying it should work fine this way:
> If the option has an argument, getopt returns the argument by storing
> it in the variable optarg. You don’t ordinarily need to copy the optarg
> string, since it is a pointer into the original argv array, not into a
> static area that might be overwritten. 

Everything works fine with Musl libc which can be tried with musl-gcc.
Consider this example program:

#define _POSIX_C_SOURCE 200809L
#include 
#include 
#include 
#include 
int main(int argc, char *argv[]) {
int opt;
while((opt = getopt(argc, argv, "a:")) != -1) {}
assert(optarg != NULL);
}

If this is invoked as './a.out -afoo', the inner assertion will
the last assertion will fail with glibc. In the absence of
a compelling reason (such as if I were using the GNU extension of
having an optional argument via '::'), standards aside, it would
be helpful for me if the variable could be left alone.

[1] https://sourceware.org/glibc/wiki/FilingBugs
[2] https://www.gnu.org/software/libc/manual/html_node/Using-Getopt.html
- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (2, 'unstable'), (1, 'testing-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.7.0-3-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libc6 depends on:
ii  libcrypt1  1:4.4.17-1
ii  libgcc-s1  10.2.0-5

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

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.74
ii  glibc-doc  2.31-3
ii  libc-l10n  2.31-3
ii  locales2.31-3

- -- debconf information:
  glibc/restart-failed:
  glibc/upgrade: true
  glibc/kernel-too-old:
  glibc/kernel-not-supported:
* libraries/restart-without-asking: true
  glibc/disable-screensaver:
  glibc/restart-services:

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQT287WtmxUhmhucNnhyvHFIwKstpwUCX1Q6TgAKCRByvHFIwKst
p+D0AQDqLFwxGh/oTV+13E5stB3WvG9zD0tpMiol/xHW0QuERgEAsPKsGbQBW2nG
VFzkfExA5cGyGj0GW7IyKg42+wLaZgI=
=WQf5
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
On 2020-09-06 21:47, Aurelien Jarno wrote:
> Hi,
> 
> On 2020-09-06 09:25, Florian Weimer wrote:
> > * John Scott:
> > 
> > > #define _POSIX_C_SOURCE 200809L
> > > #include 
> > > #include 
> > > #include 
> > > #include 
> > > int main(int argc, char *argv[]) {
> > >   int opt;
> > >   while((opt = getopt(argc, argv, "a:")) != -1) {}
> > >   assert(optarg != NULL);
> > > }
> > >
> > > If this is invoked as './a.out -afoo', the inner assertion will
> > > the last assertion will fail with glibc.
> > 
> > POSIX leaves it unspecified if optarg is changed if getopt returns -1.
> > Only optind must be left unchanged.  I do not think this is a glibc
> > bug (or a musl bug).
> 
> Thanks Florian for the explanations. This can be confirmed that optarg
> is not NULL by moving the assert in the while loop. So it doesn't seems
> like a bug to me.

I am therefore closing it.

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


Processed: found 324075 in 2.31-2

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

> found 324075 2.31-2
Bug #324075 [libc6] libc6: putwchar() returns WEOF without setting errno to 
EILSEQ
Marked as found in versions glibc/2.31-2.
> thanks
Stopping processing here.

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



Bug#512525: marked as done (regexp: missing support for non-localized but utf8 environment)

2020-10-10 Thread Debian Bug Tracking System
Your message dated Sun, 11 Oct 2020 01:56:57 +0200
with message-id <20201010235657.z7kjagdr6yhq5bal@function>
and subject line Re: Bug#512525: regexp: missing support for non-localized but 
utf8 environment
has caused the Debian Bug report #512525,
regarding regexp: missing support for non-localized but utf8 environment
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.)


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

Hello,

My goal is to grep for intervals of unicode characters in utf-8 files.
However, character intervals depend on locales, so I have to set
LC_COLLATE to C, but doing so makes grep not know that my files are
utf-8, so I set LC_CTYPE to a UTF-8 locale, however that fails:

$ LANG=C LC_CTYPE=fr_FR.UTF-8 grep '[é-ë]' test.txt
grep: Invalid collation character

which comes from libc' re_compile_pattern() function.

Samuel

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

Kernel: Linux 2.6.28 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libc6 depends on:
ii  libgcc1  1:4.3.2-1.1 GCC support library

libc6 recommends no packages.

Versions of packages libc6 suggests:
ii  glibc-doc 2.7-18 GNU C Library: Documentation
ii  locales   2.7-18 GNU C Library: National Language (

-- debconf information excluded

-- 
Samuel
We are Pentium of Borg. Division is futile. You will be approximated.
(seen in someone's .signature)


--- End Message ---
--- Begin Message ---
Hello,

John Scott, le sam. 10 oct. 2020 09:29:09 -0400, a ecrit:
> On Wednesday, January 21, 2009 8:27:19 AM EDT Samuel Thibault wrote:
> > My goal is to grep for intervals of unicode characters in utf-8 files.
> > However, character intervals depend on locales, so I have to set
> > LC_COLLATE to C, but doing so makes grep not know that my files are
> > utf-8, so I set LC_CTYPE to a UTF-8 locale, however that fails:
> > 
> > $ LANG=C LC_CTYPE=fr_FR.UTF-8 grep '[é-ë]' test.txt
> > grep: Invalid collation character
> > 
> > which comes from libc' re_compile_pattern() function.
> For this you could try the C.UTF-8 locale.

Ah, that appeared in the meantime indeed :)

Samuel--- End Message ---


Processed: Default to C.UTF-8: merge reports

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

> notfound 874160 2.24-17
Bug #874160 [src:glibc] src:glibc: default locale to C.UTF-8
No longer marked as found in versions glibc/2.24-17.
> reassign 874160 libc6 2.24-17
Bug #874160 [src:glibc] src:glibc: default locale to C.UTF-8
Bug reassigned from package 'src:glibc' to 'libc6'.
Ignoring request to alter found versions of bug #874160 to the same values 
previously set
Ignoring request to alter fixed versions of bug #874160 to the same values 
previously set
Bug #874160 [libc6] src:glibc: default locale to C.UTF-8
Marked as found in versions glibc/2.24-17.
> severity 874160 normal
Bug #874160 [libc6] src:glibc: default locale to C.UTF-8
Severity set to 'normal' from 'wishlist'
> forwarded 874160 https://sourceware.org/bugzilla/show_bug.cgi?id=17318
Bug #874160 [libc6] src:glibc: default locale to C.UTF-8
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=17318'.
> forcemerge 719590 874160
Bug #719590 [libc6] Provide a C.UTF-8 locale by default
Bug #748215 [libc6] Provide a C.UTF-8 locale by default
Bug #748215 [libc6] Provide a C.UTF-8 locale by default
Marked as found in versions glibc/2.24-17.
Marked as found in versions glibc/2.24-2 and glibc/2.24-17.
Added tag(s) patch.
Added tag(s) patch.
Bug #874160 [libc6] src:glibc: default locale to C.UTF-8
Marked as found in versions eglibc/2.18-1, eglibc/2.17-92, and glibc/2.24-2.
Added tag(s) l10n and upstream.
Merged 719590 748215 874160
> thanks
Stopping processing here.

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



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

2020-10-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Oct 2020 21:18:50 +
with message-id 
and subject line Bug#963007: fixed in tzdata 2020b-1
has caused the Debian Bug report #963007,
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.)


-- 
963007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963007
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. 
 

-- 
Kind regards,
Frans Spiesschaert



nl.po.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: tzdata
Source-Version: 2020b-1
Done: Aurelien Jarno 

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 963...@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: Sat, 10 Oct 2020 22:50:56 +0200
Source: tzdata
Architecture: source
Version: 2020b-1
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 871051 960783 963007
Changes:
 tzdata (2020b-1) unstable; urgency=medium
 .
   * New upstream version, affecting the following past and future
 timestamps:
 - Revised predictions for Morocco's changes starting in 2023.
 - Macquarie Island has stayed in sync with Tasmania since 2011.
 - Casey, Antarctica is at +08 in winter and +11 in summer since 2018.
   * Update German debconf translation, by Helge Kreutzmann.  Closes:
 #960783.
   * Update Dutch debconf translation, by Frans Spiesschaert.  Closes:
 #963007.
   * Update Portuguese debconf translation, by Rui Branco.  Closes:
 #871051.
   * Update debian/upstream/signing-key.asc.
   * Get rid of old SystemV timezones, as this has been fully removed
 upstream. Convert existing configuration to the "new" America/*
 names.
   * Drop pacificnew support, it has been removed upstream.
Checksums-Sha1:
 82198f6bc736614be00f77ac90d2b672fe05e32d 2237 tzdata_2020b-1.dsc
 89f5295b0bdbc8315f97fd8f7f5ed035f238a1e7 400017 tzdata_2020b.orig.tar.gz
 c9327c81eecf9d2804902bfac4d1d8f70ba82941 833 tzdata_2020b.orig.tar.gz.asc
 f7761325f7c51a92aab1a3e3639aa650e922b4e4 105064 tzdata_2020b-1.debian.tar.xz
 1d9369046ebc0632aff36c820d543684e5458f61 5158 tzdata_2020b-1_source.buildinfo
Checksums-Sha256:
 f16572adefedff758212c5ffede67ecba6ffc165507f3e90714eae075632a7bc 2237 
tzdata_2020b-1.dsc
 9b053f951d245ce89d850b96ee4711d82d833559b1fc96ba19f90bc4d745e809 400017 
tzdata_2020b.orig.tar.gz
 2e9e0492e556500d9f6d33b4290667d53d85af37f14929371f56c147354157ce 833 
tzdata_2020b.orig.tar.gz.asc
 e801eb64e5b44b092d11dd73bc60216bc2fc57a7a1ca98f5bb56b1c028e03dbc 105064 
tzdata_2020b-1.debian.tar.xz
 39293012de53cb994cc111e0bae7de9929f20c470f96074354847f141dfc79ac 5158 
tzdata_2020b-1_source.buildinfo
Files:
 e3a14b11359f700bad69f5e685439142 2237 localization required tzdata_2020b-1.dsc
 8902c580f7042c0ce94a6b05b0798ec9 400017 localization required 
tzdata_2020b.orig.tar.gz
 17ec06854d8f0e7ac4ea9e3a1c192733 833 localization required 
tzdata_2020b.orig.tar.gz.asc
 3ab087700c1a22c6b52c6bc2bcb94d4e 105064 localization required 
tzdata_2020b-1.debian.tar.xz
 e1ee19f287ea9a2c7fcd06a74e32bffe 5158 localization required 
tzdata_2020b-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl+CHu8ACgkQE4jA+Jno
M2v/Ig/+Iazdn5KwnKgeE9lZYLOgtL8BYsJO/UbEtijj4LA56BKJFBIVegr4IwNF
nAHP9v5GKEw9YcclfpKzs6ii8BT5i8OzQ3kT/JcZScs6BGdUDePyqeBTjmq7wh47
rx0PWoIUdCHaVITfQPaDY9o0nfxNRWjnpnjIIYYw/Jl8cKsm1b9YkzXg2ViFUUk/
QcAKDrhXYZ20gIeBNhkr+YuUg5UtgpTNP86DjUxIh6fu0xI4h7GB/KiF9BJW+v8O
Pw2ywYppMdR74rVy0NSrnSDlQ+KPZpiS0YGM28lBq+fFfX3Jt/XLUw

Bug#960783: marked as done (tzdata: [INTL:de] updated German debconf translation)

2020-10-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Oct 2020 21:18:50 +
with message-id 
and subject line Bug#960783: fixed in tzdata 2020b-1
has caused the Debian Bug report #960783,
regarding tzdata: [INTL:de] 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.)


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

Please find the updated German debconf translation for tzdata
attached.

Please place this file in debian/po/ as de.po for your next upload.

If you update your template, please use 
'msgfmt --statistics '
to check the po-files for fuzzy or untranslated strings.

If there are such strings, please contact me so I can update the 
German translation.

Greetings
Helge
# Translation of tzdata debconf templates to German
# Copyright (C) Helge Kreutzmann , 2007, 2008.
# Copyright (C) Holger Wansing , 2010, 2011, 2013, 
2016, 2017.
# This file is distributed under the same license as the tzdata package.
# Holger Wansing , 2019.
msgid ""
msgstr ""
"Project-Id-Version: tzdata 2020a-20a-1\n"
"Report-Msgid-Bugs-To: tzd...@packages.debian.org\n"
"POT-Creation-Date: 2020-04-24 21:28+0200\n"
"PO-Revision-Date: 2020-05-16 17:58+0200\n"
"Last-Translator: Holger Wansing \n"
"Language-Team: German \n"
"Language: de\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: Lokalize 2.0\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 "Afrika"

#. 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 "Amerika"

#. 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 "Antarktis"

#. 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 "Australien"

#. 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 "Arktis"

#. 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 "Asien"

#. 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 "Atlantic"
msgstr "Atlantik"

#. 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 "Europe"
msgstr "Europa"

#. Type: select
#. Choices
#. Note to translators:
#. - "Etc" will present users with a list
#. of &

Bug#871051: marked as done (tzdata: [INTL:pt] Updated Portuguese translation for debconf messages)

2020-10-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Oct 2020 21:18:50 +
with message-id 
and subject line Bug#871051: fixed in tzdata 2020b-1
has caused the Debian Bug report #871051,
regarding tzdata: [INTL:pt] Updated Portuguese translation for 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.)


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

Package: fookebox
Version: 2017b-2
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for tzdata's debconf messages.
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team .
--
Best regards,

"Traduz" - Portuguese Translation Team
http://www.DebianPT.org









# Portuguese translations for tzdata package.
# Copyright (C) 2007 Ricardo Silva
# This file is distributed under the same license as the tzdata package.
# Ricardo Silva , 2007-2008.
# Miguel Figueiredo , 2011-2013.
# Rui Branco , 2017.
#
msgid ""
msgstr ""
"Project-Id-Version: tzdata 2017b-2\n"
"Report-Msgid-Bugs-To: tzd...@packages.debian.org\n"
"POT-Creation-Date: 2017-03-04 01:52+0100\n"
"PO-Revision-Date: 2017-08-05 11:05+0100\n"
"Last-Translator: Rui Branco \n"
"Language-Team: Portuguese \n"
"Language: pt\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Gtranslator 2.91.7\n"
"Plural-Forms: nplurals=2; plural=(n != 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 "África"

#. 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érica"

#. 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 "Antárctida"

#. 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 "Austrália"

#. 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 "Árctico"

#. 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 "Ásia"

#. 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 "Atlantic"
msgstr "Atlântico"

#. 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 "Europe"
msgstr "Europa"

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

Bug#968260: marked as done (libc6: breaks translations when changing the charset to ...//TRANSLIT)

2020-10-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Oct 2020 20:33:37 +
with message-id 
and subject line Bug#968260: fixed in glibc 2.31-4
has caused the Debian Bug report #968260,
regarding libc6: breaks translations when changing the charset to ...//TRANSLIT
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.)


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

Since the upgrade to 2.31-3, the translations are no longer working
in Mutt.

In my config, the charset gets automatically set to UTF-8//TRANSLIT
(possibly with something else instead of UTF-8). There is the same
issue with ISO-8859-1//TRANSLIT, but not with UTF-8 or ISO-8859-1.

Reverting to 2.31-2 solves the issue (at least with UTF-8//TRANSLIT).

I can reproduce the issue with:

  LC_MESSAGES=fr_FR /usr/bin/mutt -F muttrc foo

where the muttrc file contains:

set charset=UTF-8//TRANSLIT

or

set charset=ISO-8859-1//TRANSLIT

I get "To: foo@..." instead of "À : foo@...".

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

Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libc6 depends on:
ii  libcrypt1  1:4.4.16-1
ii  libgcc-s1  10.2.0-5

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

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.74
ii  glibc-doc  2.31-3
ii  libc-l10n  2.31-3
ii  locales2.31-3

-- debconf information:
  glibc/kernel-not-supported:
  glibc/disable-screensaver:
* glibc/restart-services: postfix cups cron atd
  glibc/kernel-too-old:
  glibc/upgrade: true
* libraries/restart-without-asking: false
  glibc/restart-failed:

-- 
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 ---
--- Begin Message ---
Source: glibc
Source-Version: 2.31-4
Done: Aurelien Jarno 

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 968...@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: Sat, 10 Oct 2020 21:54:24 +0200
Source: glibc
Architecture: source
Version: 2.31-4
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 968260 968342 969219 970199
Changes:
 glibc (2.31-4) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/{unsubmitted-sbrk-_end.diff,tg-pie-sbrk.diff}:
 Merge into...
   * debian/patches/hurd-i386/git-sbrk-end.diff: ... committed patch.
   * debian/patches/hurd-i386/unsubmitted-sched_sets.diff: Rename to...
   * debian/patches/hurd-i386/git-sched_sets.diff: ... committed patch.
   * debian/patches/hurd-i386/local-posix_cputime.diff: New patch to avoid
 applications trying to use extended clock ids.
   * debian/patches/hurd-i386/git-bsd4.3-ioctls.diff: New patch to avoid
 defining elder macros.
 .
   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Handle translation output codesets with suffixes.  Closes: #968260.
   * debian/control.in/libc: add a Breaks: against libgegl-0.4-0 (<< 0.4.18).
 Closes: #968342.
   * debian/control.in/libc: add a Breaks: against busybox (<< 1.30.1-6) due to
 bug #966074.
   * debian/debhelper.in/libc-dev{,-alt}.lintian-overrides: remove files as
 

Bug#970199: marked as done (glibc: [INTL:pt_BR] Brazilian Portuguese debconf templates translation)

2020-10-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Oct 2020 20:33:37 +
with message-id 
and subject line Bug#970199: fixed in glibc 2.31-4
has caused the Debian Bug report #970199,
regarding glibc: [INTL:pt_BR] Brazilian Portuguese debconf templates 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.)


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

Package: glibc
Tags: l10n patch
Severity: wishlist

Hello,

Please, Could you update the Brazilian Portuguese Translation?

Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is
tested with msgfmt and podebconf-display-po.

Kind regards.


pt_BR.po.gz
Description: application/gzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.31-4
Done: Aurelien Jarno 

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 970...@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: Sat, 10 Oct 2020 21:54:24 +0200
Source: glibc
Architecture: source
Version: 2.31-4
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 968260 968342 969219 970199
Changes:
 glibc (2.31-4) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/{unsubmitted-sbrk-_end.diff,tg-pie-sbrk.diff}:
 Merge into...
   * debian/patches/hurd-i386/git-sbrk-end.diff: ... committed patch.
   * debian/patches/hurd-i386/unsubmitted-sched_sets.diff: Rename to...
   * debian/patches/hurd-i386/git-sched_sets.diff: ... committed patch.
   * debian/patches/hurd-i386/local-posix_cputime.diff: New patch to avoid
 applications trying to use extended clock ids.
   * debian/patches/hurd-i386/git-bsd4.3-ioctls.diff: New patch to avoid
 defining elder macros.
 .
   [ Aurelien Jarno ]
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Handle translation output codesets with suffixes.  Closes: #968260.
   * debian/control.in/libc: add a Breaks: against libgegl-0.4-0 (<< 0.4.18).
 Closes: #968342.
   * debian/control.in/libc: add a Breaks: against busybox (<< 1.30.1-6) due to
 bug #966074.
   * debian/debhelper.in/libc-dev{,-alt}.lintian-overrides: remove files as
 lintian is now smarter.
   * debian/po/it.po: Update Italian debconf translation, by Luca Monducci.
 Closes: #969219.
   * debian/po/pt_BR.po: Update Brazilian Portuguese debconf translation, by
 Adriano Rafael Gomes. Closes: #970199.
   * debian/po/de.po: recode to UTF-8.
   * debian/rules.d/build.mk: stop passing --enable-obsolete-nsl.
   * debian/debhelper.in/libc-dev{,-alt}.install: do not install libnsl.a.
   * debian/debhelper.in/libc-dev.install.hurd-i386: ditto.
   * debian/libc0.1.symbols.common, debian/libc0.3.symbols.hurd-i386,
 debian/libc6.1.symbols.alpha, debian/libc6.symbols{common,hppa,sparc}:
 remove libnss_nis.so.2 and libnss_nisplus.so.2 symbols.
   * debian/rules.d/build.mk: do not ship  and
  as they are shipped by libnsl-dev.
   * debian/control.in/libc, debian/rules.d/debhelper.mk: make libc6 to depend 
on
 libnss-nis and libnss-nisplus, except for stage1 and stage2.
   * debian/control.in/libc, debian/rules.d/debhelper.mk: make libc6-dev to
 depend on libnsl-dev, except for stage1 and stage2.
Checksums-Sha1:
 98a5a1dc6168fd74dab01f9e9767be6053682cb3 8195 glibc_2.31-4.dsc
 eba880f310ed80b875cac127a940106b1405b01f 845380 glibc_2.31-4.debian.tar.xz
 1887144ea4177972e0ec4a99ef0c93a95468ac81 6769 glibc_2.31-4_source.buildinfo
Checksums-Sha256:
 a6785bf68ba69e80f98ec3ed1855981f628cfa7045c62fa8d74cd2631589f5e7 8195 
glibc_2.31-4.dsc
 c4ee83f481d8c640ab1a5309d44bd09ab21f24f400116010921ec73a180bd255 845380 
glibc_2.31-4.debian.tar.xz
 6d3ae5add8980e89c45e614669b4585a8e64beab472697687df94c848b97266e 6769 
glibc_2.31-4_source.buildinfo
Files:
 1434ac15497025a4dd381028972765

Bug#969219: marked as done (glibc: [INTL:it] Italian translations updated)

2020-10-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Oct 2020 20:33:37 +
with message-id 
and subject line Bug#969219: fixed in glibc 2.31-4
has caused the Debian Bug report #969219,
regarding glibc: [INTL:it] Italian translations updated
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.)


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

Hi,
updated Italian translation for debconf templates is attached.

Regards,
Luca




# Italian (it) translation of debconf templates for glibc
# This file is distributed under the same license as the glibc package.
# Luca Monducci , 2005-2020.
#
msgid ""
msgstr ""
"Project-Id-Version: glibc 2.31 debconf templates\n"
"Report-Msgid-Bugs-To: gl...@packages.debian.org\n"
"POT-Creation-Date: 2017-08-26 13:35+0200\n"
"PO-Revision-Date: 2020-08-29 14:41+0200\n"
"Last-Translator: Luca Monducci \n"
"Language-Team: Italian \n"
"Language: it\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: multiselect
#. Choices
#: ../debhelper.in/locales.templates:1001
msgid "All locales"
msgstr "Tutti i «locale»"

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid "Locales to be generated:"
msgstr "«Locale» da generare:"

#. 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 ""
"I «locale» sono l'infrastruttura che permette di passare da una lingua a "
"un'altra e consente agli utenti di utilizzare la propria lingua, paese, "
"caratteri, criteri di ordinamento, ecc."

#. 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 ""
"Scegliere quali «locale» generare. È opportuno scegliere i «locale» UTF-8, "
"in particolare sulle nuove installazioni. Gli altri set di caratteri "
"potrebbero essere utili per risolvere problemi di compatibilità all'indietro "
"con sistemi o programmi più vecchi."

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

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid "Default locale for the system environment:"
msgstr "«Locale» predefinito sul sistema:"

#. 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 ""
"Molti pacchetti Debian usano i «locale» per mostrare messaggi nella lingua "
"dell'utente. È possibile scegliere, fra quelli generati, un «locale» come "
"predefinito per il sistema."

#. 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 speak the default "
"language, they will experience difficulties."
msgstr ""
"Questo imposta la lingua predefinita per l'intero sistema. Se questo è un "
"sistema multi-utente e alcuni utenti non parlano la lingua predefinita, "
"quegli utenti potrebbero avere delle difficoltà."

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid "Do you want to upgrade glibc now?"
msgstr "Aggiornare glibc adesso?"

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid ""
"Running services and programs that are using NSS need to be restarted, "
"otherwise they might not be able to do lookup or authentication any more. "
"The installation process i

Processed: Bug#968260 marked as pending in glibc

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

> tag -1 pending
Bug #968260 [libc6] libc6: breaks translations when changing the charset to 
...//TRANSLIT
Added tag(s) pending.

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



Processed (with 2 errors): Bug#725936: close attempt #2 electric boogaloo

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

> reopen 725936 !
Bug #725936 {Done: John Scott } [libc-bin] getconf: 
bash-completion support
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
Changed Bug submitter to 'John Scott ' from 'Josh Triplett 
'.
No longer marked as fixed in versions 1:2.8-1.
> reassign 725936 bash-completion 1:2.0-1
Bug #725936 [libc-bin] getconf: bash-completion support
Bug reassigned from package 'libc-bin' to 'bash-completion'.
No longer marked as found in versions eglibc/2.17-93.
Ignoring request to alter fixed versions of bug #725936 to the same values 
previously set
Bug #725936 [bash-completion] getconf: bash-completion support
Marked as found in versions bash-completion/1:2.0-1.
> close -1 1:2.8-1
Failed to add fixed version '1:2.8-1' to -1: The 'bug' parameter ("-1") to 
Debbugs::Control::set_fixed did not pass regex check
.

Failed to mark -1 as done: The 'bug' parameter ("-1") to 
Debbugs::Control::set_done did not pass regex check
.

> thanks
Stopping processing here.

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



Processed: Bug#970199 marked as pending in glibc

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

> tag -1 pending
Bug #970199 [glibc] glibc: [INTL:pt_BR] Brazilian Portuguese debconf templates 
translation
Added tag(s) pending.

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



Processed: found 512525 in libc6/2.31-3, tagging 555922 ..., affects 607573, found 607573 in glibc/2.27-3 ...

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

> found 512525 libc6/2.31-3
Bug #512525 [libc6] regexp: missing support for non-localized but utf8 
environment
The source libc6 and version 2.31-3 do not appear to match any binary packages
Marked as found in versions libc6/2.31-3.
> tags 555922 + upstream
Bug #555922 [libc6] libc6: UTF-8 decoding is not conforming to the Unicode 
standard
Added tag(s) upstream.
> forwarded 555922 https://www.sourceware.org/bugzilla/show_bug.cgi?id=2373
Bug #555922 [libc6] libc6: UTF-8 decoding is not conforming to the Unicode 
standard
Set Bug forwarded-to-address to 
'https://www.sourceware.org/bugzilla/show_bug.cgi?id=2373'.
> affects 607573 src:proftpd-dfsg
Bug #607573 [src:glibc] setxattr, fsetxattr and lsetxattr are ENOSYS stubs
Added indication that 607573 affects src:proftpd-dfsg
> found 607573 glibc/2.27-3
Bug #607573 [src:glibc] setxattr, fsetxattr and lsetxattr are ENOSYS stubs
Marked as found in versions glibc/2.27-3.
> forcemerge 607573 897335
Bug #607573 [src:glibc] setxattr, fsetxattr and lsetxattr are ENOSYS stubs
Bug #897335 [src:glibc] extattr prototypes declared in kernel headers 
sys/extattr.h but not implemented by libc0.1
The source glibc and version 2.11.2-7 do not appear to match any binary packages
Marked as found in versions glibc/2.11.2-7.
Added tag(s) help.
Merged 607573 897335
> thanks
Stopping processing here.

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



Processed (with 1 error): Re: Bug#725936: getconf: bash-completion support

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

> reassign -1 bash-completion/1:2.0-1
Unknown command or malformed arguments to command.

> affects -1 libc-bin
Bug #725936 [libc-bin] getconf: bash-completion support
Added indication that 725936 affects libc-bin
> forwarded -1 https://github.com/scop/bash-completion/commit/55ed68da
Bug #725936 [libc-bin] getconf: bash-completion support
Set Bug forwarded-to-address to 
'https://github.com/scop/bash-completion/commit/55ed68da'.
> close -1 1:2.8-1
Bug #725936 [libc-bin] getconf: bash-completion support
There is no source info for the package 'libc-bin' at version '1:2.8-1' with 
architecture ''
Unable to make a source version for version '1:2.8-1'
Marked as fixed in versions 1:2.8-1.
Bug #725936 [libc-bin] getconf: bash-completion support
Marked Bug as done

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



Processed: Bug#871051 marked as pending in tzdata

2020-10-07 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #871051 [tzdata] tzdata: [INTL:pt] Updated Portuguese translation for 
debconf messages
Added tag(s) pending.

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



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

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

> forwarded 916276 https://sourceware.org/bugzilla/show_bug.cgi?id=23960
Bug #916276 [src:glibc] glibc: Please add prelimenary patch to fix regression 
on qemu-user
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=23960'.
> thanks
Stopping processing here.

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



Processed: tagging 969926

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

> tags 969926 - security
Bug #969926 [src:glibc] glibc: Parsing of /etc/gshadow can return bad pointers 
causing segfaults in applications
Bug #967938 [src:glibc] libc6: systemd-sysusers SEGV due to glibc bug in 
fgetgsent
Bug #967940 [src:glibc] libc6: systemd-sysusers SEGV due to glibc bug in 
fgetgsent
Removed tag(s) security.
Removed tag(s) security.
Removed tag(s) security.
> thanks
Stopping processing here.

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



Processed: forcibly merging 967938 969926

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

> forcemerge 967938 969926
Bug #967938 [src:glibc] libc6: systemd-sysusers SEGV due to glibc bug in 
fgetgsent
Bug #967940 [src:glibc] libc6: systemd-sysusers SEGV due to glibc bug in 
fgetgsent
Bug #967938 [src:glibc] libc6: systemd-sysusers SEGV due to glibc bug in 
fgetgsent
Marked as found in versions glibc/2.28-10.
Marked as found in versions glibc/2.28-10.
Added tag(s) security.
Added tag(s) security.
Bug #969926 [src:glibc] glibc: Parsing of /etc/gshadow can return bad pointers 
causing segfaults in applications
Severity set to 'normal' from 'serious'
Added tag(s) fixed-upstream.
Bug #967940 [src:glibc] libc6: systemd-sysusers SEGV due to glibc bug in 
fgetgsent
Merged 967938 967940 969926
> thanks
Stopping processing here.

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



Processed: severity of 967938 is important

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

> severity 967938 important
Bug #967938 [src:glibc] libc6: systemd-sysusers SEGV due to glibc bug in 
fgetgsent
Bug #967940 [src:glibc] libc6: systemd-sysusers SEGV due to glibc bug in 
fgetgsent
Bug #969926 [src:glibc] glibc: Parsing of /etc/gshadow can return bad pointers 
causing segfaults in applications
Severity set to 'important' from 'normal'
Severity set to 'important' from 'normal'
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

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



Processed: reassign 967940 to src:glibc

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

> reassign 967940 src:glibc
Bug #967940 [libc6] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent
Bug #967938 [libc6] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent
Bug reassigned from package 'libc6' to 'src:glibc'.
Bug reassigned from package 'libc6' to 'src:glibc'.
No longer marked as found in versions glibc/2.28-10.
No longer marked as found in versions glibc/2.28-10.
Ignoring request to alter fixed versions of bug #967940 to the same values 
previously set
Ignoring request to alter fixed versions of bug #967938 to the same values 
previously set
> thanks
Stopping processing here.

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



Processed (with 1 error): Re: Bug#969926: glibc: Parsing of /etc/gshadow can return bad pointers causing segfaults in applications

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

> forcemerge 967938 969926
Bug #967938 [libc6] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent
Bug #967940 [libc6] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent
Unable to merge bugs because:
package of #969926 is 'src:glibc' not 'libc6'
Failed to forcibly merge 967938: Did not alter merged bugs.


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



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

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

> forwarded 969926 https://sourceware.org/bugzilla/show_bug.cgi?id=20338
Bug #969926 [src:glibc] glibc: Parsing of /etc/gshadow can return bad pointers 
causing segfaults in applications
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=20338'.
> thanks
Stopping processing here.

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



Bug#969645: marked as done (glibc: deferred error : (error "Deferred process exited abnormally:)

2020-09-07 Thread Debian Bug Tracking System
Your message dated Mon, 7 Sep 2020 10:06:13 +0200
with message-id <20200907080613.gb2...@aurel32.net>
and subject line Re: Bug#969645: glibc: deferred error : (error "Deferred 
process exited abnormally:
has caused the Debian Bug report #969645,
regarding glibc: deferred error : (error "Deferred process exited abnormally:
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.)


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

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   try to use jedi-mode on emacs
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   M-x jedi:install-server
   * What was the outcome of this action?
   deferred error : (error "Deferred process exited abnormally:
  command: /home/aurelien/.emacs.d/.python-environments/default/bin/pip
  exit status: exit 1
  event: exited abnormally with code 1
  buffer contents: 
\"/home/aurelien/.emacs.d/.python-environments/default/bin/python3: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by 
/home/aurelien/.emacs.d/.python-e\
nvironments/default/bin/python3)
\"")

   * What outcome did you expect instead?
   something that works!

*** End of the template - remove these template lines ***


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

Kernel: Linux 5.7.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
On 2020-09-07 09:37, Aurelien Jarno wrote:
> On 2020-09-07 07:05, Aurelien DESBRIERES wrote:
> > I have not copied anything nor pip stuff from another environment.
> 
> Do you have any idea how that file has been installed on your system
> (likely something command involving pip3 and/or virtualenv):
> 
> /home/aurelien/.emacs.d/.python-environments/default/bin/python3 ?
> 
> It has been installed for the wrong system.
> 

Submitter answered privately that the issue is reproducible but he
doesn't want to provide a way to reproduce the issue. Closing the bug.

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


Processed: Bug#969219 marked as pending in glibc

2020-09-06 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #969219 [glibc] glibc: [INTL:it] Italian translations updated
Added tag(s) pending.

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



Bug#636286: marked as done (eglibc: SIGSEGV in strcoll in UTF-8 locales with certain characters)

2020-08-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Aug 2020 20:42:48 + (UTC)
with message-id 
and subject line Re: Bug#636286: eglibc: SIGSEGV in strcoll in UTF-8 locales 
with certain characters
has caused the Debian Bug report #636286,
regarding eglibc: SIGSEGV in strcoll in UTF-8 locales with certain 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.)


-- 
636286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eglibc
Version: 2.13-11
Severity: normal

(Only normal severity because this doesn't happen on i386)

root@aranym:~ # LC_ALL=C ./sfl; echo $?
1
root@aranym:~ # LC_ALL=CUT ./sfl; echo $?
sfl: setlocale: No such file or directory
4
root@aranym:~ # LC_ALL=C.UTF-8 ./sfl; echo $?
Segmentation fault
139

Works with no or a nonexistent locale, but not with
a UTF-8 locale. The problem was found in the code of
localechooser (a d-i component which runs sort over
native language lists at build).

Program received signal SIGSEGV, Segmentation fault.
0xc0094940 in findidx (s1=0x8556 " ব", s2=0x855b " ভ", l=0xc0145990) at 
../locale/weight.h:126
126   return indirect[-i + offset];
(gdb) bt
#0  0xc0094940 in findidx (s1=0x8556 " ব", s2=0x855b " ভ", 
l=0xc0145990) at ../locale/weight.h:126
#1  __strcoll_l (s1=0x8556 " ব", s2=0x855b " ভ", l=0xc0145990) at 
strcoll_l.c:213
#2  0xc008f960 in strcoll (s1=0x8556 " ব", s2=0x855b " ভ") at 
strcoll.c:37
#3  0x848e in main () at sfl.c:16
(gdb) print indirect
$1 = 
(gdb) print i
$2 = 
(gdb) print offset
$3 = 

I’ve got libc6-dbg installed, but it doesn’t seem to pick that
up, even with LD_LIBRARY_PATH=/usr/lib/debug/lib/m68k-linux-gnu
set. It does however load the symbols:

Reading symbols from /lib/m68k-linux-gnu/libc.so.6...Reading symbols from 
/usr/lib/debug/lib/m68k-linux-gnu/libc-2.13.so...done.   

I had to manually unpack and quilt push -a the source to get this
far, though. How am I supposed to use the libc6-dbg package then?

The error does NOT occur if the test programme is linked statically.

By preventing inlining and handcompiling strcoll_l.c with a
slightly adjusted (duplocale and __strcoll_l using) programme
I got this:

0x8796 in findidx (cpp=0xefbc0728) at ../locale/weight.h:126
126   return indirect[-i + offset];
(gdb) print cpp
$1 = (const unsigned char **) 0xefbc0728
(gdb) print *cpp
$2 = (const unsigned char *) 0x8000107c "\246\254"
(gdb) x/4xb *cpp
0x8000107c :  0xa60xac0x000x20
(gdb) print indirect
Cannot access memory at address 0xcda56b30
(gdb) print i
$3 = -1130053888
(gdb) print offset
$4 = 

Sorry, can’t debug this further.


https://wiki.debian.org/Aranym/Quick has an easy way to get a VM
image for testing.



-- System Information:
Debian Release: wheezy/sid
Architecture: m68k

Kernel: Linux 3.0.0-1-atari
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/mksh-static


--- End Message ---
--- Begin Message ---
John Paul Adrian Glaubitz dixit:

>Looks like the bug is no longer reproducible:

Thanks; in this case, we can close the bug.

bye,
//mirabilos
-- 
15:41⎜ Somebody write a testsuite for helloworld :-)--- End Message ---


Processed: Re: Bug#968299: Desktot Xfcee in English and locales in Portuguese

2020-08-13 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 xfce4
Bug #968299 [locales] Desktot Xfcee in English and locales in Portuguese
Bug reassigned from package 'locales' to 'xfce4'.
No longer marked as found in versions glibc/2.24-11+deb9u4.
Ignoring request to alter fixed versions of bug #968299 to the same values 
previously set

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



Processed: Re: Bug#968260: libc6: breaks translations when changing the charset to ...//TRANSLIT

2020-08-13 Thread Debian Bug Tracking System
Processing control commands:

> forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=26383
Bug #968260 [libc6] libc6: breaks translations when changing the charset to 
...//TRANSLIT
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=26383'.
> tag -1 + upstream
Bug #968260 [libc6] libc6: breaks translations when changing the charset to 
...//TRANSLIT
Added tag(s) upstream.

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



Processed: Re: Bug#968342: libgegl-sc-0.4.so: undefined symbol: __exp_finite

2020-08-13 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 libgegl-sc-0.4.so: undefined symbol: __exp_finite
Bug #968342 [gimp] gimp does not start, error GEGL operation missing!
Changed Bug title to 'libgegl-sc-0.4.so: undefined symbol: __exp_finite' from 
'gimp does not start, error GEGL operation missing!'.
> reassign -1 libgegl-0.4-0 0.4.12-2
Bug #968342 [gimp] libgegl-sc-0.4.so: undefined symbol: __exp_finite
Bug reassigned from package 'gimp' to 'libgegl-0.4-0'.
No longer marked as found in versions gimp/2.10.8-2.
Ignoring request to alter fixed versions of bug #968342 to the same values 
previously set
Bug #968342 [libgegl-0.4-0] libgegl-sc-0.4.so: undefined symbol: __exp_finite
Marked as found in versions gegl/0.4.12-2.
> affects -1 + gimp
Bug #968342 [libgegl-0.4-0] libgegl-sc-0.4.so: undefined symbol: __exp_finite
Added indication that 968342 affects gimp
> tags -1 + bullseye sid
Bug #968342 [libgegl-0.4-0] libgegl-sc-0.4.so: undefined symbol: __exp_finite
Added tag(s) bullseye and sid.
> clone -1 -2
Bug #968342 [libgegl-0.4-0] libgegl-sc-0.4.so: undefined symbol: __exp_finite
Bug 968342 cloned as bug 968349
> severity -2 minor
Bug #968349 [libgegl-0.4-0] libgegl-sc-0.4.so: undefined symbol: __exp_finite
Severity set to 'minor' from 'grave'
> retitle -2 libc6: please consider adding Breaks on libgegl-0.4-0 (<< 0.4.18)
Bug #968349 [libgegl-0.4-0] libgegl-sc-0.4.so: undefined symbol: __exp_finite
Changed Bug title to 'libc6: please consider adding Breaks on libgegl-0.4-0 (<< 
0.4.18)' from 'libgegl-sc-0.4.so: undefined symbol: __exp_finite'.
> reassign -2 libc6 2.31.2
Bug #968349 [libgegl-0.4-0] libc6: please consider adding Breaks on 
libgegl-0.4-0 (<< 0.4.18)
Bug reassigned from package 'libgegl-0.4-0' to 'libc6'.
No longer marked as found in versions gegl/0.4.12-2.
Ignoring request to alter fixed versions of bug #968349 to the same values 
previously set
Bug #968349 [libc6] libc6: please consider adding Breaks on libgegl-0.4-0 (<< 
0.4.18)
There is no source info for the package 'libc6' at version '2.31.2' with 
architecture ''
Unable to make a source version for version '2.31.2'
Marked as found in versions 2.31.2.

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



Processed: [bts-link] source package glibc

2020-08-10 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 #967940 (http://bugs.debian.org/967940)
> # Bug title: libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent
> #  * http://sourceware.org/bugzilla/show_bug.cgi?id=20338
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 967940 + fixed-upstream
Bug #967940 [libc6] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent
Bug #967938 [libc6] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 967940 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> # remote status report for #967940 (http://bugs.debian.org/967940)
> # Bug title: libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent
> #  * http://sourceware.org/bugzilla/show_bug.cgi?id=20338
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 967940 + fixed-upstream
Bug #967940 [libc6] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent
Bug #967938 [libc6] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent
Ignoring request to alter tags of bug #967940 to the same tags previously set
Ignoring request to alter tags of bug #967938 to the same tags previously set
> usertags 967940 + status-RESOLVED resolution-FIXED
Usertags were: status-RESOLVED resolution-FIXED.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

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



Processed: forcibly merging 967938 967940

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

> forcemerge 967938 967940
Bug #967938 [libc6] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent
Bug #967940 [libc6] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent
Merged 967938 967940
> thanks
Stopping processing here.

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



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

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

> forwarded 967938 https://sourceware.org/bugzilla/show_bug.cgi?id=20338
Bug #967938 [libc6] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent
Bug #967940 [libc6] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=20338'.
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=20338'.
> thanks
Stopping processing here.

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



Bug#967905: marked as done (glibc: Provide a libc6-lse package on arm64)

2020-08-04 Thread Debian Bug Tracking System
Your message dated Tue, 4 Aug 2020 18:27:49 +0200
with message-id <20200804162749.ga2011...@aurel32.net>
and subject line Re: Bug#967905: glibc: Provide a libc6-lse package on arm64
has caused the Debian Bug report #967905,
regarding glibc: Provide a libc6-lse package on arm64
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.)


-- 
967905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.31-2
Severity: wishlist
User: de...@kali.org
Usertags: origin-kali
X-Debbugs-Cc: st...@kali.org, rbal...@ubuntu.com

Hello,

in Kali we are providing many images for ARM devices and some of the ARM
devices that we support have support for the LSE (Large System Extensions)
atomics. We would like to be able use a version of glibc with LSE support
enabled to see whether we can get better performances.

Ubuntu is already shipping a libc6-lse package on arm64 and it would be
nice if Debian could do the same. Balint Reczey (in CC) implemented the
support in Ubuntu, maybe he can share some hints on what's involved and
whether we should expect some related issues.

The patch used by Ubuntu looks like this one:
https://git.launchpad.net/ubuntu/+source/glibc/commit/?id=d38433a40db82a14c006bb9f411d9fc22b594fa4
(except the hunk on debian/testsuite-xfail-debian.mk which is the other
change in that same upload)

Can you consider applying a similar change?

Thank you in advance for your feedback.

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

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
On 2020-08-04 18:11, Raphaël Hertzog wrote:
> Source: glibc
> Version: 2.31-2
> Severity: wishlist
> User: de...@kali.org
> Usertags: origin-kali
> X-Debbugs-Cc: st...@kali.org, rbal...@ubuntu.com
> 
> Hello,
> 
> in Kali we are providing many images for ARM devices and some of the ARM
> devices that we support have support for the LSE (Large System Extensions)
> atomics. We would like to be able use a version of glibc with LSE support
> enabled to see whether we can get better performances.

Since glibc 2.31-0experimental2, Debian supports LSE on arm64
transparently using the -moutline-atomics option of GCC. Therefore there
is no plan to add a libc6-lse package in Debian (see bug #956418 for
the corresponding discussion).

I am therefore closing the bug.

Aurelien

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


Bug#856503: marked as done (glibc: CVE-2016-10228: iconv(1) with -c option hangs on illegal multi-byte sequences)

2020-08-04 Thread Debian Bug Tracking System
Your message dated Tue, 04 Aug 2020 15:19:07 +
with message-id 
and subject line Bug#856503: fixed in glibc 2.31-3
has caused the Debian Bug report #856503,
regarding glibc: CVE-2016-10228: iconv(1) with -c option hangs on illegal 
multi-byte sequences
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.)


-- 
856503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.19-18
Severity: important
Tags: upstream security
Forwarded: https://sourceware.org/bugzilla/show_bug.cgi?id=19519

Hi,

the following vulnerability was published for glibc.

CVE-2016-10228[0]:
glibc iconv program can hang when invoked with the -c option

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-10228
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10228
[1] https://sourceware.org/bugzilla/show_bug.cgi?id=19519

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.31-3
Done: Aurelien Jarno 

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 856...@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, 04 Aug 2020 17:02:38 +0200
Source: glibc
Architecture: source
Version: 2.31-3
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 856503 962457
Changes:
 glibc (2.31-3) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/control.in/libc: add a Breaks: against openarena (<< 0.8.8+dfsg-4~)
 due to bug#966150.
   * debian/control.in/libc: add a Breaks: against ioquake3
 (<< 1.36+u20200211.f2c61c1~dfsg-2~) as previous versions are not correctly
 linked with libm.
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix an infinite loop in the iconv program (CVE-2016-10228).  Closes:
   #856503.
 - debian/patches/any/submitted-selinux-deprecations.diff: upstreamed.
 - debian/patches/x32/submitted-fix-nptl-setgroups-x32.diff: upstreamed.
   * debian/rules.d/build.mk: install  in the
 multiarch path.  Closes: #962457.
 .
   [ Samuel Thibault ]
   * debian/libc0.3.symbols.hurd-i386: Fix dependency of __errno_location and
 __h_errno_location symbols in libpthread.
   * patches/hurd-i386/unsubmitted-sbrk-_end.diff: Fix _end symbol appearance
 by reworking sbrk.
   * patches/hurd-i386/unsubmitted-sched_sets.diff: Add sched_set/getscheduler.
   * patches/hurd-i386/git-pthread_atfork-hidden.diff: Hide pthread_atfork
 symbols imported to applications, to avoid leaking them.
Checksums-Sha1:
 51042e7e252f974e753a23d88e3f93fb5c08d376 8195 glibc_2.31-3.dsc
 c3c1c43eedc1eeb109cab92cf3c89da103fb0d0e 843860 glibc_2.31-3.debian.tar.xz
 996608535549a3ae2b4dd093d6b1d5dae3fa4b6f 6654 glibc_2.31-3_source.buildinfo
Checksums-Sha256:
 d620bb217b3cda48e48d21f29fbf73aa907f78b8f77d674cae0ce452c886ae3e 8195 
glibc_2.31-3.dsc
 973658d166dd9bbf481e4747487fea35101c70a03066de1f14e5e87ed7477c29 843860 
glibc_2.31-3.debian.tar.xz
 c105f6da16e5b3f69f11c38d9ca6e016e8c6d4649e152281a0832788eaebe03d 6654 
glibc_2.31-3_source.buildinfo
Files:
 0374bd34e1f6495dabe7996552251d32 8195 libs required glibc_2.31-3.dsc
 73f4bb753825e4700578f3e0f83b9de5 843860 libs required 
glibc_2.31-3.debian.tar.xz
 137bbc65a88a2bf109ac5bfe3d4033eb 6654 libs required 
glibc_2.31-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl8peqIACgkQE4jA+Jno
M2t90w/+MbKr0hy2c58sfIObUKHZopnmDl0ZLTM57ykPakI5U6jdzbTakRgj6u0s
tcYlaboWew+tTL1hv4aCXBfhnFFJ3SC033RT2MdJjmSGCD2gGJ/DWR6e/sclOy3e
zix2vKGjmdj9mOWML8KMXKG2udnQ4aTm//hAFfPaYtCe1vfHFIHSh+kAweuiJ694
cfc5TFUTxtBfMNDKxZQpYf2C+oNLeIqRZhTRobOcOwYD4R3SBcEKrJc8Z7AEYZXu
qTY6CHIoEW80SpJgi+C64urLR0D7UZtB

Bug#962457: marked as done (installation of finclude/math-vector-fortran.h)

2020-08-04 Thread Debian Bug Tracking System
Your message dated Tue, 04 Aug 2020 15:19:07 +
with message-id 
and subject line Bug#962457: fixed in glibc 2.31-3
has caused the Debian Bug report #962457,
regarding installation of finclude/math-vector-fortran.h
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.)


-- 
962457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:glibc
Version: 2.30-8
Severity: important
Tags: sid bullseye

2.30-2 removed the installation of finclude/math-vector-fortran.h, which leads
to build errors like reported in https://launchpad.net/bugs/1879092

glibc (2.30-2) unstable; urgency=medium

  * debian/rules.d/build.mk: do not install 
for now as it is not multiarch safe.


Forwarded the discussion to
https://gcc.gnu.org/pipermail/gcc/2020-June/232779.html

It looks like the current x86 variant of this file is conditionalized and
installable on any architecture. So instead of dropping the file, just install
the x86 variant on every architecture.
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.31-3
Done: Aurelien Jarno 

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 962...@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, 04 Aug 2020 17:02:38 +0200
Source: glibc
Architecture: source
Version: 2.31-3
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 856503 962457
Changes:
 glibc (2.31-3) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/control.in/libc: add a Breaks: against openarena (<< 0.8.8+dfsg-4~)
 due to bug#966150.
   * debian/control.in/libc: add a Breaks: against ioquake3
 (<< 1.36+u20200211.f2c61c1~dfsg-2~) as previous versions are not correctly
 linked with libm.
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix an infinite loop in the iconv program (CVE-2016-10228).  Closes:
   #856503.
 - debian/patches/any/submitted-selinux-deprecations.diff: upstreamed.
 - debian/patches/x32/submitted-fix-nptl-setgroups-x32.diff: upstreamed.
   * debian/rules.d/build.mk: install  in the
 multiarch path.  Closes: #962457.
 .
   [ Samuel Thibault ]
   * debian/libc0.3.symbols.hurd-i386: Fix dependency of __errno_location and
 __h_errno_location symbols in libpthread.
   * patches/hurd-i386/unsubmitted-sbrk-_end.diff: Fix _end symbol appearance
 by reworking sbrk.
   * patches/hurd-i386/unsubmitted-sched_sets.diff: Add sched_set/getscheduler.
   * patches/hurd-i386/git-pthread_atfork-hidden.diff: Hide pthread_atfork
 symbols imported to applications, to avoid leaking them.
Checksums-Sha1:
 51042e7e252f974e753a23d88e3f93fb5c08d376 8195 glibc_2.31-3.dsc
 c3c1c43eedc1eeb109cab92cf3c89da103fb0d0e 843860 glibc_2.31-3.debian.tar.xz
 996608535549a3ae2b4dd093d6b1d5dae3fa4b6f 6654 glibc_2.31-3_source.buildinfo
Checksums-Sha256:
 d620bb217b3cda48e48d21f29fbf73aa907f78b8f77d674cae0ce452c886ae3e 8195 
glibc_2.31-3.dsc
 973658d166dd9bbf481e4747487fea35101c70a03066de1f14e5e87ed7477c29 843860 
glibc_2.31-3.debian.tar.xz
 c105f6da16e5b3f69f11c38d9ca6e016e8c6d4649e152281a0832788eaebe03d 6654 
glibc_2.31-3_source.buildinfo
Files:
 0374bd34e1f6495dabe7996552251d32 8195 libs required glibc_2.31-3.dsc
 73f4bb753825e4700578f3e0f83b9de5 843860 libs required 
glibc_2.31-3.debian.tar.xz
 137bbc65a88a2bf109ac5bfe3d4033eb 6654 libs required 
glibc_2.31-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl8peqIACgkQE4jA+Jno
M2t90w/+MbKr0hy2c58sfIObUKHZopnmDl0ZLTM57ykPakI5U6jdzbTakRgj6u0s
tcYlaboWew+tTL1hv4aCXBfhnFFJ3SC033RT2MdJjmSGCD2gGJ/DWR6e/sclOy3e
zix2vKGjmdj9mOWML8KMXKG2udnQ4aTm//hAFfPaYtCe1vfHFIHSh+kAweuiJ694
cfc5TFUTxtBfMNDKxZQpYf2C+oNLeIqRZhTRobOcOwYD4R3SBcEKrJc8Z7AEYZXu
qTY6CHIoEW80SpJgi+C64urLR0D7UZtBi36FPwjbzV2ubDhO/cF8

Processed: Re: Bug#962457: installation of finclude/math-vector-fortran.h

2020-08-04 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #962457 [src:glibc] installation of finclude/math-vector-fortran.h
Severity set to 'normal' from 'important'

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



Processed: Bug#962457 marked as pending in glibc

2020-08-04 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #962457 [src:glibc] installation of finclude/math-vector-fortran.h
Added tag(s) pending.

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



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

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

> forwarded 903514 https://sourceware.org/bugzilla/show_bug.cgi?id=15686
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
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=15686'.
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=15686'.
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=15686'.
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=15686'.
> 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: Bug#924891: glibc: misc/tst-pkey fails due to cleared PKRU register after signal in amd64 32-bit compat mode

2020-08-02 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 src:linux
Bug #924891 [src:glibc] glibc: misc/tst-pkey fails due to cleared PKRU register 
after signal in amd64 32-bit compat mode
Bug reassigned from package 'src:glibc' to 'src:linux'.
No longer marked as found in versions glibc/2.28-8.
Ignoring request to alter fixed versions of bug #924891 to the same values 
previously set
> retitle -1 linux: cleared PKRU register after signal in amd64 32-bit compat 
> mode
Bug #924891 [src:linux] glibc: misc/tst-pkey fails due to cleared PKRU register 
after signal in amd64 32-bit compat mode
Changed Bug title to 'linux: cleared PKRU register after signal in amd64 32-bit 
compat mode' from 'glibc: misc/tst-pkey fails due to cleared PKRU register 
after signal in amd64 32-bit compat mode'.
> close -1 4.10-1~exp1
Bug #924891 [src:linux] linux: cleared PKRU register after signal in amd64 
32-bit compat mode
Marked as fixed in versions linux/4.10-1~exp1.
Bug #924891 [src:linux] linux: cleared PKRU register after signal in amd64 
32-bit compat mode
Marked Bug as done
> affects -1 glibc
Bug #924891 {Done: Aurelien Jarno } [src:linux] linux: 
cleared PKRU register after signal in amd64 32-bit compat mode
Added indication that 924891 affects glibc

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



Bug#837123: marked as done ([anna] segfault in wheezy installer)

2020-07-29 Thread Debian Bug Tracking System
Your message dated Wed, 29 Jul 2020 22:02:30 +0200
with message-id <20200729200230.ga14...@aurel32.net>
and subject line Re: Bug#837123: [anna] segfault in wheezy installer
has caused the Debian Bug report #837123,
regarding [anna] segfault in wheezy installer
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.)


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

Package: libc6-udeb
Version: 2.13-38+deb7u10
Severity: grave
Justification: breaks installation entirely

The wheezy installer fails with anna reporting a segfault:

...
anna[5033]: DEBUG: retrieving libc6-udeb 2.13-38+deb7u10
anna[5033]: DEBUG: retrieving finish-install 2.41wheezy1
anna[5033]: DEBUG: Segmentation fault
anna[5033]: WARNING **: package retrieval failed
kernel: [   66.427372] wget[5382]: segfault a 0 ip 7176c922c0ca sp 
7ffc8ca83890 error 6 in libresolv-2.13.so[7f76c9222000+13000]

This occurs shortly after libc6-udev is downloaded,
according to the installer interactive display.

Background
--
I was trying to reinstall an older system with wheezy.
I was using the PXE install image available on 2016-09-08 UTC, at
ftp.au.debian.org/debian/dists/wheezy/main/installer-amd64/current/images/netboot

The mirror shows the last update timestamp as 2016-05-31.
debian-installer/amd64/boot-screens/f1.txt has the fairly useless
build date stamp 20130613+deb7u3+b2.

This installation method was working fine with earlier installer
versions. The breakage has been there some months I'd say.
I only became fully aware of it yesterday.

I don't think the mirror is out of date; I got the same result
with the netboot installer image downloaded from ftp.us.debian.org.


The log above was copied by eye from the console,
I was unable to install the openssh-client=udeb to copy the logs,
thanks to the segfault.

The core of the issue is probably screwed up libc6 versions,
see bugs 740068, 833432

Other package versions that may be of interest
 base-installer: 1.130
 cdebconf-udeb: 0.182
 di-utils: 1.92+deb7u1
 libc6-udeb: 2.13-38+deb7u10
 anna: 1.44+deb7u1

It's really unfortunate to have the oldstable installer break like this.
I hope it can be fixed, age notwithstanding.

Kind regards
Vince
-- 
--- End Message ---
--- Begin Message ---
Hi,

It happens this bug has been forgotten in the bts as it is somehow
considered to be reported about the libc6-udeb *source* package. I
believe that since the time the problem is not reproducible anymore.

I am therefore closing the bug, if it can still be reproduced with
recent releases, feel free to reopen the bug.

Regards,
Aurelien

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


Bug#910923: marked as done (libc6: broken support for curly braces DST)

2020-07-29 Thread Debian Bug Tracking System
Your message dated Wed, 29 Jul 2020 18:20:55 +0200
with message-id <20200729162055.ga6...@aurel32.net>
and subject line Re: Bug#910923: $PLATFORM is no longer expanded.
has caused the Debian Bug report #910923,
regarding libc6: broken support for curly braces DST
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Reproduction:
$ strace -ELD_PRELOAD='/sss/${PLATFORM}/'  -s300  /bin/cat
execve("/bin/cat", ["/bin/cat"], 0x55ddc6b820f0 /* 64 vars */) = 0
brk(NULL)   = 0x56046d9c1000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or directory)
readlink("/proc/self/exe", "/bin/cat", 4096) = 8
openat(AT_FDCWD, "/sss/x86_64/", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
writev(2, [{iov_base="ERROR: ld.so: object '", iov_len=22}, 
{iov_base="/sss/${PLATFORM}/", iov_len=21}, {iov_base="' from ", 
iov_len=7}, {iov_base="LD_PRELOAD", iov_len=10}, {iov_base=" cannot be 
preloaded (", iov_len=22}, {iov_base="cannot open shared object file", 
iov_len=30}, {iov_base="): ignored.\n", iov_len=12}], 7ERROR: ld.so: object 
'/sss/${PLATFORM}/' from LD_PRELOAD cannot be preloaded (cannot open shared 
object file): ignored.
) = 124

So $PLATFORM is not expanded. This is a regression from 2.24
According to
https://sourceware.org/bugzilla/show_bug.cgi?id=22299
it *should* be fixed in 2.27, but it is clerly still reproducible in
debian testing/sid.

This is causing the following problem for me:
https://community.sonarsource.com/t/sonarqube-c-ubuntu-build-wrapper-ld-preload-error/300/2

Roman.

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEjkF6151RK40WXe2HCDw+u0oWieAFAlvB74kACgkQCDw+u0oW
ieC64A/+NJUBom7TnJ2IDVydGFTAtoEpBU/ShodqYPuZ/Yh020UHL/xQ6Y/XEeGk
/hjR0VadQFxJlIQcCygUVb10+q1JslT2FMWAtL4nyfD3FhSHjzBgzKthqbd0Gj4X
9SY4eZ6J85zUv+V505sAu550oUgGI9HQmxsVPa4yZqkAvL5Q6bZTW6w8vKZUH7ix
yaInTC7KXT9n0GCyoGiiLoW3hmH0JYcw99Emt26HaTyHCbMiMMZlPYxAp5UnxAFF
1VTZp69rYxePLQvuCi+wv452WVSdA8xeN6LO1uxvpkHuHefNj2v6XGmzmLEE8LWU
zTMFyyNu29bX7YYKNVLLUA3gPz9hqgTysEK3tLotLho0gTwYUt//RBiJD8/XktHP
pC0TDVbhMO/gqfsSLWLwHx5OOMXv+Xif5Z5OyQS/RI7O2deF2lsBDXGFmghUPGh2
nsZ/gTqdK/37UvtL4UgnSg5AOd4+VE6rI6XuLUrbbGsJ/OBDTj+HbriaSgStDo/k
O82reGp8M/33iyR0UN5YjqBgcVL27KtcJdDZKUmnQFcVfkbE3iFp44EMSOY0180A
QTZXYw4xA2yTdrq7JdfQqAws6f3X+e4S9JHoWIp5rRqpjRlH9HLwWzQ/+j9cR32U
eAvtOowmWRSoQbRO5muoGd96aRGeqcLwHHv4GYLBqR/Xziu6NFE=
=8rcH
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
On 2018-12-31 12:10, Aurelien Jarno wrote:
> On 2018-10-15 00:49, Roman Lebedev wrote:
> > On Sun, Oct 14, 2018 at 10:51 PM Aurelien Jarno  
> > wrote:
> > >
> > > control: severity -1 normal
> > > control: retitle -1 libc6: broken support for curly braces DST
> > >
> > > On 2018-10-13 16:13, Roman Lebedev wrote:
> > > > Source: glibc
> > > > Version: 2.27-6
> > > > Severity: important
> > > >
> > > > Reproduction:
> > > > $ strace -ELD_PRELOAD='/sss/${PLATFORM}/'  -s300  /bin/cat
> > > > execve("/bin/cat", ["/bin/cat"], 0x55ddc6b820f0 /* 64 vars */) = 0
> > > > brk(NULL)   = 0x56046d9c1000
> > > > access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
> > > > directory)
> > > > readlink("/proc/self/exe", "/bin/cat", 4096) = 8
> > > > openat(AT_FDCWD, "/sss/x86_64/", O_RDONLY|O_CLOEXEC) = -1 ENOENT 
> > > > (No such file or directory)
> > Hm actually wait, i think i'm confused here.
> > Both the ${PLATFORM} and $PLATFORM seem to expand just fine.
> > 
> > $ strace -ELD_PRELOAD

Processed: tagging 965323

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

> tags 965323 + wontfix
Bug #965323 [locales] postinst script deletes custom locales
Ignoring request to alter tags of bug #965323 to the same tags previously set
> thanks
Stopping processing here.

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



Processed: reopen

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

> reopen 965323
Bug #965323 [locales] postinst script deletes custom locales
Bug 965323 is not marked as done; doing nothing.
>
End of message, stopping processing here.

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



Bug#966343: marked as done (libc6: Permission denied, intermittent in execve)

2020-07-28 Thread Debian Bug Tracking System
Your message dated Wed, 29 Jul 2020 00:14:54 +0200
with message-id <20200728221454.gj8...@aurel32.net>
and subject line Re: Bug#966343: bug#498: libc6: Permission denied, 
intermittent in execve
has caused the Debian Bug report #966343,
regarding libc6: Permission denied, intermittent in execve
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.)


-- 
966343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: GNU C Library (Debian GLIBC 2.28-10) stable release version 2.28.
Severity: normal


 Forwarded Message 
Subject: libc6: Permission denied, intermittent in execve
Date: Mon, 27 Jul 2020 10:25:27 +0200
From: Alessandro Vesely 
To: Devuan Bug Tracking System 


Dear Maintainer,

in certain situations, execve fails setting errno to EACCESS.  The same
program, launched by the same user in different ways, succeeds or fails
according to preceding actions.

None of the failure conditions for EACCESS is met.

The case at hand happens with an old version of Thunderbird and a LibreOffice
attachment.  After saving the attachment, Thunderbird execs gio-launch-desktop.
The latter tries to exec libreoffice6.4 and fails.

I strace'd the full arguments used in the failed execve(), and copied them to a
simple C program which runs just that execve() call.  When called from the
command line, the program succeeds.  Then I replaced the gio-launch-desktop
executable with my straw men.  When called from Thunderbird, the program fails.

See also:
https://unix.stackexchange.com/questions/600174/permission-denied-intermittent-in-execve


-- System Information:
Distributor ID: Debian
Description:Devuan GNU/Linux 3 (beowulf)
Release:3
Codename:   beowulf
Architecture: x86_64

Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Hi,

On 2020-07-27 19:01, Alessandro Vesely wrote:
> On Mon, 27 Jul 2020 12:13:44 +0200 Samuel Thibault  
> wrote:
> > Alessandro Vesely, le lun. 27 juil. 2020 11:47:34 +0200, a ecrit:
> > > So this turns out to be a documentation bug.  The execve man page should 
> > > mention that EACCESS can result as an (unforeseen) apparmor impediment.
> > 
> > Well, basically all system calls would then need this...
> 
> 
> Yeah, likely.  How many man pages have snippets like "[...] denied for one of 
> the directories in the path [...]"?
>
> Yet, considering the following examples, they seem to have been written 
> manually rather than resorting to some sort of script:

There are many syscalls that might end up returning EACCESS. Mapping
them to the corresponding libc functions might not be always fully
linear.

[snip]

> Philip Couling commented that the man page /could/ mention security 
> extensions since they are prevelent. See:
> https://unix.stackexchange.com/questions/600174/identical-execve-causes-permission-denied-for-one-program-but-not-another/600529#comment1121270_600529
> 
> For execve, for example, one could add that permissions are not derived from 
> file flags only.  For example:
> 
> OLD:
> 
>EACCES Execute permission is denied for the file or a script or ELF 
> interpreter.
> 
> NEW:
> 
>EACCES Execute permission for the file or a script or ELF interpreter 
> is denied either by flags or by security modules.
> 
> 
> Would that be correct?  Do all "DENIED" operations result in EACCES?  And 
> what do other security modules do?  Hmm...  Starting to document that mess 
> from the point of view of programs getting such failure codes would allow 
> better logging and better troubleshooting.

That seems correct for apparmor (although it can also return ENOENT in
case of race condition), not sure about other security modules. seccomp
just kills the process, not sure you want to mention that in every
possible manpages.

In any case this is now out of scope for the glibc package, so I am
closing the bug. If you feel that the doc needs to be updated, please
open a bug against the corresponding package.

Regards,
Aurelien

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


Processed: Re: Bug#966312: Weird getaddrinfo

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

> reassign -1 libc6
Bug #966312 [libc] Weird getaddrinfo
Warning: Unknown package 'libc'
Bug reassigned from package 'libc' to 'libc6'.
No longer marked as found in versions 2.28.
Ignoring request to alter fixed versions of bug #966312 to the same values 
previously set

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



Bug#966265: marked as done ([libc6] Breaks is too broad for openssh on 64-bit)

2020-07-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 Jul 2020 17:30:19 +0200
with message-id <20200725153019.ga10...@qmqm.qmqm.pl>
and subject line Re: [libc6] Breaks is too broad for openssh on 64-bit
has caused the Debian Bug report #966265,
regarding [libc6] Breaks is too broad for openssh on 64-bit
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.)


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

--- Please enter the report below this line. ---

A fix for bug #965932 added a Breaks: for openssh-server and -client,
but the restriction covers all arches instead of 32-bit only, and so
prevents upgrading only libc to testing from stable on amd64.

--- System information. ---
(irrelevant)

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.
--- End Message ---
--- Begin Message ---
On Sat, Jul 25, 2020 at 05:07:36PM +0200, Michał Mirosław wrote:
> Package: libc6
> Version: 2.31-2
> Severity: normal
> 
> --- Please enter the report below this line. ---
> 
> A fix for bug #965932 added a Breaks: for openssh-server and -client,
> but the restriction covers all arches instead of 32-bit only, and so
> prevents upgrading only libc to testing from stable on amd64.

Oh, it is intentional, but was not there in 2.31-1.
Please close the bug as invalid.

Best Regards,
Michał Mirosław--- End Message ---


Bug#965091: marked as done (glibc: setgroups: Bad address [2.31/x32, regression from 2.30])

2020-07-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jul 2020 22:51:17 +
with message-id 
and subject line Bug#965091: fixed in glibc 2.31-2
has caused the Debian Bug report #965091,
regarding glibc: setgroups: Bad address [2.31/x32, regression from 2.30]
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.)


-- 
965091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.31-1
Severity: grave
Justification: renders package unusable

This is related to #965086 and #965087 (and, in fact, possibly
causing them). After a glibc upgrade half the system services
(postfix, sshd, apt-get(!)) don’t work any more.

Downgrading with dpkg -i the following set of packages fixes it:

libc-bin_2.30-8_x32.deb
libc-dev-bin_2.30-8_x32.deb
libc-l10n_2.30-8_all.deb
libc6-dbg_2.30-8_x32.deb
libc6-dev_2.30-8_x32.deb
libc6_2.30-8_amd64.deb
libc6_2.30-8_i386.deb
libc6_2.30-8_x32.deb
locales-all_2.30-8_x32.deb
locales_2.30-8_all.deb
unscd_0.53-1+b3_x32.deb

Snippet from strace:

[…]
9839  getpid()  = 9839
9839  chroot("/run/sshd")   = 0
9839  chdir("/")= 0
9839  write(7, "\0\0\0$\0\0\0\7\0\0\0\34privsep user:group 1"..., 40) = 40
9839  setgroups(1, 0xff866750 
9794  <... poll resumed>)   = 1 ([{fd=6, revents=POLLIN}])
9839  <... setgroups resumed>)  = -1 EFAULT (Bad address)
9794  read(6,  
9839  write(7, "\0\0\0\36\0\0\0\1\0\0\0\26setgroups: Bad addre"..., 34 

[…]

Noticeable: the sign-extended address.

I haven’t yet managed to reproduce this in a stand-alone program.

-- 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 5.7.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages libc6 depends on:
ii  libcrypt1  1:4.4.16-1
ii  libgcc-s1  10.1.0-6

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

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.74
ii  glibc-doc  2.31-1
ii  libc-l10n  2.31-1
ii  locales2.31-1

-- debconf information:
  glibc/disable-screensaver:
* libraries/restart-without-asking: true
  glibc/restart-failed:
  glibc/kernel-too-old:
* glibc/upgrade: true
* glibc/restart-services: postfix openbsd-inetd cups cron
  glibc/kernel-not-supported:
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.31-2
Done: Aurelien Jarno 

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 965...@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, 23 Jul 2020 00:26:24 +0200
Source: glibc
Architecture: source
Version: 2.31-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 961452 965091 965932 965941
Changes:
 glibc (2.31-2) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/control.in/libc: add a Breaks: against macs (<< 2.2.7.1-3~) due to
 bug #965073.
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix a signed comparison vulnerability in the ARMv7 memcpy and memmove
   functions (CVE-2020-6096).  Closes: #961452.
   * debian/control.in/libc: do not limit the openssh-server breaks to 32-bit
 architectures, clock_nanosleep has to be allowed in addition to
 clock_gettime64.  Closes: #965932.
   * debian/patches/any/submitted-selinux-deprecations.diff: proposed patch to
 ignore the selinux deprecations introduced in libselinux (>= 3.1), fixing
 an FTBFS.  Closes: #965

Bug#965941: marked as done (src:glibc: FTBFS with libselinux-dev (>= 3.1) due to deprecations warnings)

2020-07-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jul 2020 22:51:17 +
with message-id 
and subject line Bug#965941: fixed in glibc 2.31-2
has caused the Debian Bug report #965941,
regarding src:glibc: FTBFS with libselinux-dev (>= 3.1) due to deprecations 
warnings
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.)


-- 
965941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:glibc
Version: 2.31-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)

Since the upload of libselinux 3.1 to unstable, glibc doesn't build
anymore due to deprecation warnings:

| ...
| x86_64-linux-gnu-gcc-10 makedb.c -c -std=gnu11 -fgnu89-inline  -pipe -O2 -g 
-fdebug-prefix-map=/home/aurel32/work/glibc/glibc-2.31=. -Wall -Wwrite-strings 
-Wundef -Werror -fmerge-all-constants -frounding-math -fstack-protector-strong 
-Wstrict-prototypes -Wold-style-definition -fmath-errno   -fpie   -isystem 
/home/aurel32/work/glibc/glibc-2.31/debian/include  -I../include 
-I/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss  
-I/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc  
-I../sysdeps/unix/sysv/linux/x86_64/64  -I../sysdeps/unix/sysv/linux/x86_64  
-I../sysdeps/unix/sysv/linux/x86/include -I../sysdeps/unix/sysv/linux/x86  
-I../sysdeps/x86/nptl  -I../sysdeps/unix/sysv/linux/wordsize-64  
-I../sysdeps/x86_64/nptl  -I../sysdeps/unix/sysv/linux/include 
-I../sysdeps/unix/sysv/linux  -I../sysdeps/nptl  -I../sysdeps/pthread  
-I../sysdeps/gnu  -I../sysdeps/unix/inet  -I../sysdeps/unix/sysv  
-I../sysdeps/unix/x86_64  -I../sysdeps/unix  -I../sysdeps/posix  
-I../sysdeps/x86_64/64  -I../sysdeps/x86_64/fpu/multiarch  
-I../sysdeps/x86_64/fpu  -I../sysdeps/x86/fpu/include -I../sysdeps/x86/fpu  
-I../sysdeps/x86_64/multiarch  -I../sysdeps/x86_64  -I../sysdeps/x86  
-I../sysdeps/ieee754/float128  -I../sysdeps/ieee754/ldbl-96/include 
-I../sysdeps/ieee754/ldbl-96  -I../sysdeps/ieee754/dbl-64/wordsize-64  
-I../sysdeps/ieee754/dbl-64  -I../sysdeps/ieee754/flt-32  
-I../sysdeps/wordsize-64  -I../sysdeps/ieee754  -I../sysdeps/generic  -I.. 
-I../libio -I. -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/10/include 
-isystem /home/aurel32/work/glibc/glibc-2.31/debian/include  -D_LIBC_REENTRANT 
-include 
/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/libc-modules.h 
-DMODULE_NAME=nonlib -include ../include/libc-symbols.h  -DPIC 
-DTOP_NAMESPACE=glibc -o 
/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss/makedb.o -MD -MP 
-MF /home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss/makedb.o.dt 
-MT /home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss/makedb.o
| makedb.c: In function 'set_file_creation_context':
| makedb.c:849:3: error: 'security_context_t' is deprecated 
[-Werror=deprecated-declarations]
|   849 |   security_context_t ctx;
|   |   ^~
| makedb.c:863:3: error: 'matchpathcon' is deprecated: Use selabel_lookup 
instead [-Werror=deprecated-declarations]
|   863 |   if (matchpathcon (outname, S_IFREG | mode, ) == 0 && ctx != 
NULL)
|   |   ^~
| In file included from makedb.c:50:
| /usr/include/selinux/selinux.h:500:12: note: declared here
|   500 | extern int matchpathcon(const char *path,
|   |^~~~
| cc1: all warnings being treated as errors
| make[3]: *** [../o-iterator.mk:9: 
/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc/nss/makedb.o] Error 1
| make[3]: *** Waiting for unfinished jobs
| make[3]: Leaving directory '/home/aurel32/work/glibc/glibc-2.31/nss'
| make[2]: *** [Makefile:487: nss/others] Error 2
| make[2]: Leaving directory '/home/aurel32/work/glibc/glibc-2.31'
| make[1]: *** [Makefile:9: all] Error 2
| make[1]: Leaving directory 
'/home/aurel32/work/glibc/glibc-2.31/build-tree/amd64-libc'
| make: *** [debian/rules.d/build.mk:114: 
/home/aurel32/work/glibc/glibc-2.31/stamp-dir/build_libc] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.31-2
Done: Aurelien Jarno 

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 965...@bugs.debian.org,
and the maintainer will reopen the

Bug#961452: marked as done (CVE-2020-6096)

2020-07-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jul 2020 22:51:16 +
with message-id 
and subject line Bug#961452: fixed in glibc 2.31-2
has caused the Debian Bug report #961452,
regarding CVE-2020-6096
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.)


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

Please see
https://sourceware.org/bugzilla/show_bug.cgi?id=25620
https://talosintelligence.com/vulnerability_reports/TALOS-2020-1019

Cheers,
Moritz

--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.31-2
Done: Aurelien Jarno 

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 961...@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, 23 Jul 2020 00:26:24 +0200
Source: glibc
Architecture: source
Version: 2.31-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 961452 965091 965932 965941
Changes:
 glibc (2.31-2) unstable; urgency=medium
 .
   [ Aurelien Jarno ]
   * debian/control.in/libc: add a Breaks: against macs (<< 2.2.7.1-3~) due to
 bug #965073.
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fix a signed comparison vulnerability in the ARMv7 memcpy and memmove
   functions (CVE-2020-6096).  Closes: #961452.
   * debian/control.in/libc: do not limit the openssh-server breaks to 32-bit
 architectures, clock_nanosleep has to be allowed in addition to
 clock_gettime64.  Closes: #965932.
   * debian/patches/any/submitted-selinux-deprecations.diff: proposed patch to
 ignore the selinux deprecations introduced in libselinux (>= 3.1), fixing
 an FTBFS.  Closes: #965941.
   * debian/patches/x32/submitted-fix-nptl-setgroups-x32.patch: proposed patch
 to fix the setgroups functions in threaded applications on x32 (without
 the testsuite part).  Closes: #965091.
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/local-tls-ie-align.diff: Fix TLS IE load with >=
 8 byte alignment.
   * debian/testsuite-xfail-debian.mk: Update backtrace result.
   * debian/patches/hurd-i386/git-fix-longjmp.diff: Fix longjmp from dl loader.
 Notably fixes calling setuid programs from eatmydata.
   * debian/control: Build-depend on gnumach-dev with userland driver RPC 
interface.
   * debian/libc0.3.symbols.hurd-i386: Add userland driver RPC interface stubs.
   * debian/patches/hurd-i386/local-clock_gettime_MONOTONIC.diff: Make
 clock_nanosleep accept CLOCK_MONOTONIC as well.
Checksums-Sha1:
 de6f87b63f42f73654f720a5a39e511ca62d09a6 8195 glibc_2.31-2.dsc
 7fa2322888e002362003b52eef5461c0458c9046 832956 glibc_2.31-2.debian.tar.xz
 17b00b1ebec24339a160116dfc4034d6ea98 6939 glibc_2.31-2_source.buildinfo
Checksums-Sha256:
 1e68e21c7c03f539fe4f7b6cd6b04edc124dcbdd4c64a742a0e8defc6c446e03 8195 
glibc_2.31-2.dsc
 2f09126faa95ae00641c8848a4602cf108849d980ce88d9d129adab596ea835d 832956 
glibc_2.31-2.debian.tar.xz
 c76049c623ea0b2ff84c04c3be9a2738da6e9fdf7cd2cc90a83d1185e349c30d 6939 
glibc_2.31-2_source.buildinfo
Files:
 118a87db2b3d4629465eb10c47946718 8195 libs required glibc_2.31-2.dsc
 73afb447f5e0e822f158dac21adaee3f 832956 libs required 
glibc_2.31-2.debian.tar.xz
 01bdd8e9c0f02ac876ca8ec1b98b5cf5 6939 libs required 
glibc_2.31-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl8Yvd4ACgkQE4jA+Jno
M2vMkA/+KIfz4B04ywg0bvms3cfIQKuw+FQojw8inBrERUMpKDxZ94AkD30FwSIE
wyao0KZTKGT42cQCwnQ8boYt2EfhFGXKXeDei40srZW1gMd138Fubsf1b3ClTW68
WKufygMDWbThbEahswn60w/2dxFaqQT4pIV29W/80dOMiPMfiSbNm79uK8Jp1jz2
6x//TP8zZCaKvGiF5uHI8Xjib/sMWGjHQBbBkpYZmF/ab4qdS/zRWLWaEajOZ91J
P3O1hsn3IU5KQiMXL3k9V8llZV7DaBU+Hum+TJRfcjG0zMkGN5PARR3Fok89zs1u
1oD5voXnnshXqvCmz6AhVpy0rxdsVr4P1ozr79RM8bdAsjyxC1ora8fGy4GRts61
DfNdBApSSnijon0Erfm4U4Lw0/U9kcb848+jEAzkrUzk46jHI5BH

Bug#965932: marked as done (libc6: breaks openssh-server/buster)

2020-07-22 Thread Debian Bug Tracking System
Your message dated Wed, 22 Jul 2020 22:51:17 +
with message-id 
and subject line Bug#965932: fixed in glibc 2.31-2
has caused the Debian Bug report #965932,
regarding libc6: breaks openssh-server/buster
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.)


-- 
965932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.31-1
Severity: critical
Justification: breaks unrelated software; breaks remote access

TL;DR: sshd privsep child dies with SIGSYS in clock_nanosleep() (libc6 2.31-1)
while it succeeded using nanosleep() under libc6 2.30-8

The machine in question is running buster with some selected packages
(mainly compilers and development stuff) from bullseye (and is located
at a remote location).

The running kernel is 4.19.0-9-amd64 4.19.118-2.
openssh-server 1:7.9p1-10+deb10u2 is running.
After upgrading libc6 from 2.30-8 to 2.31-1 (which caused sshd to restart),
sshd was running, but dropped incoming connections during authentication.
Luckily I still had a terminal open and could downgrade again to 2.30-8
which restored accessibility.

Thanks to the people trying to guess usernames and passwords, I noticed this
difference in /var/log/auth.log:

with 2.31-1:
Jul 20 21:52:11 hostname sshd[25603]: Invalid user ping from 139.219.0.102 port 
39588
Jul 20 21:52:11 hostname sshd[25603]: pam_unix(sshd:auth): check pass; user 
unknown
Jul 20 21:52:11 hostname sshd[25603]: pam_unix(sshd:auth): authentication 
failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.219.0.102 
Jul 20 21:52:13 hostname sshd[25603]: Failed password for invalid user ping 
from 139.219.0.102 port 39588 ssh2

after downgrading to 2.30-8:
Jul 20 21:54:33 hostname sshd[26824]: Invalid user mickey from 51.83.131.123 
port 32822
Jul 20 21:54:33 hostname sshd[26824]: pam_unix(sshd:auth): check pass; user 
unknown
Jul 20 21:54:33 hostname sshd[26824]: pam_unix(sshd:auth): authentication 
failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.83.131.123 
Jul 20 21:54:35 hostname sshd[26824]: Failed password for invalid user mickey 
from 51.83.131.123 port 32822 ssh2
Jul 20 21:54:35 hostname sshd[26824]: Received disconnect from 51.83.131.123 
port 32822:11: Bye Bye [preauth]
Jul 20 21:54:35 hostname sshd[26824]: Disconnected from invalid user mickey 
51.83.131.123 port 32822 [preauth]


I can reproduce this by running sshd in a mininmal buster chroot and
upgrading libc6 (+ libgcc-s1 libcrypto1 libc-bin).
(There is even no need to restart sshd (which was started under 2.31-1) after
downgrading libc6 again to 2.30-8 to get it functional again.)
I haven't tried sshd/bullseye. I haven't tried booting with 2.31-1.

$ ssh -vvv foo@localhost -p 9922
[...]
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:/07awyZSdCd9QgaTWi1dn3kEg9rbZtYC+ejHd6ZFi2w
debug3: put_host_port: [127.0.0.1]:9922
debug3: put_host_port: [localhost]:9922
debug3: hostkeys_foreach: reading file "/home/beckmann/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file 
/home/beckmann/.ssh/known_hosts:4
debug3: load_hostkeys: loaded 1 keys from [localhost]:9922
debug1: Host '[localhost]:9922' is known and matches the ECDSA host key.
debug1: Found key in /home/beckmann/.ssh/known_hosts:4
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey after 134217728 blocks
debug1: Will attempt key: /home/beckmann/.ssh/id_dsa
debug1: Will attempt key: /home/beckmann/.ssh/id_ecdsa
debug1: Will attempt key: /home/beckmann/.ssh/id_ed25519
debug1: Will attempt key: /home/beckmann/.ssh/id_xmss
debug2: pubkey_prepare: done
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: 
server-sig-algs=
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
Connection closed by 127.0.0.1 port 9922

# /usr/sbin/sshd -ddd
debug2: load_server_config: filename /etc/ssh/sshd_config
debug2: load_server_config: done config len = 328
debug2: parse_server_config: config /etc/ssh/sshd_config len 328
debug3: /etc/ssh/sshd_config:13 setting Port 9922
debug3: /etc/ssh/sshd_config:26 setting SyslogFacility LOCAL7
debug3: /etc/ssh/sshd_config:27 setting LogLevel DEBUG3
de

Processed: Bug#965091 marked as pending in glibc

2020-07-22 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #965091 [libc6] glibc: setgroups: Bad address [2.31/x32, regression from 
2.30]
Added tag(s) pending.

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



Processed: Bug#965941 marked as pending in glibc

2020-07-22 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #965941 [src:glibc] src:glibc: FTBFS with libselinux-dev (>= 3.1) due to 
deprecations warnings
Added tag(s) pending.

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



Processed: Bug#965932 marked as pending in glibc

2020-07-20 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #965932 [libc6] libc6: breaks openssh-server/buster
Added tag(s) pending.

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



Processed: Re: Bug#964477: libc6-dev: Fails to cleanly upgrade from Stable

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

> reassign 964477 apt
Bug #964477 [libc6-dev] libc6-dev: Fails to cleanly upgrade from Stable
Bug reassigned from package 'libc6-dev' to 'apt'.
No longer marked as found in versions glibc/2.28-10.
Ignoring request to alter fixed versions of bug #964477 to the same values 
previously set
> thanks
Stopping processing here.

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



Processed: Re: Bug#965091: glibc: setgroups: Bad address [2.31/x32, regression from 2.30]

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

> severity 965091 important
Bug #965091 [libc6] glibc: setgroups: Bad address [2.31/x32, regression from 
2.30]
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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



Processed: Re: Bug#965323: postinst script deletes custom locales

2020-07-19 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 + wontfix
Bug #965323 [locales] postinst script deletes custom locales
Added tag(s) wontfix.

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



Processed: Bug#961452 marked as pending in glibc

2020-07-16 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #961452 [src:glibc] CVE-2020-6096
Added tag(s) pending.

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



Processed: reassign

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

> reassign 965109 qemu
Bug #965109 [libc6] libc6: 'semop(1): encountered an error: Function not 
implemented' in fakeroot under qemu
Bug reassigned from package 'libc6' to 'qemu'.
No longer marked as found in versions glibc/2.31-1.
Ignoring request to alter fixed versions of bug #965109 to the same values 
previously set
> affects 965109 libc6
Bug #965109 [qemu] libc6: 'semop(1): encountered an error: Function not 
implemented' in fakeroot under qemu
Added indication that 965109 affects libc6
> retitle 965109 qemu: missing support for the semtimedop syscall
Bug #965109 [qemu] libc6: 'semop(1): encountered an error: Function not 
implemented' in fakeroot under qemu
Changed Bug title to 'qemu: missing support for the semtimedop syscall' from 
'libc6: 'semop(1): encountered an error: Function not implemented' in fakeroot 
under qemu'.
> --
Stopping processing here.

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



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

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

> forwarded 965091 https://sourceware.org/bugzilla/show_bug.cgi?id=26248
Bug #965091 [libc6] glibc: setgroups: Bad address [2.31/x32, regression from 
2.30]
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=26248'.
> thanks
Stopping processing here.

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



Processed: tagging 965091

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

> tags 965091 + upstream
Bug #965091 [libc6] glibc: setgroups: Bad address [2.31/x32, regression from 
2.30]
Added tag(s) upstream.
> thanks
Stopping processing here.

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



Processed: your mail

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

> affects 965091 openssh-server
Bug #965091 [libc6] glibc: setgroups: Bad address [2.31/x32, regression from 
2.30]
Added indication that 965091 affects openssh-server
> affects 965091 postfix
Bug #965091 [libc6] glibc: setgroups: Bad address [2.31/x32, regression from 
2.30]
Added indication that 965091 affects postfix
> thanks
Stopping processing here.

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



Bug#964141: marked as done (libc6: "cannot allocate memory in static TLS block" with some library combinations on arm64)

2020-07-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Jul 2020 19:49:11 +
with message-id 
and subject line Bug#964141: fixed in glibc 2.31-1
has caused the Debian Bug report #964141,
regarding libc6: "cannot allocate memory in static TLS block" with some library 
combinations on arm64
to be marked as done.

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


-- 
964141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.30-8
Control: block 960073 by -1

Dear glibc maintainers,

Originally I got two reports about issues when loading Qt WebEngine library
from Python using PyQt and PySide bindings, see #960073 and #963709 for
context.

However I can reproduce it without any Python code and even without Qt.

The attached C program tries to load three popular libraries: libsystemd.so.0,
libavformat.so.58 (from ffmpeg) and libglapi.so.0 (from mesa).

When trying to run it on arm64, I get the following:

$ gcc test.c -ldl
$ ./a.out
Failed to load libglapi.so.0: /usr/lib/aarch64-linux-gnu/libglapi.so.0: cannot 
allocate memory in static TLS block

This does not happen on other architectures. This makes me think the amount
of TLS storage on arm64 is too low, can it be somehow increased?

When swapping second and third blocks, it works fine.

Here is an upstream bug report that may be related:
https://sourceware.org/bugzilla/show_bug.cgi?id=25051

And here is patch, currently under review, that may be also related:
https://sourceware.org/pipermail/libc-alpha/2020-May/114247.html

If you think it is a bug not in glibc/dlopen but in one of these libraries,
please let me know.

--
Dmitry Shachnev
#include 
#include 

int main() {
void *systemd_handle, *avformat_handle, *glapi_handle;

systemd_handle = dlopen("libsystemd.so.0", RTLD_LAZY);
if (!systemd_handle) {
printf("Failed to load libsystemd.so.0: %s\n", dlerror());
}

avformat_handle = dlopen("libavformat.so.58", RTLD_LAZY);
if (!avformat_handle) {
printf("Failed to load libavformat.so.58: %s\n", dlerror());
return 1;
}

glapi_handle = dlopen("libglapi.so.0", RTLD_LAZY);
if (!glapi_handle) {
printf("Failed to load libglapi.so.0: %s\n", dlerror());
return 1;
}

dlclose(glapi_handle);
dlclose(avformat_handle);
dlclose(systemd_handle);
return 0;
}


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.31-1
Done: Aurelien Jarno 

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 964...@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: Mon, 13 Jul 2020 21:34:17 +0200
Source: glibc
Architecture: source
Version: 2.31-1
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 964141
Changes:
 glibc (2.31-1) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/control: Build-depend on gcc-10 version that defaults to i686 on
 hurd-i386.
   * debian/control: Build-depend on mig-for-host instead of mig.
   * debian/sysdeps/hurd-i386.mk: Drop adding -march=i686.
   * debian/hurd-i386/git-pselect.diff: Fix pselect atomicity.
   * debian/hurd-i386/git-fexecve.diff: Fix fexecve.
   * debian/hurd-i386/git-cond_destroy.diff: Fix cond_destroy synchronization
 with woken threads.
   * debian/hurd-i386/git-holes.diff: Fix detecting support for file holes.
   * debian/hurd-i386/local-clock_gettime_MONOTONIC.diff: Also fix clock_getres
 with CLOCK_MONOTONIC.
   * debian/hurd-i386/git-longjmp-onstack.diff: Fix longjmp-ing from altstack.
   * debian/hurd-i386/git-register-atfork2.diff: Fix register-atfork ordering.
   * debian/hurd-i386/git-intr-msg-unwind.diff: Fix unwinding over interruptible
 RPC.
   * debian/hurd-i386/git-strtol-test.diff: Fix testing strtol errors.
   * d

Processed: Bug#964141 marked as pending in glibc

2020-07-13 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #964141 [libc6] libc6: "cannot allocate memory in static TLS block" with 
some library combinations on arm64
Ignoring request to alter tags of bug #964141 to the same tags previously set

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



Processed: Bug#964141 marked as pending in glibc

2020-07-13 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #964141 [libc6] libc6: "cannot allocate memory in static TLS block" with 
some library combinations on arm64
Added tag(s) pending.

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



Processed: Re: Bug#964141: libc6: "cannot allocate memory in static TLS block" with some library combinations on arm64

2020-07-13 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + fixed-upstream
Bug #964141 [libc6] libc6: "cannot allocate memory in static TLS block" with 
some library combinations on arm64
Added tag(s) fixed-upstream.

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



Bug#964948: marked as done (tzdata: The leap-seconds.list file is expired)

2020-07-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Jul 2020 12:13:22 +0200
with message-id <20200713101322.ge8...@aurel32.net>
and subject line Re: Bug#964948: tzdata: The leap-seconds.list file is expired
has caused the Debian Bug report #964948,
regarding tzdata: The leap-seconds.list file is expired
to be marked as 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.)


-- 
964948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tzdata
Version: 2019c-0+deb9u1
Severity: normal

Dear Maintainer,

It appears the leap-seconds.list file of tzdata in debian stable is now expired.
This is a potential issue if new leap seconds are introduced, and thus, as far 
as I understand, deserve an upgrade even in debian oldstable. The sid version of
this package expires on 28 December 2020.

$ grep "File expires" /usr/share/zoneinfo/leap-seconds.list 
#   File expires on:  28 June 2020

Best regards


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

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

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

tzdata recommends no packages.

tzdata suggests no packages.

-- debconf information:
  tzdata/Zones/Australia:
  tzdata/Zones/SystemV:
* tzdata/Areas: Etc
  tzdata/Zones/Europe:
  tzdata/Zones/Indian:
  tzdata/Zones/Pacific:
  tzdata/Zones/Africa:
* tzdata/Zones/America: New_York
  tzdata/Zones/Asia:
  tzdata/Zones/Arctic:
* tzdata/Zones/Etc: UTC
  tzdata/Zones/Atlantic:
  tzdata/Zones/US:
  tzdata/Zones/Antarctica:
--- End Message ---
--- Begin Message ---
Version: 2020a-0+deb9u1 

Hi,

On 2020-07-13 07:35, Pierre Ducroquet wrote:
> Package: tzdata
> Version: 2019c-0+deb9u1
> Severity: normal
> 
> Dear Maintainer,
> 
> It appears the leap-seconds.list file of tzdata in debian stable is now 
> expired.

I guess you mean oldstable, not stable here.

> This is a potential issue if new leap seconds are introduced, and thus, as 
> far 
> as I understand, deserve an upgrade even in debian oldstable. The sid version 
> of
> this package expires on 28 December 2020.
> 
> $ grep "File expires" /usr/share/zoneinfo/leap-seconds.list 
> #   File expires on:  28 June 2020
> 

The package tzdata 2020a-0+deb9u1 which fixes that issue is already
ready, and is available in oldstable-proposed-updates [1]. It'll be
released with the last version of debian oldstable on July 18th [2].

Aurelien

[1] 
http://ftp.debian.org/debian/pool/main/t/tzdata/tzdata_2020a-0+deb9u1_all.deb
[2] 
https://release.debian.org/proposed-updates/oldstable.html#tzdata_2020a-0+deb9u1
 

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


Processed: Re: Bug#964477: libc6-dev: Fails to cleanly upgrade from Stable

2020-07-12 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + help
Bug #964477 [libc6-dev] libc6-dev: Fails to cleanly upgrade from Stable
Added tag(s) help.

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



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

2020-07-09 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 #856503 (http://bugs.debian.org/856503)
> # Bug title: glibc: CVE-2016-10228: iconv(1) with -c option hangs on illegal 
> multi-byte sequences
> #  * http://sourceware.org/bugzilla/show_bug.cgi?id=19519
> #  * remote status changed: ASSIGNED -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 856503 + fixed-upstream
Bug #856503 [src:glibc] glibc: CVE-2016-10228: iconv(1) with -c option hangs on 
illegal multi-byte sequences
Added tag(s) fixed-upstream.
> usertags 856503 - status-ASSIGNED
Usertags were: status-ASSIGNED.
Usertags are now: .
> usertags 856503 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> # remote status report for #961452 (http://bugs.debian.org/961452)
> # Bug title: CVE-2020-6096
> #  * http://sourceware.org/bugzilla/show_bug.cgi?id=25620
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 961452 + fixed-upstream
Bug #961452 [src:glibc] CVE-2020-6096
Added tag(s) fixed-upstream.
> usertags 961452 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 961452 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> thanks
Stopping processing here.

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



Bug#963508: marked as done (/lib/ld-linux.so.2: LD_PRELOAD breaks with plain filename)

2020-07-03 Thread Debian Bug Tracking System
Your message dated Sat, 4 Jul 2020 00:22:39 +0200
with message-id <2020070339.gc8...@aurel32.net>
and subject line Re: Bug#963508: /lib/ld-linux.so.2: LD_PRELOAD breaks with 
plain filename [and 1 more messages]
has caused the Debian Bug report #963508,
regarding /lib/ld-linux.so.2: LD_PRELOAD breaks with plain 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.)


-- 
963508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.28-10
Severity: normal
File: /lib/ld-linux.so.2

Hi.  I found this behaviour:

$ eatmydata man ls >/dev/null 
ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
$

Experimenting shows that the problem is triggered by having LD_PRELOAD
containing only the library name:

$ faketime yesterday printenv | grep PREL
LD_PRELOAD=libgtk3-nocsd.so.0:/usr/$LIB/faketime/libfaketime.so.1
$ faketime yesterday env LD_PRELOAD=libfaketime.so.1 man ls >/dev/null 
ERROR: ld.so: object 'libfaketime.so.1' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libfaketime.so.1' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libfaketime.so.1' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libfaketime.so.1' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libfaketime.so.1' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libfaketime.so.1' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libfaketime.so.1' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libfaketime.so.1' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
$

The problem is not limited to man:

$ faketime yesterday env LD_PRELOAD=libfaketime.so.1 dash -c true
ERROR: ld.so: object 'libfaketime.so.1' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
$

This message on debian-user seems related:
  https://lists.debian.org/debian-user/2017/03/msg00335.html

Colin Watson (CC'd) reports that sid works.

Thanks for your attention.

Ian.

-- System Information:
Debian Release: 10.4
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

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

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

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

-- debconf information excluded
--- End Message ---
--- Begin Message ---
On 2020-06-23 17:24, Aurelien Jarno wrote:
> On 2020-06-23 14:17, Ian Jackson wrote:
> > 
> > Aurelien Jarno writes ("Re: Bug#963508: /lib/ld-linux.so.2: LD_PRELOAD 
> > breaks with plain filename"):
> > > [stuff]
> > 
> > Thanks for your explanations and sorry for being dense.
> > 
> > >   In secure-execution mode, preload pathnames containing slashes are
> > >   ignored.  Furthermore, shared objects are preloaded only from the
> > >   standard search directories and only if they have set-user-ID mode bit
> > >   enabled (which is not typical).
> > 
> > Obviously it wouldn't be right for eatmydata to be loaded by actually
> > setuid programs.
> > 
> > Ian Jackson writes ("Re: Bug#963508: /lib/ld-linux.so.2: LD_PRELOAD breaks 
> > with plain filename"):
> > > (As an aside, I'm not sure why it makes sense for

Processed: Bug#963007 marked as pending in tzdata

2020-07-03 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #963007 [tzdata] tzdata: [INTL:nl] Dutch translation of debconf messages
Added tag(s) pending.

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



Processed: Re: libc6: "cannot allocate memory in static TLS block" with some library combinations on arm64

2020-07-03 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 patch
Bug #964141 [libc6] libc6: "cannot allocate memory in static TLS block" with 
some library combinations on arm64
Added tag(s) patch.

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



Processed: libc6: "cannot allocate memory in static TLS block" with some library combinations on arm64

2020-07-02 Thread Debian Bug Tracking System
Processing control commands:

> block 960073 by -1
Bug #960073 [python-pyqt5] Package:python-pyqt5 Run the example code with Trace 
and crash (SIGABRT)
960073 was not blocked by any bugs.
960073 was not blocking any bugs.
Added blocking bug(s) of 960073: 964141

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



Processed: tagging 961452, bug 961452 is forwarded to https://sourceware.org/bugzilla/show_bug.cgi?id=25620

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

> tags 961452 + security
Bug #961452 [src:glibc] CVE-2020-6096
Added tag(s) security.
> forwarded 961452 https://sourceware.org/bugzilla/show_bug.cgi?id=25620
Bug #961452 [src:glibc] CVE-2020-6096
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=25620'.
> thanks
Stopping processing here.

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



Processed: Re: Bug#960536: locales: $LANGUAGE and $LC_ALL are not set

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

> tag 960536 + unreproducible
Bug #960536 [locales] locales:  $LANGUAGE and $LC_ALL are not set
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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



Bug#956418: marked as done (src:glibc: Please provide optimized builds for ARMv8.1)

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 22:33:45 +
with message-id 
and subject line Bug#956418: fixed in glibc 2.31-0experimental2
has caused the Debian Bug report #956418,
regarding src:glibc: Please provide optimized builds for ARMv8.1
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.)


-- 
956418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:glibc
Version: 2.30-4
Severity: wishlist
X-Debbugs-CC: debian-...@lists.debian.org

The ARMv8.1 spec, as implemented by the ARM Neoverse N1 processor,
introduces a set of instructions [1] that result in significant performance
improvements for multithreaded applications.  Sample code demonstrating the
performance improvements is attached.  When run on a 16-core Neoverse N1
host with glibc 2.30-4, runtimes vary significantly, ranging from lows
around 250ms to highs around 15 seconds.  When linked against glibc rebuilt
with support for these instructions, runtimes are consistently <50ms.
Significant performance impact has also been observed in less contrived
cases (MariaDB and Postgres), but I don't have a repro to share.

Gcc provides two ways to enable support for these instructions at build
time.  The simplest, and least disruptive, is to enable -moutline-atomics
globally in the arm64 glibc build.  As described at [2], this option enables
runtime checks for the availability of the atomic instructions.  If found,
they are used, otherwise ARMv8.0 compatible code is used.  The drawback of
this option is that the check happens at runtime, thus introducing some
overhead on all arm64 installations.

The second option is to provide libraries built with explicit support for
the ARM v8.1a spec via the -march=armv8.1-a flag.  This option is also
described at [2].  This build would be incompatible with earlier versions of
the spec, so it would need to be provided in a location where the linker
will automatically discover it if it is usable (e.g.
/lib/aarch64-linux-gnu/atomics/).  This does not incur any runtime overhead,
but obviously involves an additional libc build, and the corresponding
complixity and disk space utilization.  I'm not sure if this is an option
that the glibc maintainers are interested in pursuing.

I've tested both options and found them to be acceptable on v8.1a (Neoverse
N1) and v8a (Cortex A72) CPUs.  I can provide bulk test run data of the
various different configuration permutations if you'd like to see additional
data.

I can provide patches or merge requests implementing either option, at least
for a starting point, if you'd like to see them.

Thanks!
noah

1. https://static.docs.arm.com/ddi0557/a/DDI0557A_b_armv8_1_supplement.pdf
   Section B1
2. https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html
/*
 * Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
 *
 * Licensed under the Apache License, Version 2.0 (the "License"). You may
 * not use this file except in compliance with the License. A copy of the
 * License is located at
 *
 *  http://aws.amazon.com/apache2.0/
 *
 * or in the "license" file accompanying this file. This file is distributed
 * on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either
 * express or implied. See the License for the specific language governing
 * permissions and limitations under the License.
*/

/* Build with:
 * gcc -O2 -o a.out a.c -lpthread -DITER=1000 -DTHREADS=64
*/

#include 
#include 
#include 
#include 

#ifndef ITER
# define ITER 1000
#endif
#ifndef THREADS
# define THREADS 3
#endif

#if THREADS < 1
# error "THREADS is supposed to be at least 1"
#endif

static pthread_mutex_t lock = PTHREAD_MUTEX_INITIALIZER;
static int shared_ptr = 0;

typedef struct stats_s {
  uint64_t min, max;
  int times;
  uint64_t total;
  uint64_t flips;
} stats_t;

stats_t stats[THREADS + 1];
pthread_t threads[THREADS];

#ifdef __aarch64__
static uint64_t cpu_shift() {
  uint64_t shift = 0;
  __asm__ __volatile__ ("mrs %0,cntfrq_el0; clz %w0, %w0":"="(shift));
  return shift;
}
#endif

static uint64_t gettime() {
#ifdef __aarch64__
  uint64_t ret = 0;
  __asm__ __volatile__ ("isb; mrs %0,cntvct_el0":"=r"(ret));
  return ret << cpu_shift();

#elif defined __x86_64__
  uint64_t a, d;
  __asm__ __volatile__ ("rdtsc" : "=a" (a), "=d" (d));
  return ((uint64_t)a + ((uint64_t)d << 32));
#endif

  return 0;
}

static void init_stats() {
  int i;
  for (i = 0; i <= THREADS; i++

Bug#960739: marked as done (libc-bin: getaddrinfo() fails with EAI_AGAIN when the DNS query returns a large number of A and AAAA records.)

2020-05-18 Thread Debian Bug Tracking System
Your message dated Mon, 18 May 2020 20:22:48 +0200
with message-id <87lflp85mv@mid.deneb.enyo.de>
and subject line Re: Bug#960739: libc-bin: getaddrinfo() fails with EAI_AGAIN 
when the DNS query returns a large number of A and  records.
has caused the Debian Bug report #960739,
regarding libc-bin: getaddrinfo() fails with EAI_AGAIN when the DNS query 
returns a large number of A and  records.
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.)


-- 
960739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc-bin
Version: 2.30-7
Severity: important
Tags: ipv6

Dear Maintainer,

When attempting to follow the instructions for installing the latest version of 
Docker Engine at 
https://docs.docker.com/engine/install/debian/ I noticed that 'apt-get update' 
and curl were both
failing to resolve download.docker.com.  The error message from both ping and 
curl was 
"Temporary failure in name resolution"

However, running 'host download.docker.com' yielded the following results:

download.docker.com is an alias for d2h67oheeuigaw.cloudfront.net.
d2h67oheeuigaw.cloudfront.net has address 13.227.73.43
d2h67oheeuigaw.cloudfront.net has address 13.227.73.44
d2h67oheeuigaw.cloudfront.net has address 13.227.73.95
d2h67oheeuigaw.cloudfront.net has address 13.227.73.15
d2h67oheeuigaw.cloudfront.net has IPv6 address 
2600:9000:2202:c00:3:db06:4200:93a1
d2h67oheeuigaw.cloudfront.net has IPv6 address 
2600:9000:2202:5000:3:db06:4200:93a1
d2h67oheeuigaw.cloudfront.net has IPv6 address 
2600:9000:2202:7a00:3:db06:4200:93a1
d2h67oheeuigaw.cloudfront.net has IPv6 address 
2600:9000:2202:9200:3:db06:4200:93a1
d2h67oheeuigaw.cloudfront.net has IPv6 address 
2600:9000:2202:9600:3:db06:4200:93a1
d2h67oheeuigaw.cloudfront.net has IPv6 address 
2600:9000:2202:9c00:3:db06:4200:93a1
d2h67oheeuigaw.cloudfront.net has IPv6 address 
2600:9000:2202:a200:3:db06:4200:93a1
d2h67oheeuigaw.cloudfront.net has IPv6 address 
2600:9000:2202:f600:3:db06:4200:93a1

After examining the source code for iputils-ping, I was able to determine that 
the cause of the
error message was getaddrinfo() returning EAI_AGAIN

The following workarounds were effective:

* curl -4 https://download.docker.com/... (Forcing curl to use IPv4 only)
* ping -4 download.docker.com (Forcing IPv4 ping to use IPv4 only)
* Forcing apt to use IPv4 by adding 'Acquire::ForceIPv4 "true";' to apt.conf

It is also noteworthy that not all hostnames with both A and  records 
trigger this bug. In fact,
hostnames with a low total record count like www.google.com have no problem 
whatsoever


root@sandbox:~# host www.google.com
www.google.com has address 172.217.6.36
www.google.com has IPv6 address 2607:f8b0:4005:809::2004
...
root@sandbox:~# ping www.google.com
PING www.google.com (172.217.6.36) 56(84) bytes of data.
64 bytes from sfo03s08-in-f4.1e100.net (172.217.6.36): icmp_seq=1 ttl=63 
time=29.6 ms
...
^C
--- www.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2005ms
rtt min/avg/max/mdev = 29.572/37.733/42.045/5.774 ms


Please note that this bug also affects libc-bin 2.28-10 in buster.

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

Kernel: Linux 4.19.0-9-amd64 (SMP w/4 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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libc-bin depends on:
ii  libc6  2.30-7

Versions of packages libc-bin recommends:
ii  manpages  5.06-1

libc-bin suggests no packages.

-- Configuration Files:
/etc/gai.conf changed [not included]

-- no debconf information
--- End Message ---
--- Begin Message ---
* Mike Przybylski:

> Since you’ve pointed out pretty clearly from the pcap that Google
> and VirtualBox are having some bizarre interaction, I think we can
> close this as “not a bug.”  I apologize for taking up your time with
> it.

It's the DNS implementation in Virtualbox that's broken, particularly
in the area of TCP support.  Upstream glibc occasionally receives bug
reports about it, too.--- End Message ---


Bug#960737: marked as done (libc6: on the Unicode character U+1F928 and above, iswctype returns false for all properties)

2020-05-17 Thread Debian Bug Tracking System
Your message dated Sun, 17 May 2020 17:22:54 +0200
with message-id <20200517152254.ge2...@aurel32.net>
and subject line Re: Bug#960737: libc6: on the Unicode character U+1F928 and 
above, iswctype returns false for all properties
has caused the Debian Bug report #960737,
regarding libc6: on the Unicode character U+1F928 and above, iswctype returns 
false for all properties
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.)


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

On the Unicode character U+1F928 and above, iswctype returns false for
all properties. It should have the graph, print and punct properties.

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

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(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  libcrypt1  1:4.4.16-1
ii  libgcc-s1  10.1.0-1

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

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.74
ii  glibc-doc  2.30-8
ii  libc-l10n  2.30-8
ii  locales2.30-8

-- debconf information:
* glibc/restart-services: postfix cups cron atd
  glibc/upgrade: true
* libraries/restart-without-asking: false
  glibc/disable-screensaver:
  glibc/kernel-not-supported:
  glibc/kernel-too-old:
  glibc/restart-failed:

-- 
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 ---
--- Begin Message ---
Version: 2.31-0experimental0

On 2020-05-16 02:12, Vincent Lefevre wrote:
> Package: libc6
> Version: 2.30-8
> Severity: normal
> 
> On the Unicode character U+1F928 and above, iswctype returns false for
> all properties. It should have the graph, print and punct properties.

This is correct and is fixed in glibc version 2.31. Therefore marking
the bug as fixed in this version.

Aurelien

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


Processed: Bug#960783 marked as pending in tzdata

2020-05-16 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #960783 [tzdata] tzdata: [INTL:de] updated German debconf translation
Added tag(s) pending.

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



Bug#960529: marked as done (libc6: After update the integrated camera (uvcvideo) is not longer detected)

2020-05-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 May 2020 23:10:48 +0200
with message-id <20200516211048.gd2...@aurel32.net>
and subject line Re: Bug#960529: Info received (Bug#960529: libc6: After update 
the integrated camera (uvcvideo) is not longer detected)
has caused the Debian Bug report #960529,
regarding libc6: After update the integrated camera (uvcvideo) is not longer 
detected
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.)


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

After running this morning an upgrade, the camera integrated into my Laptop 
(Thinkpad T530) is not longer available.




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

Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de:en_GB (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libc6 depends on:
ii  libcrypt1  1:4.4.16-1
ii  libgcc-s1  10.1.0-1

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

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.74
pn  glibc-doc  
ii  libc-l10n  2.30-7
ii  locales2.30-7

-- debconf information:
  glibc/restart-services:
  glibc/upgrade: true
  glibc/kernel-too-old:
  glibc/disable-screensaver:
* libraries/restart-without-asking: true
  glibc/restart-failed:
  glibc/kernel-not-supported:
--- End Message ---
--- Begin Message ---
On 2020-05-13 21:57, Reiner Nix wrote:
> Hi,
> 
> now, I have tried again to start a video conference (just to check connecting 
> zoom to an alternative device) ... and this laptop works with zoom and jitsi 
> without any further config change. Very strange.
> 
> I guess that this ticket can be closed and apologize for any inconvenience 
> caused by the ticket.

No problem, closing it with that mail.

Aurelien

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


Processed: Re: Bug#960739: libc-bin: getaddrinfo() fails with EAI_AGAIN when the DNS query returns a large number of A and AAAA records.

2020-05-16 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 libc6
Bug #960739 [libc-bin] libc-bin: getaddrinfo() fails with EAI_AGAIN when the 
DNS query returns a large number of A and  records.
Bug reassigned from package 'libc-bin' to 'libc6'.
No longer marked as found in versions glibc/2.30-7.
Ignoring request to alter fixed versions of bug #960739 to the same values 
previously set

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



Processed: affects 960739

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

> affects 960739 curl apt
Bug #960739 [libc-bin] libc-bin: getaddrinfo() fails with EAI_AGAIN when the 
DNS query returns a large number of A and  records.
Added indication that 960739 affects curl and apt
> thanks
Stopping processing here.

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



Processed: Bug#956418 marked as pending in glibc

2020-05-12 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #956418 [src:glibc] src:glibc: Please provide optimized builds for ARMv8.1
Added tag(s) pending.

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



Bug#941174: marked as done (glibc: FTBFS on hppa - new test failures)

2020-05-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 May 2020 21:48:37 +
with message-id 
and subject line Bug#941174: fixed in glibc 2.30-5
has caused the Debian Bug report #941174,
regarding glibc: FTBFS on hppa - new test failures
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.)


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

Dear Maintainer,

Since version 2.29-2, glibc fails to build on hppa.  We have the following
test fails:

+-+
| Encountered regressions that don't match expected failures. |
+-+
FAIL: nptl/tst-cond21
FAIL: nptl/tst-rwlock19
FAIL: nptl/tst-stackguard1
FAIL: nptl/tst-tls1
FAIL: stdio-common/tst-vfprintf-user-type

These fails are not fully consistent from build to build.  2.29-1 built
successfully.

I did a build outside the buildd and all these tests passed.  One test
failed:

+-+
| Encountered regressions that don't match expected failures. |
+-+
FAIL: elf/tst-pldd

dave@mx3210:~/debian/glibc/glibc-2.29$ cat 
./build-tree/hppa-libc/elf/tst-pldd.out
error: xposix_spawn.c:30: posix_spawn to /usr/bin/pldd file failed: No such 
file or directory
error: 1 test failures

It seems like pldd got installed in the wrong place:
mv -f /home/dave/debian/glibc/glibc-2.29/debian/tmp-libc/usr/bin/pldd.new 
/home/dave/debian/glibc/glibc-2.29/debian/tmp-libc/usr/bin/pldd

Regards,
Dave Anglin

-- System Information:
Debian Release: bullseye/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 4.14.146+ (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (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.30-5
Done: Aurelien Jarno 

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 941...@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: Mon, 04 May 2020 23:39:18 +0200
Source: glibc
Architecture: source
Version: 2.30-5
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 910685 941174 953654 955270 958674
Changes:
 glibc (2.30-5) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/git-trunc-times.diff: New patch to fix updating
 mtime/ctime on O_TRUNC.  Closes: #955270.
   * debian/control: Drop dependency on libihash-dev, not used any more by htl.
   * debian/sysdeps/hurd.mk: Try to symlink mach/hurd headers from multiarch
 directory when they are there.
 .
   [ Aurelien Jarno ]
   * debian/rules: Add -fdebug-prefix-map= to CFLAGS to improve
 reproducibility.
   * debian/control.in/libc: Make libcX-dev declare a Breaks against python3.7
 (<< 3.7.7-1+b1) and python3.8 (<< 3.8.2-1+b1) due to #955474.
   * debian/rules.d/debhelper.mk: install the dynamic loader symlink in the
 udeb package.
   * debian/control: conflict against libgcc-X-dev versions that might need the
 __glibc_has_include macro.
   * debian/patches/any/local-revert-glibc_has_include.diff: drop patch,
 obsolete.
   * debian/control.in/libc: add a Provides: libc6-dbgsym to the libc6-dbg
 package.  Closes: #953654.
   * debian/control.in/libc: qualify the libselinux-dev build-depends with
 .
   * debian/debhelper.in/libc.postinst: drop the code removing
 /etc/ld.so.hwcappkgs, it's not needed anymore since Squeeze.
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fixes data race in setting function descr

Bug#958674: marked as done (glibc: refactor generation of multilib include symlinks)

2020-05-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 May 2020 21:48:37 +
with message-id 
and subject line Bug#958674: fixed in glibc 2.30-5
has caused the Debian Bug report #958674,
regarding glibc: refactor generation of multilib include symlinks
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.)


-- 
958674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.30-4
Severity: wishlist
Tags: patch
Control: block 798955 by -1

Hi Aurelien,

as you might have noticed, I resumed work on the long-standing multiarch
glibc headers issue. It seems that we're mostly done with prerequisites
now. Most patches with the exception of a qmake one have been filed a
while ago, so it seems like time to move forward a little.

The resulting patch to glibc is not entirely trivial, so I've tried to
split it into more manageable pieces:

 * This bug: Refactor generation of multilib include symlinks. It is
   essentially pulling a pile of duplicated code into a make define. As
   such it can be considered a cleanup patch (net -160 lines) and does
   not affect resulting packages in an observable way. It is readily
   applicable.

 * #798955 will receive an updated patch after applying this one. The
   updated patch is much smaller, which makes it easier to review.

Please don't let this patch sit in the bts for long. Either you like my
approach of splitting the diff and can apply it. Fine. Or you disagree
with it on some level. In that case, I'd like to learn your reason and
have this bug closed and tagged wontfix.

Helmut
diff --minimal -Nru glibc-2.30/debian/changelog glibc-2.30/debian/changelog
--- glibc-2.30/debian/changelog 2020-03-25 13:56:56.0 +0100
+++ glibc-2.30/debian/changelog 2020-04-24 08:02:13.0 +0200
@@ -1,3 +1,10 @@
+glibc (2.30-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Refactor generation of multilib include symlinks. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 24 Apr 2020 08:02:13 +0200
+
 glibc (2.30-4) unstable; urgency=medium
 
   [ Aurelien Jarno ]
diff --minimal -Nru glibc-2.30/debian/rules.d/build.mk 
glibc-2.30/debian/rules.d/build.mk
--- glibc-2.30/debian/rules.d/build.mk  2020-03-25 13:36:06.0 +0100
+++ glibc-2.30/debian/rules.d/build.mk  2020-04-24 08:02:08.0 +0200
@@ -2,6 +2,16 @@
 # PASS_VAR, we need to call all variables as $(call xx,VAR)
 # This little bit of magic makes it possible:
 xx=$(if $($(curpass)_$(1)),$($(curpass)_$(1)),$($(1)))
+define generic_multilib_extra_pkg_install
+set -e; \
+mkdir -p debian/$(1)/usr/include/sys; \
+ln -sf $(DEB_HOST_GNU_TYPE)/bits debian/$(1)/usr/include/; \
+ln -sf $(DEB_HOST_GNU_TYPE)/gnu debian/$(1)/usr/include/; \
+ln -sf $(DEB_HOST_GNU_TYPE)/fpu_control.h debian/$(1)/usr/include/; \
+for i in `ls debian/tmp-libc/usr/include/$(DEB_HOST_GNU_TYPE)/sys`; do \
+   ln -sf ../$(DEB_HOST_GNU_TYPE)/sys/$$i debian/$(1)/usr/include/sys/$$i; 
\
+done
+endef
 
 ifneq ($(filter stage1,$(DEB_BUILD_PROFILES)),)
 libc_extra_config_options = $(extra_config_options) 
--disable-sanity-checks \
diff --minimal -Nru glibc-2.30/debian/sysdeps/amd64.mk 
glibc-2.30/debian/sysdeps/amd64.mk
--- glibc-2.30/debian/sysdeps/amd64.mk  2020-03-25 13:36:06.0 +0100
+++ glibc-2.30/debian/sysdeps/amd64.mk  2020-04-24 08:02:08.0 +0200
@@ -20,21 +20,13 @@
 
 define libc6-dev-i386_extra_pkg_install
 
-mkdir -p debian/libc6-dev-i386/usr/include
-ln -sf x86_64-linux-gnu/bits debian/libc6-dev-i386/usr/include/
-ln -sf x86_64-linux-gnu/gnu debian/libc6-dev-i386/usr/include/
-ln -sf x86_64-linux-gnu/fpu_control.h debian/libc6-dev-i386/usr/include/
+$(call generic_multilib_extra_pkg_install,libc6-dev-i386)
 
 mkdir -p debian/libc6-dev-i386/usr/include/x86_64-linux-gnu/gnu
 cp -a debian/tmp-i386/usr/include/gnu/lib-names-32.h \
debian/tmp-i386/usr/include/gnu/stubs-32.h \
debian/libc6-dev-i386/usr/include/x86_64-linux-gnu/gnu
 
-mkdir -p debian/libc6-dev-i386/usr/include/sys
-for i in `ls debian/tmp-libc/usr/include/x86_64-linux-gnu/sys` ; do \
-ln -sf ../x86_64-linux-gnu/sys/$$i 
debian/libc6-dev-i386/usr/include/sys/$$i ; \
-done
-
 endef
 
 define libc6-i386_extra_pkg_install
diff --minimal -Nru glibc-2.30/debian/sysdeps/armel.mk 
glibc-2.30/debian/sysdeps/armel.mk
--- glibc-2.30/debian/sysdeps/armel.mk  2020-03-11 22:13:40.0 +0100
+++ glibc-2.30/debian/sysdeps/armel.mk  2020-04-24 08:02:08.0 +0200
@@ -15,21 +15,13 @@
 #
 #define libc6-dev-armhf_extra_pkg_install
 #
-#mkdir -p debian/libc6-dev-armhf/usr/include
-#ln

Bug#910685: marked as done (glibc: please support DPKG_ROOT)

2020-05-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 May 2020 21:48:37 +
with message-id 
and subject line Bug#910685: fixed in glibc 2.30-5
has caused the Debian Bug report #910685,
regarding glibc: please support DPKG_ROOT
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.)


-- 
910685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibc
Version: 2.27-6
Severity: wishlist
Tags: patch
Control: user debian-d...@lists.debian.org
Control: usertag -1 + dpkg-root-support

Hi,

In version 1.18.5, dpkg gained a new way for installing binary packages.
It now supports executing maintainer scripts outside the system it is
operating on. The feature is tracked at
https://wiki.debian.org/Teams/Dpkg/Spec/InstallBootstrap. This is
relevant in two ways:
 * When running debootstrap, ordering postinsts is tricky due to the
   number of dependency loops. By executing them outside the chroot,
   some loops can be broken as utilities of the outer system can be
   used.
 * When creating chroots for foreign architectures, the utilities
   inside such chroots usually cannot be executed at all.

To support this, dpkg now unconditionally exports an environment
variable called DPKG_ROOT. It will point to the installation root with
the trailing slash stripped. That means under normal conditions, it is
empty. Since scripts are normally run under chroot(2) even when passing
--root to dpkg, it is empty in that case as well. Only when explicitly
activating the new mode, the chroot call is skipped and DPKG_ROOT can be
non-empty. It is yet unclear under what conditions this mode should be
enabled, so for the time being the only way to do so is to use
--force-script-chrootless and I stress that this is only meant for
testing.

Currently in Debian sid, there are 57 packages that need to be installed
for the whole Essential:yes set. Most of them Depend (directly or
indirectly) on libc6. Attached patch adds $DPKG_ROOT to a couple of
places of the preinst and postinst of libc6 and that will make 37 of
these 57 install without problems. The patch adds $DPKG_ROOT in more
places than strictly necessary for just installing packages. For example
I didn't test the upgrade scenario. If you like, I can prepare a smaller
patch with only the code paths that I tested.

It would be nice if you could consider applying attached patch because
it is required for the majority of packages in the Essential:yes set to
be successfully installed with the --force-script-chrootless mode.

To test you can run:

dpkg --root "$target" --log "$target/var/log/dpkg.log" 
--force-script-chrootless -i libc6_2.27-6.1_amd64.deb

Thanks!

cheers, josch
diff -Nru glibc-2.27/debian/changelog glibc-2.27/debian/changelog
--- glibc-2.27/debian/changelog 2018-09-04 21:13:02.0 +0200
+++ glibc-2.27/debian/changelog 2018-10-09 06:02:02.0 +0200
@@ -1,3 +1,10 @@
+glibc (2.27-6.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * support DPKG_ROOT
+
+ -- Johannes 'josch' Schauer   Tue, 09 Oct 2018 06:02:02 
+0200
+
 glibc (2.27-6) unstable; urgency=medium
 
   [ Samuel Thibault ]
diff -Nru glibc-2.27/debian/debhelper.in/libc.postinst 
glibc-2.27/debian/debhelper.in/libc.postinst
--- glibc-2.27/debian/debhelper.in/libc.postinst2018-01-06 
01:49:53.0 +0100
+++ glibc-2.27/debian/debhelper.in/libc.postinst2018-10-09 
06:02:02.0 +0200
@@ -17,14 +17,14 @@
 if [ "$type" = "configure" ]
 then
 # We don't use a registry anymore, remove the old file
-rm -f /etc/ld.so.hwcappkgs
+rm -f "$DPKG_ROOT/etc/ld.so.hwcappkgs"
  
 # /etc/ld.so.nohwcap code:
 __NOHWCAP__
 
 # Load debconf module if available
-if [ -f /usr/share/debconf/confmodule ] ; then
-   . /usr/share/debconf/confmodule
+if [ -f "$DPKG_ROOT/usr/share/debconf/confmodule" ] ; then
+   . "$DPKG_ROOT/usr/share/debconf/confmodule"
 fi
 
 if [ -n "$preversion" ] && [ -x "$(which ischroot)" ] && ! ischroot; then
@@ -41,7 +41,7 @@
__NSS_CHECK__
if [ -n "$services" ]; then
 
-   if [ -f /usr/share/debconf/confmodule ] ; then
+   if [ -f "$DPKG_ROOT/usr/share/debconf/confmodule" ] ; then
db_version 2.0
db_input critical libraries/restart-without-asking || true
db_go || true
@@ -116,7 +116,7 @@
done
  

Bug#953654: marked as done (libc6-dbg should be renamed (or at least Provide:) libc6-dbgsym)

2020-05-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 May 2020 21:48:37 +
with message-id 
and subject line Bug#953654: fixed in glibc 2.30-5
has caused the Debian Bug report #953654,
regarding libc6-dbg should be renamed (or at least Provide:) libc6-dbgsym
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.)


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

Every other debug symbol package in debian is named $foo-dbgsym.  libc6
seems to be the exception.

Can we please rename this package (along with a transitional package to
help folks upgrade from libc6-dbg) and set up an appropriate Provides:
at least?

This can be a stumbling block for people trying to get software
development work done on debian, as evidenced by me screwing up over
here:

https://lists.debian.org/debian-powerpc/2020/03/msg00029.html

 --dkg


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.30-5
Done: Aurelien Jarno 

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 953...@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: Mon, 04 May 2020 23:39:18 +0200
Source: glibc
Architecture: source
Version: 2.30-5
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 910685 941174 953654 955270 958674
Changes:
 glibc (2.30-5) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/git-trunc-times.diff: New patch to fix updating
 mtime/ctime on O_TRUNC.  Closes: #955270.
   * debian/control: Drop dependency on libihash-dev, not used any more by htl.
   * debian/sysdeps/hurd.mk: Try to symlink mach/hurd headers from multiarch
 directory when they are there.
 .
   [ Aurelien Jarno ]
   * debian/rules: Add -fdebug-prefix-map= to CFLAGS to improve
 reproducibility.
   * debian/control.in/libc: Make libcX-dev declare a Breaks against python3.7
 (<< 3.7.7-1+b1) and python3.8 (<< 3.8.2-1+b1) due to #955474.
   * debian/rules.d/debhelper.mk: install the dynamic loader symlink in the
 udeb package.
   * debian/control: conflict against libgcc-X-dev versions that might need the
 __glibc_has_include macro.
   * debian/patches/any/local-revert-glibc_has_include.diff: drop patch,
 obsolete.
   * debian/control.in/libc: add a Provides: libc6-dbgsym to the libc6-dbg
 package.  Closes: #953654.
   * debian/control.in/libc: qualify the libselinux-dev build-depends with
 .
   * debian/debhelper.in/libc.postinst: drop the code removing
 /etc/ld.so.hwcappkgs, it's not needed anymore since Squeeze.
   * debian/patches/git-updates.diff: update from upstream stable branch:
 - Fixes data race in setting function descriptor during lazy binding on
   hppa. Closes: #941174.
 - debian/patches/any/local-tst-system-disable-shell-tests.diff: obsolete.
 .
   [ Helmut Grohne ]
   * Refactor generation of multilib include symlinks. (Closes: #958674).
   * Initial, minimal support for DPKG_ROOT. (Closes: #910685).
Checksums-Sha1:
 3b3c6a4261a3798cc8a98041eba6998cc5765155 8649 glibc_2.30-5.dsc
 b0a42a939acd662ca2991e725644c4cd1d03ab76 847904 glibc_2.30-5.debian.tar.xz
 878760868cee957900b0b17fe9b7003e9f8c40dc 7622 glibc_2.30-5_source.buildinfo
Checksums-Sha256:
 4b078d541ec8066688d3705d7c967850d3f3fb50dda75ba9ea0e3de9e3c73d25 8649 
glibc_2.30-5.dsc
 ec4d7fc611721314fa3f26a16a2f59a740f6fa27d2c5a2d06229ad33d306f7b5 847904 
glibc_2.30-5.debian.tar.xz
 c9253a39b35cf4ec0ad497f6f1b3840f1eb3af0e7232335985513d08b58db01e 7622 
glibc_2.30-5_source.buildinfo
Files:
 c514204efe096f2b1aac6bbd2776e22f 8649 libs required glibc_2.30-5.dsc
 7ac32873dcaa8d1ecd4ab1acbb032267 847904 libs required 
glibc_2.30-5.debian.tar.xz
 2ebc279f84f54591a5750a03301b99eb 7622 libs required 
glibc_2.30-5_source.buildinfo

-BEGIN P

Bug#955270: marked as done (hurd: fails to update file mtime)

2020-05-04 Thread Debian Bug Tracking System
Your message dated Mon, 04 May 2020 21:48:37 +
with message-id 
and subject line Bug#955270: fixed in glibc 2.30-5
has caused the Debian Bug report #955270,
regarding hurd: fails to update file mtime
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.)


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

I first reported this on the mailing list:
https://lists.debian.org/debian-hurd/2020/03/msg00023.html

Now I logged in on the porterbox (exodar.debian.net) to try and
reproduce, and voilà, I can:

tg@exodar:~$ rm a b
tg@exodar:~$ :>a
tg@exodar:~$ sleep 1
tg@exodar:~$ :>b
tg@exodar:~$ stat a b | grep ^Mod
Modify: 2020-03-29 03:54:03.0 +0200
Modify: 2020-03-29 03:54:09.0 +0200
tg@exodar:~$ sleep 1
tg@exodar:~$ :>a
tg@exodar:~$ stat a b | grep ^Mod
Modify: 2020-03-29 03:54:03.0 +0200
Modify: 2020-03-29 03:54:09.0 +0200

For comparison, this is how it looks on GNU/Linux:

tglase@tglase-nb:~ $ rm a b
tglase@tglase-nb:~ $ :>a
tglase@tglase-nb:~ $ sleep 1
tglase@tglase-nb:~ $ :>b
tglase@tglase-nb:~ $ stat a b | grep ^Mod
Modify: 2020-03-29 03:58:04.989345171 +0200
Modify: 2020-03-29 03:58:05.993371946 +0200
tglase@tglase-nb:~ $ sleep 1
tglase@tglase-nb:~ $ :>a
tglase@tglase-nb:~ $ stat a b | grep ^Mod
Modify: 2020-03-29 03:58:07.001398828 +0200
Modify: 2020-03-29 03:58:05.993371946 +0200

Sub-second timestamps aside, you’ll notice how the first of the
two stat(1) lines updated. This is the common expectation for the
command true, redirected to a file.

Please reassign to the correct package, should I be mistaken.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hurd-i386 (i686-AT386)

Kernel: GNU-Mach 1.8+git20191117-486-dbg/Hurd-0.9
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 hurd depends on:
ii  hurd-libs0.3   1:0.9.git20191228-1
ii  libblkid1  2.34-0.1
ii  libc0.32.29-10
ii  libdaemon0 0.14-7
ii  libgcrypt201.8.5-5
ii  liblwip0   2.1.2+dfsg1-6
ii  libncursesw6   6.2-1
ii  libpciaccess0  0.16-1+hurd.1
ii  libtinfo6  6.2-1
ii  libx11-6   2:1.6.9-2
ii  lsb-base   11.1.0
ii  sysv-rc2.96-2.1
ii  xkb-data   2.29-2

Versions of packages hurd recommends:
ii  bf-utf-source  0.08
ii  netdde 0.0.20150828-8

Versions of packages hurd suggests:
pn  hurd-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.30-5
Done: Aurelien Jarno 

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 955...@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: Mon, 04 May 2020 23:39:18 +0200
Source: glibc
Architecture: source
Version: 2.30-5
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 910685 941174 953654 955270 958674
Changes:
 glibc (2.30-5) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * debian/patches/hurd-i386/git-trunc-times.diff: New patch to fix updating
 mtime/ctime on O_TRUNC.  Closes: #955270.
   * debian/control: Drop dependency on libihash-dev, not used any more by htl.
   * debian/sysdeps/hurd.mk: Try to symlink mach/hurd headers from multiarch
 directory when they are there.
 .
   [ Aurelien Jarno ]
   * debian/rules: Add -fdebug-prefix-map= to CFLAGS to improve
 reproducibility.
   * debian/control.in/libc: Make libcX-dev declare a Breaks against python3.7
 (<< 3.7.7-1+b1) and python3.8 (<< 3.8.2-1+b1) due to #955474.
   * debian/rules.d/debhelper.mk: install the dynamic loader symlink in the
 udeb package.
   * debian/control: conflict

Processed: Bug#941174 marked as pending in glibc

2020-05-04 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #941174 [src:glibc] glibc: FTBFS on hppa - new test failures
Added tag(s) pending.

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



Processed: Bug#910685 marked as pending in glibc

2020-05-04 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #910685 [src:glibc] glibc: please support DPKG_ROOT
Added tag(s) pending.

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



Processed: Bug#958674 marked as pending in glibc

2020-05-04 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #958674 [src:glibc] glibc: refactor generation of multilib include symlinks
Added tag(s) pending.

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



Processed: Bug#953654 marked as pending in glibc

2020-05-03 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #953654 [libc6-dbg] libc6-dbg should be renamed (or at least Provide:) 
libc6-dbgsym
Added tag(s) pending.

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



Processed: glibc: refactor generation of multilib include symlinks

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

> block 798955 by -1
Bug #798955 [src:glibc] Moving glibc headers from /usr/include to 
/usr/include/$(DEB_HOST_MULTIARCH)
798955 was blocked by: 912605 857708 875921 909964 909965 912422 910235 911860 
911574 911556 911491 911489 911359 911455 910055 857535 958479 910097 911394 
909967 909969 910127 910322 909966 911393 911358 911683 910299 911456
798955 was not blocking any bugs.
Added blocking bug(s) of 798955: 958674

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



Processed: qmake passes unsupported -isystem to gcc

2020-04-22 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 + src:deepin-music
Bug #958479 [qt5-qmake] qmake passes unsupported -isystem to gcc
Added indication that 958479 affects src:deepin-music
> block 798955 by -1
Bug #798955 [src:glibc] Moving glibc headers from /usr/include to 
/usr/include/$(DEB_HOST_MULTIARCH)
798955 was blocked by: 911860 911456 875921 909967 911556 909965 909964 911359 
909969 911491 909966 910055 911358 912422 911393 910322 911455 910097 911489 
912605 910235 911394 911683 857535 910299 911574 910127 857708
798955 was not blocking any bugs.
Added blocking bug(s) of 798955: 958479

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



Processed: Patch to add memusage and memusagestat

2020-04-21 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 + patch
Bug #91815 [src:glibc] Build memusage and memusagestat ?
Bug #214257 [src:glibc] Include memusage in distribution
Bug #264039 [src:glibc] libc6-dev: memusage and libmemusage missing
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.

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



Bug#930734: marked as done (glibc: Doesn't honor noudeb build profile)

2020-04-20 Thread Debian Bug Tracking System
Your message dated Mon, 20 Apr 2020 21:20:01 +0200
with message-id <20200420192001.ga409...@aurel32.net>
and subject line Re: Bug#930734: glibc: Doesn't honor noudeb build profile
has caused the Debian Bug report #930734,
regarding glibc: Doesn't honor noudeb build profile
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.)


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

https://wiki.debian.org/BuildProfileSpec documents noudeb specifically to
disable building .udeb packages, but the glibc sources only honor the
(deprecated!) stage1 profile.
The attached patch disables building udebs if stage1 isn't given but noudeb
is (stage1 already disabled them).

Cheers,
Sven
--- debian/rules.orig	2019-06-19 13:59:00.249150884 +0200
+++ debian/rules	2019-06-19 14:00:35.224406795 +0200
@@ -138,7 +138,11 @@
 else
   DEB_ARCH_REGULAR_PACKAGES = $(libc) $(libc)-dev $(libc)-dbg $(libc)-pic libc-bin libc-dev-bin multiarch-support
   DEB_INDEP_REGULAR_PACKAGES = glibc-doc glibc-source libc-l10n locales
-  DEB_UDEB_PACKAGES = $(libc)-udeb
+  ifneq ($(filter noudeb,$(DEB_BUILD_PROFILES)),)
+DEB_UDEB_PACKAGES = 
+  else
+DEB_UDEB_PACKAGES = $(libc)-udeb
+  endif
   ## Locales can only be pre-generated during native compiles
   ifeq ($(DEB_HOST_ARCH),$(DEB_BUILD_ARCH))
 DEB_ARCH_REGULAR_PACKAGES += locales-all
--- End Message ---
--- Begin Message ---
Version: 2.29-0experimental0

On 2019-07-29 23:24, Aurelien Jarno wrote:
> On 2019-06-19 14:51, Sven Mueller wrote:
> > Package: glibc
> > Version: 2.28-10
> > Tags: patch
> > 
> > https://wiki.debian.org/BuildProfileSpec documents noudeb specifically to
> > disable building .udeb packages, but the glibc sources only honor the
> > (deprecated!) stage1 profile.
> 
> Actually it's deprecated for general package, but it's the correct way
> for "early cross-compiler bootstrap phase", which is the case here.
> Anyway stage1 is still actively used by other packages.
> 
> > The attached patch disables building udebs if stage1 isn't given but noudeb
> > is (stage1 already disabled them).
> 
> Thanks applied.

And I forgot to add the bug number, so this bug has been left opened.
Closing it with this bug.

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


Processed: reassign 954230 to procps

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

> reassign 954230 procps
Bug #954230 {Done: Aurelien Jarno } [libc6] libc6: In a 
sticky directory root cannot write to files owned by normal users
Bug reassigned from package 'libc6' to 'procps'.
No longer marked as found in versions glibc/2.30-2.
Ignoring request to alter fixed versions of bug #954230 to the same values 
previously set
> thanks
Stopping processing here.

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



  1   2   3   4   5   6   7   8   9   10   >