[Git][glibc-team/glibc][sid] debian/patches/any/submitted-localedef-check-magic.patch: new patch to display...

2021-12-05 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
7fc9d83d by Aurelien Jarno at 2021-12-05T15:56:44+01:00
debian/patches/any/submitted-localedef-check-magic.patch: new patch to display 
a proper error message for bad locale-archive files.  Closes: #993772.

- - - - -


3 changed files:

- debian/changelog
- + debian/patches/any/submitted-localedef-check-magic.patch
- debian/patches/series


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/7fc9d83d19df69335efe76ad91023f7031929ee9

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/7fc9d83d19df69335efe76ad91023f7031929ee9
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] 3 commits: debian/patches/git-updates.diff: update from upstream stable branch:

2021-12-05 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
8f8c3d79 by Aurelien Jarno at 2021-12-05T11:47:41+01:00
debian/patches/git-updates.diff: update from upstream stable branch:

* debian/patches/git-updates.diff: update from upstream stable branch:
  - Fix bad conversion from ISO-2022-JP-3 with iconv (CVE-2021-43396).
Closes: #998622.

- - - - -
a373aa54 by Aurelien Jarno at 2021-12-05T12:06:42+01:00
debian/control.in/main: rename libselinux-dev build-dependency into 
libselinux1-dev.

- - - - -
68b02da0 by Aurelien Jarno at 2021-12-05T12:06:47+01:00
Regenerate debian/control

- - - - -


4 changed files:

- debian/changelog
- debian/control
- debian/control.in/main
- debian/patches/git-updates.diff


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/f0b32b609c442083a8af7099ca58fbd74b77befe...68b02da080df28178b78f7b6a58d66bea30d9a7c

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/f0b32b609c442083a8af7099ca58fbd74b77befe...68b02da080df28178b78f7b6a58d66bea30d9a7c
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] debian/tzdata.config: do not try to get a value from debconf if it hasn't been...

2021-12-04 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
4d9ff6fc by Aurelien Jarno at 2021-12-05T00:22:15+01:00
debian/tzdata.config: do not try to get a value from debconf if it hasnt 
been seen yet.  Closes: #999465.

- - - - -


2 changed files:

- debian/changelog
- debian/tzdata.config


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/4d9ff6fcce85c018213fe16823cb3e6d0f7679e6

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/4d9ff6fcce85c018213fe16823cb3e6d0f7679e6
You're receiving this email because of your account on salsa.debian.org.




Bug#998438: invalidate caches on package removal

2021-12-04 Thread Aurelien Jarno
control: tag -1 + moreinfo

Hi,

On 2021-11-04 10:19, Harald Dunkel wrote:
> Package: nscd
> Version: 2.31-13+deb11u2
> 
> The nscd.prerm script should cleanup the caches
> 
>   nscd -i {group,hosts,netgroup,passwd,services}
>   rm -f /var/cache/nscd/{group,hosts,netgroup,passwd,services}
> 
> to invalidate and remove all caches, before the service is stopped
> and removed.

What is the reason to remove the cache in the prerm? The cache is
removed in the postrm when the --purge option is used, as specified by
the policy.

> The nscd -i is necessary to tell running processes about the change.
> They might keep these cache files open with a local file descriptor,
> even if they are erased.

The nscd process is stopped before the package is removed (in the
prerm), so it will stop using those cache files when the postinst script
is ran.

> You might want to consider to move /var/cache/nscd to /run.

/run is a tmpfs filesystem backed by RAM, which might be limited, and
thus not designed to hold caches. While on most system the nscd cache is
relatively small, it might get relatively big on some system.

Regards,
Aurelien

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



Bug#998211: libc6: MAXNS should be increased to allow for redundant IPv6 nameservers

2021-12-04 Thread Aurelien Jarno
control: severity -1 minor

On 2021-11-01 05:50, Daniel Gröber wrote:
> Package: libc6
> Version: 2.31-13
> Severity: important
> Tags: ipv6
> X-Debbugs-Cc: d...@darkboxed.org
> 
> Dear Maintainer,
> 
> glibc currently limits the number of nameserver directives in
> resolv.conf to 3. On IPv4/6 dual-stack hosts this can be quite
> limiting. When redundant nameservers are available we can either
> choose to have redundancy on v4 or v6 which is unsatisfying.
> 
> I'm not aware of this problem having been discussed in Debian before,
> but Ubuntu has an open bug[1] for it. There also is a surprisingly
> insightful Stackoverflow post[2] on how one might go about increasing
> MAXNS without an ABI break.

As you pointed out changing MAXNS would cause an ABI break. The proposal
you pointed out looks like a good way to do the change, but it needs to
be done upstream in order to keep a compatible ABI between all
distributions.

In the meantime using a local resolver like unbound is the best
workaround.

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



[Git][glibc-team/glibc][sid] 2 commits: debian/control.in/libc: add a breaks against tinydns (<< 1:1.05-14). Closes: #997912.

2021-12-04 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
7dbed6b2 by Aurelien Jarno at 2021-12-04T22:25:03+01:00
debian/control.in/libc: add a breaks against tinydns ( 1:1.05-14). 
Closes: #997912.

- - - - -
f0b32b60 by Aurelien Jarno at 2021-12-04T22:27:10+01:00
debian/debhelper.in/libc-bin.postinst: stop replacing older versions from 
/etc/nsswitch.conf.  Closes: #998008.

- - - - -


3 changed files:

- debian/changelog
- debian/control.in/libc
- debian/debhelper.in/libc-bin.postinst


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/bcc3e606225b7fb7bd529ab165b49ec4c7f43c3f...f0b32b609c442083a8af7099ca58fbd74b77befe

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/bcc3e606225b7fb7bd529ab165b49ec4c7f43c3f...f0b32b609c442083a8af7099ca58fbd74b77befe
You're receiving this email because of your account on salsa.debian.org.




Re: /usr/bin/ld.so as a symbolic link for the dynamic loader

2021-12-04 Thread Aurelien Jarno
Hi,

On 2021-12-02 19:51, Florian Weimer wrote:
> I'd like to provide an ld.so command as part of glibc.  Today, ld.so can
> be used to activate preloading, for example.  Compared to LD_PRELOAD,
> the difference is that it's specific to one process, and won't be
> inherited by subprocesses—something is that exactly what is needed.
> There is also some useful diagnostic output in --help,
> --list-diagnostics.

This sounds a good idea, I guess for instance that in the future the ldd
feature could be implemented as an option.

However before exposing directly to user, there might be some work need
to improve error reporting. For instance running the dynamic linker
against a static library like ldconfig just causes a segmentation fault
(at least in 2.34, I haven't tried in HEAD). I haven't tried either
binaries from other libc, but we should make sure that an error is
correctly reported if users try that. At least a binary from a different
architecture correctly reports the error.

> Having ld.so as a real command makes the name architecture-agnostic.
> This discourages from hard-coding non-portable paths such as
> /lib64/ld-linux-x86-64.so.2 or even (the non-ABI-compliant)
> /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 in scripts that require
> specific functionality offered by such an explicit loader invocation.

Do you actually have example of usage of the non-ABI-compliant dynamic
loader in Debian? Independently of the current discussion, this should
probably be fixed.

> I thought that commands with file extensions might be Policy violation.
> Policy actually talks about file extensions for programs installed in
> /usr/bin—but only for scripts.  So it's technically okay.  And today,
> there's already an ld.so manual page, although it's in section 8 and 1.
> (I think /usr/bin is still appropriate because running ld.so does not
> require special privileges.)
> 
> The initial implementation will be just a symbolic link.  This means
> that multi-arch support will be missing: the amd64 loader will not be
> able to redirect execution to the s390x loader.  In principle, it should
> be possible to find PT_INTERP with a generic ELF parser and redirect to
> that, but that's vaporware at present.  I don't know yet if it will be
> possible to implement this without some knowledge of Debian's multi-arch
> support in the loader.  Upstream doesn't have those features (we only
> support /usr/lib vs /usr/lib64 and some minor variants of that), so
> integration might be lacking.

A simple symlink would work as a start, however it means creating a
new non-multiarch package. If we want that feature to be available to
all system, we need a way to ensure this package is automatically
installed.

What is the plan about supporting /usr/lib vs /usr/lib64? If upstream go
the wrapper way, there might not be a lot of differences with what is
needed to support multiarch. From what I understand a wrapper would need
to have a basic understanding of the arguments passed to ld.so to find
the binary that needs to be loaded. Looking at PT_INTERP is one way to
go, however we should define what would be the behaviour for non GNU
libc dynamic loader.

> If someone wants to upstream the multi-arch patches, that would be
> great.  glibc now accepts submissions under DCO, so copyright assignment
> should no longer be an obstacle.

I don't think copyright assignment is really the issue there. We have
two patches left that haven't been merged upstream, one from Steve
Langasek and one from me. The problem is more that there is work to add
proper upstream support for multiarch, I guess the idea would be to use
a configure option. On the Debian side multiarch support is basically
done by defining libdir, slibdir and rtlldir in the configparms file,
plus two patches:
- 
https://salsa.debian.org/glibc-team/glibc/-/blob/sid/debian/patches/any/local-ldconfig-multiarch.diff
  This patch basically changes the way ldconfig gets its standard search
  paths. I guess this is something that could be upstream, probably with
  some changes but I haven't recently look at it in details.
- 
https://salsa.debian.org/glibc-team/glibc/-/blob/sid/debian/patches/any/local-ld-multiarch.diff
  This patch does actually two things. The first part makes sure that
  ld.so still looks in the non-multiarch paths. This doesn't look
  upstreamable in the way its done. The second patch just change the way
  the initial '/' is dropped from $(slibdir) so that it works for two
  level paths. This part looks upstreamable.

> Anyway, do you see any problems with providing /usr/bin/ld.so for use by
> skilled end users?

As said above it might require a bit more work to make that possible,
but, but I do not see it as an issue as principle.

Regards,
Aurelien

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



[Git][glibc-team/tzdata] Pushed new tag debian/2021a-0+deb10u3

2021-10-25 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2021a-0+deb10u3 at GNU Libc Maintainers / 
tzdata

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/tree/debian/2021a-0+deb10u3
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][buster] 2 commits: Cherry-pick patches from tzdata-2021d and tzdata-2021e:

2021-10-25 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch buster at GNU Libc Maintainers / tzdata


Commits:
27907569 by Aurelien Jarno at 2021-10-25T19:28:05+02:00
Cherry-pick patches from tzdata-2021d and tzdata-2021e:

* Cherry-pick patches from tzdata-2021d and tzdata-2021e:
  - 04-fiji-dst.patch: Fiji suspends DST for the 2021/2022 season.
  - 05-palestine-dst.patch: Palestine will fall back 2021-10-29 (not
2021-10-30) at 01:00.

- - - - -
1447bccc by Aurelien Jarno at 2021-10-25T19:34:27+02:00
releasing package tzdata version 2021a-0+deb10u3

- - - - -


4 changed files:

- debian/changelog
- + debian/patches/04-fiji-dst.patch
- + debian/patches/05-palestine-dst.patch
- debian/patches/series


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/f71f3b18bd65e8c0a83169ecee771ded57e81512...1447bcccf48c7c8f80e7f4695f0f85f100400dda

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/f71f3b18bd65e8c0a83169ecee771ded57e81512...1447bcccf48c7c8f80e7f4695f0f85f100400dda
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata] Pushed new tag debian/2021a-1+deb11u2

2021-10-25 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2021a-1+deb11u2 at GNU Libc Maintainers / 
tzdata

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/tree/debian/2021a-1+deb11u2
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][bullseye] 2 commits: Cherry-pick patches from tzdata-2021d and tzdata-2021e:

2021-10-25 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch bullseye at GNU Libc Maintainers / tzdata


Commits:
d530c6f1 by Aurelien Jarno at 2021-10-25T19:14:31+02:00
Cherry-pick patches from tzdata-2021d and tzdata-2021e:

* Cherry-pick patches from tzdata-2021d and tzdata-2021e:
  - 04-fiji-dst.patch: Fiji suspends DST for the 2021/2022 season.
  - 05-palestine-dst.patch: Palestine will fall back 2021-10-29 (not
2021-10-30) at 01:00.

- - - - -
02643e88 by Aurelien Jarno at 2021-10-25T19:14:56+02:00
releasing package tzdata version 2021a-1+deb11u2

- - - - -


4 changed files:

- debian/changelog
- + debian/patches/04-fiji-dst.patch
- + debian/patches/05-palestine-dst.patch
- debian/patches/series


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/3a70b475d8eacff2fccafe6dabedab4c3d5778c4...02643e88611f362d614c0e093b9c583c4adaa7a2

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/3a70b475d8eacff2fccafe6dabedab4c3d5778c4...02643e88611f362d614c0e093b9c583c4adaa7a2
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata] Pushed new tag debian/2021e-1

2021-10-25 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2021e-1 at GNU Libc Maintainers / tzdata

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/tree/debian/2021e-1
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] 2 commits: New upstream version:

2021-10-25 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
01c25569 by Aurelien Jarno at 2021-10-25T12:04:21+02:00
New upstream version:

* New upstream version:
  - Palestine will fall back 2021-10-29 (not 2021-10-30) at 01:00.

- - - - -
8d19ce70 by Aurelien Jarno at 2021-10-25T12:04:47+02:00
releasing package tzdata version 2021e-1

- - - - -


