Hello You-Sheng, or anyone else affected,
Accepted ipu6-drivers into noble-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/ipu6-drivers/0~git202404110253.97c94720-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by
linux-restricted-modules providing 550 is now available, so closing this
blocking bug.
** Changed in: nvidia-graphics-drivers-550-server (Ubuntu)
Status: New => Fix Released
** Changed in: nvidia-graphics-drivers-550 (Ubuntu)
Status: New => Fix Released
--
You received this bug
I believe this also applies to 550-open and 550-server, so demoting
these also.
** Also affects: nvidia-graphics-drivers-550-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
nvidia-settings 510.47.03-0ubuntu2 is built in -proposed but not on
armhf. This will not block migration because armhf binaries are being
removed from the release pocket, but unless addressed will regress armhf
availability of this package in 24.04 LTS.
** Affects:
You say "recent kernel or local kernel." What Ubuntu-provided kernel for
Ubuntu 22.04 LTS do you see this with?
** Changed in: linux (Ubuntu Jammy)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
It is not clear that this is a behavior change in the kernel that should
have been included as part of the hwe backports. cryptsetup may not be
the only package affected.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance:
** Summary changed:
- partproke is broken on empty loopback device
+ partprobe is broken on empty loopback device
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2049689
Title:
this appears to have been done, none of these packages are present in
noble or noble-proposed.
** Changed in: linux (Ubuntu Noble)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
linux-headers-generic is not a dependency of linux-image-generic. It IS
a dependency of linux-generic, which is what ubiquity installs. But any
mismatches here are likely in the kernel dependencies, not the
installer.
** Package changed: ubiquity (Ubuntu) => linux (Ubuntu)
--
You received
** Tags removed: regression-release
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2028165
Title:
nvidia-dkms-* FTBS with linux 6.5
Status in
You've filed a bug in debian against software which is not used in
Ubuntu.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906067
Title:
Boot from ISO - exFAT support missing
Status in
Removing packages from noble:
nvidia-graphics-drivers-515-server 515.105.01-0ubuntu2 in noble
libnvidia-cfg1-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-cfg1-510-server 515.105.01-0ubuntu2 in noble arm64
Removing packages from noble:
nvidia-graphics-drivers-460 460.91.03-0ubuntu1 in noble
libnvidia-cfg1-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-cfg1-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-common-450 460.91.03-0ubuntu1 in noble
Same for 515-server:
$ reverse-depends src:nvidia-graphics-drivers-515-server
Reverse-Depends
===
* libnvidia-decode-510-server (for libnvidia-decode-515-server)
* libnvidia-encode-510-server (for libnvidia-encode-515-server)
Packages without architectures listed are
All older source packages listed in this bug report have been removed,
and yet:
$ reverse-depends src:nvidia-graphics-drivers-460
Reverse-Depends
===
* libnvidia-decode-455 (for libnvidia-decode-460)
* libnvidia-encode-455 (for libnvidia-encode-460)
*
Removing packages from noble:
fabric-manager-515 515.105.01-0ubuntu1 in noble
cuda-drivers-fabricmanager-510 515.105.01-0ubuntu1 in noble
amd64
nvidia-fabricmanager-510 515.105.01-0ubuntu1 in noble amd64
nvidia-fabricmanager-dev-510
Removing packages from noble:
libnvidia-nscq-515 515.105.01-0ubuntu1 in noble
libnvidia-nscq-510 515.105.01-0ubuntu1 in noble amd64
Comment: Auxiliary package for obsolete driver version; LP: #2048782
1 package successfully removed.
** Changed in: libnvidia-nscq-515
Removing packages from noble:
libnvidia-nscq-510 510.85.02-0ubuntu2 in noble
Comment: Auxiliary package for obsolete driver version; LP: #2048782
1 package successfully removed.
** Changed in: libnvidia-nscq-510 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
Removing packages from noble:
libnvidia-nscq-460 460.106.00-0ubuntu1 in noble
Comment: Auxiliary package for obsolete driver version; LP: #2048782
1 package successfully removed.
** Changed in: libnvidia-nscq-460 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
Removing packages from noble:
fabric-manager-450 450.248.02-0ubuntu1 in noble
cuda-drivers-fabricmanager-450 450.248.02-0ubuntu1 in noble
amd64
nvidia-fabricmanager-450 450.248.02-0ubuntu1 in noble amd64
nvidia-fabricmanager-dev-450
Removing packages from noble:
fabric-manager-510 510.85.02-0ubuntu2 in noble
Comment: Auxiliary package for obsolete driver version; LP: #2048782
1 package successfully removed.
** Changed in: fabric-manager-510 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
Removing packages from noble:
libnvidia-nscq-450 450.248.02-0ubuntu1 in noble
libnvidia-nscq-450 450.248.02-0ubuntu1 in noble amd64
Comment: Auxiliary package for obsolete driver version; LP: #2048782
1 package successfully removed.
** Changed in: libnvidia-nscq-450
Removing packages from noble:
fabric-manager-460 460.106.00-0ubuntu1 in noble
Comment: Auxiliary package for obsolete driver version; LP: #2048782
1 package successfully removed.
** Changed in: fabric-manager-460 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
Removing packages from noble:
nvidia-graphics-drivers-450 450.119.03-0ubuntu1 in noble
libnvidia-cfg1-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-common-440 450.119.03-0ubuntu1 in noble amd64
libnvidia-common-440 450.119.03-0ubuntu1 in
Removing packages from noble:
nvidia-graphics-drivers-440 440.100-0ubuntu1 in noble
libnvidia-cfg1-430 440.100-0ubuntu1 in noble amd64
libnvidia-common-430 440.100-0ubuntu1 in noble amd64
libnvidia-common-430 440.100-0ubuntu1 in noble arm64
Removing packages from noble:
nvidia-graphics-drivers-515 515.105.01-0ubuntu3 in noble
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.
** Changed in: nvidia-graphics-drivers-515 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
Removing packages from noble:
nvidia-graphics-drivers-530 530.41.03-0ubuntu2 in noble
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.
** Changed in: nvidia-graphics-drivers-530 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
The other packages in this listed are reported by reverse-depends to
have non-empty revdeps. However it looks like these all come from other
packages that have just been removed. Rather than tracing this manually
and possibly making a mistake, I'll let the others sit for another
round.
--
You
Removing packages from noble:
nvidia-graphics-drivers-455 455.45.01-0ubuntu1 in noble
libnvidia-cfg1-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-common-435 455.45.01-0ubuntu1 in noble amd64
libnvidia-common-435 455.45.01-0ubuntu1 in noble
Removing packages from noble:
nvidia-graphics-drivers-510 510.108.03-0ubuntu3 in noble
libnvidia-cfg1-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-common-495 510.108.03-0ubuntu3 in noble amd64
libnvidia-common-495 510.108.03-0ubuntu3 in
Removing packages from noble:
nvidia-graphics-drivers-435 435.21-0ubuntu8 in noble
Comment: Unsupported driver version; LP: #2048087
1 package successfully removed.
** Changed in: nvidia-graphics-drivers-435 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
Removing packages from noble:
nvidia-graphics-drivers-340 340.108-0ubuntu8 in noble
libcuda1-340 340.108-0ubuntu8 in noble amd64
libcuda1-340 340.108-0ubuntu8 in noble armhf
nvidia-340 340.108-0ubuntu8 in noble amd64
Removing packages from noble:
nvidia-graphics-drivers-430 430.50-0ubuntu3 in noble
libnvidia-cfg1-418 430.50-0ubuntu3 in noble amd64
libnvidia-common-418 430.50-0ubuntu3 in noble amd64
libnvidia-common-418 430.50-0ubuntu3 in noble arm64
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification
Normally, changing a conffile in an SRU is iffy because this may result
in conffile prompts for the user on upgrade, and will cause unattended-
upgrades to hold the package back.
In this case we're fixing a regression in a conffile that was introduced
already in -updates. So, ok.
** Changed in:
Hello Mauricio, or anyone else affected,
Accepted zfs-linux into mantic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/2.2.0-0ubuntu1~23.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
The usbio-drivers package that was uploaded to the noble NEW queue has
been rejected due to an incorrect debian/copyright. The upstream
copyright declarations all indicate that they are GPL 2.0, not GPL 2.0
or any later version. The debian/copyright uses the correct short name
for the actual
LP: #2048087 has been opened with a superset of removal requests, so
marking invalid the tasks here in favor of that separate bug with
independent history.
** Changed in: nvidia-graphics-drivers-430 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: nvidia-graphics-drivers-435 (Ubuntu)
I actually agree that we should aim to remove these packages entirely,
rather than merely demoting them.
I think removal of the server is a clear-cut case. Nobody should need
to run a pptp server nowadays on Ubuntu, and if anyone is, forcing them
to migrate to a better VPN solution on upgrade
Removing packages from noble:
pptpd 1.4.0-12build2 in noble
bcrelay 1.4.0-12build2 in noble amd64
bcrelay 1.4.0-12build2 in noble arm64
bcrelay 1.4.0-12build2 in noble armhf
bcrelay 1.4.0-12build2 in noble ppc64el
** Description changed:
Remove dangerously insecure MPPE PPTP from Ubuntu
https://pptpclient.sourceforge.net/protocol-security.phtml
It has been dead for over 20 years now.
- IPSec OpenVPN Strongswan are much better alternatives.
+ Current Windows versions natively support IPSec
** Tags added: regression-security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2046116
Title:
bluetooth device connected but not recognised as output device
Status in bluez package
>From the linked page:
However, that doesn't mean people don't accept the risks. There are many
corporations and individuals using PPTP with full knowledge of these
risks. Some use mitigating controls, and some don't.
No one has ever run pptp on Linux, as either a client or server, because
they
Oh. To the question of whether there was a systemd change in this
window: yes absolutely, because this is the point at which the riscv64
builders moved from lgw manually-operated qemu with a 20.04 guest image,
to bos03 openstack-operated qemu with a 22.04 guest image.
Which is also why we've
On Sat, Dec 09, 2023 at 05:13:28PM -, Andy Whitcroft wrote:
> Was there any systemd/udev change in this timeframe? As the device
> files are very much connected to those.
My understanding is that these devices are supposed to be created directly
by the kernel on devtmpfs and NOT via udev,
https://launchpad.net/~ubuntu-
cdimage/+livefs/ubuntu/noble/cpc/+build/544490 is a log from a build
with a new livecd-rootfs that spits out more debugging info on failure.
+ sgdisk binary/boot/disk-uefi.ext4 --print
Disk binary/boot/disk-uefi.ext4: 9437184 sectors, 4.5 GiB
Sector size (logical):
Hello You-Sheng, or anyone else affected,
Accepted firmware-sof into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.0-1ubuntu4.5 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Chris, or anyone else affected,
Accepted firmware-sof into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.0-1ubuntu4.5 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello You-Sheng, or anyone else affected,
Accepted firmware-sof into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.2.6-1ubuntu1.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Chris, or anyone else affected,
Accepted firmware-sof into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.2.6-1ubuntu1.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
zfs-linux (2.2.2-0ubuntu1~23.10) mantic; urgency=medium
* New upstream release. LP: #2044657
- Address potential data corruption
I'm assuming the plan for fixing it on earlier releases does not involve
updating to 2.2.2.
And this does not fall under a hardware enablement exception. AND
Failing build had kernel
Kernel version: Linux bos03-riscv64-014 5.19.0-1021-generic
#23~22.04.1-Ubuntu SMP Thu Jun 22 12:49:35 UTC 2023 riscv64
The build immediately before the first failure had kernel
Kernel version: Linux riscv64-qemu-lgw01-069 5.13.0-1019-generic
#21~20.04.1-Ubuntu SMP Thu
November 16 was 2 days after livecd-rootfs 24.04.4 landed in the noble
release pocket, superseding 24.04.2.
The code delta between 24.04.2 and 24.04.4 includes removal of support
for "legacy" images (SUBPROJECT=legacy) which doesn't apply here; and
some reorganization of code related to
Public bug reported:
In mantic, we migrated livecd-rootfs to use losetup -P instead of
kpartx, with the expectation that this would give us a reliable, race-
free way of loop-mounting partitions from a disk image during image
build.
In noble, we are finding that it is no longer reliable, and in
Hello You-Sheng, or anyone else affected,
Accepted ivsc-driver into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ivsc-
driver/0~git202212210258.94ecb88b-0ubuntu0.23.10.3 in a few hours, and
then in the -proposed repository.
Please help us
I'd really recommend not open new bug tasks for further source packages
on a bug like this; we clearly aren't going to remove any of those other
packages from mantic now...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Hello Chris, or anyone else affected,
Accepted firmware-sof into lunar-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.2.4+2.2.6-0ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Chris, or anyone else affected,
Accepted firmware-sof into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.2.6-1ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
*** This bug is a duplicate of bug 2038745 ***
https://bugs.launchpad.net/bugs/2038745
Thank you for highlighting this. I have released the update now to
lunar as well. Marking this as a duplicate of LP: #2038745.
** This bug has been marked a duplicate of bug 2038745
NV31 XTX cannot
This has been marked as fixed in mantic, but this bug does not say what
the plan is for lunar, which is still the supported upgrade path from
jammy.
** Changed in: gdm3 (Ubuntu Jammy)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of
The firmware-sof upload in lunar-proposed contains a sha256sum.txt with
the checksums of all the firmware. But every line of this file is
different from every line in the previous version, because the version
number is encoded. Likewise, the file paths within the package encode
the version.
** Description changed:
- SRU Jusitification for firmware-sof
+ SRU Justification for firmware-sof
[Impact]
To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6
[Fix]
Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too
[Test Case]
Install the fixes
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2038292
Title:
This does not appear to be a blocker for Ubuntu 23.10; removing the
milestone.
** Changed in: linux (Ubuntu Mantic)
Milestone: ubuntu-23.10 => None
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux-firmware-raspi (Ubuntu Mantic)
Milestone: ubuntu-23.10 => mantic-updates
** Changed in: linux-firmware-raspi (Ubuntu Mantic)
Milestone: mantic-updates => None
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
My understanding is this will be able to go into the mantic release
pocket with the kernel respin currently in progress, so should not need
to be an SRU.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member
marking this fix committed for linux, version 6.5.0-9.9 in mantic-
proposed should contain the fix.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Removing packages from mantic:
nvidia-graphics-drivers-450-server 450.248.02-0ubuntu2 in mantic
libnvidia-cfg1-440-server 450.248.02-0ubuntu2 in mantic amd64
libnvidia-cfg1-450-server 450.248.02-0ubuntu2 in mantic amd64
Now:
$ reverse-depends src:nvidia-graphics-drivers-450-server
Reverse-Depends
===
* libnvidia-decode-440-server (for libnvidia-decode-450-server)
* libnvidia-encode-440-server (for libnvidia-encode-450-server)
* libnvidia-fbc1-440-server (for libnvidia-fbc1-450-server)
*
418 is clean.
$ reverse-depends src:nvidia-graphics-drivers-418-server
No reverse dependencies found
$ reverse-depends src:nvidia-graphics-drivers-418-server -a source
No reverse dependencies found
$
Removing packages from mantic:
nvidia-graphics-drivers-418-server 418.226.00-0ubuntu5 in
Removing packages from mantic:
nvidia-graphics-drivers-440-server 440.95.01-0ubuntu2 in mantic
Comment: EOL, obsolete source package; LP: #2035189
1 package successfully removed.
** Changed in: nvidia-graphics-drivers-440-server (Ubuntu)
Status: Confirmed => Fix Released
--
You
The reason for adding bumblebee is that Recommends and alternative
Depends on removed packages can cause them to be retained on end user
systems after upgrade. Better to remove the references than to try to
work out if nvidia would manage to not be affected.
--
You received this bug
Ok, on the correct package reverse-depends now shows:
$ reverse-depends src:nvidia-graphics-drivers-450-server
Reverse-Depends
===
* libnvidia-decode-440-server (for libnvidia-decode-450-server)
* libnvidia-encode-440-server (for libnvidia-encode-450-server)
*
$ reverse-depends src:nvidia-graphics-drivers-450
Reverse-Depends
===
* libnvidia-cfg1-430 [amd64](for libnvidia-cfg1-440)
* libnvidia-common-430 (for libnvidia-common-440)
* libnvidia-compute-430 [amd64 i386]
* libnvidia-decode-430 [amd64 i386]
* libnvidia-encode-430
Removing packages from mantic:
nvidia-graphics-drivers-390 390.157-0ubuntu8 in mantic
libcuda1-384 390.157-0ubuntu8 in mantic amd64
libnvidia-cfg1-390 390.157-0ubuntu8 in mantic amd64
libnvidia-common-390 390.157-0ubuntu8 in mantic amd64
$ reverse-depends src:nvidia-graphics-drivers-390
Reverse-Depends
===
* bumblebee-nvidia (for nvidia-driver-390)
$
bumblebee should be updated to drop the reference, so that any users who
still have this installed don't have it kept installed as a result of
this
https://git.launchpad.net/~ubuntu-cdimage/debian-
cd/+git/ubuntu/commit/?id=3b282009dc2eda1d450b88699d338b001ad43651
Result confirmed in https://cdimage.ubuntu.com/ubuntu-server/daily-
live/20230928.5/mantic-live-server-s390x.list.
** Changed in: ubuntu-cdimage
Status: New => Fix Released
** Changed in: ubuntu-drivers-common (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Mantic)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
On Wed, Sep 27, 2023 at 11:16:52PM -, Brian Murray wrote:
> However, using software-properties-gtk to install the proprietary driver
> (broadcom-sta-dkms) worked and the b43 driver was blacklisted and I was
> able to connect to a wireless network.
Does this mean the driver was not offered to
it's in the release pocket now.
** Changed in: dkms (Ubuntu Mantic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2036951
Title:
unblock request:
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided => Critical
** Also affects: nvidia-graphics-drivers-535 (Ubuntu Mantic)
Importance: Critical
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Bug description does not describe a beta-critical issue, only
autopkgtest failures. Should be unblocked after Beta is released.
** Changed in: dkms (Ubuntu Mantic)
Milestone: ubuntu-23.10-beta => None
--
You received this bug notification because you are a member of Kernel
Packages, which
The verification of the Stable Release Update for glibc 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
An upload of zfs-linux to jammy-proposed has been rejected from the
upload queue for the following reason: "no response from uploader to
incomplete bug status for >1m".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
the zfs dependency in question is systemd-udev-settle.
Sep 1 17:49:20 xubuntu udevadm[1064]: systemd-udev-settle.service is
deprecated. Please fix zfs-load-module.service, zfs-import-cache.service
not to pull it in.
(heh)
Sep 1 17:49:20 xubuntu systemd[1]: systemd-udev-settle.service: start
$ rmadison -s focal-proposed linux-ibm-lts-20.04
linux-ibm-lts-20.04 | 5.4.0.1056.85 | focal-proposed | amd64
$
It looks like the last request is superseded:
** Changed in: linux-meta-ibm-5.15 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a
looks good, thank you
** Changed in: zfs-linux (Ubuntu Mantic)
Status: New => Fix Committed
** Changed in: zfs-linux (Ubuntu Mantic)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Kernel
Packages,
Hello Ionut, or anyone else affected,
Accepted mutter into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The purpose of the size check in u-r-u is to ensure that we don't fail
mid-upgrade due to lack of disk space on /boot.
But AIUI that's not what happened here to the bug submitter; this is an
upgrade within an Ubuntu series between individual kernel packages.
We should NOT have a check in u-r-u
Removing packages from jammy-updates:
linux-meta-azure-fde-5.19 5.19.0.1025.28~22.04.1.7 in jammy
linux-azure-fde-5.19-edge 5.19.0.1025.28~22.04.1.7 in jammy
amd64
linux-cloud-tools-azure-fde-5.19-edge 5.19.0.1025.28~22.04.1.7
in jammy amd64
"@Andreas firmware-sof in Mantic is 2.2.6, which already has everything
in Acelan's merge proposal."
** Changed in: firmware-sof (Ubuntu Mantic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Anthony, I have no preference about 1 vs 2, I only ask that the bug (and
therefore the SRU verification process) be consistent with the upload.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
Hello Bin, or anyone else affected,
Accepted linux-restricted-modules-media-fixup into jammy-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/linux-restricted-modules-media-
fixup/22.04.1 in a few hours, and then in the -proposed repository.
Please
1 - 100 of 2524 matches
Mail list logo
