Ubuntu 20.10 (Groovy Gorilla) reached its End of Life on July 22 2021,
hence I'm updating the groovy entry of this ticket - and with that the
overall ticket status.
** Changed in: glibc (Ubuntu Groovy)
Status: Fix Committed => Won't Fix
** Changed in: ubuntu-z-systems
Status: Fix Co
** Changed in: glibc (Ubuntu Groovy)
Assignee: Balint Reczey (rbalint) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904419
Title:
Upgrade glibc 2.32 by required upstream patch
** Tags removed: block-proposed-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904419
Title:
Upgrade glibc 2.32 by required upstream patches
To manage notifications about this bug go to:
htt
Thx, I'm updating the tags accordingly ...
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Hello bugproxy, or anyone else affected,
Accepted glibc into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.32-0ubuntu3.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
** Tags added: block-proposed-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904419
Title:
Upgrade glibc 2.32 by required upstream patches
To manage notifications about this bug go to:
https
Thx for the verification, I'm adjusting the tags accordingly.
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notificati
Hello bugproxy, or anyone else affected,
Accepted glibc into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.32-0ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
** Changed in: ubuntu-z-systems
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904419
Title:
Upgrade glibc 2.32 by required upstream patches
To manage notifica
** Changed in: glibc (Ubuntu Groovy)
Status: New => In Progress
** Changed in: glibc (Ubuntu Groovy)
Assignee: Canonical Foundations Team (canonical-foundations) => Balint
Reczey (rbalint)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Ok, just wanted to be sure - this will justify a glibc SRU.
(clicking the bug number earlier opened it as LP bug, which is
wrong and is usually an indicator for me that it's an internal IBM BZ number -
but I've found the glibc upstream BZs now
thx ...)
I've created a first SRU justification ba
--- Comment From s...@de.ibm.com 2020-12-11 10:43 EDT---
It has nothing to do with a performance improvement. It's just broken. Thus
your Ubuntu 20.10 has a regression compared to Ubuntu 20.04! The issues were
reported via glibc-upstream bugzillas:
- "Bug 26636 - 32-bit shmctl(IPC_INFO) c
Ok, so the following two topics remain:
1)
"Fixing unneeded extra conversion of IPC_INFO and SHM_INFO for __IPC_TIME64,
since their information does not contain any time related fields."
Fixed with:
commit "sysvipc: Fix IPC_INFO and SHM_INFO handling [BZ #26636]"
(https://sourceware.org/git/?p=g
But we don't use nss_resolve from libc6 by default, we use systemd-
resolved. Do we need the resolv fixes? (i.e. transaction IDs are handled
by resolved)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
--- Comment From s...@de.ibm.com 2020-12-10 10:23 EDT---
The sysvipc related bugs were introduced with glibc 2.32 and are fixed upstream
and will be included in upcoming glibc 2.33 release. In addition those commits
were also cherry-picked to the release/2.32/master branch. Therefore no u
Regarding the original question we don't automatically follow the
release branches in stable releases especially not in interim releases
which have only 9 months of support.
I'm collecting patches for an upcoming SRU for Focal and Groovy, and the
patches listed here can be included as well, but to
** Summary changed:
- Ugrade glibc 2.32 by required upstream patches
+ Upgrade glibc 2.32 by required upstream patches
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904419
Title:
Upgrade glibc 2.3
17 matches
Mail list logo