1 changed file:

- debian/changelog


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/7d718473902290f1c18b08cae2bb76b7c6b6d427...8d19ce70e05aeb7ac20c295b743a15514b627dca

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/7d718473902290f1c18b08cae2bb76b7c6b6d427...8d19ce70e05aeb7ac20c295b743a15514b627dca
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] 4 commits: New upstream version:

2021-10-17 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
ddbc027a by Aurelien Jarno at 2021-10-17T23:22:12+02:00
New upstream version:

* New upstream version:
  - Fiji suspends DST for the 2021/2022 season.

- - - - -
bf421a35 by Aurelien Jarno at 2021-10-17T23:27:48+02:00
Update Polish debconf translation.

- - - - -
59587df3 by Aurelien Jarno at 2021-10-17T23:32:12+02:00
Update English debconf translation.

- - - - -
7d718473 by Aurelien Jarno at 2021-10-17T23:52:15+02:00
releasing package tzdata version 2021d-1

- - - - -


3 changed files:

- debian/changelog
- debian/po/en.po
- debian/po/pl.po


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/7ca3658065b3acb5570f8e54c4c631d3f602b210...7d718473902290f1c18b08cae2bb76b7c6b6d427

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/7ca3658065b3acb5570f8e54c4c631d3f602b210...7d718473902290f1c18b08cae2bb76b7c6b6d427
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata] Pushed new tag debian/2021d-1

2021-10-17 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2021d-1 at GNU Libc Maintainers / tzdata

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/tree/debian/2021d-1
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][glibc-2.33] 2 commits: debian/debhelper.in/libc-dev{,-alt}.install, debian/rules.d/build.mk: install...

2021-10-16 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch glibc-2.33 at GNU Libc Maintainers / glibc


Commits:
b0c2c958 by Aurelien Jarno at 2021-10-16T20:33:57+02:00
debian/debhelper.in/libc-dev{,-alt}.install, debian/rules.d/build.mk: install 
an empty libpthread_nonshared.a to support broken closed source software. 
Closes: #971273.

- - - - -
a120b72a by Aurelien Jarno at 2021-10-16T20:34:21+02:00
debian/sysdeps/arm64.mk: enable Memory Tagging Extension (MTE) (heap) checking 
on arm64.  Closes: #995269.

- - - - -


5 changed files:

- debian/changelog
- debian/debhelper.in/libc-dev-alt.install
- debian/debhelper.in/libc-dev.install
- debian/rules.d/build.mk
- debian/sysdeps/arm64.mk


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/7b1c24336b30a090f96e5e235dd225ba4b8a...a120b72a15a6698fd05a72c17db24823602281a7

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/7b1c24336b30a090f96e5e235dd225ba4b8a...a120b72a15a6698fd05a72c17db24823602281a7
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] releasing package tzdata version 2021c-3

2021-10-15 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
7ca36580 by Aurelien Jarno at 2021-10-15T22:01:10+02:00
releasing package tzdata version 2021c-3

- - - - -


1 changed file:

- debian/changelog


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/7ca3658065b3acb5570f8e54c4c631d3f602b210

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/7ca3658065b3acb5570f8e54c4c631d3f602b210
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] Update French debconf translation. Closes: #996163.

2021-10-15 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
dcc6e72f by Aurelien Jarno at 2021-10-15T22:00:23+02:00
Update French debconf translation.  Closes: #996163.

- - - - -


2 changed files:

- debian/changelog
- debian/po/fr.po


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/dcc6e72f25b041cc85a9e50ef18113b37f0b7799

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/dcc6e72f25b041cc85a9e50ef18113b37f0b7799
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] 3 commits: Update Portuguese debconf translation. Closes: #996264.

2021-10-13 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
55d98f9c by Aurelien Jarno at 2021-10-13T23:02:04+02:00
Update Portuguese debconf translation.  Closes: #996264.

- - - - -
4f1ef6a9 by Aurelien Jarno at 2021-10-13T23:07:34+02:00
Replace underscore by space in the following debconf translations: be, fr, gu, 
hr, hu, id, ku, lt, ml, pt, pt_BR, sk, sq, vi, wo.

- - - - -
73d1647b by Aurelien Jarno at 2021-10-13T23:11:17+02:00
Update Japanese debconf translation.

- - - - -


15 changed files:

- debian/changelog
- debian/po/be.po
- debian/po/fr.po
- debian/po/gu.po
- debian/po/hr.po
- debian/po/hu.po
- debian/po/id.po
- debian/po/ja.po
- debian/po/ku.po
- debian/po/lt.po
- debian/po/ml.po
- debian/po/pt.po
- debian/po/pt_BR.po
- debian/po/sk.po
- debian/po/sq.po


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/1e13a8e989735d4defb5b3698706ddb6af533861...73d1647bc6b736e279c5338d3ba9eeedaf267347

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/1e13a8e989735d4defb5b3698706ddb6af533861...73d1647bc6b736e279c5338d3ba9eeedaf267347
You're receiving this email because of your account on salsa.debian.org.




Bug#996163: tzdata: [INTL:fr] French templates translation

2021-10-13 Thread Aurelien Jarno
Hi,

On 2021-10-11 18:32, Jean-Pierre Giraud wrote:
> Package: tzdata
> Severity: wishlist
> Tags: patch l10n
> 
> Hi!
> 
> Please find attached the updated french templates translation, proofread
> by the debian-l10n-french mailing list contributors.
> 
> This file should be put as debian/po/fr.po in your package build tree.

Thanks for the translation, however it seems you forgot to attach the
file.

Regards,
Aurelien

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



[Git][glibc-team/tzdata][sid] 4 commits: Update Swedish debconf translation. Closes: #995697.

2021-10-09 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
984d458c by Aurelien Jarno at 2021-10-09T20:09:35+02:00
Update Swedish debconf translation.  Closes: #995697.

- - - - -
05d0c5ac by Aurelien Jarno at 2021-10-09T20:16:33+02:00
Add Korean debconf translation.  Closes: #995701.

- - - - -
03601535 by Aurelien Jarno at 2021-10-09T20:16:34+02:00
Update Dutch debconf translation.  Closes: #995998.

- - - - -
1e13a8e9 by Aurelien Jarno at 2021-10-09T20:16:34+02:00
Update Catalan debconf translation.

- - - - -


5 changed files:

- debian/changelog
- debian/po/ca.po
- + debian/po/ko.po
- debian/po/nl.po
- debian/po/sv.po


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/862b4b23e3f54d376a75c0a14fb26c1e1e5899a2...1e13a8e989735d4defb5b3698706ddb6af533861

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/862b4b23e3f54d376a75c0a14fb26c1e1e5899a2...1e13a8e989735d4defb5b3698706ddb6af533861
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata] Pushed new tag debian/2021c-2

2021-10-07 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2021c-2 at GNU Libc Maintainers / tzdata

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/tree/debian/2021c-2
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] releasing package tzdata version 2021c-2

2021-10-07 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
862b4b23 by Aurelien Jarno at 2021-10-07T23:25:19+02:00
releasing package tzdata version 2021c-2

- - - - -


1 changed file:

- debian/changelog


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/862b4b23e3f54d376a75c0a14fb26c1e1e5899a2

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/862b4b23e3f54d376a75c0a14fb26c1e1e5899a2
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] 3 commits: Update Galician debconf translation.

2021-10-07 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
c6d491df by Aurelien Jarno at 2021-10-07T23:22:49+02:00
Update Galician debconf translation.

- - - - -
816e2fe1 by Aurelien Jarno at 2021-10-07T23:24:14+02:00
Update Czech debconf translation.

- - - - -
b903c521 by Aurelien Jarno at 2021-10-07T23:24:57+02:00
Update Turkish debconf translation.

- - - - -


4 changed files:

- debian/changelog
- debian/po/cs.po
- debian/po/gl.po
- debian/po/tr.po


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/f75e42889c347722e8eb9f695779163f925d0713...b903c5210bbb69f8e2fd0d528e749023767408d1

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/f75e42889c347722e8eb9f695779163f925d0713...b903c5210bbb69f8e2fd0d528e749023767408d1
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] Update Polish debconf translation.

2021-10-03 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
f75e4288 by Aurelien Jarno at 2021-10-03T15:12:16+02:00
Update Polish debconf translation.

- - - - -


2 changed files:

- debian/changelog
- debian/po/pl.po


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/f75e42889c347722e8eb9f695779163f925d0713

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/f75e42889c347722e8eb9f695779163f925d0713
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] Update Spanish debconf translation.

2021-10-02 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
157da21d by Aurelien Jarno at 2021-10-02T22:23:28+02:00
Update Spanish debconf translation.

- - - - -


2 changed files:

- debian/changelog
- debian/po/es.po


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/157da21d3ddbad35df5d1887621b82bffdb19037

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/157da21d3ddbad35df5d1887621b82bffdb19037
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] Update German debconf translation.

2021-10-02 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
31947379 by Aurelien Jarno at 2021-10-02T21:17:26+02:00
Update German debconf translation.

- - - - -


2 changed files:

- debian/changelog
- debian/po/de.po


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/31947379259b7244a8fccc822d88848d5468cbcc

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/31947379259b7244a8fccc822d88848d5468cbcc
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata] Pushed new tag debian/2021c-1

2021-10-02 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2021c-1 at GNU Libc Maintainers / tzdata

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/tree/debian/2021c-1
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] 5 commits: New upstream version.

2021-10-02 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
45754420 by Aurelien Jarno at 2021-10-02T18:23:23+02:00
New upstream version.

* New upstream version.
  - Drop 01-fix-jan-mayen-typo.patch.

- - - - -
2539a9b3 by Aurelien Jarno at 2021-10-02T18:34:12+02:00
Remove whitespaces

- - - - -
e65388a3 by Aurelien Jarno at 2021-10-02T18:34:16+02:00
Bump debhelper compatibility to 13.

- - - - -
0be8db84 by Aurelien Jarno at 2021-10-02T18:53:43+02:00
Bump Standards-Version to 4.6.0 (no changes).

- - - - -
2e6fb55e by Aurelien Jarno at 2021-10-02T19:00:27+02:00
releasing package tzdata version 2021c-1

- - - - -


4 changed files:

- debian/changelog
- debian/control
- − debian/patches/01-fix-jan-mayen-typo.patch
- − debian/patches/series


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/bcf7f21feca7c6314dd71c08367cb9a6c5e249be...2e6fb55ea65eddf6b00257cf5fb9b6fc5585a126

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/bcf7f21feca7c6314dd71c08367cb9a6c5e249be...2e6fb55ea65eddf6b00257cf5fb9b6fc5585a126
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc] Pushed new tag debian/2.31-13+deb11u2

2021-10-02 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2.31-13+deb11u2 at GNU Libc Maintainers / 
glibc

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.31-13+deb11u2
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][bullseye] releasing package glibc version 2.31-13+deb11u2

2021-10-02 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch bullseye at GNU Libc Maintainers / glibc


Commits:
84cc9bf9 by Aurelien Jarno at 2021-10-02T14:47:44+02:00
releasing package glibc version 2.31-13+deb11u2

- - - - -


1 changed file:

- debian/changelog


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/84cc9bf9b07281d80d7d1fbd3ed160475ecb6eab

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/84cc9bf9b07281d80d7d1fbd3ed160475ecb6eab
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][bullseye] debian/debhelper.in/libc.preinst: do not try to detect if debconf is available...

2021-10-02 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch bullseye at GNU Libc Maintainers / glibc


Commits:
98a49e5d by Aurelien Jarno at 2021-10-02T14:47:25+02:00
debian/debhelper.in/libc.preinst: do not try to detect if debconf is available 
when the debconf frontend has already been loaded.

- - - - -


2 changed files:

- debian/changelog
- debian/debhelper.in/libc.preinst


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/98a49e5dd80196fa284df418539a48264b9a02f3

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/98a49e5dd80196fa284df418539a48264b9a02f3
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc] Pushed new tag debian/2.31-13+deb11u1

2021-09-30 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2.31-13+deb11u1 at GNU Libc Maintainers / 
glibc

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.31-13+deb11u1
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][bullseye] releasing package glibc version 2.31-13+deb11u1

2021-09-30 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch bullseye at GNU Libc Maintainers / glibc


Commits:
2d44506b by Aurelien Jarno at 2021-09-30T22:48:07+02:00
releasing package glibc version 2.31-13+deb11u1

- - - - -


1 changed file:

- debian/changelog


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/2d44506bab3e9c0e5fe0bbad47c0d6e1be533684

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/2d44506bab3e9c0e5fe0bbad47c0d6e1be533684
You're receiving this email because of your account on salsa.debian.org.




Re: libcrypt1: symlink points to libpthread

