Hi!
Thank you for taking the time to report this. Could you confirm on which
version of Ubuntu you're seeing this issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libtimezonemap in Ubuntu.
https://bugs.launchpad.net/bug
** Also affects: python3.12 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
-debian/rules override_dh_auto_test
+ [Description]
+
+ Python 3.12 gzip.GZipFile.write() outputs truncated data in some cases
+ (maybe all?)
+
+ [Test Plan]
+
+ Run the following scrip
After further investigations into the gzip issue in python 3.12, it
turns out there was an undocumented change: it is now a buffered writer.
So the fire&forget pattern used in the snippet above doesn't work
anymore, we now need to use it as a proper IO object instead.
I still think this should be
Public bug reported:
The autopkgtests for liblocale-gettext-perl fail against glibc 2.39 with
the following errors:
autopkgtest [15:27:03]: test autodep8-perl-build-deps: [---
243s t/bind.t ...
243s 1..1
243s # Running under perl version 5.036000 for linux
243s # Current
** Tags added: foundations-todo
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: glibc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
We had a mitigation for this in glibc but the latest change from simply
denying the unshare() call to allowing it but then denying anything
requiring capabilities *presumably* broke the glibc test suite again.
I'm only basing this from looking at the test logs, as I'm temporarily
unable to run auto
Public bug reported:
As a header to all .conf files in systemd there's a comment saying
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file (or a copy of it placed in
# /etc/ if the original file is shipped in /usr/), or by
Public bug reported:
Release of Ubuntu: Noble
Package Version: 5.72-0ubuntu1
My headset changed profile from A2DP to HSP as I received a phone call on my
phone (the headset can connect to multiple BT devices).
I'd expect the system to adapt to the new profile (add a new source, change the
prope
Unless I'm missing something, the issue you're linking is about glib,
not glibc. Reassigning the bug accordingly.
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notification becau
It turns out the fix was already in the upstream repo as a PR for a
while (couple of years?). I've submitted a Salsa MR to proactively
address the issue before it shows up there:
https://salsa.debian.org/perl-team/modules/packages/liblocale-gettext-
perl/-/merge_requests/1
and I've uploaded the s
** Changed in: glibc (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to liblocale-gettext-perl in
Ubuntu.
https://bugs.launchpad.net/bugs/2052930
Title:
liblocale-gettext-perl autopkg
Oh, hang on. The bash build has apparently been uploaded just a day
after the t64 gcc, which means gcc was presumably still building when
the bash build started:
gcc-13 armhf 13.2.0-13ubuntu1 (from the bash build logs)
A bash rebuild should "fix" this somewhat. Well, at least a little bit.
** Al
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on armhf,
- and possibly on all archs.
+ click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on ppc64el,
+ s390x.
- armhf
What now remains to be done is to heavily patch faketime to, when on
armhf:
1/ use the proper symbols from glibc (e.g. __clock_gettime64 instead of
__clock_gettime)
2/ expose those symbols instead of the legacy 32-bit ones.
--
You received this bug notification because you are a member of Ubunt
** Also affects: apport-symptoms (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu)
Status: New => Invalid
** Description changed:
Apport version: 2.28.0-0ubuntu1
Ubuntu-Server 24.04 Beta amd64 (20240410.1)
- See attached screenshot for error.
+ /us
** Changed in: shadow (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2063200
Title:
useradd --extraus
Quick repro steps:
❯ lxc launch ubuntu-daily:noble shadow
Creating shadow
Starting shadow
❯ lxc exec shadow bash
root@shadow:~# mv /etc /etc_write
root@shadow:~# mkdir /etc
root@shadow:~# mount -o bind,ro /etc_write /etc
root@shadow:~# useradd --extrausers --groups somegroup somenewuser
useradd: c
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2063200
Title:
useradd --extrausers --groups tries to lock /etc/group
Status in shadow packa
The issue was introduced with https://github.com/shadow-
maint/shadow/pull/237
Basically, the previous group validation was done using glibc's getgrid
directly, which was presumably coping well with the RO status of
/etc/group, but that poses consistency problems because you could add a
local user
** Description changed:
- openssl.cnf as provided misses some directive, which make it a bit
- difficult to change security level, which since openssl 3 disables SHA1
- signatures.
+ [Impact]
+
+ The OpenSSL 3.0 lead to a lot of broken setups. Some of them are
+ regressions, but others are simply
** Description changed:
+ [Impact]
+
+ The TLS test server `openssl s_server` can very easily be led into an
+ infinite loop if configured with incompatible settings and used via
+ DTLS. This makes it harder to test one's TLS configuration.
+
+ [Test plan]
+
+ In one session:
+ $ openssl s_serv
Public bug reported:
Some certificates in the openssl package expired on 2022-06-01, making
the test suite fail.
** Affects: openssl (Ubuntu)
Importance: Critical
Status: Confirmed
** Affects: openssl (Ubuntu Bionic)
Importance: Undecided
Status: New
** Affects: open
** Summary changed:
- openssl: FTBFS due to missing certificates
+ openssl: FTBFS due to expired certificates
** Tags added: ftbfs
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net
** Description changed:
+ [Impact]
+
Some certificates in the openssl package expired on 2022-06-01, making
- the test suite fail.
+ the test suite fail. This needs to be fixed to facilitate future
+ security updates.
+
+ [Test Plan]
+
+ Build the package. It currently fails with the followin
** Tags added: block-proposed-bionic block-proposed-focal block-
proposed-impish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1978093
Title:
openssl: FTBFS due to expire
** Tags added: fr-2459
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1978129
Title:
Incomplete support for DT_RELR relocations on Ubuntu 22.04
Status in The Ubuntu-powe
-6ubuntu2 is the version that will get to Jammy (22.04), 9ubuntu1 is the
version currently in the devel series (future Kinetic, 22.10).
In general it is preferable to use the version compiled for your current
series, even though using the one in -devel might make sense in a
testing context, as was
https://launchpad.net/ubuntu/+source/openssl/3.0.2-0ubuntu1.4 builds
fine, marking it as jammy-verified.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
You'll need to contact your provider. I'm guessing their script isn't
compatible with OpenSSL 3.0, but without more information (such as the
stdout/stderr of the openssl CLI invocation here) there isn't much we
can do on this end.
Whatever the precise issue though, it's almost certainly NOT relate
Just to confirm, on a fresh LXC Jammy container:
root@rational-polliwog:~# dpkg -l openssl | tail -n 1
ii openssl3.0.2-0ubuntu1.4 amd64Secure Sockets Layer toolkit -
cryptographic utility
root@rational-polliwog:~# grep SECLEVEL /etc/ssl/openssl.cnf
CipherString = DEFAULT:@SECLEVE
On a fresh Jammy LXC container:
root@rational-polliwog:~# dpkg -l openssl | tail -n 1
ii openssl3.0.2-0ubuntu1.4 amd64Secure Sockets Layer toolkit -
cryptographic utility
root@rational-polliwog:~# openssl s_server -nocert -psk 01020304 -dtls1
Using default temp DH parameters
ACCE
On a fresh Jammy LXC container:
root@rational-polliwog:~# dpkg -l libssl-dev | tail -n 1
ii libssl-dev:amd64 3.0.2-0ubuntu1.4 amd64Secure Sockets Layer toolkit
- development files
root@rational-polliwog:~# cat < openssl_test.c
#include
int main()
{
EVP_PKEY_Q_keygen(NULL, NULL, "EC"
*** This bug is a duplicate of bug 1940141 ***
https://bugs.launchpad.net/bugs/1940141
** This bug has been marked a duplicate of bug 1940141
OpenSSL servers can send a non-empty status_request in a CertificateRequest
--
You received this bug notification because you are a member of Ubunt
I'm just watching from the sidelines here, but why do we need to have
a transition for this? Is there an ABI break I'm not aware of? Or is zlib
usually statically linked in Debian packages?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is su
** Description changed:
+ [Impact]
+ While the default configuration works fine for every package that uses the
system libssl3, any software that uses libssl1.1, either separately packaged
(e.g. as an upgrade leftover) or vendored in (as in nodejs in our own archive)
will fail to load the conf
** Tags added: fr-2537
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nettle in Ubuntu.
https://bugs.launchpad.net/bugs/1959469
Title:
[22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)
Status in Ubuntu on IB
Many thanks for raising this :)
I was prepared to argue for this change as (if working as intended) it
has basically no impact on our own applications and could help quite a
few unsuspecting users, but since you asked for evidence I did a little
digging, and was somewhat surprised by what I found.
** Description changed:
- [Impact]
- While the default configuration works fine for every package that uses the
system libssl3, any software that uses libssl1.1, either separately packaged
(e.g. as an upgrade leftover) or vendored in (as in nodejs in our own archive)
will fail to load the conf
Public bug reported:
When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often (pretty
much always) a crash from tracker-extract, as described in the following
error report:
https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0
The crash occurs during the upgrade, which mean
** Package changed: tracker (Ubuntu) => tracker-miners (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1983859
Title:
tracker-extract crashes with SIGSYS when upgr
Public bug reported:
We need to merge the new version from Debian, notably because of
CVE-2022-2097 (the other security issue already being fixed as a cherry-
picked patch)
** Affects: openssl (Ubuntu)
Importance: High
Assignee: Simon Chopin (schopin)
Status: Confirmed
** Changed in: openssl (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1987047
Title:
openssl: merge 3.0.5-2 from Debian un
Public bug reported:
Merge new upstream version into kinetic.
** Affects: libvpx (Ubuntu)
Importance: High
Assignee: Simon Chopin (schopin)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Changed in: libvpx (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1987051
Title:
libvpx: merge 1.12.0-1 from Debian
Uploaded, thanks :)
** Changed in: p11-kit (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1982841
Title:
[22.10 FEAT]
Public bug reported:
Hi,
lxc currently fails to build against glibc 2.36, which also affects its
autopkgtests. Here's an excerpt of the failed build logs containing the
first error detected:
gcc -DHAVE_CONFIG_H -I. -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE
-Wvla -std=gnu11 -fms-extens
Yup, I cherry-picked the patches already, thanks for those :).
I'm tracking down a build failure on ppc64el that's presumably caused by
gcc-12 on -O3, and once I have a solve (other than forcing -O2) I'll
post it all here.
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- Availability of tzdata 2022c for Ubuntu 20.04
+ [FFe] tzdata 2022c update
** Description changed:
- tzdata 2022b and 2022c were just released that includes some timezone
- changes for Chile. According to the tzdata lib listed for Ubuntu 20.04,
- the latest package is 2022a.
This update has been prepared in the following PPA:
https://launchpad.net/~schopin/+archive/ubuntu/tzdata
The kinetic upload has been prepared as a full merge from Debian,
however I kept the other series' diff as small as possible by doing a
plain "upstream update". Notably, I didn't pick up the D
** Changed in: tzdata (Ubuntu Kinetic)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Focal)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Bionic)
Importance: Undecided => High
** Changed i
Public bug reported:
Imported from Debian bug http://bugs.debian.org/984297:
Package: src:presage
Version: 0.9.1-2.2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue op
*** This bug is a duplicate of bug 1986984 ***
https://bugs.launchpad.net/bugs/1986984
** This bug has been marked a duplicate of bug 2022
iso-codes is not available for breezy
** This bug is no longer a duplicate of bug 2022
iso-codes is not available for breezy
** Description changed
Apologies for the metadata bug traffic, I hadn't realized there were
duplicates, and actually use different bug numbers in the SRU and devel
uploads. Marking this manually as released on Kinetic, as the SRU
uploads use this bug number.
** Changed in: tzdata (Ubuntu Kinetic)
Status: Triaged
I verified the upload on Jammy, Focal and Bionic via fresh LXC
containers, using the attached script.
For the ESM releases, it has been handled by sbeattie from the Security
Team. As I understand, the packages are already available in the ESM
security PPA (I don't have access to it).
** Attachmen
Hi!
I apologize, I thought I'd sent here the gameplan for the issue, but it
must have only been discussed out of band within the team. As noted by
Robie, the consensus is not to change the default configuration, but
instead patching node.js on Jammy (patches welcome for that one though).
I've alr
@dragu-stelian, you do not have the same issue. Looking at your logs, it
seems your client cannot reach your server over the network. This is not
related to openssl. If it were, the issue would manifest no matter from
where you're attempting to connect.
--
You received this bug notification becau
I just tried it on all releases up to Kinetic, they're all affected. I
suspect it's actually a bug in systemd-networkd, as the files generated
in /run/systemd/networkd/ look sane enough:
root@firm-mayfly:~# cat /run/systemd/network/10-netplan-eno1.network
[Match]
MACAddress=00:16:3e:10:7a:c2
Type
** Changed in: apport
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2068933
Title:
all reports with LaunchpadPrivate in them are tagged
Public bug reported:
Despite the distribution having enabled frame pointers globally, the
binaries shipped by libdmapsharing don't have frame pointers.
It is likely due to the build system being pretty screwed up: it builds
the library once using the CFLAGS, then rebuilds it with custom flags
for
** Merge proposal linked:
https://code.launchpad.net/~hectorcao/ubuntu/+source/shadow/+git/shadow/+merge/469556
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2073338
Tit
Public bug reported:
To help in the development of apport we're using the chaos-marmosets set
of binaries, which triggers various crashes. In particular, we're using
/usr/bin/divide-by-zero which does as its name indicates, which
naturally triggers a native crash.
However, GDB fails on s390x. Not
:
package: sbuild-build-depends-main-dummy
version: 0.invalid.0
architecture: s390x
unsat-dependency: gcc-multilib:s390x
** Affects: zlib (Ubuntu)
Importance: High
Assignee: Simon Chopin (schopin)
Status: New
** Tags: foundations-todo
--
You received this bug
This feature should be postponed to the 2.31 version (i.e. the 25.04
cycle), as we don't fully understand the typical usage patterns of
apport-retrace. We're talking about a substantial change, and having it
targeted to 2.30 (which needs to be cut in the coming two weeks) would
be rushing it, even
** Changed in: zlib (Ubuntu)
Importance: Undecided => Critical
** Changed in: zlib (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: zlib (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Tou
Frank, can you confirm that you got in touch with the upstream author
about it?
I probably could "fix" it by sprinkling casts all over the place, which
could be wildly unsafe depending on the exact properties of __int128, or
by actually using a local __int128 variable and memcpy it or something
li
** Also affects: gcc-14 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: ftbfs update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/2075567
Title:
This is fixed by doko in 1:1.3.dfsg-3.1ubuntu3 but it's currently stuck
in -proposed due to bug 2075567
** Changed in: zlib (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in
** Changed in: zlib (Ubuntu)
Assignee: Ravi Kant Sharma (ravi-sharma) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/2073992
Title:
Ple
** Changed in: zlib (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/2073992
Title:
Please merge zlib 1:1.3.dfsg+really1.3.1-1 into
** Merge proposal linked:
https://code.launchpad.net/~hectorcao/ubuntu/+source/shadow/+git/shadow/+merge/471145
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2076898
Tit
Public bug reported:
In particular, testing against a version of glibc in -proposed will fail
with the following error:
3784s libc6-dbg : Depends: libc6 (= 2.39-0ubuntu9) but 2.40-1ubuntu1 is
to be installed
(2.39-0ubuntu9 is the version in the release pocket, 2.40-1ubuntu1 is
the one in -propo
** Changed in: shadow (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2076898
Title:
Numeric name is accepted as valid u
I checked the gcc packages, and indeed the lib32z1-dev dependency has
been fixed, including in the oracular release pocket. I think we're
hitting a bug in reverse-depends, since it shows up even for riscv64:
❯ reverse-depends -b -a riscv64 lib32z1-dev
Reverse-Build-Depends
=
*
zlib has just migrate to the release pocket (along with glibc), closing
this bug.
** Changed in: zlib (Ubuntu)
Status: In Progress => Fix Released
** Changed in: glibc (Ubuntu)
Status: Incomplete => Invalid
** Tags removed: update-excuse
--
You received this bug notification beca
I looked at the s390-tools build logs and have verified that the -fno-
omit-frame-pointer flags that were present in the previous build are now
gone on both ppc64el and s390x but not on amd64. In addition,
-mbackchain is present on s390x.
--
You received this bug notification because you are a me
** Bug watch added: Debian Bug tracker #1077804
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077804
** Also affects: fink via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077804
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
FWIW, it's not a regression as the behaviour is the same in Focal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2077883
Title:
usermod silently fails modifying group memb
Hi,
Thanks for taking the time to report this issue.
Presumably, your boost.asio was not built against the libssl-dev headers
provided in Ubuntu, since in that version those function names aren't
provided as symbols but rather as preprocessor aliases to the more
modern TLS_* alternatives (see
htt
See https://github.com/linux-pam/linux-pam/blob/master/NEWS -> release
1.5.3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2077712
Title:
lastlog does not capture all logi
** Changed in: systemd (Ubuntu Oracular)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2044104
Title:
[UBUNTU 20.04] chzdev -e is rebuil
Looking at the logs, this bug seems rather to be in
/usr/share/perl5/Debconf/Db.pm, which is in debconf. Reassigning it
there.
** Also affects: debconf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notif
Hi!
Seeing this line:
Unpacking libssl-dev:i386 (3.0.2-0ubuntu1.7) over (1.0.1f-1ubuntu2.27)
makes me think you either are trying to upgrade directly from Trusty
(which would be weird given your install medium is Jammy), or have
third-party packages on your system, most likely installed through
Public bug reported:
The nipype autopkgtests have started failing with the following stack
trace:
ERROR collecting pipeline/plugins/tests/test_tools.py _
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], packag
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1028603:
Package: dh-python
Version: 5.20221001
Severity: normal
X-Debbugs-Cc: scho...@ubuntu.com
For instance, pylint has "tomli>=1.1.0;python_version<'3.11'" in its
pyproject.toml, which is translated as "python3-tomli (>= 1.
Uploaded, thanks :)
** Changed in: p11-kit (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/2003548
Title:
Merge Debian unstabl
Public bug reported:
Hi,
During a mass rebuild of Lunar, the package libunistring failed to build
against a snapshot of the upcoming glibc 2.37, while building fine using
2.36 as present in the archive.
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-glibc-2.37-luna
The failure is in a gnulib test. I've bisected it to the following glibc
upstream commit:
https://sourceware.org/git/?p=glibc.git;a=commit;h=642933158e7cf072d873231b1a9bb03291f2b989
The issue has been reported upstream.
** Bug watch added: Sourceware.org Bugzilla #30065
https://sourceware.org
The issue has been fixed upstream just before the final 2.37 release,
thus closing this.
** Changed in: libunistring (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunistring in
Uploaded, thanks!
** Changed in: openssl (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/2006954
Title:
openssl: merge unstabl
No upgrade log present (probably fresh install)
** Changed in: apport (Ubuntu Lunar)
Assignee: Benjamin Drung (bdrung) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https
Verified in a fresh Lunar VM.
** Tags removed: verification-needed verification-needed-lunar
** Tags added: verification-done verification-done-lunar
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://b
I am not going to upload this, because I'm widely uncomfortable with bug
1990216 (details there).
In addition, I have a few superficial suggestions for aesthetics:
* Use lpX subdirectories in d/patches rather than add a prefix to the
patchname
* Add a Bug-Ubuntu field with a LP URL to each p
I'm very much against uploading this fix as an SRU. While it is a shame
that we have interop problems with the rest of the world, fixing this in
Jammy right now means we *will* break production for anyone that stores
Blowfish-encrypted data.
Doing `apt upgrade` on a production server is supposed t
In addition, could the test plan maybe be edited to answer the following
question?
"How can one validate that the package in -proposed addresses the
issue?"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
h
A version containing a fix for this has been uploaded to the Jammy queue
to be processed by the SRU team. Thanks, Adrien :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/203
A version containing a fix for this has been uploaded to the Jammy queue
to be processed by the SRU team. Thanks, Adrien :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/202
A version containing a fix for this has been uploaded to the Jammy queue
to be processed by the SRU team. Thanks, Adrien :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/199
> I don't know why LP expired this bug since you commented after I changed
> the its status...
AFAIK, LP will not switch back the status to anything after a comment has been
left. That makes sense, as it wouldn't know what the new status is
supposed to be.
--
You received this bug notification b
How about directly sending a SIGSEGV or a SIGABRT to a working
teamviewer process using kill(1) ? That's what I usually do when I test
apport crash reporting code, this might trigger the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
Tagging this to discuss this during the Foundations weekly meeting
** Tags added: rls-ff-incoming rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2044
1 - 100 of 367 matches
Mail list logo
