>From your logs, I see this:
apt remove --purge python3.*
I'm sorry, but that will break your system.
** Changed in: python3-defaults (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Unless we want to be specific about ubuntu-specific proxy settings, when
the test runs in our infrastructure.
--
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/2106664
Title:
This was further troubleshooted this morning, and was a problem with
proxy settings in the test bed in the plucky image being used. This has
since been fixed.
I don't think further action is needed here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
Public bug reported:
I'm seeing a lot of these lately[1]:
4268s + mkosi_tree=/tmp/autopkgtest.9oT0q6/autopkgtest_tmp/mkosi
4268s + git clone https://github.com/systemd/mkosi.git
/tmp/autopkgtest.9oT0q6/autopkgtest_tmp/mkosi
4268s Cloning into '/tmp/autopkgtest.9oT0q6/autopkgtest_tmp/mkosi'...
4
> Algorithms missing in "APT::Key::Assert-Pubkey-Algo" cause errors now,
> whereas algorithms in
> "APT::Key::Assert-Pubkey-Algo::Next" cause warnings.
The word "missing" is, er, missing, in the second part of that sentence,
right? The full correct sentence is (diff capitalized by me):
Algori
# Noble verification
Problem reproduced with:
$ apt-cache policy rsyslog
rsyslog:
Installed: 8.2312.0-3ubuntu9
Candidate: 8.2312.0-3ubuntu9
Version table:
*** 8.2312.0-3ubuntu9 500
500 http://br.archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
[M
Hello Benjamin, or anyone else affected,
Accepted tzdata into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2025b-0ubuntu0.20.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Normally we don't release SRUs which just include a DEP8 fix, like
exchange-calendars, specially given that that fix is skipping the
troublesome test. There is some movement in the upstream issue[1], is
that something we could apply to this package instead of skipping the
test? Otherwise, perhaps a
The verification of the Stable Release Update for rsyslog 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
The verification of the Stable Release Update for rsyslog 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
The verification of the Stable Release Update for tzdata 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 r
Early releasing tzdata due to impending real world timezone change[1].
1.
https://matrix.to/#/!slcYrFqWytcsbPzMxA:ubuntu.com/$6knNQEJPWkAU2vSpblFW9lkBaWrHQWExERBkjLRDVmA?via=ubuntu.com&via=matrix.org&via=matrix.debian.social
--
You received this bug notification because you are a member of Ubun
The verification of the Stable Release Update for rsyslog 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
The verification of the Stable Release Update for rsyslog 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
Public bug reported:
I came here following
https://wiki.ubuntu.com/i386#How_to_expand_i386_port_scope
Assuming this is the right thing to do, I would like to ask that
src:rpds-py also builds on i386. The reason is that currently jq is an
FTBFS[1] in oracular and plucky because:
jq -> Build-Depen
I'd say it's a mirror issue.
> And it's the same with your mirror.
What do you mean exactly? My mirror (br.archive.ubuntu.com) showed
0ubuntu2.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
http
You still don't see 0ubuntu2, so your mirror is perhaps outdated. Here:
$ apt-cache policy python3 python3-venv
python3:
Installed: 3.12.3-0ubuntu2
Candidate: 3.12.3-0ubuntu2
Version table:
*** 3.12.3-0ubuntu2 500
500 http://br.archive.ubuntu.com/ubuntu noble-updates/main amd64
Pac
Please run:
sudo apt update
And then show the output of:
apt-cache policy python3 python3-venv
I installed python3-venv just fine in my noble system.
** Changed in: python3-defaults (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member
Hello Julian, or anyone else affected,
Accepted apt into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.0.11 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Te
Hello Julian, or anyone else affected,
Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.14 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Te
Hello Julian, or anyone else affected,
Accepted apt into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.8.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Tes
Hello Julian, or anyone else affected,
Accepted apt into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.8.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Tes
Hello Ankush, or anyone else affected,
Accepted apt into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.8.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Tes
Hello Julian, or anyone else affected,
Accepted apt into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.8.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Tes
I'm having second thoughts about the "deny / r," rule, because it
affects rsyslog as a whole, and not just the imfile module.
With that rule in place, we won't know (via apparmor logs) if we are
suddenly blocking something else in rsyslog, and this could make
troubleshooting harder in the future.
** Also affects: rsyslog (Ubuntu Plucky)
Importance: Low
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/2101180
Title:
Multiple DENIED apparm
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => In Progress
** Also affects: rsyslog (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: rsyslog (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you ar
Public bug reported:
We recently started getting more apparmor-related bugs in rsyslog. Most
are just about the noise the DENIED messages produce in the logs, with
one or two there something was actually preventing rsyslog from working
with a specific module.
There are some apparmor tests, but th
Hello Moritz, or anyone else affected,
Accepted openssh into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:8.9p1-3ubuntu0.12 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
The status of this update now is:
a) it needs someone to perform the verification on jammy and focal, as per the
test plan from the bug's description
b) since it's been in proposed for so long (about a year), we should have a new
run of the autopkgtests. I'll try to trigger that. The existing run
Removing the block tag, this is now back into normal SRU processing (and
I'm on shift today, so I'll take a new look).
** Tags removed: block-proposed-focal block-proposed-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The jammy upload is also adding the new DEP8 test, but disabled:
--- a/debian/tests/python
+++ b/debian/tests/python
@@ -217,6 +217,13 @@ class TestZoneinfo(unittest.TestCase):
date = timezone.localize(datetime.datetime(2025, 3, 23))
self.assertEqual(self._hours(date.utcoffset()),
2025b is in plucky-unapproved, because we are about to release the
plucky beta. It should be allowed in after today.
--
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/2104284
Ti
Hello Benjamin, or anyone else affected,
Accepted tzdata into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2025b-0ubuntu0.22.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello Benjamin, or anyone else affected,
Accepted tzdata into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2025b-0ubuntu0.24.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Thanks for the updated test plan for focal.
** Changed in: tzdata (Ubuntu Oracular)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-oracular
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
Hello Benjamin, or anyone else affected,
Accepted tzdata into oracular-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/tzdata/2025b-0ubuntu0.24.10 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
** Changed in: tzdata (Ubuntu Jammy)
Status: Incomplete => New
--
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/2104284
Title:
tzdata 2025b release
Status in tzdata p
Thanks @Seth! Your comment #18 seems to have focused mostly on the RSA
keys, did you get a chance to also look at the new NIST, brainpoolP, and
secp algorithms that were added/swapped around? From the table in
comment #22 (also comment #20), looks like another change is that NIST
P-{256,384,512} in
The changes in 13.6 and 13.7 were reverted, and this bug is open again.
Removing the block-proposed-noble tag.
** Changed in: openssh (Ubuntu Noble)
Status: Fix Committed => Confirmed
** Tags removed: block-proposed-noble verification-done verification-
done-noble
--
You received this bu
The changes in 13.6 and 13.7 were reverted, and this bug is open again.
Removing the block-proposed-noble tag.
** Changed in: openssh (Ubuntu Noble)
Status: Fix Committed => Confirmed
** Tags removed: block-proposed-noble noble verification-done-noble
verification-needed
--
You received
The changes in noble's 13.6 and 13.7 were reverted, and this bug is open
again. Removing the block-proposed-noble tag.
** Tags removed: block-proposed-noble noble verification-done
verification-done-noble
** Changed in: openssh (Ubuntu Noble)
Status: Fix Committed => Confirmed
--
You rec
Here is a screenshot of the document from comment #20
** Attachment added: "apt-security-levels.png"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2073126/+attachment/5867457/+files/apt-security-levels.png
--
You received this bug notification because you are a member of Ubuntu
Touch se
The verification of the Stable Release Update for tzdata 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 r
> I don't understand why today is the right day to allow weaker RSA
keys.
I don't think that changed. To recap (and these changes are confusing,
yes, but this is my understanding of the final result):
# Noble release
- there is only one list of crypto algorithms: Assert-Pubkey-Algo
- anything NOT
The DEP8 tests for rsyslog in both noble and oracular are green, and in
particular, also green in the s390x architecture:
rsyslog noble s390x 8.2312.0-3ubuntu9.1:
https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/s390x/r/rsyslog/20250314_133403_d5201@/log.gz
rsyslog oracular s390x 8
# oracular verification
$ apt-cache policy rsyslog
rsyslog:
Installed: 8.2406.0-1ubuntu2
Candidate: 8.2406.0-1ubuntu2
Version table:
*** 8.2406.0-1ubuntu2 500
500 http://br.archive.ubuntu.com/ubuntu oracular/main amd64 Packages
Created the imjournal config, and restarted rsyslog. C
@ubuntu-security, could I please get your take on the changes introduced
by this SRU? I believe I summarized them in comment #16 (unless @juliank
chimes in with a correction!).
It's basically the list of crypto algorithms that need checking.
RSA1024 still triggers a "weak key" warning.
https://
So from my understanding, these are the big changes in this SRU,
regarding the crypto config.
a) Algorithms MISSING from Assert-Pubkey-Algo are now treated as an
ERROR, whereas before (noble release) they were WARNINGS;
b) The list of algorithms in Assert-Pubkey-Algo changed:
">=rsa2048,ed2551
I tested with (only changed rsa from the defaults):
APT::Key::Assert-Pubkey-Algo
">=rsa2048,ed25519,ed448,nistp256,nistp384,nistp512,brainpoolP256r1,brainpoolP320r1,brainpoolP384r1,brainpoolP512r1,secp256k1";
APT::Key::Assert-Pubkey-Algo::Next
">=rsa5120,ed25519,ed448,nistp256,nistp384,nistp512";
Public bug reported:
I was actually trying to report a bug on dracut (ubuntu-bug dracut), and
this showed up.
ProblemType: AptSolver
DistroRelease: Ubuntu 25.04
Package: apt 2.9.33
ProcVersionSignature: Ubuntu 6.14.0-11.11-generic 6.14.0-rc7
Uname: Linux 6.14.0-11-generic x86_64
NonfreeKernelModu
So to summarize, and please confirm or deny my understanding below,
comparing to 2.7.14build2 which is current noble release+updates:
- Assert-Pubkey-Algo reintroduces >= rsa1024 (was rsa2048), and allows more
nist curves[1]. It's downgrading the RSA key size to 1024.
- there is no error whatsoev
Hello Julian, or anyone else affected,
Accepted apt into oracular-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.9.8ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ub
Got a reply in matrix:
https://matrix.to/#/!QMtJBibTYYOCvXJEdv:ubuntu.com/$5j5unfVxa669Oq3weDg2m_RiXiId_OuvJmzJCj6UkYQ?via=ubuntu.com&via=matrix.org&via=matrix.debian.social
tl;dr: does not affect the cache db
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I'm not super familiar with apt-ftparchive. Going through the
description in the bug, and manpage, I see mention on a cache db.
Do the changes here in this bug invalidate existing cache db files? I
see that the list of packages is now ordered, does that affect the
caching?
In other words, some re
Public bug reported:
andreas@nsnx:~$ head /var/lib/dpkg/info/apparmor.postinst
#!/bin/sh
# postinst script for apparmor
#
# see: dh_installdeb(1)
set -ex
. /usr/share/debconf/confmodule
. /lib/apparmor/rc.apparmor.functions
# summary of how this script can be called:
andreas@nsnx:~$ dpkg -l a
bug #2080216 is back on schedule to be fixed. We are proceeding with one
fix at a time now, carefully going over the 3 fixes the failed SRU had
before.
The current openssh SRU in proposed[1] is fixing:
[ Lukas Märdian ]
* d/p/gssapi.patch: Fix interaction between gssapi-keyex and pubkey auth
Remaining autopkgtest failures in excuses:
* oracular:
https://ubuntu-archive-team.ubuntu.com/proposed-migration/oracular/update_excuses.html#tzdata
* jammy:
https://ubuntu-archive-team.ubuntu.com/proposed-migration/jammy/update_excuses.html#tzdata
* focal:
https://ubuntu-archive-team.u
** Changed in: rsyslog (Ubuntu Noble)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: rsyslog (Ubuntu Oracular)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
** Description changed:
+ [ Impact ]
+
There is a consistent autopkgtest failure in s390x only, where the
logcheck test fails because there is an unexpected boot notice in the
output[1]:
136s ** Running logcheck
136s This email is sent by logcheck. If you no longer wish to receive
** Also affects: rsyslog (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: rsyslog (Ubuntu Oracular)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslo
@ptitoliv,
if you put this in /etc/apparmor.d/local/usr.sbin.rsyslogd:
/var/ r,
/var/log/ r,
deny /r,
And then run:
sudo apparmor_parser -r -W -T /etc/apparmor.d/usr.sbin.rsyslogd
Does it silence the warnings, and does
I would consider that a bug, yes. Could you share your rsyslog
configuration please?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/2101180
Title:
Multiple DENIED apparmor
Hello Sebastien, or anyone else affected,
Accepted software-properties into noble-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/software-
properties/0.99.49.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
Hello James, or anyone else affected,
Accepted software-properties into noble-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/software-
properties/0.99.49.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packa
Hello Sebastien, or anyone else affected,
Accepted software-properties into noble-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/software-
properties/0.99.49.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
Hello Sebastien, or anyone else affected,
Accepted software-properties into noble-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/software-
properties/0.99.49.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
Hello Sebastien, or anyone else affected,
Accepted software-properties into noble-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/software-
properties/0.99.49.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
Hello Sebastien, or anyone else affected,
Accepted software-properties into noble-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/software-
properties/0.99.49.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
Thanks, uploaded:
Uploading gzip_1.13-1ubuntu3.dsc
Uploading gzip_1.13-1ubuntu3.debian.tar.xz
Uploading gzip_1.13-1ubuntu3_source.buildinfo
Uploading gzip_1.13-1ubuntu3_source.changes
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
Public bug reported:
There is a consistent autopkgtest failure in s390x only, where the
logcheck test fails because there is an unexpected boot notice in the
output[1]:
136s ** Running logcheck
136s This email is sent by logcheck. If you no longer wish to receive
136s such mail, you can either un
@enr0n is the above all the testing we can realistically do wrt this
bug?
--
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/2088069
Title:
systemd-stub should provide a way t
Patch and fix from upstream:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66709#10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gzip in Ubuntu.
https://bugs.launchpad.net/bugs/2100598
Title:
dfltcc.c FTBFS on s390x
Sta
** Description changed:
DFLTCC on s390x is a feature that was disabled to address an FTBFS in
that code. This was done before feature freeze in [1].
- We later found out the real fix[2] for the FTBFS, and it's in an MP attached
to this bug. The diff is two fold:
+ We later found out the re
** Changed in: gzip (Ubuntu Plucky)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: gzip (Ubuntu Plucky)
Status: New => In Progress
** Changed in: gzip (Ubuntu Plucky)
Importance: Undecided => High
** Summary changed:
- dfltcc.c FTBFS on s390x
+
** Description changed:
- I'm still gathering information about this bug.
+ DFLTCC on s390x is a feature that was disabled to address an FTBFS in
+ that code. This was done before feature freeze in [1].
- UPDATE #1: see comment #2, this started out as an FTBFS.
- UPDATE #2: filed upstream bug a
Public bug reported:
I'm still gathering information about this bug.
Reportedly there was a SIGILL on gzip/s390x such that the hardware
acceleration on that platform for gzip had to be disabled in an
upload[1].
I found a matrix thread[2] about it.
Looks like it happened during a PPA build[3]:
** Description changed:
I'm still gathering information about this bug.
UPDATE #1: see comment #2, this started out as an FTBFS.
+ UPDATE #2: filed upstream bug at
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=76644
Reportedly there was a SIGILL on gzip/s390x such that the hardware
gzip 1.13 release notes contain the word "stdalign" :)
2023-08-19 Jim Meyering
version 1.13
* NEWS: Record release date.
maint: remove use gnulib's deprecated stdalign module
* bootstrap.conf (gnulib_modules): Remove deprecated stdalign.
It was not directly used.
buil
No build failure on debian[1], but we have gcc-15, they have gcc-14.
1.
https://buildd.debian.org/status/fetch.php?pkg=gzip&arch=s390x&ver=1.13-1&stamp=1737110118&raw=0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gzip in
> No build failure on debian[1], but we have gcc-15, they have gcc-14.
Our default still seems to be 14, though.
Ok, I'll stop guessing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gzip in Ubuntu.
https://bugs.launchpad.
I did a revert of [2], and uploaded to this PPA[3]. The PPA has proposed
enabled.
Building started.
1.
https://git.launchpad.net/~ahasenack/ubuntu/+source/gzip/commit/?id=389a495334db07cc37b1e2a2fa2d51f2c83fddd3
2. https://launchpad.net/ubuntu/+source/gzip/1.13-1ubuntu2
3. https://launchpad.net/
Ok, the straight revert, with plucky-proposed, got an FTBFS[1]:
gcc -DHAVE_CONFIG_H -I. -I.. -I./lib -I../lib -Wdate-time -D_FORTIFY_SOURCE=3
-DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e -g -O2
-Werror=implicit-function-declaration -mbackchain
-ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects
-fst
Hello Nick, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.15 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
The verification of the Stable Release Update for packagekit 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 encounte
The verification of the Stable Release Update for libdnf 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 r
The remaining packages from this bug no longer pose a high risk of
hitting the bug, because they have no diverts. It will be good to fix
them, but only worth it if together with another update, for another
reason. Therefore, I'm adding the block-proposed-noble tag.
--
You received this bug notifi
Hello Chengen, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.15 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Hello Nick, or anyone else affected,
Accepted systemd into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/255.4-1ubuntu8.6 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Hello Valentin, or anyone else affected,
Accepted systemd into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/255.4-1ubuntu8.6 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello Paul, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.15 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello Danilo, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.15 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
Hello frantisek, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.15 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
Hello Skia, or anyone else affected,
Accepted systemd into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/249.11-0ubuntu3.15 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
> @ahasenack I can modify unattended upgrades to utilize systemd-ac-power, but
> this will also require me to
> backport any missing systemd-ac-power patches to it to make sure the script
> covers as many scenarios as
> possible.
I rather have to SRU powermgmt-base for a on-power-detection is
The verification of the Stable Release Update for lvm2 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 reg
Autopkgtests for src:tdb are failing[1]:
79s autopkgtest [00:47:43]: apt-source tdb
81s autopkgtest [00:47:45]: ERROR: erroneous package: rules extract failed
with exit code 1
81s blame: tdb
81s badpkg: rules extract failed with exit code 1
1.
https://objectstorage.pro
I did a no-change-rebuild of rsyslog on focal and jammy, and it also
fails in the same gzip tests, so I added tasks for gzip on those ubuntu
releases.
** Also affects: gzip (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: zlib (Ubuntu Focal)
Importance: Undecided
** Also affects: gzip (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: zlib (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: rsyslog (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: gzip (Ubuntu Jammy)
Status:
I just saw that gzip got a new upload earlier this month disabling
hardware acceleration on s390x[1]:
gzip (1.13-1ubuntu2) plucky; urgency=medium
* Turn off DFLTCC optimizations on s390x, they're causing decompression to
crash with an illegal instruction
-- Aaron Rainbolt Tue, 11 Feb 2
1 - 100 of 1363 matches
Mail list logo