2021-09-30 Thread Aurelien Jarno
On 2021-09-30 15:46, shichimohedron wrote:
> >Can you please try to call /usr/sbin/ldconfig.old to check if the wrong
> link is recreated? That's needed to confirm if ldconfig is the culprit
> here.
> >Can you confirm it's libpthread.so.1 and not libpthread.so.0? If so can
> you please tell how did you install that file?
> 
> Here is a shell log, literally
> 
> ~# ls -l /lib/x86_64-linux-gnu/ | grep libcrypt
> -rw-r--r--  1 root root266262 Apr 18 20:46 libcrypt.a
> lrwxrwxrwx  1 root root35 Apr 18 20:46 libcrypt.so -> 
> /lib/x86_64-linux-gnu/libcrypt.so.1
> lrwxrwxrwx  1 root root17 Apr 18 20:46 libcrypt.so.1 -> 
> libcrypt.so.1.1.0
> -rw-r--r--  1 root root202680 Apr 18 20:46 libcrypt.so.1.1.0
> ~# /usr/sbin/ldconfig.old
> ~# ls -l /lib/x86_64-linux-gnu/ | grep libcrypt
> -rw-r--r--  1 root root266262 Apr 18 20:46 libcrypt.a
> lrwxrwxrwx  1 root root35 Apr 18 20:46 libcrypt.so -> 
> /lib/x86_64-linux-gnu/libcrypt.so.1
> lrwxrwxrwx  1 root root15 Sep 30 07:53 libcrypt.so.1 -> 
> libpthread.so.1
> -rw-r--r--  1 root root202680 Apr 18 20:46 libcrypt.so.1.1.0

Thanks for this log, it confirms that the wrong link is created by
ldconfig.
 
> I struggle to reveal the origins of libpthread.so.1. It can easily be a 
> result of unqualified experimentation, but not necessarily. Of course, if 
> this is the case its presence in the system is completely my fault and not in 
> any sense yours. Anyway, dpkg -S doesn't match it with any of packages 
> currently installed, and another attempts to guess where the library comes 
> from didn't lead to any answer.

It could be that this libpthread.so.1 file is actually a copy of an old
libcrypt.so.1. It's something you can check with:

readelf --dynamic /lib/x86_64-linux-gnu/libpthread.so.1 | grep SONAME

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



Re: libcrypt1: symlink points to libpthread

2021-09-30 Thread Aurelien Jarno
On 2021-09-29 10:33, Flying Sea Buckthorn wrote:
> Package: libcrypt1
> Version: 1:4.4.18-4
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: shichimohed...@protonmail.com
> 
> Dear Maintainer,
> 
> Recently I have upgraded from Buster to Bullseye and, among other things, 
> have installed libcrypt1 package.
> Curiuosly enough, I found out that the symlink that should have been pointing 
> to crypto library (/lib/x86_64-linux-gnu/libcrypto.so.1 -> 
> libcrypto.so.1.1.0) pointed to libpthread.so.1 instead since upgrade.

Can you confirm it's libpthread.so.1 and not libpthread.so.0? If so can
you please tell how did you install that file?

Thanks,
Aurelien

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



Re: Bug#995308: libcrypt1: symlink points to libpthread

2021-09-30 Thread Aurelien Jarno
On 2021-09-30 02:45, Marco d'Itri wrote:
> Maybe then the glibc people know what could make ldconfig create a link 
> to the wrong library.

I don't see how that could happen. ldconfig uses the SONAME entry to
create the links. First we have to get confirmed that ldconfig is the
culprit.

> On Sep 30, shichimohedron  wrote:
> 
> > >Does it still happen after something like this?
> > 
> > > mv /usr/sbin/ldconfig /usr/sbin/ldconfig.old
> > > cp -a /bin/true /usr/sbin/ldconfig
> > > dpkg -i .../libcrypt1_*.deb
> > 
> > I tried this out, and it worked: the effect disappeared completely, 
> > reinstallation binds the links to proper files. Thank you and sorry for 
> > bothering!
> 
> -- 
> ciao,
> Marco



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


signature.asc
Description: PGP signature


Bug#995323: libc6: 2.33-0experimental2 breaks maxima

2021-09-29 Thread Aurelien Jarno
control: reassign -1 gcl
control: affects -1 libc6
control: retitle -1 gcl: fails to start with glibc 2.33
control: forwarded -1 https://savannah.gnu.org/bugs/index.php?60161
control: patch -1 + upstream
control: patch -1 + patch

Hi,

On 2021-09-29 10:51, Andreas Kloeckner wrote:
> Package: libc6
> Version: 2.33-0experimental2
> Severity: normal
> 
> Dear Maintainer,
> 
> Upgrading libc6 to 2.33-0experimental2  causes maxima to fail at startup
> with the message:
> 
> The assertion realpath(s,o) on line 475 of main.c in function mbin failed: 
> Invalid argument[1]468085 abort (core dumped)  maxima
> 
> To reproduce, simply 'apt install maxima' (version 5.44.0-3) and run
> 'maxima'.
> 

Thanks for testing glibc 2.33. This is actually a bug in gcl, triggered
by a change in glibc 2.33. It has already been reported upstream with a
patch:

https://savannah.gnu.org/bugs/index.php?60161

Regards,
Aurelien

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



[Git][glibc-team/tzdata] Pushed new tag debian/2021b-1

2021-09-28 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2021b-1 at GNU Libc Maintainers / tzdata

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/tree/debian/2021b-1
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] 6 commits: New upstream version.

2021-09-28 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
bfd0b5c2 by Aurelien Jarno at 2021-09-28T23:55:38+02:00
New upstream version.

* New upstream version.
  - Drop 01-no-leap-second-2021-12-31.patch.
  - Drop 02-samoa-dst.patch.
  - Drop 03-jordan-dst.patch.

- - - - -
314958e5 by Aurelien Jarno at 2021-09-28T23:55:39+02:00
Cherry pick patch from upstream:

* Cherry pick patch from upstream:
  - 01-fix-jan-mayen-typo.patch: fix for Atlantic/Jan_Mayen from upstream..

- - - - -
19c88995 by Aurelien Jarno at 2021-09-29T00:29:12+02:00
Update debian/upstream/signing-key.asc.

- - - - -
3cf9c985 by Aurelien Jarno at 2021-09-29T00:38:54+02:00
Handle Pacific/Enderbury to Pacific/Kanton renaming:

* Handle Pacific/Enderbury to Pacific/Kanton renaming:
  - Add an entry to tzdata.config
  - Do not translate Pacific/Enderbury.
  - Update debconf templates and translations.

- - - - -
4b0b8678 by Aurelien Jarno at 2021-09-29T01:02:42+02:00
Set urgency to low as this new upstream version merged many pre-1970 timezones, 
and this needs more testing.

- - - - -
bcf7f21f by Aurelien Jarno at 2021-09-29T01:02:57+02:00
releasing package tzdata version 2021b-1

- - - - -


30 changed files:

- debian/changelog
- + debian/patches/01-fix-jan-mayen-typo.patch
- − debian/patches/01-no-leap-second-2021-12-31.patch
- − debian/patches/02-samoa-dst.patch
- − debian/patches/03-jordan-dst.patch
- debian/patches/series
- debian/po/be.po
- debian/po/bg.po
- debian/po/ca.po
- debian/po/cs.po
- debian/po/da.po
- debian/po/de.po
- debian/po/en.po
- debian/po/es.po
- debian/po/eu.po
- debian/po/fi.po
- debian/po/fr.po
- debian/po/gl.po
- debian/po/gu.po
- debian/po/he.po
- debian/po/hr.po
- debian/po/hu.po
- debian/po/id.po
- debian/po/it.po
- debian/po/ja.po
- debian/po/ku.po
- debian/po/lt.po
- debian/po/ml.po
- debian/po/nl.po
- debian/po/pl.po


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/7f97d77c858ebc0e447aba251ece4e9370f2ac10...bcf7f21feca7c6314dd71c08367cb9a6c5e249be

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/7f97d77c858ebc0e447aba251ece4e9370f2ac10...bcf7f21feca7c6314dd71c08367cb9a6c5e249be
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] Fix a typo

2021-09-28 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
7f97d77c by Aurelien Jarno at 2021-09-28T22:57:22+02:00
Fix a typo

- - - - -


1 changed file:

- debian/changelog


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/7f97d77c858ebc0e447aba251ece4e9370f2ac10

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/commit/7f97d77c858ebc0e447aba251ece4e9370f2ac10
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata] Pushed new tag debian/2021a-0+deb10u2

2021-09-27 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2021a-0+deb10u2 at GNU Libc Maintainers / 
tzdata

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/tree/debian/2021a-0+deb10u2
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][buster] 2 commits: Cherry-pick patches from tzdata-2021b until the upstream situation gets less confused:

2021-09-27 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch buster at GNU Libc Maintainers / tzdata


Commits:
d714d4c0 by Aurelien Jarno at 2021-09-27T18:53:03+02:00
Cherry-pick patches from tzdata-2021b until the upstream situation gets less 
confused:

* Cherry-pick patches from tzdata-2021b until the upstream situation gets
  less confused:
  - 01-no-leap-second-2021-12-31.patch: No leap second on 2021-12-31 as per
IERS Bulletin C 62.
  - 02-samoa-dst.patch: Samoa no longer observes DST.
  - 03-jordan-dst.patch: Jordan now starts DST on Februarys last Thursday.

- - - - -
f71f3b18 by Aurelien Jarno at 2021-09-27T18:53:33+02:00
releasing package tzdata version 2021a-0+deb10u2

- - - - -


5 changed files:

- debian/changelog
- + debian/patches/01-no-leap-second-2021-12-31.patch
- + debian/patches/02-samoa-dst.patch
- + debian/patches/03-jordan-dst.patch
- debian/patches/series


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/11c0f1557ad5d4fb91cf873032182ec2919062a2...f71f3b18bd65e8c0a83169ecee771ded57e81512

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/11c0f1557ad5d4fb91cf873032182ec2919062a2...f71f3b18bd65e8c0a83169ecee771ded57e81512
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata] Pushed new tag debian/2021a-1+deb11u1

2021-09-27 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2021a-1+deb11u1 at GNU Libc Maintainers / 
tzdata

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/tree/debian/2021a-1+deb11u1
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][bullseye] 2 commits: Cherry-pick patches from tzdata-2021b until the upstream situation gets less confused:

2021-09-27 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch bullseye at GNU Libc Maintainers / tzdata


Commits:
f9914379 by Aurelien Jarno at 2021-09-27T18:27:06+02:00
Cherry-pick patches from tzdata-2021b until the upstream situation gets less 
confused:

* Cherry-pick patches from tzdata-2021b until the upstream situation gets
  less confused:
  - 01-no-leap-second-2021-12-31.patch: No leap second on 2021-12-31 as per
IERS Bulletin C 62.
  - 02-samoa-dst.patch: Samoa no longer observes DST.
  - 03-jordan-dst.patch: Jordan now starts DST on Februarys last Thursday.

- - - - -
3a70b475 by Aurelien Jarno at 2021-09-27T18:27:22+02:00
releasing package tzdata version 2021a-1+deb11u1

- - - - -


5 changed files:

- debian/changelog
- + debian/patches/01-no-leap-second-2021-12-31.patch
- + debian/patches/02-samoa-dst.patch
- + debian/patches/03-jordan-dst.patch
- + debian/patches/series


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/e0ffe297688d15298f5f272afc60d5aa9c7476a5...3a70b475d8eacff2fccafe6dabedab4c3d5778c4

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/e0ffe297688d15298f5f272afc60d5aa9c7476a5...3a70b475d8eacff2fccafe6dabedab4c3d5778c4
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata] Pushed new tag debian/2021a-2

2021-09-27 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2021a-2 at GNU Libc Maintainers / tzdata

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/tree/debian/2021a-2
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/tzdata][sid] 2 commits: Cherry-pick patches from tadata-2021b until the upstream situation gets less confused:

2021-09-27 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / tzdata


Commits:
24956baf by Aurelien Jarno at 2021-09-27T18:19:56+02:00
Cherry-pick patches from tadata-2021b until the upstream situation gets less 
confused:

* Cherry-pick patches from tadata-2021b until the upstream situation gets
  less confused:
  - 01-no-leap-second-2021-12-31.patch: No leap second on 2021-12-31 as per
IERS Bulletin C 62.
  - 02-samoa-dst.patch: Samoa no longer observes DST.
  - 03-jordan-dst.patch: Jordan now starts DST on Februarys last Thursday.

- - - - -
2ade6fb8 by Aurelien Jarno at 2021-09-27T18:21:05+02:00
releasing package tzdata version 2021a-2

- - - - -


5 changed files:

- debian/changelog
- + debian/patches/01-no-leap-second-2021-12-31.patch
- + debian/patches/02-samoa-dst.patch
- + debian/patches/03-jordan-dst.patch
- + debian/patches/series


View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/12b4cc8aebff8b5fa9a56d20f2ea54901310b57e...2ade6fb8221af1497eb906f736999efe8c742a90

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/tzdata/-/compare/12b4cc8aebff8b5fa9a56d20f2ea54901310b57e...2ade6fb8221af1497eb906f736999efe8c742a90
You're receiving this email because of your account on salsa.debian.org.




Bug#987266: preinst check for kernel release > 255 may no longer be needed

2021-09-26 Thread Aurelien Jarno
Hi,

