Bug#992653: glibc breaks openconnect autopkgtest: FAIL: auth-nonascii
control: tag -1 patch
Hi,
On 2021-08-21 21:52, Paul Gevers wrote:
> Source: glibc, openconnect
> Control: found -1 glibc/2.31-16
> Control: found -1 openconnect/8.10-2
> Severity: serious
> Tags: sid bookworm
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: breaks needs-update
>
> Dear maintainer(s),
>
> With a recent upload of glibc the autopkgtest of openconnect fails in
> testing when that autopkgtest is run with the binary packages of glibc
> from unstable. It passes when run with only packages from testing. In
> tabular form:
>
>passfail
> glibc from testing2.31-16
> openconnectfrom testing8.10-2
> versioned deps [0] from testingfrom unstable
> all others from testingfrom testing
>
> I copied some of the output at the bottom of this report. Unfortunately,
> the log is rather brief.
>
> Currently this regression is blocking the migration of glibc to testing
> [1]. Due to the nature of this issue, I filed this bug report against
> both packages. Can you please investigate the situation and reassign the
> bug to the right package?
The openconnect auth-nonascii test uses two locales for its tests:
cs_CZ.UTF-8 and cs_CZ.ISO8859-2. It get those locales from the
locales-all package. Starting with glibc 2.31-14, non-UTF-8 locales are
deprecated and not provided anymore by locales-all. Therefore the test
fails as the cs_CZ.ISO8859-2 is not available anymore.
One option would simply be to disable the test with the cs_CZ.ISO8859-2
locale as done in the attached patch. If non-UTF-8 locales are not
supported anymore, I don't think we need to test them.
Also please note that while this new glibc broke the openconnect
testsuite, it didn't break openconnect itself which is still functional
from the user point of view. In that regard there is no need to declare
a Breaks: openconnect on the glibc side.
Regards,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
--- openconnect-8.10.orig/tests/auth-nonascii
+++ openconnect-8.10/tests/auth-nonascii
@@ -31,7 +31,7 @@ wait_server $PID
KEY=${srcdir}/certs/user-key-nonascii-password.p12
set -x
-for CHARSET in UTF-8 ISO8859-2; do
+for CHARSET in UTF-8; do
echo -n "Connecting to obtain cookie (with password charset ${CHARSET})... "
CERTARGS="-c ${KEY} --key-password $(cat ${srcdir}/pass-${CHARSET})"
( echo "test" | LC_ALL=cs_CZ.${CHARSET} LD_PRELOAD=libsocket_wrapper.so $OPENCONNECT -q $ADDRESS:443 -u test $CERTARGS --servercert=d66b507ae074d03b02eafca40d35f87dd81049d3 --cookieonly --passwd-on-stdin ) ||
signature.asc
Description: PGP signature
Processed: Re: Bug#992653: glibc breaks openconnect autopkgtest: FAIL: auth-nonascii
Processing control commands: > tag -1 patch Bug #992653 [src:glibc, src:openconnect] glibc breaks openconnect autopkgtest: FAIL: auth-nonascii Added tag(s) patch. -- 992653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992654: glibc breaks ruby-rugged autopkgtest: RemoteNetworkTest#test_remote_check_connection_push_credentials
tag: control -1 + unreproducible On 2021-08-21 22:00, Paul Gevers wrote: > Source: glibc, ruby-rugged > Control: found -1 glibc/2.31-16 > Control: found -1 ruby-rugged/1.1.0+ds-4 > Severity: serious > Tags: sid bookworm > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: breaks needs-update > > Dear maintainer(s), > > With a recent upload of glibc the autopkgtest of ruby-rugged fails in > testing when that autopkgtest is run with the binary packages of glibc > from unstable. It passes when run with only packages from testing. In > tabular form: > >passfail > glibc from testing2.31-16 > ruby-ruggedfrom testing1.1.0+ds-4 > versioned deps [0] from testingfrom unstable > all others from testingfrom testing Unfortunately I have not been able to reproduce this behaviour. In my testing, the autopktest failure happens already happen in pure testing (i.e. glibc 2.31-13), and it also appears with testing + glibc 2.31-16. I therefore don't believe glibc has anything to do with this failure. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: PGP signature
[Git][glibc-team/glibc][glibc-2.32] debian/testsuite-xfail-debian.mk: Update tests
Samuel Thibault pushed to branch glibc-2.32 at GNU Libc Maintainers / glibc Commits: e5ad157a by Samuel Thibault at 2021-08-21T23:17:48+02:00 debian/testsuite-xfail-debian.mk: Update tests - - - - - 2 changed files: - debian/changelog - debian/testsuite-xfail-debian.mk View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/e5ad157a8112a38b0481cdc468ee03e65bab2056 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/e5ad157a8112a38b0481cdc468ee03e65bab2056 You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/glibc][glibc-2.32] hurd: Complete MONOTONIC patch with timed locks.
Samuel Thibault pushed to branch glibc-2.32 at GNU Libc Maintainers / glibc Commits: 73ec4b2d by Samuel Thibault at 2021-08-21T21:57:53+02:00 hurd: Complete MONOTONIC patch with timed locks. * debian/patches/hurd-i386/local-clock_gettime_MONOTONIC.diff - - - - - 2 changed files: - debian/changelog - debian/patches/hurd-i386/local-clock_gettime_MONOTONIC.diff View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/73ec4b2d539e18608dac65c916aa910deb956c31 -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/73ec4b2d539e18608dac65c916aa910deb956c31 You're receiving this email because of your account on salsa.debian.org.
Bug#992654: glibc breaks ruby-rugged autopkgtest: RemoteNetworkTest#test_remote_check_connection_push_credentials
Source: glibc, ruby-rugged Control: found -1 glibc/2.31-16 Control: found -1 ruby-rugged/1.1.0+ds-4 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of glibc the autopkgtest of ruby-rugged fails in testing when that autopkgtest is run with the binary packages of glibc from unstable. It passes when run with only packages from testing. In tabular form: passfail glibc from testing2.31-16 ruby-ruggedfrom testing1.1.0+ds-4 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of glibc to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from glibc/2.31-16. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=glibc https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-rugged/14750518/log.gz autopkgtest [11:15:38]: test gem2deb-test-runner: [--- ┌──┐ │ Checking Rubygems dependency resolution on ruby2.7 │ └──┘ GEM_PATH= ruby2.7 -e gem\ \"rugged\" ┌──┐ │ Run tests for ruby2.7 from debian/ruby-tests.rb │ └──┘ mv lib .gem2deb.lib mv ext .gem2deb.ext RUBYLIB=. GEM_PATH= ruby2.7 debian/ruby-tests.rb Run options: --seed 56390 # Running: S....F... Finished in 16.209826s, 33.8683 runs/s, 144.0484 assertions/s. 1) Failure: RemoteNetworkTest#test_remote_check_connection_push_credentials [/tmp/autopkgtest-lxc.3h184rhw/downtmp/build.1At/src/test/remote_test.rb:40]: Expected false to be truthy. 549 runs, 2335 assertions, 1 failures, 0 errors, 5 skips You have skipped tests. Run with --verbose for details. mv .gem2deb.lib lib mv .gem2deb.ext ext autopkgtest [11:15:55]: test gem2deb-test-runner: ---] OpenPGP_signature Description: OpenPGP digital signature
Processed: glibc breaks ruby-rugged autopkgtest: RemoteNetworkTest#test_remote_check_connection_push_credentials
Processing control commands: > found -1 glibc/2.31-16 Bug #992654 [src:glibc, src:ruby-rugged] glibc breaks ruby-rugged autopkgtest: RemoteNetworkTest#test_remote_check_connection_push_credentials Marked as found in versions glibc/2.31-16. > found -1 ruby-rugged/1.1.0+ds-4 Bug #992654 [src:glibc, src:ruby-rugged] glibc breaks ruby-rugged autopkgtest: RemoteNetworkTest#test_remote_check_connection_push_credentials Marked as found in versions ruby-rugged/1.1.0+ds-4. -- 992654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992654 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992653: glibc breaks openconnect autopkgtest: FAIL: auth-nonascii
Source: glibc, openconnect Control: found -1 glibc/2.31-16 Control: found -1 openconnect/8.10-2 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of glibc the autopkgtest of openconnect fails in testing when that autopkgtest is run with the binary packages of glibc from unstable. It passes when run with only packages from testing. In tabular form: passfail glibc from testing2.31-16 openconnectfrom testing8.10-2 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Unfortunately, the log is rather brief. Currently this regression is blocking the migration of glibc to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from glibc/2.31-16. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=glibc https://ci.debian.net/data/autopkgtest/testing/amd64/o/openconnect/14748886/log.gz autopkgtest [07:17:01]: test upstream-test-suite: [--- PASS: auth-certificate FAIL: auth-nonascii PASS: auth-pkcs11 PASS: auth-username-pass PASS: id-test autopkgtest [07:17:36]: test upstream-test-suite: ---] OpenPGP_signature Description: OpenPGP digital signature
Processed: glibc breaks openconnect autopkgtest: FAIL: auth-nonascii
Processing control commands: > found -1 glibc/2.31-16 Bug #992653 [src:glibc, src:openconnect] glibc breaks openconnect autopkgtest: FAIL: auth-nonascii Marked as found in versions glibc/2.31-16. > found -1 openconnect/8.10-2 Bug #992653 [src:glibc, src:openconnect] glibc breaks openconnect autopkgtest: FAIL: auth-nonascii Marked as found in versions openconnect/8.10-2. -- 992653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989147: marked as done (glibc: CVE-2021-33574: mq_notify does not handle separately allocated thread attributes)
Your message dated Sat, 21 Aug 2021 20:14:52 +0200 with message-id and subject line Bug#989147: glibc: CVE-2021-33574: mq_notify does not handle separately allocated thread attributes has caused the Debian Bug report #989147, regarding glibc: CVE-2021-33574: mq_notify does not handle separately allocated thread attributes to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 989147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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 Hi, The following vulnerability was published for glibc, basically purely to track the upstream issue and fix once coming downstream. CVE-2021-33574[0]: | The mq_notify function in the GNU C Library (aka glibc) through 2.33 | has a use-after-free. It may use the notification thread attributes | object (passed through its struct sigevent parameter) after it has | been freed by the caller, leading to a denial of service (application | crash) or possibly unspecified other impact. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-33574 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33574 [1] https://sourceware.org/bugzilla/show_bug.cgi?id=27896 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- 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 > > > Hi, > > The following vulnerability was published for glibc, basically purely > to track the upstream issue and fix once coming downstream. > > CVE-2021-33574[0]: > | The mq_notify function in the GNU C Library (aka glibc) through 2.33 > | has a use-after-free. It may use the notification thread attributes > | object (passed through its struct sigevent parameter) after it has > | been freed by the caller, leading to a denial of service (application > | crash) or possibly unspecified other impact. > > > If you fix the vulnerability please also make sure to include the > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. > > For further information see: > > [0] https://security-tracker.debian.org/tracker/CVE-2021-33574 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33574 > [1] https://sourceware.org/bugzilla/show_bug.cgi?id=27896 > > Please adjust the affected versions in the BTS as needed. 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. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net--- End Message ---
[Git][glibc-team/glibc][glibc-2.32] Fix bug number
Aurelien Jarno pushed to branch glibc-2.32 at GNU Libc Maintainers / glibc Commits: f035fbbb by Aurelien Jarno at 2021-08-21T20:12:00+02:00 Fix bug number - - - - - 1 changed file: - debian/changelog View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/f035fd3ea22b4808cad24240e1bbc84bab0d -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/f035fd3ea22b4808cad24240e1bbc84bab0d You're receiving this email because of your account on salsa.debian.org.
glibc_2.32-0experimental0_source.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 21 Aug 2021 19:24:41 +0200 Source: glibc Architecture: source Version: 2.32-0experimental0 Distribution: experimental Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Aurelien Jarno Closes: 964477 Changes: glibc (2.32-0experimental0) experimental; urgency=medium . [ Aurelien Jarno ] * New upstream release: - Fixes a use-after-free in the mq_notify function (CVE-2021-33574). Closes: #964477. - debian/symbols.wildcard: add 2.32. - debian/patches/localedata/supported.diff: refresh. - debian/patches/localedata/git-unicode-13-support.diff: upstreamed. - debian/patches/amd64/git-x86_64-remove-pie-check.diff: upstreamed. - debian/patches/hurd-i386/git-fork-pthread_exit.diff: upstreamed. - debian/patches/hurd-i386/git-spin_lock.diff: upstreamed. - debian/patches/hurd-i386/git-barrier-1.diff: upstreamed. - debian/patches/hurd-i386/git-sem-intr.diff: upstreamed. - debian/patches/hurd-i386/git-register-atfork.diff: upstreamed. - debian/patches/hurd-i386/git-register-atfork2.diff: upstreamed. - debian/patches/hurd-i386/git-pthread_self.diff: upstreamed. - debian/patches/hurd-i386/git-trunc-times.diff: upstreamed. - debian/patches/hurd-i386/git-ss_init.diff: upstreamed. - debian/patches/hurd-i386/git-tst-udp.diff: upstreamed. - debian/patches/hurd-i386/git-pselect.diff: upstreamed. - debian/patches/hurd-i386/git-fexecve.diff: upstreamed. - debian/patches/hurd-i386/git-cond_destroy.diff: upstreamed. - debian/patches/hurd-i386/git-holes.diff: upstreamed. - debian/patches/hurd-i386/git-longjmp-onstack.diff: upstreamed. - debian/patches/hurd-i386/git-intr-msg-unwind.diff: upstreamed. - debian/patches/hurd-i386/git-strtol-test.diff: upstreamed. - debian/patches/hurd-i386/git-fix-longjmp.diff: upstreamed. - debian/patches/hurd-i386/git-pthread_atfork-hidden.diff: upstreamed. - debian/patches/hurd-i386/git-raise.diff: upstreamed. - debian/patches/hurd-i386/git-pthread_link_tests.diff: upstreamed. - debian/patches/hurd-i386/git-libpthread_syms.diff: upstreamed. - debian/patches/hurd-i386/git-libpthread-nodelete.diff: upstreamed. - debian/patches/hurd-i386/git-pthread_get_cleanup_stack.diff: upstreamed. - debian/patches/hurd-i386/git-libpthread-testcancel.diff: upstreamed. - debian/patches/hurd-i386/git-SEM_VALUE_MAX.diff: upstreamed. - debian/patches/hurd-i386/git-sigstate_thread_reference.diff: rebased. - debian/patches/hurd-i386/git-libpthread_plt.diff: rebased. - debian/patches/hurd-i386/git-lll-ptr.diff: rebased. - debian/patches/hurd-i386/git-ld-library-path-checks.diff: rebased. - debian/patches/hurd-i386/git-sem-pshared.diff: rebased. - debian/patches/hurd-i386/git-sem-open.diff: rebased. - debian/patches/hurd-i386/git-waitid.diff: rebased. - debian/patches/hurd-i386/tg-sendmsg-SCM_CREDS.diff: rebased. - debian/patches/hurd-i386/tg-EIEIO-fr.diff: rebased. - debian/patches/hurd-i386/tg-EGREGIOUS-fr.diff: rebased. - debian/patches/kfreebsd/submitted-auxv.diff: rebased. - debian/patches/all/local-remove-manual.diff: rebased. - debian/patches/any/local-bindresvport_blacklist.diff: removed, obsolete. - debian/patches/all/submitted-po-fr-fixes.diff: rebased. - debian/patches/any/local-ldso-disable-hwcap.diff: rebased. - debian/patches/any/local-nss-overflow.diff: rebased. - debian/patches/any/submitted-ld.so-cache-new-format.diff: upstreamed. - debian/patches/debian/patches/any/git-surplus-tls-accounting.diff: upstreamed. - debian/patches/any/git-ld.so-cache-endianness-markup.diff: rebased. - debian/patches/hurd-i386/unsubmitted-mremap.diff: removed, obsolete. * debian/patches/hurd-i386/git-sched_gets_hidden.diff: new patch from upstream to fix FTBFS on hurd-i386. Checksums-Sha1: b34f9501bee4a9fee10816e1e4c431ad015343c9 9810 glibc_2.32-0experimental0.dsc 7dd0eb395d505f6e044e5cbeb9f0206cb64a06ef 17339504 glibc_2.32.orig.tar.xz c5f574ba9d1f4b6ebb4567538b315e37c7b5ab6b 839212 glibc_2.32-0experimental0.debian.tar.xz 562a16038dd3913d6c2aea1ed01b758bfe35a7e7 8717 glibc_2.32-0experimental0_source.buildinfo Checksums-Sha256: d248873ed0139cb2341cdc441eaff74eba564a6da9f727d89afe646f3a8cc9de 9810 glibc_2.32-0experimental0.dsc 98367884c13188ae59a90b59a1628bb109f67fa14fceba42f0cbeb08412bb69c 17339504 glibc_2.32.orig.tar.xz 939859034b05824d8c73b717b6c78b311e02be731367bef3c2e0c28364cf36ed 839212 glibc_2.32-0experimental0.debian.tar.xz b0fd3acd33b8c84d76b9093d4960ba6165246b6d921d405218a1bff970a80143 8717 glibc_2.32-0experimental0_source.buildinfo Files: ed5ecca88f64eaab8017b8aaeb5dc893 9810 libs required glibc_2.32-0experimental0.dsc a2a63eb3c91647d2690a8afe3b39878e 17339504 libs required glibc_2.32.orig.tar.xz 4ceacd590d755f33dd2ca1ba6a397500
Processing of glibc_2.32-0experimental0_source.changes
glibc_2.32-0experimental0_source.changes uploaded successfully to localhost along with the files: glibc_2.32-0experimental0.dsc glibc_2.32.orig.tar.xz glibc_2.32-0experimental0.debian.tar.xz glibc_2.32-0experimental0_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Re: ARC rebootstrap prereq (was Re: switching ARC to 64-bit time_t )
Hi, On 2020-08-26 23:16, Aurelien Jarno wrote: > Hi Helmut, > > On 2020-08-26 17:43, Helmut Grohne wrote: > > Hi Vineet, > > > > On Wed, Aug 26, 2020 at 02:39:53PM +, Vineet Gupta wrote: > > > Following up as ARC glibc port was merged upstream in 2.32. Can we now > > > give > > > rebootstrap a spin for ARC Debian enablement. > > > > That's great news. Unfortunately, it's not that easy yet. rebootstrap > > requires the relevant software to be packaged for Debian and the glibc > > packaging has only reached 2.31 yet. 2.32 is not even in experimental > > yet. > > > > Trying rebootstrap with an experimental glibc is not entirely trivial, > > but possible. > > > > Aurelien (Cced via d-glibc@l.d.o), are there plans to upload 2.32 to > > experimental anytime soon? > > No it's not planned soon. glibc 2.32 has removed support for nsl and > rpc, so we first have to do the transition to their replacement. That is > libnsl, libnss-nis and libnss-nisplus for nsl, and rpcsvc-proto and > libtirpc3 for rpc. The nsl transition is in good state, but the packages > are stuck in NEW. We've started to work on the rpc transition, however > there is a lot more work, we have at least ~50 packages that FTBFS and > need to be manually patched to use libtirpc3 instead of the glibc > implementation. > > We definitely need to use experimental to test those two transitions and > ask for archive rebuilds, so it's not possible to upload a 2.32 package > there. > Now that the RPC transition is ongoing, I have just uploaded glibc 2.32 to experimental. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
[Git][glibc-team/glibc] Pushed new tag debian/2.32-0experimental0
Aurelien Jarno pushed new tag debian/2.32-0experimental0 at GNU Libc Maintainers / glibc -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/tree/debian/2.32-0experimental0 You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/glibc][glibc-2.32] releasing package glibc version 2.32-0experimental0
Aurelien Jarno pushed to branch glibc-2.32 at GNU Libc Maintainers / glibc Commits: 2aa53aa9 by Aurelien Jarno at 2021-08-21T19:25:00+02:00 releasing package glibc version 2.32-0experimental0 - - - - - 1 changed file: - debian/changelog View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/2aa53aa92fa50f6738f6e5e7cdb03f2dbb2ba05b -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/commit/2aa53aa92fa50f6738f6e5e7cdb03f2dbb2ba05b You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/glibc] Pushed new branch glibc-2.32
Aurelien Jarno pushed new branch glibc-2.32 at GNU Libc Maintainers / glibc -- View it on GitLab: https://salsa.debian.org/glibc-team/glibc/-/tree/glibc-2.32 You're receiving this email because of your account on salsa.debian.org.
