Uploaded, thanks (with some rich history as a bonus ;-) )
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/2083302
Title:
lvm2 ftbfs against autoconf 2.72
Status in lvm2 packa
** Changed in: lvm2 (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 lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/2083302
Title:
lvm2 ftbfs against autoc
** 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
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
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
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
** 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
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
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 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
=
*
** 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
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
** 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
** 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
** 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
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
** 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:
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
** 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
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
:
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
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
** 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:
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
** 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
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
** 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
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
** 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
** 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
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: 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
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
** 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
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
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
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
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
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
** 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
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
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
** 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
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
** Changed in: glibc (Ubuntu)
Status: Triaged => Fix Released
** Changed in: pango1.0 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.ne
So, after some fairly exhausting debugging, I kind of gave up on that
bug, but as a last ditch effort I tried a rebuild against the latest
snapshot (even though the changelog didn't seem particularly relevant),
nd... Now it builds.
I'm so tired.
--
You received this bug notificat
** Changed in: glibc (Ubuntu)
Importance: Undecided => Critical
** Changed in: glibc (Ubuntu)
Status: New => Triaged
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
** Tags added: foundations-todo
--
You received this bug notification be
I'm currently focused on cataloguing failures, but I'll try to
investigate it if nobody has picked it up by then.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2049881
Tit
Public bug reported:
Hi,
The package pango1.0 failed to build during the recent full archive test
rebuild against a snapshot of the the development branch for the
upcoming glibc 2.39, expected to land in Noble. This was subsequently
confirmed locally against a more recent snapshot.
Full logs for
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu)
Status: New => Triaged
** Changed in: glibc (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
Hi! Thanks for raising the issue.
Given the relative complexity of the patch and the low number of
affected people, I don't feel we should be shipping this as a Ubuntu-
specific patch. It might be a better idea for you to raise the issue on
the upstream ML, possibly amending the original patch to
sarnold, good point!
Holger: I can't pretend speaking for the SRU team, but I'd be willing to
bet that having "the fix is trivial" as a test plan would result in the
SRU being trivially rejected :-).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Reviewed and uploaded.
For the particular patch series attached to this very bug, I'm seeing
the patchset as two distincts parts. First are a few optimization
patches by being more selective in flushing some caches, whereas the
second part are behaviour changes that belong more in the realm of fix
Hi! Thank you for filing a bug and contributing to Ubuntu.
We're able to partially confirm this bug by simply having cloud-init
installed on our system and running `ubuntu-bug libc6`, which will start
off by printing 'cloud-init run data not found on system. Unable to add
cloud-specific data.' on
Little bit of data here. For some reason glib2.0 is thinking we're in a
GDB context and so is spitting out a SIGTRAP rather than the expected
SIGABRT, see
https://sources.debian.org/src/glib2.0/2.78.3-1/glib/gmessages.c/#L556
Now, why is it aborting I'm not too sure. The stack trace gives us a
hin
Hi again!
Thanks for filing the multiple detailed bugs, this is greatly
appreciated as it makes triaging much easier!
In this instance, I'm closing this as Invalid since this output isn't
directly apport/ubuntu-bug related, it's the output of some tools we're
invoking under the hood, and/or GTK b
Hi, thanks for taking the time to report this issue and contributing to
Ubuntu :)
I confirmed this issue (along with the one with firefox snap vs deb).
This is a bit bigger of an issue, as it means some non-privileged users
won't be able to report issues (or at least would give up as soon as the
Hi, thanks for taking the time to report this issue and contributing to
Ubuntu :)
I just confirmed on my system.
Since the number of transitional packages is fairly small, I think we
should just maintain a hardcoded list in Apport and hide the .deb by
default (with maybe a way to override this?)
** Changed in: openssl (Ubuntu Jammy)
Assignee: Adrien Nader (adrien-n) => Simon Chopin (schopin)
--
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/2033422
Ti
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
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
> 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
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
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
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
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
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
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
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
Looking at the code it seems to be affecting Lunar as well. I'm spinning
up a VM to confirm it (LXD containers are being difficult for this)
** Changed in: apport (Ubuntu)
Status: In Progress => Fix Committed
** Also affects: apport (Ubuntu Mantic)
Importance: High
Assigne
This was caused by the addition of this feature:
https://github.com/canonical/apport/pull/131
It broke an assumption that Dependencies was only added by the late
stage info collection, and said collection also had some other side-
effects that were relied upon to trigger the upload.
I'll create a
** Also affects: pastedeploy (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/2035337
Title:
dh-python: Cannot exclude
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1051837:
Source: dh-python
Version: 6.20230825
Severity: normal
X-Debbugs-Cc: scho...@ubuntu.com
We have a FTBFS on src:pastescript because its test suite embeds a
FakePlugin Python package, including its .egg-info, and the rec
Hi,
I'm sorry, I'm not entirely sure I understood that correctly, but if
you're looking for the apport sources, you can find them there:
https://github.com/canonical/apport
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to app
Hi,
Thanks for the patch. I took care of the LP metadata for the bug
(targetting the proper series), and unsubscribe ubuntu-sponsors since
it's not ready for upload yet. Please resubscribe ubuntu-sponsors once
you feel it's ready for upload.
@enr0n can you chime in on this, do we have things pend
I'll reiterate my point: the issue being discussed is a Green Linux
issue, this should be discussed wherever that distribution does its
development, and investigated by its developers. For the `apport` Ubuntu
package this is completely out of scope.
I'll also clarify our position as upstream Appor
Hi,
Thanks for taking the time to report the issue. I've tried to reproduce
the issue in Ubuntu in a fresh Jammy VM, without success, and the
provided logs don't really help us out.
However, it appears you're not using Ubuntu, but rather a derivative.
While we'd probably welcome patches in the up
This has been re-broken in the glibc package when upstream changed the
name of the actual ld.so binary, thus escaping the stripping exception.
I've fixed this in the git tree in preparation of the mantic upload.
There's currently a Jammy SRU in -proposed, I won't supersede it for
this fix since th
Hi,
Thanks for adressing Steve's comments, I uploaded the Jammy debdiff,
it's now in the SRU queue. I also unsubscribe ubuntu-sponsors, so if by
any chance there's a need to revisit this upload do remember to
subscribe it again :)
--
You received this bug notification because you are a member of
** Changed in: initramfs-tools (Ubuntu Jammy)
Status: Confirmed => In Progress
--
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/1983359
Title:
[SRU] hwrng dri
Quoting Thomas Hoffmann (2023-06-07 16:39:03)
> The repo file /usr/lib/python3/dist-packages/OpenSSL/crypto.py has the same
> reference to OpenSSL_add_all_algorithms but it doesn't seem to cause a
> problem.
That's because it uses the distro python3-cryptography, which provides
the problematic fu
Hi,
In addition to what Adrien asks, could you show us the version of
python3-cryptography you're using? The bindings used by pyOpenSSL are
actually provided by the cryptography package. Also, could you make sure
you don't have a local version of said code in /usr/local, similar to
your PyOpenSSL
Quoting Steven R. Loomis (2023-04-12 17:30:25)
> What ICU is this? I can't tell which version from here. Your analysis
That'd be 72.1-3ubuntu1, now ubuntu2 with this patch. This bug was
mostly for reference for the folks in the Ubuntu release team since
we're in feature freeze, almost at final fre
Public bug reported:
During the last test rebuild, it was noticed that icu failed to build
from source, with the following failures in the test suite:
-
| *** FAILING TEST SUMMARY FOR: intltest
TestAliasedNames
TestCanonicalID
TimeZoneTest
Public bug reported:
There's been a bunch of security patches to the Kinetic version of vim,
those need to be applied to Lunar as well:
* CVE-2033-0433
* CVE-2023-1170
* CVE-2023-1175
* CVE-2023-1264
In addition, the following only affect the version in Lunar:
* CVE-2023-0512
* CVE-2023-1127
*
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
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
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
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
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:
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.
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
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
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
** Tags added: fr-2936
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1995601
Title:
tzdata 2022f ICU data update
Status in tzdata package in Ubuntu:
Triaged
Status in t
Public bug reported:
The ICU data we embed in tzdata was out of sync on the 2022f-0ubuntu1
upload, still matching the 2022e data instead. It's been updated
upstream, so we need to do another round of SRUs for it:
https://github.com/unicode-org/icu-
data/commit/ad9d2568d02b2130f1ba34f876fc82cad32c
All verifications done (except for ICU data which wasn't ready) on
bionic, focal, jammy and kinetic using fresh LXC containers and the
instructions from
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984 adjusted
for the new data updates.
** Tags removed: verification-needed verificatio
Folded into the LP #1990379 uploads to Jammy, Kinetic and Lunar.
** Also affects: zlib (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: zlib (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Uploaded to Lunar, Kinetic, Jammy and Focal
--
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/1990379
Title:
[UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC
1 - 100 of 298 matches
Mail list logo