On 2021-09-26 09:57, Salvatore Bonaccorso wrote:
> Hi Aurelien,
> 
> On Tue, Apr 20, 2021 at 06:36:33PM +0200, Andras Korn wrote:
> > Package: libc6
> > Version: 2.31-11
> > Severity: normal
> > 
> > Hi,
> > 
> > due to
> > https://salsa.debian.org/glibc-team/glibc/-/commit/6ddfa57577af0d96df9ddd7be401f5ce9a9bcc0f
> > (a commit from 2004) the preinst script for glibc checks whether the
> > "z" in the "x.y.z" of the kernel version is less than 255. If yes,
> > the package refuses to install.
> > 
> > I hit this problem on a box with a custom 4.9.266 kernel.
> > 
> > Based on this lkml thread:
> > https://lore.kernel.org/lkml/7pR0YCctzN9phpuEChlL7_SS6auHOM80bZBcGBTZPuMkc6XjKw7HUXf9vZUPi-IaV2gTtsRVXgywQbja8xpzjGRDGWJsVYSGQN5sNuX1yaQ=@protonmail.com/T/,
> > the check is no longer needed because the kernel caps the version
> > code it reports to 255, even if uname prints a higher number.
> > 
> > Of course, you could conceivably still hit the problem with earlier
> > kernels, so I suppose the logic of the check should be modified, not
> > removed entirely, to be technically correct.
> > 
> > If forced at gunpoint to make a guess, I would guess, though, that
> > removing the check would have very little actual impact; it also
> > doesn't protect the user from installing a kernel with an
> > unsupported version number after having installed glibc.
> 
> Prompted by
> https://lore.kernel.org/stable/yvaholtsb0nk0...@kroah.com/T/#t and
> given this was addressed with
> https://salsa.debian.org/glibc-team/glibc/-/commit/b3c76cf1cd0c8b6e4844c6362a45143c136a2900
> is this something we should do consider as well for the older releases
> where it is not acutally needed for people compiling their own custom
> kernels?

The bug has been reported with severity normal, and it seemed it was
limited to a rather small range of users. Now if you thing it is a more
widespread issue, feel free to raise the severity so that we can
consider it from buster and bullseye. The fix has been in testing/sid
for a few weeks, so this should be acceptable for older releases.

At least for bullseye, we have an update scheduled, currently being
under review by the release team (bug #992693). But we won't be able to
fix Raspbian ;-).

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



[Git][glibc-team/glibc] Pushed new tag debian/2.33-0experimental2

2021-09-22 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2.33-0experimental2 at GNU Libc 
Maintainers / glibc

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.33-0experimental2
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][glibc-2.33] 8 commits: Nitpick: format the messages consistently

2021-09-22 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch glibc-2.33 at GNU Libc Maintainers / glibc


Commits:
5b123cf4 by Aurelien Jarno at 2021-09-15T08:03:07+02:00
Nitpick: format the messages consistently

- - - - -
a86df9fe by Aurelien Jarno at 2021-09-16T22:35:49+02:00
debian/debhelper.in/libc.preinst: make sure USE_DEBCONF cant be defined 
from the environment.

- - - - -
04cd3259 by Aurelien Jarno at 2021-09-19T18:53:16+02:00
debian/patches/git-updates.diff: update from upstream stable branch:

* debian/patches/git-updates.diff: update from upstream stable branch:
  - debian/patches/any/submitted-getcwd-gnu-extension-warning.diff:
upstreamed.

- - - - -
e0c3bee9 by Aurelien Jarno at 2021-09-19T18:55:23+02:00
debian/control.in/libc: remove the Breaks against dazzdb, it will be fixed in 
Buster.

- - - - -
c5deb4ee by Aurelien Jarno at 2021-09-19T20:46:22+02:00
debian/patches/i386/local-setcontext-revert-eax-ecx-edx.patch: revert upstream 
commit to not save and restore EAX, ECX and EDX in setcontext to temporarily 
workaround a bug in libunwind8. See bug#994510.

- - - - -
bcc3e606 by Aurelien Jarno at 2021-09-19T20:47:08+02:00
releasing package glibc version 2.32-4

- - - - -
28660c7a by Aurelien Jarno at 2021-09-22T06:56:22+02:00
Merge branch sid into glibc-2.33

- - - - -
b617ae89 by Aurelien Jarno at 2021-09-22T22:10:01+02:00
releasing package glibc version 2.33-0experimental2

- - - - -


8 changed files:

- debian/changelog
- debian/control
- debian/control.in/libc
- debian/debhelper.in/libc.preinst
- − debian/patches/any/submitted-getcwd-gnu-extension-warning.diff
- debian/patches/git-updates.diff
- + debian/patches/i386/local-setcontext-revert-eax-ecx-edx.patch
- debian/patches/series


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/d78434d292f1be3b80dd555d5491266e70fcd420...b617ae89476cbc028be40fea25d3985fdae9f276

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/d78434d292f1be3b80dd555d5491266e70fcd420...b617ae89476cbc028be40fea25d3985fdae9f276
You're receiving this email because of your account on salsa.debian.org.




Bug#994042: libc6: debconf text fallback failed to accept input, had to be killed leading to broken dist-upgrade

2021-09-21 Thread Aurelien Jarno
control: severity -1 serious

On 2021-09-10 16:02, Neil Williams wrote:
> Package: libc6
> Version: 2.31-13
> Severity: normal
> X-Debbugs-Cc: codeh...@debian.org
> 
> This is related to #984533 - in my case, there was no effect on the initramfs.
> 
> I am attaching the section of the apt log. (gzipped)
> I am also attaching the dpkg -l output for the package list (after upgrade).
> 
> The apt log includes the details of the --purge autoremove operation I 
> completed
> after a reboot, so those packages were also installed on buster too.
> 
> This was an upgrade from buster to bullseye.
> apt upgrade worked fine (first part of the log).
> 
> When dist-upgrade started, I got:

[snip]

> No matter what I typed to the Do you want to upgrade prompt, the process did 
> not continue.
> I needed to open a terminal tab, find the preinst process & kill it.

Not being able to perform the upgrade without having to kill the preinst
process from another tab (and having the skills do so) looks a serious
issue to me. I am therefore upgrading the severity.

Regards,
Aurelien

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



Bug#994042: libc6: debconf text fallback failed to accept input, had to be killed leading to broken dist-upgrade

2021-09-21 Thread Aurelien Jarno
Hi,

On 2021-09-15 21:54, Colin Watson wrote:
> On Fri, Sep 10, 2021 at 09:59:44PM +0200, Aurelien Jarno wrote:
> > On 2021-09-10 20:39, Colin Watson wrote:
> > > On Fri, Sep 10, 2021 at 09:03:32PM +0200, Aurelien Jarno wrote:
> > > > I gave a try with debconf-show instead. I have attached a totally
> > > > untested patch to check that we agree on the way to do it.
> > > 
> > > I think you forgot to attach the patch?
> > 
> > Dooh. Please find a new version attached.
> 
> The general idea of this looks good to me.  I've left some detailed
> review comments below, and IMO we should test it against my reproducer
> (especially since this preinst patch needs to end up in bullseye).

Thanks for the fixes.

> > > I managed to reproduce the reported bug by taking Neil's full package
> > > list, mangling it to roughly make sense on buster, installing all of
> > > that, and then doing "apt upgrade && apt full-upgrade" (my own habit is
> > > just to do "apt full-upgrade", but in this case the initial "apt
> > > upgrade" is crucial).  I'm now trying to more or less bisect the package
> > > list to find something rather more minimal; this is a slow process, but
> > > no roadblocks so far, and I'll let you know when I have something.
> > 
> > Thanks a lot for your help.
> 
> OK, it took much longer than I expected because I wasn't able to do it
> by just bisecting the package list, but here's a reproducer.  I ran this
> in a fresh container produced by "lxc launch images:debian/buster"; I
> expect other container tools can be made to exhibit this too, though it
> may be sensitive to exactly which packages are in the base image.
> 
>   # apt update && apt -y install gimp libc6-dev postgresql whiptail
>   # cat >/etc/apt/sources.list <   deb http://deb.debian.org/debian bullseye main
>   deb http://security.debian.org/debian-security bullseye-security main
>   # apt update && apt -y upgrade && apt -y dist-upgrade

Thanks for the reproducer. I have been able to use it to test the fixes,
both with upgrade + dist-upgrade to check that the problem is fixed, and
with dist-upgrade only to check that things still work when debconf is
usable.

Regards,
Aurelien

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



[Git][glibc-team/glibc][bullseye] debian/debhelper.in/libc.preinst: fix text fallback when debconf is unusable,...

2021-09-21 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch bullseye at GNU Libc Maintainers / glibc


Commits:
23d6ff1d by Aurelien Jarno at 2021-09-21T22:53:45+02:00
debian/debhelper.in/libc.preinst: fix text fallback when debconf is unusable, 
the current debconf configuration should be queried without first sourcing the 
confmodule to avoid losing control of the tty. Big thanks to Colin Watson for 
the help diagnosing the issue and for providing an easy reproducer.  Closes: 
#994042.

- - - - -


2 changed files:

- debian/changelog
- debian/debhelper.in/libc.preinst


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/23d6ff1d458c1e33324e03c3b2011c8fa899a220

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/23d6ff1d458c1e33324e03c3b2011c8fa899a220
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc] Pushed new tag debian/2.32-4

2021-09-19 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2.32-4 at GNU Libc Maintainers / glibc

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.32-4
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] 2 commits: debian/patches/i386/local-setcontext-revert-eax-ecx-edx.patch: revert upstream...

2021-09-19 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
c5deb4ee by Aurelien Jarno at 2021-09-19T20:46:22+02:00
debian/patches/i386/local-setcontext-revert-eax-ecx-edx.patch: revert upstream 
commit to not save and restore EAX, ECX and EDX in setcontext to temporarily 
workaround a bug in libunwind8. See bug#994510.

- - - - -
bcc3e606 by Aurelien Jarno at 2021-09-19T20:47:08+02:00
releasing package glibc version 2.32-4

- - - - -


3 changed files:

- debian/changelog
- + debian/patches/i386/local-setcontext-revert-eax-ecx-edx.patch
- debian/patches/series


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/e0c3bee959444e824bfc513fe0933d0a4ee0f97a...bcc3e606225b7fb7bd529ab165b49ec4c7f43c3f

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/e0c3bee959444e824bfc513fe0933d0a4ee0f97a...bcc3e606225b7fb7bd529ab165b49ec4c7f43c3f
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] debian/control.in/libc: remove the Breaks against dazzdb, it will be fixed in Buster.

2021-09-19 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
e0c3bee9 by Aurelien Jarno at 2021-09-19T18:55:23+02:00
debian/control.in/libc: remove the Breaks against dazzdb, it will be fixed in 
Buster.

- - - - -


3 changed files:

- debian/changelog
- debian/control
- debian/control.in/libc


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/e0c3bee959444e824bfc513fe0933d0a4ee0f97a

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/e0c3bee959444e824bfc513fe0933d0a4ee0f97a
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] debian/patches/git-updates.diff: update from upstream stable branch:

2021-09-19 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
04cd3259 by Aurelien Jarno at 2021-09-19T18:53:16+02:00
debian/patches/git-updates.diff: update from upstream stable branch:

* debian/patches/git-updates.diff: update from upstream stable branch:
  - debian/patches/any/submitted-getcwd-gnu-extension-warning.diff:
upstreamed.

- - - - -


4 changed files:

- debian/changelog
- − debian/patches/any/submitted-getcwd-gnu-extension-warning.diff
- debian/patches/git-updates.diff
- debian/patches/series


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/04cd32598a0263f10e3d39768cfd603291576399

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/04cd32598a0263f10e3d39768cfd603291576399
You're receiving this email because of your account on salsa.debian.org.




Bug#993973: nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull]

2021-09-16 Thread Aurelien Jarno
On 2021-09-15 00:06, Aurelien Jarno wrote:
> On 2021-09-09 00:52, Aurelien Jarno wrote:
> > control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27476
> > 
> > On 2021-09-09 00:21, Helmut Grohne wrote:
> > > Source: nss
> > > Version: 2:3.70-1
> > > Severity: serious
> > > Tags: ftbfs
> > > X-Debbugs-Cc: debian-glibc@lists.debian.org
> > > 
> > > A native build of nss now fails as follows:
> > > 
> > > | x86_64-linux-gnu-gcc -o OBJS/nsinstall.o -c -std=c99 -g -g -fPIC   
> > > -pipe -ffunction-sections -fdata-sections -DHAVE_STRERROR -DLINUX -Dlinux 
> > > -Wall -Wshadow -Werror -DXP_UNIX -DXP_UNIX -DDEBUG -UNDEBUG 
> > > -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_SOURCE 
> > > -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT -DDEBUG -UNDEBUG 
> > > -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_SOURCE 
> > > -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT -DNSS_NO_INIT_SUPPORT 
> > > -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT 
> > > -DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES 
> > > -I/<>/dist/include -I/<>/dist/public/coreconf 
> > > -I/<>/dist/private/coreconf  nsinstall.c
> > > | nsinstall.c: In function ‘main’:
> > > | nsinstall.c:70:16: error: argument 1 is null but the corresponding size 
> > > argument 2 value is 4096 [-Werror=nonnull]
> > > |70 | #define GETCWD getcwd
> > > |   |^
> > > | nsinstall.c:239:8: note: in expansion of macro ‘GETCWD’
> > > |   239 |  cwd = GETCWD(0, PATH_MAX);
> > > |   |^~
> > > | In file included from nsinstall.c:20:
> > > | /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ 
> > > declared with attribute ‘write_only (1, 2)’
> > > |   520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur
> > > |   |  ^~
> > > | nsinstall.c:70:16: error: argument 1 is null but the corresponding size 
> > > argument 2 value is 4096 [-Werror=nonnull]
> > > |70 | #define GETCWD getcwd
> > > |   |^
> > > | nsinstall.c:246:13: note: in expansion of macro ‘GETCWD’
> > > |   246 | todir = GETCWD(0, PATH_MAX);
> > > |   | ^~
> > > | In file included from nsinstall.c:20:
> > > | /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ 
> > > declared with attribute ‘write_only (1, 2)’
> > > |   520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur
> > > |   |  ^~
> > > | cc1: all warnings being treated as errors
> > > | make[2]: *** [../../coreconf/rules.mk:292: OBJS/nsinstall.o] Error 1
> > > | make[2]: Leaving directory '/<>/nss/coreconf/nsinstall'
> > > | make[1]: *** [debian/rules:100: override_dh_auto_build] Error 2
> > > | make[1]: Leaving directory '/<>'
> > > | make: *** [debian/rules:195: build] Error 2
> > > | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> > > status 2
> > > 
> > > It looks very much like this is due to the glibc 2.32 upload. My reading
> > > of man getcwd is that the call of nss is legit (as a glibc extension).
> > > Maybe this is a glibc bug?
> > 
> > This is indeed partially a glibc bug, already reported upstream there:
> > https://sourceware.org/bugzilla/show_bug.cgi?id=27476
> > 
> > Note however that the feature of calling getcwd(NULL, >0) is a GNU
> > extension, and that the above code doesn't define _GNU_SOURCE, so this
> > is also a bug in the package.
> > 
> > Please also note that there are discussion to deprecate the support of
> > size > 0 when buf is NULL:
> > https://sourceware.org/bugzilla/show_bug.cgi?id=26545
> 
> I have uploaded a version with a temporary fix, until upstream takes a
> decision. If upstream decides to drop this part of the GNU extension,
> this patch will be removed from the Debian package, so that the
> behaviour is consistent between distribution. Of course in that case
> the documentation will have to be fixed accordingly. The packages using
> this extension will have to get fixed, just like some distributions
> using glibc >= 2.32 started to do.

