** Changed in: glibc (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851263
Title:
Ubuntu 18.04.3 LTS bump Glibc 2.27 to the latest stable
To
** Description changed:
[Impact]
* Ubuntu 18.04 is missing various stability and performance fixes that
have been added to upstream's 2.27 branch. The accumulated changes are
known to fix various issues already reported to Launchpad.
[Test Case]
* Observe that
** Description changed:
[Impact]
* Ubuntu 18.04 is missing various stability and performance fixes that
have been added to upstream's 2.27 branch. The accumulated changes are
known to fix various issues already reported to Launchpad.
[Test Case]
* Observe that
** Description changed:
[Impact]
* Ubuntu 18.04 is missing various stability and performance fixes that
have been added to upstream's 2.27 branch. The accumulated changes are
known to fix various issues already reported to Launchpad.
[Test Case]
* Observe that
This bug was fixed in the package glibc - 2.27-3ubuntu1.3
---
glibc (2.27-3ubuntu1.3) bionic; urgency=medium
[ Balint Reczey ]
* debian/gbp.conf: Add initial configuration
* debian/control.in/main: Add Vcs-* pointing to Ubuntu packaging repository
* arm64: Enable searching
The verification of the Stable Release Update for glibc has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
** Tags removed: block-proposed
** Tags added: block-proposed-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851263
Title:
Ubuntu 18.04.3 LTS bump Glibc 2.27 to the latest stable
To manage
Setting block-proposed to pick the right time to land the update.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851263
Title:
Ubuntu 18.04.3 LTS bump Glibc 2.27 to
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verified 2.27-3ubuntu1.3 on Bionic:
* Observe that debian/patches/git-updates-2.diff contains the missing
upstream commits intended to be backported.
Done.
* Observe the patch being applied at build time.
I've verified that at least my issue is resolved by this:
```
docker run -it --rm ubuntu:18.04
apt update
apt install g++ wget
wget https://sourceware.org/bugzilla/attachment.cgi?id=11382 -O bug23861.c
sed -i 's/do_exit = 0/do_exit(0)/' bug23861.c
g++ bug23861.c -lpthread -o bug23861
for
** Description changed:
[Impact]
* Ubuntu 18.04 is missing various stability and performance fixes that
have been added to upstream's 2.27 branch. The accumulated changes are
known to fix various issues already reported to Launchpad.
[Test Case]
* Observe that
Hello Romain, or anyone else affected,
Accepted glibc into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.27-3ubuntu1.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ [Impact]
+
+ * Ubuntu 18.04 is missing various stability and performance fixes that
+ have been added to upstream's 2.27 branch. The accumulated changes are
+ known to fix various issues already reported to Launchpad.
+
+ [Test Case]
+ * Observe that
Hello,
Le 02/09/2020 à 17:14, Balint Reczey a écrit :
> There is a new Bileto PPA with the most likely final SRU:
>
> https://launchpad.net/~ci-train-ppa-
> service/+archive/ubuntu/4242/+packages
>
I installed the ppa and tested the glibc 2.27-3 package.
I can confirm the issue #1851263 can't
There is a new Bileto PPA with the most likely final SRU:
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4242/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851263
Title:
The SRU is being pre-tested in https://bileto.ubuntu.com/#/ticket/4217 .
There are a low number of test failures which could indicate regressions, those
are being checked and fixed if needed before the upload to the archive.
Additional testing is welcome.
--
You received this bug notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glibc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851263
Title:
Hi Adam,
Thanks for your feedback.
Do you have any info (date) about the work in progress to update Glibc 2.27 for
Ubuntu 18.04?
Best regards,
Romain
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There is an intent to rebase to 2.27/master, yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851263
Title:
Ubuntu 18.04.3 LTS bump Glibc 2.27 to the latest stable
To manage notifications about
Hi Loïc,
You're welcome.
Yes, I understand that glibc is a critical piece and we need to do the
upgrade carefully.
With my customer, we tested with several ubuntu versions:
ubuntu 14.04: glibc 2.19: OK
ubuntu 16.04: glibc 2.23: OK
ubuntu 18.04: glibc 2.27: KO
ubuntu 18.10: glibc 2.28: OK
Only
I think what Romain is asking is to rebase along release/2.27/master,
and not a different upstream version. If you don't do that, you have to
evaluate each upstream commit individually for backporting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Romain and thanks for your report,
In general, we don't make large upstream updates after release, especially for
LTS and even more so for a critical piece like glibc. If you've identified the
single patch that would address your issue, it can be considered for the SRU
process:
23 matches
Mail list logo
