** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080257
Title:
[WSL] systemd fails to upgrade on WSL1
To manage notifications ab
I added a note about this in the release notes.
** Changed in: ubuntu-release-notes
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083311
Title:
Upgrade to Oracul
Public bug reported:
E.g.: https://autopkgtest.ubuntu.com/results/autopkgtest-
oracular/oracular/amd64/s/systemd/20241003_175213_c04ab@/log.gz
Debian already skips this test due to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1075733. Let's do the same for Ubuntu.
** Affects: systemd (Ubun
Public bug reported:
During an archive rebuild, rsyslog FTBFS on s390x only:
https://launchpadlibrarian.net/751879056/buildlog_ubuntu-
oracular-s390x.rsyslog_8.2406.0-1ubuntu2_BUILDING.txt.gz
The build fails due to two tests:
FAIL: gzipwr_flushInterval
==
testbench: TZ e
Public bug reported:
Follow up for https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/2083311.
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
*** This bug is a duplicate of bug 1970018 ***
https://bugs.launchpad.net/bugs/1970018
Reviewing the files from your upgrade attempt, you have installed
packages from the deadsnakes PPA. Some of the packages installed are
newer than those in the official archive, which is keeping some python
p
LXD uses zfs by default, which may have been why zfs was loaded for you.
But yes, we dropped this quirk because it turns out ZFS support will be
in the 24.10 kernel in time for the release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => 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/2083522
Title:
The 'snap revert' hint displayed on upgrade is misleadi
** Tags added: ftbfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083243
Title:
[FFe] gsasl: FTBFS on s390x in oracular
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
** Tags added: ftbfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083245
Title:
[FFe] libgcrypt: FTBFS on s390x due to failed tests
To manage notifications about this bug go to:
https://bugs.laun
Merged and uploaded both.
** Changed in: cd-boot-images-arm64 (Ubuntu Oracular)
Status: New => In Progress
** Changed in: cd-boot-images-amd64 (Ubuntu Oracular)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Changed in: openssh (Ubuntu Noble)
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/2069041
Title:
Changing Port in sshd_config requires calling systemctl daemo
** Changed in: openssh (Ubuntu Noble)
Status: New => 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/2071815
Title:
Investigate ASLR re-randomization being disabled for children
To
** Changed in: openssh (Ubuntu Noble)
Status: New => 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/2080216
Title:
sshd cannot bind to IPv4 interfaces
To manage notifications abou
** Changed in: openssh (Ubuntu Noble)
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/2076023
Title:
Failed to apply 'Match' directive in sshd_config with sshd-so
** Description changed:
[Impact]
When users have a Match section in their sshd config, their
configuration cannot be parsed by the sshd-socket-generator (because
there is no connection, hence no connection spec to be matched), and the
generator fails. This means no custom config is ap
** Description changed:
+ [Impact]
+
The systemd-socket-activation.patch patch has an Ubuntu delta to fix bug
2011458, but this results in ASLR not being re-randomized for children
because the patch delta does "rexec_flag = 0;".
This was discovered as part of the CVE-2024-6387 discover
** Changed in: openssh (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080216
Title:
sshd cannot bind to IPv4 interfaces
To manage notifications abou
** Description changed:
+ [Impact]
+
+ The default listening sockets for sshd are different depending on
+ whether socket activation is used or not, even when /etc/ssh/sshd_config
+ is the default. E.g.:
+
+ # Socket-activated
+
+ root@n2:~# systemctl status ssh.socket
+ ● ssh.socket - OpenBSD
** Description changed:
+ [Impact]
+
+ When users have a Match section in their sshd config, their
+ configuration cannot be parsed by the sshd-socket-generator (because
+ there is no connection, hence no connection spec to be matched), and the
+ generator fails. This means no custom config is ap
** Changed in: openssh (Ubuntu)
Status: Confirmed => Triaged
** Also affects: openssh (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20
Okay, I am not sure why the ipv6 socket is not accepting ipv4, because
AFAICT (and when I test on my machine) the way IPV6_V6ONLY is being set
in the default case, it should allow ipv4.
However, I do think there is a case to be made about the socket unit
being more aligned with the contents of /et
I uploaded nose.
** Changed in: nose (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083051
Title:
nose, git-buildpackage FTBFS
To manage notifications
** Also affects: openssh (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Noble)
Importance: Undecided => Medium
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Changed in: openssh (Ubuntu Noble)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069041
Title:
Changing Port in sshd_config requires calling systemctl daemo
Ah sorry, I missed that. Can you please do the following then:
1. Enable debug logs on systemd-networkd-wait-online.service:
$ mkdir -p /etc/systemd/system/systemd-networkd-wait-online.d/
$ cat > /etc/systemd/system/systemd-networkd-wait-online.d/debug.conf << EOF
[Service]
Environment=SYSTEMD_LO
It looks like bind9 (named.service) is able to bind to the address just
fine after systemd-networkd reports the address is configured. Is named
maybe not setting SO_REUSEADDR/SO_REUSEPORT or something? Or (as an
experiment) does disabling named.service allow the others to start?
** Changed in: sys
** Changed in: lshw (Ubuntu)
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/2081759
Title:
lshw: FTBFS due to missing 'build-arch' target
To manage notification
ng)
debian/rules build
...SNIP...
[1]
https://launchpadlibrarian.net/749245587/buildlog_ubuntu-oracular-arm64.lshw_02.19.git.2021.06.19.996aaad9c7-2ubuntu1_BUILDING.txt.gz
[2]
https://launchpadlibrarian.net/737811292/buildlog_ubuntu-oracular-arm64.lshw_02.19.git.2021.06.19.996aaad9c7-2ubuntu1_BUILDIN
*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761
@mchelen Please open a new bug report by running `ubuntu-bug ubuntu-
release-upgrader-core` on the affected system. This will attach the
necessary logs to investigate your upgrade issue.
--
You received th
I'm sorry to hear about your upgrade troubles. If you have logs from the
the boot where the upgrade occurred, please open a different bug with
those logs so that the root cause for the hang can be investigated.
But, if you unplugged your machine during the upgrade because it was
unresponsive, I am
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Noble)
Status: New => Triaged
** Changed in: systemd (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Changed in: systemd (Ubuntu Noble)
Importance:
It appears to be a known issue that WSL1 does not support F_OFD_SETLKW,
which is what systemd is using here. I could add a fallback to use
F_SETLKW instead, but according to [1], it sounds like the locking is
just broken on WSL1? So the "fallback" would probably lead to even more
issues.
Do you ge
Re-adding a Linux task to see if anyone can confirm whether kernel
interface naming was changed between these two kernel versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077159
Title:
i40e i
By default, the NamePolicy=[1] (as configured in
/usr/lib/systemd/network/99-default.link) is:
[Link]
NamePolicy=keep kernel database onboard slot path
This means that if the kernel claims to assign a predictable name, then
that will take precedence over other policies, including the "onboard"
po
This error is coming from systemd-sysusers in systemd.postinst. To
isolate the failing call, can you share the output of:
$ SYSTEMD_LOG_LEVEL=debug systemd-sysusers basic.conf systemd-
journal.conf systemd-network.conf
Looking at the code, this is either failing on an open() or flock(), so
likely
I left questions on the PR.
Please note that the "Fix Committed" status is intended to indicate that
something has been uploaded to -proposed. As far as I can tell, that has
not happened yet.
** Changed in: pbdagcon (Ubuntu)
Status: Fix Committed => Incomplete
--
You received this bug no
Could you please make the test plan more clear, in particular with steps
on how to "Enable FIPS on a $RELEASE system"? I got there eventually on
Jammy with:
$ sudo pro attach
$ sudo pro enable fips-preview # Non-preview not supported yet?
$ sudo reboot
After that, I observed the exception when a
I am tracking this for future SRUs, so unsubscribing sponsors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/209
Title:
PTP device symlink missing after running udevadm trigger command
To manag
To be specific, the override I would suggest is:
$ mkdir -p /etc/tmpfiles.d
$ cat > /etc/tmpfiles.d/tmp.conf << EOF
D /tmp 1777 root root 10d
q /var/tmp 1777 root root 30d
EOF
In particular, this is flipping the 'q' to a 'D' for the /tmp line.
--
You received this bug notification because you a
This is expected behavior.
Since /tmp is a tmpfs by default, the default
/usr/lib/tmpfiles.d/tmp.conf is configured with a 10d cleanup age for
/tmp, but it is *not* configured to clean /tmp at boot, because that is
unnecessary for a tmpfs.
If you want to clean /tmp at boot *and* have your tmp.mou
** Tags added: foundations-todo
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080257
Title:
[WSL] syst
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The package built successfully:
https://launchpad.net/ubuntu/+source/systemd-hwe/255.1.4
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Are you able to run unprivileged containers instead? That would be the
suggested configuration from upstream LXD.
There are many things that do not work with systemd in privileged LXD
containers due to AppArmor etc. Upstream systemd does not like adding
workarounds for issues caused by AppArmor ru
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I suspect a support site would be more appropriate, e.g.
https://askubuntu.com, or for more options please look at
https://discourse.ubuntu.com/t/community-support/709.
** Changed in: systemd (Ubuntu)
Status
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Triaged
** Changed in: systemd (Ubuntu Jammy)
Status: In Progress => Triaged
** Changed in: systemd (Ubuntu Noble)
Status: In Progress => Triaged
** Changed in: systemd (Ubuntu Focal)
Importance: Undecided => Lo
systemd-binfmt should just exit when /proc/sys/fs/binfmt_misc is not
mounted rw, which I thought was usually the case in LXD containers.
Are you running a privileged or unprivileged container?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Imp
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I suspect a support site would be more appropriate, e.g.
https://askubuntu.com, or for more options please look at
https://discourse.ubuntu.com/t/community-support/709.
** Changed in: systemd (Ubuntu)
Status
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051407
Title:
qemu-net autopkgtest fails: Failed to send exit request: Resource
tempora
We don't remove old versions of postgres ourselves due to the risk of data
loss when upgrading to new versions so it should be an informed user-
driven process.
If you are absolutely sure you no longer need that version of postgres,
you can remove it and try the upgrade again.
** Changed in: ubun
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080233
Title:
[wsl] do-release-upgrade fails with systemd disabled
To manage notifications about this bug go to:
https:
Is sshd not accessible at all over ipv4? How did you notice that sshd
was not listening on ipv4?
In the default case, we should end up with ssh.socket listening on
[::]:22, but with IPV6_V6ONLY=0 so that sshd is still accessible over
ipv4.
> Setting net.ipv6.bindv6only=0 also helps, but that's no
I don't think I see a reason to remove from the release pocket.
** Changed in: sslh (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079513
Title:
Please rem
Public bug reported:
E.g. https://autopkgtest.ubuntu.com/results/autopkgtest-
oracular/oracular/s390x/i/initramfs-tools/20240909_091354_592dd@/log.gz
1489s autopkgtest [09:13:45]: summary
1489s qemu-ata-onlySKIP Test lists explicitly supported architectures,
but the
** Changed in: glibc (Ubuntu Noble)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058648
Title:
Support upgrades from unmerged 22.04 - was: package libc6
2.3
There is still one more build-time test failure on armhf:
https://launchpadlibrarian.net/747678259/buildlog_ubuntu-oracular-
armhf.detox_2.0.0-3ubuntu1_BUILDING.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Description changed:
sslh 2.1.1-1 is stuck in -proposed.
+
+ This package FTBFS on all arches (except riscv64), e.g.
+ https://launchpadlibrarian.net/744540879/buildlog_ubuntu-oracular-
+ amd64.sslh_2.1.1-1_BUILDING.txt.gz.
+
+ It has no reverse dependencies:
+
+ nr@six:~$ reverse-depends
Ugh, LP ate my comment and I didn't notice. Sorry about that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079513
Title:
Please remove sslh from the archive
To manage notifications about this bug
Forwarded to debian: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1081002
** Changed in: cruft-ng (Ubuntu)
Status: New => Fix Committed
** Bug watch added: Debian Bug tracker #1081002
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081002
** Also affects: cruft-ng (Debian) via
gtest [07:19:42]: test ncdu: ---]
** Affects: cruft-ng (Ubuntu)
Importance: Undecided
Assignee: Nick Rosbrook (enr0n)
Status: New
** Tags: update-excuse
** Changed in: cruft-ng (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Description
** Changed in: ubuntu-release-upgrader (Ubuntu Oracular)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074309
Title:
upgrade 22.04 -> 24.04 won't start due to fe
This patch is in v256.5, which I prepared and uploaded today.
** Changed in: systemd (Ubuntu Oracular)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/209
** Bug watch added: Debian Bug tracker #1075628
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075628
** Also affects: vstream-client (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075628
Importance: Unknown
Status: Unknown
--
You received this bug notificati
icit-function-declaration]
91 | iattr = ntohl(*(u32 *)data);
| ^
make[1]: *** [Makefile:22: object.o] Error 1
[1] https://launchpadlibrarian.net/744527373/buildlog_ubuntu-oracular-
armhf.vstream-client_1.2-7ubuntu1_BUILDING.txt.gz
** Affects: v
** Bug watch added: Debian Bug tracker #1080969
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080969
** Also affects: datalad-next (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080969
Importance: Unknown
Status: Unknown
** Changed in: datalad-next (Ubuntu)
_url
/usr/lib/python3/dist-packages/datalad/support/s3.py:23: in
import boto3
E ModuleNotFoundError: No module named 'boto3'
** Affects: datalad-next (Ubuntu)
Importance: Undecided
Assignee: Nick Rosbrook (enr0n)
Status: Fix Committed
** Affects: datalad-ne
revious definition
cc1: all warnings being treated as errors
** Affects: mmc-utils (Ubuntu)
Importance: Undecided
Assignee: Nick Rosbrook (enr0n)
Status: New
** Tags: update-excuse
** Changed in: mmc-utils (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
I did forward this to debian, but unfortunately forgot to include the
link in Bug-Debian in the patch header.
** Changed in: detox (Ubuntu)
Status: New => Fix Committed
** Bug watch added: Debian Bug tracker #1080967
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080967
** Also aff
process returned exit status 2
It seems that a simple fix is to remove the hard coded -D_FORTIFY_SOURCE
lines in the relevant Makefiles, and instead let the distro build flags
take precedence.
[1]https://launchpadlibrarian.net/744524447/buildlog_ubuntu-oracular-
amd64.detox_2.0.0-3_BUILDING.t
** Tags added: systemd-sru-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/209
Title:
PTP device symlink missing after running udevadm trigger command
To manage notifications about this bug
Public bug reported:
sslh 2.1.1-1 is stuck in -proposed.
** Affects: sslh (Ubuntu)
Importance: Undecided
Assignee: Nick Rosbrook (enr0n)
Status: New
** Tags: update-excuse
** Changed in: sslh (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Summary chan
Public bug reported:
Imported from Debian bug http://bugs.debian.org/1066361:
Source: atlas
Version: 3.10.3-14
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef
Hi,
During a rebuild of all packages in sid,
: Undecided
Assignee: Nick Rosbrook (enr0n)
Status: New
** Tags: update-excuse
** Changed in: glosstex (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Description changed:
glosstex 0.4.dfsg.1-4build1 is stuck in -proposed.
+
+ It FTBFS[1] and has no reve
c:nield -a source
No reverse dependencies found
[1]
https://launchpadlibrarian.net/744524684/buildlog_ubuntu-oracular-amd64.nield_0.6.1-2build1_BUILDING.txt.gz
[2]
https://lore.kernel.org/netdev/6f24a4f8-fb07-409b-955a-9aad4ab37...@gmail.com/T/
** Affects: nield (Ubuntu)
Importance: Undecided
As
*** This bug is a duplicate of bug 2078555 ***
https://bugs.launchpad.net/bugs/2078555
Thanks for your bug report. As you noted, this is the same issue as bug
2078555 so I am marking this as a duplicate to consolidate.
** This bug has been marked a duplicate of bug 2078555
Upgrading from 2
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078720
Title:
Upgrading from jammy to noble results in a linux-headers package being
in a broken state
To manage noti
This looks like a server side error with your mirror:
2024-08-30 17:37:16,197 DEBUG examining: 'deb
http://nl3.archive.ubuntu.com/ubuntu/ jammy main restricted'
2024-08-30 17:37:16,197 DEBUG verifySourcesListEntry: deb
http://nl3.archive.ubuntu.com/ubuntu/ noble main restricted
2024-08-30 17:37:
*** This bug is a duplicate of bug 1970018 ***
https://bugs.launchpad.net/bugs/1970018
Reviewing the files from your upgrade attempt, you have installed
packages from the deadsnakes PPA. Some of the packages installed are
newer than those in the official archive, which is keeping some python
p
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I suspect a support site would be more appropriate, e.g.
https://askubuntu.com, or for more options please look at
https://discourse.ubuntu.com/t/community-support/709.
** Changed in: ubuntu-release-upgrader (Ubunt
Hi Frode,
The debian/changelog diff does not look right to me (it should only be
adding new lines). Did you prepare this following the package merge
process[1]? If not, that would be the best way to get back up to date
with Debian.
Also, we are passed feature freeze[2][3] in the Oracular developm
It looks like this was fixed via a merge from Debian:
https://launchpad.net/ubuntu/+source/apr-util/1.6.3-3ubuntu1.
** Changed in: apr-util (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I am planning an SRU for noble in the next couple weeks.
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076023
Title:
Failed to apply 'Match' directive in sshd_con
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I suspect a support site would be more appropriate, e.g.
https://askubuntu.com, or for more options please look at
https://discourse.ubuntu.com/t/community-support/709.
** Changed in: ubuntu-release-upgrader (Ubunt
** Description changed:
+ [Impact]
+
The build in both noble and oracular fails with
FAIL: test_no_duplicates (__main__.RedundancyCheckTest.test_no_duplicates)
--
Traceback (most recent call last):
- File "/<>/./test
*** This bug is a duplicate of bug 2073278 ***
https://bugs.launchpad.net/bugs/2073278
This is intended behavior. We cannot automatically remove old
postgresql-* packages without being sure that it won't cause data loss,
for example if a database is still making use of postgresql-12 because
it
** Changed in: openssh (Ubuntu Oracular)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076023
Title:
Failed to apply 'Match' directive in sshd_config with ss
ged in: openssh (Ubuntu Noble)
Status: New => Triaged
** Changed in: openssh (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: openssh (Ubuntu Noble)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a memb
@corradoventu - the output you shared demonstrates that you are *not*
seeing this issue on 24.10.
@sunneyxue- likewise, your output demonstrates that the issue is fixed
on this system.
Note that it is possible at the time when you run `apt update`, that a
daemon-reload actually is needed, and the
The non-linux autopkgtest regressions were resolved with test
retries/baseline tests. As previously stated, the linux-* tests should
be ignored as they are denylisted. With, I believe the update could be
released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
@sunneyxue, can you share the output of the following?
$ apt policy systemd
$ sudo systemctl daemon-reload
$ sudo systemctl enable somethingthatdefinitelydoesnotexist.service
$ sudo apt update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I have verified the fixes for the regressions caused by the initial
upload of this fix, so I am going to remove the block-noble-proposed tag
now.
** Tags removed: block-proposed-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
I verified the fix using ubuntu-release-upgrader 1:24.04.22 from noble-
proposed:
nr@clean-jammy-amd64:~$ do-release-upgrade --proposed
[...SNIP...]
System upgrade is complete.
Restart required
To finish the upgrade, a restart is required.
If you select 'y' the system will be restarted.
Conti
I have verified the the fix using ubuntu-release-upgrader 1:24.04.22
from noble-proposed:
nr@clean-jammy-amd64:~$ snap info snap-store | grep "^tracking:"
tracking: latest/stable/ubuntu-22.04
nr@clean-jammy-amd64:~$ snap info firmware-updater | grep "^tracking:"
nr@clean-jammy-amd64:~$ do-rele
Given the regressions related to this original patch, I re-did SRU
verification using the latest upload:
nr@six:~$ lxc launch ubuntu:jammy j1
Launching j1
nr@six:~$ lxc launch ubuntu:jammy j2
Launching j2
nr@six:~$ lxc exec j1 bash
root@j1:~# do-release-upgrade --devel
[...SNIP...]
root@j1:~# gr
*** This bug is a duplicate of bug 1970018 ***
https://bugs.launchpad.net/bugs/1970018
Reviewing the files from your upgrade attempt, you have installed
packages from the deadsnakes PPA. Some of the packages installed are
newer than those in the official archive, which is keeping some python
p
*** This bug is a duplicate of bug 1980574 ***
https://bugs.launchpad.net/bugs/1980574
Reviewing the files from your upgrade attempt, you have installed
pipewire packages from the pipewire-debian/pipewire-upstream PPA. Some
of the packages installed are newer than those in the official archive
I have verified the fix using ubuntu-release-upgrader 1:24.04.22 from
noble-proposed:
nr@six:~$ lxc launch ubuntu:jammy j
Launching j
nr@six:~$ lxc exec j bash
root@j:~# apt-add-repository -y ppa:enr0n/lp2076913
Repository: 'deb https://ppa.launchpadcontent.net/enr0n/lp20
** Description changed:
[Impact]
It looks like the latest SRU has introduced a bug in
https://git.launchpad.net/ubuntu-release-
upgrader/commit/?id=8c592abdf5047a6bd4da20dab1e444c6dcf8c842
There is a typo in s/force_obosoletes/forced_obsoletes/ which causes upgrades
from noble to
The most recent upload contains a new quirk for an unrelated bug, and
fixes for another unrelated bug. The previous verification done with
1:24.04.21 stands.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received th
1 - 100 of 791 matches
Mail list logo