Note that the patch I submitted has been accepted, so this won't be
reverted.

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



[Git][glibc-team/glibc][sid] 2 commits: Nitpick: format the messages consistently

2021-09-16 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
5b123cf4 by Aurelien Jarno at 2021-09-15T08:03:07+02:00
Nitpick: format the messages consistently

- - - - -
a86df9fe by Aurelien Jarno at 2021-09-16T22:35:49+02:00
debian/debhelper.in/libc.preinst: make sure USE_DEBCONF cant be defined 
from the environment.

- - - - -


2 changed files:

- debian/changelog
- debian/debhelper.in/libc.preinst


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/200a4d3ac16c33a2d033e631f021f25d16ac1b1f...a86df9fe0fc420dab6097d14de45442c99fe38d7

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/200a4d3ac16c33a2d033e631f021f25d16ac1b1f...a86df9fe0fc420dab6097d14de45442c99fe38d7
You're receiving this email because of your account on salsa.debian.org.




Bug#994510: libunwind8 abuses setcontext() causing SIGSEGV on i386 with glibc >= 2.32

2021-09-16 Thread Aurelien Jarno
Package: libunwind8
Version: 1.3.2-2
Severity: grave
Tags: upstream
X-Debbugs-Cc: debian-glibc@lists.debian.org

Following the glibc 2.32 upload to unstable, the autopkgtest of the
rspamd package fails on i386, due to a segmentation fault when starting
the daemon [1].

After digging, it appears that the problem is due to libunwind and the
following upstream glibc change [2]:

| commit 15eab1e3e89129ab3ed03f5bdc3415b26e9caeb9 (master)
| Author: H.J. Lu 
| Date:   Sat Feb 1 05:44:55 2020 -0800
| 
| i386: Don't unnecessarily save and restore EAX, ECX and EDX [BZ# 25262]
| 
| On i386, since EAX, ECX and EDX are caller-saved, there are no need
| to save and restore EAX, ECX and EDX in getcontext, setcontext and
| swapcontext.  They just need to clear EAX on success.  The extra
| scratch registers are needed to enable CET.
| 
| Tested on i386.
| 
| Reviewed-by: Adhemerval Zanella 


Basically EAX, ECX and EDX and are not saved anymore across a
getcontext() / setcontext() sequence, and more importantly they are not
restored in setcontext() which is used by libunwind to restore a context
after an exception. In that case, all the registers have to be restored,
including the caller-saved one.

It happens that libunwind shall not have used setcontext() there, but
rather defined its own implementation like its already done for
getcontext() as the behaviour of setcontext() is unspecified when passed
an ucp argument obtained from different sources than getcontext() or
makecontext(). Quoting the GNU libc manual:

| If the context was created by a call to a signal handler or from any
| other source then the behaviour of setcontext is unspecified.

Quoting POSIX.1-2004 (last version before it got removed):

| The effects of passing a ucp argument obtained from any other source
| are unspecified.

Note that upstream bug #69 might be relevant there [3].


[1] https://ci.debian.net/data/autopkgtest/testing/i386/r/rspamd/15290363/log.gz
[2] 
https://sourceware.org/git/?p=glibc.git;a=commit;h=15eab1e3e89129ab3ed03f5bdc3415b26e9caeb9
[3] https://github.com/libunwind/libunwind/issues/69



[Git][glibc-team/glibc] Pushed new tag debian/2.33-0experimental1

2021-09-15 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2.33-0experimental1 at GNU Libc 
Maintainers / glibc

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.33-0experimental1
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][glibc-2.33] releasing package glibc version 2.33-0experimental1

2021-09-15 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch glibc-2.33 at GNU Libc Maintainers / glibc


Commits:
dcf6d3ac by Aurelien Jarno at 2021-09-15T07:57:00+02:00
releasing package glibc version 2.33-0experimental1

- - - - -


1 changed file:

- debian/changelog


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/dcf6d3ac0fc5411a0f296c6b2e71eedf018aef68

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/dcf6d3ac0fc5411a0f296c6b2e71eedf018aef68
You're receiving this email because of your account on salsa.debian.org.




Bug#993973: nss FTBFS with glibc 2.32: error: argument 1 is null but the corresponding size argument 2 value is 4096 [-Werror=nonnull]

2021-09-14 Thread Aurelien Jarno
On 2021-09-09 00:52, Aurelien Jarno wrote:
> control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27476
> 
> On 2021-09-09 00:21, Helmut Grohne wrote:
> > Source: nss
> > Version: 2:3.70-1
> > Severity: serious
> > Tags: ftbfs
> > X-Debbugs-Cc: debian-glibc@lists.debian.org
> > 
> > A native build of nss now fails as follows:
> > 
> > | x86_64-linux-gnu-gcc -o OBJS/nsinstall.o -c -std=c99 -g -g -fPIC   -pipe 
> > -ffunction-sections -fdata-sections -DHAVE_STRERROR -DLINUX -Dlinux -Wall 
> > -Wshadow -Werror -DXP_UNIX -DXP_UNIX -DDEBUG -UNDEBUG -D_DEFAULT_SOURCE 
> > -D_BSD_SOURCE -D_POSIX_SOURCE -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT 
> > -DDEBUG -UNDEBUG -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_SOURCE 
> > -DSDB_MEASURE_USE_TEMP_DIR -D_REENTRANT -DNSS_NO_INIT_SUPPORT 
> > -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT 
> > -DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -I/<>/dist/include 
> > -I/<>/dist/public/coreconf 
> > -I/<>/dist/private/coreconf  nsinstall.c
> > | nsinstall.c: In function ‘main’:
> > | nsinstall.c:70:16: error: argument 1 is null but the corresponding size 
> > argument 2 value is 4096 [-Werror=nonnull]
> > |70 | #define GETCWD getcwd
> > |   |^
> > | nsinstall.c:239:8: note: in expansion of macro ‘GETCWD’
> > |   239 |  cwd = GETCWD(0, PATH_MAX);
> > |   |^~
> > | In file included from nsinstall.c:20:
> > | /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ 
> > declared with attribute ‘write_only (1, 2)’
> > |   520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur
> > |   |  ^~
> > | nsinstall.c:70:16: error: argument 1 is null but the corresponding size 
> > argument 2 value is 4096 [-Werror=nonnull]
> > |70 | #define GETCWD getcwd
> > |   |^
> > | nsinstall.c:246:13: note: in expansion of macro ‘GETCWD’
> > |   246 | todir = GETCWD(0, PATH_MAX);
> > |   | ^~
> > | In file included from nsinstall.c:20:
> > | /usr/include/unistd.h:520:14: note: in a call to function ‘getcwd’ 
> > declared with attribute ‘write_only (1, 2)’
> > |   520 | extern char *getcwd (char *__buf, size_t __size) __THROW __wur
> > |   |  ^~
> > | cc1: all warnings being treated as errors
> > | make[2]: *** [../../coreconf/rules.mk:292: OBJS/nsinstall.o] Error 1
> > | make[2]: Leaving directory '/<>/nss/coreconf/nsinstall'
> > | make[1]: *** [debian/rules:100: override_dh_auto_build] Error 2
> > | make[1]: Leaving directory '/<>'
> > | make: *** [debian/rules:195: build] Error 2
> > | dpkg-buildpackage: error: debian/rules build subprocess returned exit 
> > status 2
> > 
> > It looks very much like this is due to the glibc 2.32 upload. My reading
> > of man getcwd is that the call of nss is legit (as a glibc extension).
> > Maybe this is a glibc bug?
> 
> This is indeed partially a glibc bug, already reported upstream there:
> https://sourceware.org/bugzilla/show_bug.cgi?id=27476
> 
> Note however that the feature of calling getcwd(NULL, >0) is a GNU
> extension, and that the above code doesn't define _GNU_SOURCE, so this
> is also a bug in the package.
> 
> Please also note that there are discussion to deprecate the support of
> size > 0 when buf is NULL:
> https://sourceware.org/bugzilla/show_bug.cgi?id=26545

I have uploaded a version with a temporary fix, until upstream takes a
decision. If upstream decides to drop this part of the GNU extension,
this patch will be removed from the Debian package, so that the
behaviour is consistent between distribution. Of course in that case
the documentation will have to be fixed accordingly. The packages using
this extension will have to get fixed, just like some distributions
using glibc >= 2.32 started to do.

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



[Git][glibc-team/glibc][glibc-2.33] 14 commits: debian/testsuite-xfail-debian.mk: whitelist test-xfail-tst-cond24 on hppa. Closes: #993954.

2021-09-14 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch glibc-2.33 at GNU Libc Maintainers / glibc


Commits:
92b38d08 by Aurelien Jarno at 2021-09-08T22:00:16+02:00
debian/testsuite-xfail-debian.mk: whitelist test-xfail-tst-cond24 on hppa.  
Closes: #993954.

- - - - -
e9f47f34 by Aurelien Jarno at 2021-09-09T00:54:56+02:00
debian/patches/git-updates.diff: update from upstream stable branch.

- - - - -
66359576 by Aurelien Jarno at 2021-09-11T01:13:17+02:00
debian/debhelper.in/libc.preinst: drop fragile check for working debconf 
frontend now that it is done directly in debconf (see bug#985572) and now that 
this version is available in Bullseye.

- - - - -
bca19c7e by Aurelien Jarno at 2021-09-13T08:50:16+02:00
debian/control.in/libc: add a Breaks against aide ( 0.17.3-4+b3). See 
bug#994091.

- - - - -
5c42bc12 by Aurelien Jarno at 2021-09-14T20:48:52+02:00
debian/debhelper.in/libc.preinst: force systemd-logind to do NSS lookups to 
workaround the impossibility of restarting systemd-logind.  Closes: #994006.

- - - - -
78cb3272 by Aurelien Jarno at 2021-09-14T20:55:57+02:00
debian/control.in/libc: add a Breaks against python3-iptables ( 
1.0.0-2).  Closes: #994233.

- - - - -
ee284af0 by Simon McVittie at 2021-09-14T20:56:39+02:00
Restore versioned symbol tracking for mips, mipsel, libc6-i386:x32

Commit d3f9fade debian/libc6.symbols.mips, debian/libc6.symbols.mipsel:
drop symbol overrides for TLS support accidentally removed the inclusion
of symbols.wildcards, resulting in all symbols in libc.so.6 on the
affected architectures generating an unnecessarily tight dependency on
libc6 (= 2.32-1).

Commit 5f5dfcb0 caused an equivalent issue for libc6-i386:x32.

Fixes: d3f9fade debian/libc6.symbols.mips, debian/libc6.symbols.mipsel: 
drop symbol overrides for TLS support.
Fixes: 5f5dfcb0 debian/libc6-i386.symbols.x32, debian/libc6.symbols.i386: 
drop symbol overrides for TLS support.

- - - - -
73cff4a8 by Aurelien Jarno at 2021-09-14T21:13:03+02:00
debian/patches/all/submitted-po-fr-fixes.diff: fix French translation of short 
options.  Closes: #994133.

- - - - -
68fa3f98 by Aurelien Jarno at 2021-09-14T21:15:06+02:00
debian/control.in/libc: add a Breaks against fakechroot ( 2.19-3.5). 
See bug#993946.

- - - - -
27765251 by Aurelien Jarno at 2021-09-14T21:16:27+02:00
debian/control.in/libc: add a Breaks against dazzdb ( 
1.0+git20201103.8d98c37-1.1). See bug#993770.

- - - - -
bd491ffd by Aurelien Jarno at 2021-09-14T21:19:24+02:00
debian/patches/git-updates.diff: update from upstream stable branch.

- - - - -
096db86f by Aurelien Jarno at 2021-09-14T23:46:20+02:00
debian/patches/any/submitted-getcwd-gnu-extension-warning.diff: fix a warning 
when using the GNU extension of getcwd(). This is a TEMPORARY fix until 
upstream takes a decision on the removal of this extension. This might be 
REMOVED at a later point, in that case packages should be fixed instead, like 
other distributions have already done.  Closes: #993973.

- - - - -
200a4d3a by Aurelien Jarno at 2021-09-14T23:47:46+02:00
releasing package glibc version 2.32-3

- - - - -
6d21a347 by Aurelien Jarno at 2021-09-15T00:01:45+02:00
Merge branch sid into glibc-2.33

- - - - -


12 changed files:

- debian/changelog
- debian/control
- debian/control.in/libc
- debian/debhelper.in/libc.preinst
- debian/libc6-i386.symbols.x32
- debian/libc6.symbols.mips
- debian/libc6.symbols.mipsel
- debian/patches/all/submitted-po-fr-fixes.diff
- + debian/patches/any/submitted-getcwd-gnu-extension-warning.diff
- debian/patches/git-updates.diff
- debian/patches/series
- debian/testsuite-xfail-debian.mk


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/4acc0eff30190cff90873bca1ad0e386b069fe11...6d21a3475035fd4da077e753a1f75d3b263970d3

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/4acc0eff30190cff90873bca1ad0e386b069fe11...6d21a3475035fd4da077e753a1f75d3b263970d3
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc] Pushed new tag debian/2.32-3

2021-09-14 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2.32-3 at GNU Libc Maintainers / glibc

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.32-3
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] releasing package glibc version 2.32-3

2021-09-14 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
200a4d3a by Aurelien Jarno at 2021-09-14T23:47:46+02:00
releasing package glibc version 2.32-3

- - - - -


1 changed file:

- debian/changelog


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/200a4d3ac16c33a2d033e631f021f25d16ac1b1f

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/200a4d3ac16c33a2d033e631f021f25d16ac1b1f
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] debian/patches/any/submitted-getcwd-gnu-extension-warning.diff: fix a warning...

2021-09-14 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
096db86f by Aurelien Jarno at 2021-09-14T23:46:20+02:00
debian/patches/any/submitted-getcwd-gnu-extension-warning.diff: fix a warning 
when using the GNU extension of getcwd(). This is a TEMPORARY fix until 
upstream takes a decision on the removal of this extension. This might be 
REMOVED at a later point, in that case packages should be fixed instead, like 
other distributions have already done.  Closes: #993973.

- - - - -


3 changed files:

- debian/changelog
- + debian/patches/any/submitted-getcwd-gnu-extension-warning.diff
- debian/patches/series


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/096db86fcbb754c30a5ede856edd46d82784416c

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/096db86fcbb754c30a5ede856edd46d82784416c
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] debian/patches/git-updates.diff: update from upstream stable branch.

2021-09-14 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
bd491ffd by Aurelien Jarno at 2021-09-14T21:19:24+02:00
debian/patches/git-updates.diff: update from upstream stable branch.

- - - - -


2 changed files:

- debian/changelog
- debian/patches/git-updates.diff


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/bd491ffdff3c7e9410f01879bfc3e7094f177c34

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/bd491ffdff3c7e9410f01879bfc3e7094f177c34
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] debian/control.in/libc: add a Breaks against dazzdb (<<...

2021-09-14 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
27765251 by Aurelien Jarno at 2021-09-14T21:16:27+02:00
debian/control.in/libc: add a Breaks against dazzdb ( 
1.0+git20201103.8d98c37-1.1). See bug#993770.

- - - - -


3 changed files:

- debian/changelog
- debian/control
- debian/control.in/libc


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/27765251d0953b1e772fa9791cd0ae8ebfd79f38

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/27765251d0953b1e772fa9791cd0ae8ebfd79f38
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] debian/control.in/libc: add a Breaks against fakechroot (<< 2.19-3.5). See bug#993946.

2021-09-14 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
68fa3f98 by Aurelien Jarno at 2021-09-14T21:15:06+02:00
debian/control.in/libc: add a Breaks against fakechroot ( 2.19-3.5). 
See bug#993946.

- - - - -


2 changed files:

- debian/changelog
- debian/control.in/libc


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/68fa3f980727b708bf6ac6805896eeac7e5e70c1

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/68fa3f980727b708bf6ac6805896eeac7e5e70c1
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] debian/patches/all/submitted-po-fr-fixes.diff: fix French translation of short...

2021-09-14 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
73cff4a8 by Aurelien Jarno at 2021-09-14T21:13:03+02:00
debian/patches/all/submitted-po-fr-fixes.diff: fix French translation of short 
options.  Closes: #994133.

- - - - -


2 changed files:

- debian/changelog
- debian/patches/all/submitted-po-fr-fixes.diff


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/73cff4a855eb87e2d80cba17dc199321f762b076

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/73cff4a855eb87e2d80cba17dc199321f762b076
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] Restore versioned symbol tracking for mips, mipsel, libc6-i386:x32

2021-09-14 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
ee284af0 by Simon McVittie at 2021-09-14T20:56:39+02:00
Restore versioned symbol tracking for mips, mipsel, libc6-i386:x32

Commit d3f9fade debian/libc6.symbols.mips, debian/libc6.symbols.mipsel:
drop symbol overrides for TLS support accidentally removed the inclusion
of symbols.wildcards, resulting in all symbols in libc.so.6 on the
affected architectures generating an unnecessarily tight dependency on
libc6 (= 2.32-1).

Commit 5f5dfcb0 caused an equivalent issue for libc6-i386:x32.

Fixes: d3f9fade debian/libc6.symbols.mips, debian/libc6.symbols.mipsel: 
drop symbol overrides for TLS support.
Fixes: 5f5dfcb0 debian/libc6-i386.symbols.x32, debian/libc6.symbols.i386: 
drop symbol overrides for TLS support.

- - - - -


4 changed files:

- debian/changelog
- debian/libc6-i386.symbols.x32
- debian/libc6.symbols.mips
- debian/libc6.symbols.mipsel


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/ee284af0ae6f45733be1366a6e1afbc389115d10

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/ee284af0ae6f45733be1366a6e1afbc389115d10
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] debian/debhelper.in/libc.preinst: force systemd-logind to do NSS lookups to...

2021-09-14 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
5c42bc12 by Aurelien Jarno at 2021-09-14T20:48:52+02:00
debian/debhelper.in/libc.preinst: force systemd-logind to do NSS lookups to 
workaround the impossibility of restarting systemd-logind.  Closes: #994006.

- - - - -


2 changed files:

- debian/changelog
- debian/debhelper.in/libc.preinst


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/5c42bc1216d2b59e3be423f3788c50018803a3e8

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/5c42bc1216d2b59e3be423f3788c50018803a3e8
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] debian/control.in/libc: add a Breaks against python3-iptables (<< 1.0.0-2). Closes: #994233.

2021-09-14 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
78cb3272 by Aurelien Jarno at 2021-09-14T20:55:57+02:00
debian/control.in/libc: add a Breaks against python3-iptables ( 
1.0.0-2).  Closes: #994233.

- - - - -


3 changed files:

- debian/changelog
- debian/control
- debian/control.in/libc


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/78cb3272bd1e93868e8efc62e1f587d1358605ba

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/78cb3272bd1e93868e8efc62e1f587d1358605ba
You're receiving this email because of your account on salsa.debian.org.




Bug#994006: libc6: NSS modules changes require a restart of systemd-logind, which is not possible

2021-09-14 Thread Aurelien Jarno
On 2021-09-14 08:56, Simon McVittie wrote:
> On Mon, 13 Sep 2021 at 22:59:32 +0200, Aurelien Jarno wrote:
> > - running the operation on a non-existing user, but as loginctl does a
> >   check that the user exists, it has to be done directly with the dbus
> >   API, for instance "gdbus call --system --dest org.freedesktop.login1
> >   --object-path /org/freedesktop/login1 --method
> >   org.freedesktop.login1.Manager.SetUserLinger 12345678 true true"
> > 
> > The latest is more a bit more complex to do (especially that
> > libglib2.0-bin is not necessarily installed on the system), but has the
> > advantage of exercising all configured NSS modules.
> 
> systemd happens to have its own D-Bus implementation sd-bus (a competitor
> to libdbus and GLib's GDBus) for which it provides busctl(1), an
> equivalent of gdbus(1) and dbus-send(1). So this could be written as:
> 
> busctl call --system org.freedesktop.login1 /org/freedesktop/login1 \
> org.freedesktop.login1.Manager SetUserLinger ubb $uid true true
> 
> which does not have dependencies outside systemd.deb.

Thanks a lot for the help here, as my knowledge with systemd is
relatively limited. That seems to work fine when executed just before
the libc6 upgrade in the script I use to trigger the upgrade at boot
time. I'll try to insert all pieces into libc6.preinst and see if that
still works.

> The nonexistent uid should probably be in one of the ranges reserved by
> Policy §9.2.2: perhaps 4294967294 or (uint32_t) -2, which is reserved
> as a representation of the anonymous NFS user?

Yes, that is probably a good pick. I guess we should actually disable
lingering (so ... ubb 4294967294 false false) to minimize the damages if
this user exists anyway.

Regards
Aurelien

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



Re: Bug#994133: libc-bin: [iconv] [fr] Missing word in the French output of iconv

2021-09-14 Thread Aurelien Jarno
Hi,

On 2021-09-14 12:56, Baptiste Jammet wrote:
> control: reassign -1 libc-bin
> control: retitle -1 libc-bin: [iconv] [fr] Missing word in the French
> output of iconv --help
> control: tags -1 upstream
> 
> Hi all,
> 
> >It’s in the output of iconv --help.
> 
> So it's not in the manpage, but in the po/fr.po file of the iconv
> source :
> https://sources.debian.org/src/glibc/2.32-2/po/fr.po/#L42
> introduced in upstream by:
> https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=0ffaa7be6ea3649f883248f41a2bea5065383976#patch11
> 
> Sorry for the ping-pong and thank you all for the translation work!

Oops, sorry about that, I have read manpage in the topic, so I didn't
check further as it is a common issue to report those to the wrong
package.

I have contacted the translator to get it fixed.

Regards,
Aurelien

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


signature.asc
Description: PGP signature


Bug#994232: libc6: generates unnecessarily tight dependencies on mips, mipsel

2021-09-14 Thread Aurelien Jarno
On 2021-09-14 09:28, Simon McVittie wrote:
> Package: libc6
> Version: 2.32-2
> Severity: normal
> Tags: patch
> X-Debbugs-Cc: debian-rele...@lists.debian.org
> 
> Most architectures' libc6.symbols.$arch have this pattern:
> 
> > $ cat debian/libc6.symbols.i386
> > #include "libc6.symbols.common"
> > ld-linux.so.2 #PACKAGE# #MINVER#
> > #include "symbols.wildcards"
> > libc.so.6 #PACKAGE# #MINVER#
> > #include "symbols.wildcards"
> 
> This results in any use of symbols versioned foo@GLIBC_2.23 generating a
> dependency on libc6 (>= 2.23), and so on.
> 
> However, libc6:mips and libc6:mipsel are missing the final
> '#include "symbols.wildcards"', which results in those architectures
> generating an unnecessarily strict dependency on libc6 (>= 2.32-1) and
> entangling other transitions with glibc's transition. As far as I can see,
> this was accidental?

Yes, this one indeed accidental, my cleanup to remove the complexity
from the linuxthreads to NPTL transition has been too agressive.

Thanks a lot for catching that and for the patch.

Regards,
Aurelien

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



Bug#994006: libc6: NSS modules changes require a restart of systemd-logind, which is not possible

2021-09-13 Thread Aurelien Jarno
Hi Michael,

On 2021-09-13 19:13, Michael Biebl wrote:
> Hi Aurelien,
> 
> thanks for the bug report
> 
> On Thu, 9 Sep 2021 18:48:42 +0200 Aurelien Jarno  wrote:
> 
> > One way to workaround the issue would be to force systemd-logind to do a
> > NSS lookup, just like it it s already the case when a user log onto the
> > system.
> 
> Before the upgrade, I assume, i.e. in libc6.preinst? 

Yes, exactly.

> Have you already tested this? If so, what did you use?
> Should we construct something based on systemd-run maybe?

Unfortunately it's not easy. loginctl is doing a lot of checks before
calling systemd-logind, and systemd-logind is doing a lot of tests
before doing a call to NSS functions. Most notably, it needs to be a
real login associated with a seat, so faking a login is not possible.

The only thing I have found is to ask systemd-logind to enable or
disable lingering. To avoid actually changing the configuration, the two
following options works:
- running the operation on an existing user, but without the associated
  permission. For instance running "loginctl enable-linger root" as user
  nobody.
- running the operation on a non-existing user, but as loginctl does a
  check that the user exists, it has to be done directly with the dbus
  API, for instance "gdbus call --system --dest org.freedesktop.login1
  --object-path /org/freedesktop/login1 --method
  org.freedesktop.login1.Manager.SetUserLinger 12345678 true true"

The latest is more a bit more complex to do (especially that
libglib2.0-bin is not necessarily installed on the system), but has the
advantage of exercising all configured NSS modules.

In any case we can probably check if the above trick is needed by
running something like "grep -E 'libnss_(compat|db|files)'
/proc/$(systemctl show --property MainPID --value
systemd-logind.service)/maps"

I haven't test the full pattern by including this in the preinst, but so
far I have been running the above snippet before doing the upgrade, and
I has worked.

Aurelien

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


signature.asc
Description: PGP signature


[Git][glibc-team/glibc][sid] debian/control.in/libc: add a Breaks against aide (<< 0.17.3-4+b3). See bug#994091.

2021-09-13 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
bca19c7e by Aurelien Jarno at 2021-09-13T08:50:16+02:00
debian/control.in/libc: add a Breaks against aide ( 0.17.3-4+b3). See 
bug#994091.

- - - - -


3 changed files:

- debian/changelog
- debian/control
- debian/control.in/libc


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/bca19c7e23de72629d5cd4d3bbd33bfcfe08d7b5

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/bca19c7e23de72629d5cd4d3bbd33bfcfe08d7b5
You're receiving this email because of your account on salsa.debian.org.




Bug#994133: libc-bin: [iconv] [fr] [manpage] Missing word in the French manpage of iconv

2021-09-12 Thread Aurelien Jarno
control: reassign -1 manpages-fr
control: retitle -1 manpages-fr: [iconv] [fr] [manpage] Missing word in the 
French manpage of iconv

Hi,

On 2021-09-12 15:36, Nicolas Patrois wrote:
> Package: libc-bin
> Version: 2.32-2
> Severity: minor
> Tags: l10n
> 
> Dear Maintainer,
> 
> In the French manpage, the word "forme" is missing in its end.
> 
> Les arguments obligatoires ou optionnels pour les options de forme longue
> le sont aussi pour les options de   courte.
> 
> Just before "courte".

The French manpage if iconv is not provided by libc-bin, but by
manpages-fr. I am therefore reassigning the bug to the right package.

Regards,
Aurelien

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



Bug#994102: unistd.h: non-null check not correct for getcwd()

2021-09-12 Thread Aurelien Jarno
On 2021-09-12 12:10, Jan-Benedict Glaw wrote:
> On Sun, 2021-09-12 00:16:01 +0200, Aurelien Jarno  
> wrote:
> > On 2021-09-11 22:06, Jan-Benedict Glaw wrote:
> > > Until glibc's Bugzilla issue is finally resolved
> > > (https://sourceware.org/bugzilla/show_bug.cgi?id=26545), maybe the
> > > Debian package could be changed to drop the access attribute?
> > 
> > No. Once we have patched it, we will have to differ from upstream almost
> > forever, and we want to avoid that. I already have sent a patch [1], I
> > am waiting for feedback.
> 
> Sure, but I hope Debian's libc6-dev won't keep the instrumentation
> enabled even after the patch is accepted upstream to remove it,
> waiting for the next upstream glibc to be pulled for libc6 / libc-dev?

No the point is not to wait for a released version, but to wait for a
decision if this patch is acceptable or if the support for this GNU
extension is simply dropped. In the latter case, the various software
will have to be patched, just like other distributions using glibc >=
2.32 have already done.

Regards,
Aurelien

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


signature.asc
Description: PGP signature


Bug#994102: unistd.h: non-null check not correct for getcwd()

2021-09-11 Thread Aurelien Jarno
On 2021-09-11 22:06, Jan-Benedict Glaw wrote:
> Until glibc's Bugzilla issue is finally resolved
> (https://sourceware.org/bugzilla/show_bug.cgi?id=26545), maybe the
> Debian package could be changed to drop the access attribute?

No. Once we have patched it, we will have to differ from upstream almost
forever, and we want to avoid that. I already have sent a patch [1], I
am waiting for feedback.

Regards,
Aurelien

[1] https://sourceware.org/pipermail/libc-alpha/2021-September/130886.html

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


signature.asc
Description: PGP signature


Re: Bug#994091: nmu: aide_0.17.3-4

2021-09-11 Thread Aurelien Jarno
On 2021-09-11 21:52, Adrian Bunk wrote:
> On Sat, Sep 11, 2021 at 03:59:12PM +0200, Marc Haber wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: binnmu
> > 
> > [this is my first binNMU request, I hope that I did everything right]
> 
> [ I am not a member of the release team ]
> 
> > aide is statically linked. With the new glibc, NSS calls get somehow
> > still some dynamic linking, which causes a reproducible and
> > unconditional segfault one aide uses an NSS-releated call. A rebuild
> > fixes this issue. I am currently discussing this issue with upstream to
> > find out whether we can do things a bit better in the future.
> 
> AFAIR static glibc linking and NSS is known problematic.

Indeed, I confirm. Note that this will change with glibc 2.34 which has
nss_files and nss_dns built-in.

> The dependencies should ensure that apt/dpkg only install a working set 
> of packages. Dependencies like "libc6 (>> 2.32), libc6 (<< 2.33)" might
> help, but I've added debian-glibc to Cc since I don't know for sure
> whether this would be sufficient.

This is correct, there is no breakage between minor version, only
between major version. Now, given that bookworm will very likely have
glibc >= 2.34 (at least that the goal if we are able to solve all issues
with each new upstream version), so I am not sure if it is worth
implementing such a change.

Regards,
Aurelien

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



[Git][glibc-team/glibc][sid] debian/debhelper.in/libc.preinst: drop fragile check for working debconf...

2021-09-10 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
66359576 by Aurelien Jarno at 2021-09-11T01:13:17+02:00
debian/debhelper.in/libc.preinst: drop fragile check for working debconf 
frontend now that it is done directly in debconf (see bug#985572) and now that 
this version is available in Bullseye.

- - - - -


2 changed files:

- debian/changelog
- debian/debhelper.in/libc.preinst


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/66359576b1aa793ae6c79618b188738287cf8789

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/66359576b1aa793ae6c79618b188738287cf8789
You're receiving this email because of your account on salsa.debian.org.




Bug#994042: libc6: debconf text fallback failed to accept input, had to be killed leading to broken dist-upgrade

2021-09-10 Thread Aurelien Jarno
On 2021-09-10 20:39, Colin Watson wrote:
> On Fri, Sep 10, 2021 at 09:03:32PM +0200, Aurelien Jarno wrote:
> > On 2021-09-10 16:51, Colin Watson wrote:
> > > The only way to fix what libc.preinst is currently trying to do would
> > > be:
> > > 
> > >  * Fetch the current debconf frontend *without* first sourcing the
> > >confmodule, e.g. using something like "echo GET debconf/frontend |
> > >debconf-communicate" which I *think* is safe as long as you haven't
> > >sourced the confmodule yet;
> > > 
> > >  * Decide whether to use debconf based on this and other information;
> > > 
> > >  * Only source the confmodule if you've positively decided to use it.
> > 
> > debconf-communicate might be safe, but its manpage explicitly says it
> > should not be used in maintainer scripts.
> 
> Strictly, it says "a maintainer script of a package that uses debconf".
> I think what that really means is that it shouldn't be used after
> sourcing the debconf confmodule (which is normally the same as using
> debconf since nearly everything sources it right at the top - but this
> is a weird edge case).  The point is to avoid having multiple processes
> with the debconf database open at the same time.
> 
> Put another way, for this purpose, libc6.preinst isn't really a
> maintainer script that uses debconf until it sources the confmodule.
> 
> > I gave a try with debconf-show instead. I have attached a totally
> > untested patch to check that we agree on the way to do it.
> 
> I think you forgot to attach the patch?

Dooh. Please find a new version attached.

> I wouldn't completely veto using debconf-show in this very specialized
> situation, as long as it came with a substantial comment explaining
> what's going on so that nobody else is tempted to copy it.  However, the
> output format of debconf-show isn't guaranteed, so I'm not very happy
> about it being used mechanically like this.  I'd prefer
> debconf-communicate if we can ensure that it works in this context,
> notwithstanding its documentation.

Ok, I have updated my patch to use that method.

> > > But a simpler approach might be to update debconf in buster with the
> > > change from 1.5.76 to check whether whiptail/dialog is usable before
> > > trying to use it, and then remove at least some of this fragile and
> > > broken code from libc.preinst.  At the very least, USE_DEBCONF=1 must
> > > always be set if (and only if) the debconf confmodule has been sourced.
> > 
> > While it is probably a good idea to backport that change in buster to
> > limit to reduce the risk, we don't require people to upgrade to the
> > latest buster release before starting an upgrade.
> > 
> > On the other hand, given that bullseye has a fixed debconf, I fully
> > agree that we should drop that fragile code for bookworm.
> 
> We probably agree on both points here.

Great.

> > > I'm currently seeing if I can construct a reduced reproduction recipe
> > > based on Neil's logs, since it evidently depends on exactly which order
> > > apt chooses to unpack things early on, and it would be very helpful to
> > > be able to test fixes properly.
> > 
> > Thanks, tell me if you need help on that.
> 
> I managed to reproduce the reported bug by taking Neil's full package
> list, mangling it to roughly make sense on buster, installing all of
> that, and then doing "apt upgrade && apt full-upgrade" (my own habit is
> just to do "apt full-upgrade", but in this case the initial "apt
> upgrade" is crucial).  I'm now trying to more or less bisect the package
> list to find something rather more minimal; this is a slow process, but
> no roadblocks so far, and I'll let you know when I have something.
> 

Thanks a lot for your help.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
commit d67e52a7d1997a3e461b6971b00ce94a136a5b2d
Author: Aurelien Jarno 
Date:   Fri Sep 10 20:58:48 2021 +0200

first fix for #994042

diff --git a/debian/debhelper.in/libc.preinst b/debian/debhelper.in/libc.preinst
index d679db4f..e7808a44 100644
--- a/debian/debhelper.in/libc.preinst
+++ b/debian/debhelper.in/libc.preinst
@@ -21,23 +21,22 @@ kfreebsd_compare_versions () {
 
 if [ "$type" != abort-upgrade -a -z "$DPKG_ROOT" ]
 then
-# Load debconf module if available and usable
+# Check if the debconf module is available and usable
 if [ -f /usr/share/debconf/confmodule ]; then
 # cdebconf has a working fallback mechanism in case dialog
 # is not usable, so do 

Bug#994042: libc6: debconf text fallback failed to accept input, had to be killed leading to broken dist-upgrade

2021-09-10 Thread Aurelien Jarno
Hi Colin,

On 2021-09-10 16:51, Colin Watson wrote:
> On Fri, Sep 10, 2021 at 04:02:06PM +0100, Neil Williams wrote:
> > This is related to #984533 - in my case, there was no effect on the 
> > initramfs.
> > 
> > I am attaching the section of the apt log. (gzipped)
> > I am also attaching the dpkg -l output for the package list (after upgrade).
> > 
> > The apt log includes the details of the --purge autoremove operation I 
> > completed
> > after a reboot, so those packages were also installed on buster too.
> > 
> > This was an upgrade from buster to bullseye.
> > apt upgrade worked fine (first part of the log).
> > 
> > When dist-upgrade started, I got:
> > 
> > Preparing to unpack .../92-libc6_2.31-13_amd64.deb ...
> > debconf: unable to initialize frontend: Dialog
> > debconf: (No usable dialog-like program is installed, so the dialog based 
> > frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm 
> > line 78.)
> > debconf: falling back to frontend: Readline
> > Checking for services that may need to be restarted...
> > Checking init scripts...
> > Do you want to upgrade glibc now?
> > 
> > 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 is able to restart some services (such as ssh or
> > telnetd), but other programs cannot be restarted automatically.  One such
> > program that needs manual stopping and restart after the glibc upgrade by
> > yourself is xdm - because automatic restart might disconnect your active
> > X11 sessions.
> > 
> > This script detected the following installed services which must be
> > stopped before the upgrade: postgresql 
> > 
> > If you want to interrupt the upgrade now and continue later, please
> > answer No to the question below.
> > 
> > Do you want to upgrade glibc now? [Y/n] y
> > Y
> 
> The code in libc.preinst that attempts to fall back to text mode,
> introduced in 2.31-10, is clearly incorrect; apologies for not noticing
> this earlier.  It sources the debconf confmodule and then conditionally
> sets USE_DEBCONF; but since the debconf confmodule has already been
> sourced by this point, text mode won't work properly since standard
> input and output refer to the debconf frontend.  (In particular, reading
> from stdin can't work.)

Thanks for the fast analysis, and apologies for introducing that bug.

> The only way to fix what libc.preinst is currently trying to do would
> be:
> 
>  * Fetch the current debconf frontend *without* first sourcing the
>confmodule, e.g. using something like "echo GET debconf/frontend |
>debconf-communicate" which I *think* is safe as long as you haven't
>sourced the confmodule yet;
> 
>  * Decide whether to use debconf based on this and other information;
> 
>  * Only source the confmodule if you've positively decided to use it.

debconf-communicate might be safe, but its manpage explicitly says it
should not be used in maintainer scripts. I gave a try with debconf-show
instead. I have attached a totally untested patch to check that we
agree on the way to do it.

> But a simpler approach might be to update debconf in buster with the
> change from 1.5.76 to check whether whiptail/dialog is usable before
> trying to use it, and then remove at least some of this fragile and
> broken code from libc.preinst.  At the very least, USE_DEBCONF=1 must
> always be set if (and only if) the debconf confmodule has been sourced.

While it is probably a good idea to backport that change in buster to
limit to reduce the risk, we don't require people to upgrade to the
latest buster release before starting an upgrade.

On the other hand, given that bullseye has a fixed debconf, I fully
agree that we should drop that fragile code for bookworm.

> I'm currently seeing if I can construct a reduced reproduction recipe
> based on Neil's logs, since it evidently depends on exactly which order
> apt chooses to unpack things early on, and it would be very helpful to
> be able to test fixes properly.

Thanks, tell me if you need help on that.

Regards,
Aurelien

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



Bug#994006: libc6: NSS modules changes require a restart of systemd-logind, which is not possible

2021-09-09 Thread Aurelien Jarno
On 2021-09-09 18:26, Aurelien Jarno wrote:
> Package: libc6
> Version: 2.32-1
> Severity: serious
> X-Debbugs-Cc: pkg-systemd-maintain...@lists.alioth.debian.org
> 
> The NSS modules provided by glibc 2.32 require new symbols, which are
> therefore not provided by libc6 2.31. This is why we require restarting
> daemons after the new libc6 is installed.
> 
> systemd-logind is also using NSS modules, so it needs to be restarted.
> Unfortunately that's not something possible without killing Xorg
> sessions (see bug#919509). Not restarting systemd-logind means that it
> is not able to load new NSS modules, howeveralready loaded modules are
> still usable.

One way to workaround the issue would be to force systemd-logind to do a
NSS lookup, just like it it s already the case when a user log onto the
system.

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



Bug#994006: libc6: NSS modules changes require a restart of systemd-logind, which is not possible

2021-09-09 Thread Aurelien Jarno
Package: libc6
Version: 2.32-1
Severity: serious
X-Debbugs-Cc: pkg-systemd-maintain...@lists.alioth.debian.org

The NSS modules provided by glibc 2.32 require new symbols, which are
therefore not provided by libc6 2.31. This is why we require restarting
daemons after the new libc6 is installed.

systemd-logind is also using NSS modules, so it needs to be restarted.
Unfortunately that's not something possible without killing Xorg
sessions (see bug#919509). Not restarting systemd-logind means that it
is not able to load new NSS modules, howeveralready loaded modules are
still usable.

One visible consequence is that on systems where no user sessions have
been registered with systemd-logind, new sessions will fail to register
after the libc6 upgrade with the following king of error:

  sshd[647]: pam_systemd(sshd:session): Failed to create session: No such 
process

Not registering the session causes among other things XDG_RUNTIME_DIR to
not be defined (or even created), causing autopkgtest failures:
https://ci.debian.net/data/autopkgtest/testing/amd64/c/calibre/15138528/log.gz

Here is a simpler way to reproduce the problem:
- Schedule the libc6 upgrade from 2.31 to 2.32 (currently bookworm to
  sid) to happen on a system which hasn't seen any user login since it
  has been booted. For instance trigger it from /etc/rc.local.
- Log onto the system (for instance through TTY or SSH), observe the
  error message in the logs and the absence of XDG_RUNTIME_DIR in the
  environment.



[Git][glibc-team/glibc][sid] debian/patches/git-updates.diff: update from upstream stable branch.

2021-09-08 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
e9f47f34 by Aurelien Jarno at 2021-09-09T00:54:56+02:00
debian/patches/git-updates.diff: update from upstream stable branch.

- - - - -


2 changed files:

- debian/changelog
- debian/patches/git-updates.diff


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/e9f47f346c85747b4d6680c4ba17fff179fae3db

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/e9f47f346c85747b4d6680c4ba17fff179fae3db
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] debian/testsuite-xfail-debian.mk: whitelist test-xfail-tst-cond24 on hppa. Closes: #993954.

2021-09-08 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
92b38d08 by Aurelien Jarno at 2021-09-08T22:00:16+02:00
debian/testsuite-xfail-debian.mk: whitelist test-xfail-tst-cond24 on hppa.  
Closes: #993954.

- - - - -


2 changed files:

- debian/changelog
- debian/testsuite-xfail-debian.mk


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/92b38d08ec0bb9e34d4f03ce29f7bdac720326a8

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/92b38d08ec0bb9e34d4f03ce29f7bdac720326a8
You're receiving this email because of your account on salsa.debian.org.




Bug#989147: glibc: CVE-2021-33574: mq_notify does not handle separately allocated thread attributes

2021-09-08 Thread Aurelien Jarno
On 2021-09-08 13:25, Jonas Andradas wrote:
> Hi, 
> 
> On Sat, 21 Aug 2021 20:14:52 +0200 Aurelien Jarno  
> wrote:
> > Version: 2.32-0experimental0
> > 
> > On 2021-05-26 21:57, Salvatore Bonaccorso wrote:
> > > Source: glibc
> > > Version: 2.31-12
> > > Severity: important
> > > Tags: security upstream
> > > Forwarded: https://sourceware.org/bugzilla/show_bug.cgi?id=27896
> > > X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> 
> > > 
> [...snip...]
> > 
> > This bug has been fixed in the glibc 2.32-0experimental0 upload to
> > experimental, but wasn't close due to a typo in the changelog. Closing
> > the bug manually.
> > 
> 
> Is there an estimated timeline for when the experimental, fixed package would 
> transition to sid (and possibly testing/bookworm)?  Is there an estimate for 

The fix is already in sid for a few days. Transition to testing/bookworm
depends on many factors that are out of control of the glibc
maintainers.

> when the fix will be backported to bullseye? 

Unfortunately the fixes are not trivial to get backported, as they
depend on new symbols exported through GLIBC_PRIVATE. This is something
in progress, but I have no ETA so far.

Best regards,
Aurelien 

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



[Git][glibc-team/glibc][glibc-2.33] 7 commits: debian/testsuite-xfail-debian.mk: Update hurd tests.

2021-09-07 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch glibc-2.33 at GNU Libc Maintainers / glibc


Commits:
7761c4a4 by Samuel Thibault at 2021-09-06T10:40:12+02:00
debian/testsuite-xfail-debian.mk: Update hurd tests.

- - - - -
d912597c by Aurelien Jarno at 2021-09-07T13:11:57+02:00
debian/rules.d/debhelper.mk: do not try to install audit/sotruss-lib.so in 
stage1 profile.

- - - - -
c41038a6 by Aurelien Jarno at 2021-09-07T21:48:06+02:00
debian/debhelper.in/libc.postinst: grab patch from Ubuntu to carefully restart 
systemd on libc6 upgrade.  Closes: #993821.

- - - - -
3a44265c by Aurelien Jarno at 2021-09-07T21:57:18+02:00
debian/debhelper.in/libc.lintian-overrides: and an override about the systemctl 
call in libc6.postinst.

- - - - -
3b91171b by Aurelien Jarno at 2021-09-07T21:57:42+02:00
releasing package glibc version 2.32-2

- - - - -
e9d8b821 by Aurelien Jarno at 2021-09-07T22:20:51+02:00
Merge branch sid into glibc-2.33

- - - - -
4acc0eff by Aurelien Jarno at 2021-09-07T22:24:01+02:00
debian/patches/git-updates.diff: update from upstream stable branch.

- - - - -


6 changed files:

- debian/changelog
- debian/debhelper.in/libc.lintian-overrides
- debian/debhelper.in/libc.postinst
- debian/patches/git-updates.diff
- debian/rules.d/debhelper.mk
- debian/testsuite-xfail-debian.mk


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/7fbd0beef2a6212f6b332962e47b4cc1d5cfeeb6...4acc0eff30190cff90873bca1ad0e386b069fe11

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/compare/7fbd0beef2a6212f6b332962e47b4cc1d5cfeeb6...4acc0eff30190cff90873bca1ad0e386b069fe11
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc] Pushed new tag debian/2.32-2

2021-09-07 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed new tag debian/2.32-2 at GNU Libc Maintainers / glibc

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.32-2
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] releasing package glibc version 2.32-2

2021-09-07 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
3b91171b by Aurelien Jarno at 2021-09-07T21:57:42+02:00
releasing package glibc version 2.32-2

- - - - -


1 changed file:

- debian/changelog


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/3b91171bdce241dddf8724449c522cd8009c5d58

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/3b91171bdce241dddf8724449c522cd8009c5d58
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] debian/debhelper.in/libc.lintian-overrides: and an override about the...

2021-09-07 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
3a44265c by Aurelien Jarno at 2021-09-07T21:57:18+02:00
debian/debhelper.in/libc.lintian-overrides: and an override about the systemctl 
call in libc6.postinst.

- - - - -


2 changed files:

- debian/changelog
- debian/debhelper.in/libc.lintian-overrides


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/3a44265c8510701d4aaa47d461879b9b872f02dd

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/3a44265c8510701d4aaa47d461879b9b872f02dd
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] debian/debhelper.in/libc.postinst: grab patch from Ubuntu to carefully restart...

2021-09-07 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
c41038a6 by Aurelien Jarno at 2021-09-07T21:48:06+02:00
debian/debhelper.in/libc.postinst: grab patch from Ubuntu to carefully restart 
systemd on libc6 upgrade.  Closes: #993821.

- - - - -


2 changed files:

- debian/changelog
- debian/debhelper.in/libc.postinst


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/c41038a6380be47b2c4873d4623840e51394bf5f

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/c41038a6380be47b2c4873d4623840e51394bf5f
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][sid] debian/rules.d/debhelper.mk: do not try to install audit/sotruss-lib.so in stage1 profile.

2021-09-07 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc


Commits:
d912597c by Aurelien Jarno at 2021-09-07T13:11:57+02:00
debian/rules.d/debhelper.mk: do not try to install audit/sotruss-lib.so in 
stage1 profile.

- - - - -


2 changed files:

- debian/changelog
- debian/rules.d/debhelper.mk


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/d912597c096cd669d6cc3172fefb2d4d78a41e4b

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/d912597c096cd669d6cc3172fefb2d4d78a41e4b
You're receiving this email because of your account on salsa.debian.org.




Re: Bug#993821: After upgrading libc, some services are unable to restart (including systemd-resolved)

2021-09-07 Thread Aurelien Jarno
Hi,

On 2021-09-07 10:39, Michael Hudson-Doyle wrote:
> On Tue, 7 Sept 2021 at 10:21, Michael Biebl  wrote:
> 
> > Am 06.09.21 um 23:45 schrieb Vincent Bernat:
> >  > Package: systemd
> >  > Version: 247.9-1
> >  > Severity: normal
> >  >
> > > Hey!
> > >
> > > After upgrading to libc6 2.32-1, some services are unable to restart.
> > > In my case, systemd-resolved, systemd-timesyncd and colord. Using
> > > "systemctl daemon-reexec" fixes the issue. Unsure if there is really
> > > something to be fixed but as I didn't find anything about that, a bug
> > > report may help others. I suppose the problem is related to NSS.
> > >
> > > Sep 06 23:06:43 chocobo systemd[1]: Starting Network Time
> > Synchronization...
> > > Sep 06 23:06:43 chocobo systemd[236983]: systemd-timesyncd.service:
> > Failed to determine user credentials: No such process
> > > Sep 06 23:06:43 chocobo systemd[236983]: systemd-timesyncd.service:
> > Failed at step USER spawning /lib/systemd/systemd-timesyncd: No such process
> > >
> > >
> >
> >
> > @libc maintainers: any ideas what could be causing this? If this is
> > triggered by a libc6 update, should this be reassigned to glibc?
> >
> 
> We went through this in Ubuntu recently and decided that restarting systemd
> in glibc's postinst was the safest option:
> https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1942276
> 
> What's happening is that systemd is running with the old glibc, forks and
> then does NSS things that cause the new glibc's NSS modules to load and
> they don't necessarily work, leading to failures in any unit that specifies
> User=. At least for Ubuntu's builds the NSS modules seem to be ABI
> compatible between 2.32 and 2.33 (I didn't try 2.31 vs 2.32) but they are
> definitely not between 2.33 and 2.34.

Thanks for this feedback and the pointer to the patch used in Ubuntu. It
seems to be a good solution, and matches what is done for other init
systems.

On the other hand, the problem is supposed to only happen for major
glibc version upgrade where the NSS modules might have a different ABI.
In that regard, I would be tempted to restart it only for major versions
upgrade like it's done for other daemons. Now if the systemd maintainers
consider it's fine restarting it for each glibc upgrade, we should
probably go that way.

Regards,
Aurelien

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



[Git][glibc-team/glibc][debian/2.33-0experimental0] Fix distribution

2021-09-05 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to tag debian/2.33-0experimental0 at GNU Libc Maintainers 
/ glibc


Commits:
627ce65a by Aurelien Jarno at 2021-09-06T07:08:48+02:00
Fix distribution

- - - - -


1 changed file:

- debian/changelog


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/627ce65a07293626284056b26216e76f6239861a

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/627ce65a07293626284056b26216e76f6239861a
You're receiving this email because of your account on salsa.debian.org.




[Git][glibc-team/glibc][glibc-2.33] Fix distribution

2021-09-05 Thread Aurelien Jarno (@aurel32)


Aurelien Jarno pushed to branch glibc-2.33 at GNU Libc Maintainers / glibc


Commits:
627ce65a by Aurelien Jarno at 2021-09-06T07:08:48+02:00
Fix distribution

- - - - -


1 changed file:

- debian/changelog


View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/627ce65a07293626284056b26216e76f6239861a

-- 
View it on GitLab: 
https://salsa.debian.org/glibc-team/glibc/-/commit/627ce65a07293626284056b26216e76f6239861a
You're receiving this email because of your account on salsa.debian.org.




<    2   3   4   5   6   7   8   9   10   11   >