Public bug reported:
>From edos-distcheck report at https://magenta.jak-linux.org/ubuntu-
archive/distcheck/impish/release.txt
Packages build-depending on ukui-settings-daemon-dev:amd64:
* kylin-greeterbuild-depends on missing
ukui-settings-daemon-dev:amd64
This
Public bug reported:
My Unicomp has a right windows key and alt key in swapped positions, so
I configured right windows key to act as a second Alt_R (well
ISO_Level3_Shift), using gnome-tweaks, leading to:
/org/gnome/desktop/input-sources/xkb-options
['caps:none', 'lv3:rwin_switch']
Opening th
** Description changed:
[Impact]
Apple users were blocked from upgrading to hirsute in bug 1929449, the
underlying issue in shim has now been resolved, and they can upgrade again.
[Test plan]
- Upgrade an Apple machine running groovy to hirsute
+ Upgrade an Apple machine running groovy t
** Changed in: shim (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/1934780
Title:
shim crashes on Mellanox BF1 SmartNIC
To manage notifications about thi
While that is true, we also discovered another regression yesterday
which breaks booting on real hardware: In bug 1934780, we discovered
that Mellanox BF1 SmartNic do not support querying variable storage
info, and hence fail to boot. SUSE discovered similar issues.
I don't think this is ready for
The opposite, it only reads the mirrored ones, soon to be replaced by
config table.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934506
Title:
Mirrored MOK variables could be accidentally deleted
bionic looks good, in fresh multipass VM:
[...]
Get:4 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 autopkgtest
all 5.3.1ubuntu1.1 [126 kB]
focal 👍
ubuntu@focal:~$ sudo apt install autopkgtest
[...]
Get:4 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 autopkgtest
all 5.11ubuntu1.1 [137 kB]
[...]
ubuntu@focal:~$ autopkgtest-build-lxd ubuntu:hirsute
[...]
ubuntu@focal:~$ lxc launch autopkgtest/ubuntu/hirsute/amd64 t
Creatin
Marking as done, then; thanks Dan!
** Tags removed: verification-needed verification-needed-hirsute
** Tags added: verification-done verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
The regressions in autopkgtest reports are the same as last time, and
unrelated to this change - please bump the version number of the hint.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934650
Title
hirsute 👍 - all releases verified now
ubuntu@hirsute:~$ sudo apt install autopkgtest
[...]
Get:4 http://archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 autopkgtest
all 5.16ubuntu0.1 [141 kB]
[...]
ubuntu@hirsute:~$ lxd init --auto
ubuntu@hirsute:~$ autopkgtest-build-lxd ubuntu:hirsute
[...
Thank you for your bug report. Unfortunately, this is an issue in a
third-party package, and not in Ubuntu. I suggest you raise it with
them.
Presumably they are a Chrome-like package and this is a side-effect of
https://bugs.chromium.org/p/chromium/issues/detail?id=1106309&q=&can=4 -
if they inst
Patch
https://github.com/OpenMandrivaAssociation/grub2/blob/master/grub-2.02-fuse3.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935659
Title:
Please switch to fuse3
To manage notifications
Public bug reported:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if /usr/bin/zstd
does not exist, it will pas
Split out APT / python-apt into bug 1923845
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
To manage notifications about this bug go to:
Never mind the multiple requests thing, it's not going to work at the
moment anyway, because it's using async notifications rather than
waiting for the hook to answer. So that needs a 0.3 protocol :)
Anyhow, negotiating 0.2 shouldn't be too hard. If you see 0.2 in the
versions list, respond back w
This blocks apt in impish from migrating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925787
Title:
migrate advise-snap --from-apt to APT JSON hooks 0.2
To manage notifications about this bug go
Yes, see the tasks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921626
Title:
size mismatch error if request of unknown size is larger than others
To manage notifications about this bug go to:
h
Yes, it's exactly the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
shim-signed 15.4 does not boot on EFI 1.10 systems
To manage notifications about this bug go to:
https://bug
** Description changed:
[Impact]
APT in xenial needs to learn about zstd support to enable Launchpad to work
with zstd packages.
python-apt in all releases needs to be adjusted to pass the compressor
names instead of programs to ExtractTar, as otherwise, if /usr/bin/zstd
does not exi
OK, so what's going on is that ubuntu-release-upgrader-gtk is not
installed, and apt only updates phasing to upgrades, but not new
installs. Which fails in this case. Presumably it needs to apply phasing
to all packages in a source package if one of them is installed, but
that might be slow :(
--
Or we phase _everything_. Also makes code faster
** Also affects: apt (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Impish)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926150
Title:
[SRU] Backport
autopkgtests for apt have passed. I've build a patched version of
python-apt and verified that it worked with the apt version, so the apt
side is verified now :D
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You recei
FWIW, "during the life cycle" = "today" - the revocations for the old
shims have been published today: https://uefi.org/revocationlistfile
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925010
Title:
FWIW, I upgraded python-apt to the version in xenial-proposed
Unpacking python3-apt (1.1.0~beta1ubuntu0.16.04.12) over
(1.1.0~beta1ubuntu0.16.04.11) ...
And verified that the script
import apt_inst, apt_pkg
apt_pkg.init()
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").contro
** Changed in: python-apt (Ubuntu)
Assignee: (unassigned) => Steve Langasek (vorlon)
** Package changed: python-apt (Ubuntu) => apt (Ubuntu)
** Changed in: apt (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Maybe it should be a warning in the SRUs as opposed to a failure, but I
don't have a strong opinion. I'm a bit scared of breaking scripts. But
maybe that's a good thing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Just to not forget: This should work. We pass the ESP/boot partition to
kernel, initramfs then looks at it, and if it finds UUID on same drive,
it will take that one. If not it will take UUID from any drive, thus
handling RAID or encryption automagically.
--
You received this bug notification bec
That _is_ the kernel, well, its EFI stub.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865515
Title:
Chainbooting from grub over the network to local shim breaks chain of
trust
To manage notifi
Going to mark this as verified again for xenial, as .32 was a regression
fix for the relocation, but did not affect validation of this bug.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notificat
I reran the update-notifier test that failed with grub error in xenial
with the new grub added as trigger, and it installed now, so it's good
to go :D
Unpacking grub-efi-arm64 (2.04-1ubuntu44) over (2.02~beta2-36ubuntu3.29) ...
Preparing to unpack .../grub-efi-arm64-bin_2.04-1ubuntu44_arm64.deb ..
The xenial SRU should be good to go now, the snapcraft failures are
unrelated and also reproduced in vorlon's retry of snapcraft itself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926437
Title:
Public bug reported:
[Impact]
If a pocket is empty, apt will not download the empty packages files, causing
the repository to not be added to the cache. This in turn breaks commands such
as using apt install -t hirsute-backports as apt is unable to find the release
in the archive.
[Test plan]
Public bug reported:
[Impact]
TLS handshakes are reported as fatal errors rather than transient errors like
other connection errors on unencrypted connections. This seems wrong - a server
may just be spinning up or down and fail during the handshake, and prevents
retrying such downloads
[Test
** Changed in: apt (Ubuntu)
Importance: Undecided => Medium
** Changed in: apt (Ubuntu)
Importance: Medium => Low
** Changed in: apt (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
We set Acquire::Retries to 10 on autopkgtest.
** Changed in: apt (Ubuntu)
Status: New => Invalid
** Changed in: auto-package-testing
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
All the SRUs were released the same day, block tags were ignored :-(
** Changed in: apt (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918928
Title:
A
** Changed in: apt (Ubuntu)
Status: Fix Committed => 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/1918920
Title:
Harden test for no new acquires after transaction abort
To mana
** Changed in: apt (Ubuntu)
Status: New => Triaged
** Changed in: apt (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918930
Title:
Unexpected file si
The status file seems fine, apt is happy with it, this is either a bug
in apt-listchanges or a specific FS corruption, but haven't seen that
before.
** Package changed: apt (Ubuntu) => apt-listchanges (Ubuntu)
** Changed in: apt-listchanges (Ubuntu)
Status: New => Triaged
--
You received
The package foliocloudplugin is broken, it was probably written on a Mac
- the description ends lines with ^M instead of a newline. (and also
does not use a continuation line).
That said, apt-listchanges really ought to use apt_pkg TagFile parser
and not hack up its own one.
** Also affects: dpkg
dpkg also probably should validate the contents of that field and clean
it up if needed or reject install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854772
Title:
/var/lib/dpkg/status has fault
** Changed in: apt (Ubuntu Hirsute)
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/1921626
Title:
size mismatch error if request of unknown size is larger than
** Description changed:
+ [Impact]
+
+ Downloads fail if:
+
+ - there is at least one package each with Size and no size on a mirror
+ - a package without a Size field is larger than a package with a Size field
that's currently in the pipeline
+
+ Also, this was silent, we need to add an error
** Changed in: ubiquity (Ubuntu Hirsute)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: ubiquity (Ubuntu Hirsute)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: ubiquity (Ubuntu Hirsute)
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/1893964
Title:
Installation of Ubuntu Groovy with manual partitioni
It seems you are not using libapt-pkg6.0 in version 2.1.10ubuntu0.2 or
later? This issue was fixed in that version.
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
I mean 2.0.4, of course, which is included in the current LTS images
(20.04.2); your image is the previous version (20.04.1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923150
Title:
unexpected e
This was fixed in Version: 1.6~alpha6
** Changed in: apt (Ubuntu)
Status: Fix Committed => 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/310262
Title:
APT::Acquire::Retries onl
Marking the packaging tags as invalid, as the bug is fixed in apt 2.0.4
which is in the 20.04.2 images. This bug was tracked as bug 1871268 back
when it was being fixed.
** Changed in: apt (Ubuntu)
Status: Incomplete => Invalid
** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
Sta
Also add a Depends: apt in debian/tests/control so the test is triggered
automatically by apt!
** Changed in: update-manager (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Can confirm it's broken:
^['linux-.*'-5\.4\.0-72-generic$|^ 'kfreebsd-.*'-5\.4\.0-72-generic$|^
'gnumach-.*'-5\.4\.0-72-generic$|^ '.*-modules'-5\.4\.0-72-generic$|^
'.*-kernel'-5\.4\.0-72-generic$|^ 'linux-.*'-5\.4\.0-72-generic$|^
'kfreebsd-.*'-5\.4\.0-72-generic$|^ 'gnumach-.*'-5\
.4\.0-72-g
What you want is define
def set_versioned_kernel_pkgs(real_versioned_kernel_pkgs):
apt_pkg.config.clear("APT::VersionedKernelPackages")
for k in real_versioned_kernel_pkgs:
apt_pkg.config.set("APT::VersionedKernelPackages::", k)
and then use
real_versioned_kernel_pkgs = apt.apt_p
You must have accidentally mounted something into (/target)/boot/efi, as
otherwise the code does not trigger anymore. It seems likely you did
infact mount a removable ESP into it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Hmm I did not get the warning message about missing ESP when booting the
ISO as an usb stick instead of a CD. This is odd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924823
Title:
Ubiquity Ubunt
So what happens is that partman automatically discovers the ESP on the
USB stick, and configures it as EFI system partition (you can see it
says efi in the line). You have to go to the partition and tell it to
not use it.
Not sure what the right fix is. Cheap hack would be to only include EFI
syst
*** This bug is a duplicate of bug 1924823 ***
https://bugs.launchpad.net/bugs/1924823
** This bug has been marked a duplicate of bug 1924823
Ubiquity Ubuntu 21.04 install fail on legacy bios
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
*** This bug is a duplicate of bug 1924823 ***
https://bugs.launchpad.net/bugs/1924823
** This bug is no longer a duplicate of bug 1923134
replace prior 18.04 installation with 21.04 (no format of partition sda1)
** This bug has been marked a duplicate of bug 1924823
Ubiquity Ubuntu 21.0
*** This bug is a duplicate of bug 1924823 ***
https://bugs.launchpad.net/bugs/1924823
** This bug is no longer a duplicate of bug 1923134
replace prior 18.04 installation with 21.04 (no format of partition sda1)
** This bug has been marked a duplicate of bug 1924823
Ubiquity Ubuntu 21.0
*** This bug is a duplicate of bug 1924823 ***
https://bugs.launchpad.net/bugs/1924823
** This bug has been marked a duplicate of bug 1924823
Ubiquity Ubuntu 21.04 install fail on legacy bios
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Summary changed:
- Ubiquity Ubuntu 21.04 install fail on legacy bios
+ ESP on install medium automatically configured as ESP for install, failing
inst all
** Summary changed:
- ESP on install medium automatically configured as ESP for install, failing
inst all
+ ESP on install medium automa
*** This bug is a duplicate of bug 1924823 ***
https://bugs.launchpad.net/bugs/1924823
** This bug is no longer a duplicate of bug 1907180
hirsute QA-test install; 'grub-install /dev/sda failed' .. box regularly
used for QA-test installs (BIOS only box, but uEFI error?)
** This bug has be
*** This bug is a duplicate of bug 1924823 ***
https://bugs.launchpad.net/bugs/1924823
** This bug is no longer a duplicate of bug 1907180
hirsute QA-test install; 'grub-install /dev/sda failed' .. box regularly
used for QA-test installs (BIOS only box, but uEFI error?)
** This bug has be
*** This bug is a duplicate of bug 1924823 ***
https://bugs.launchpad.net/bugs/1924823
** This bug has been marked a duplicate of bug 1924823
Ubiquity Ubuntu 21.04 install fail on legacy bios
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Jeremie, you reported a separate bug for the issue of the installer
automatically picking up the USB stick's USB, please comment there if
you have to.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893
Yes, of course if you don't install the fixed version you still have the
broken one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923150
Title:
unexpected error pop-up after 'apt install nvidia-dr
Comment #11 - it looks you installed on GPT without a bios boot
partition, so there's no space to embed BIOS grub. The installer will
have warned you, please listen to it.
Jeremie, the correct workaround is to deselect the EFI system partition
when you configure partitions in the installer, as I e
This is a feature, not a bug.
** Changed in: ubiquity (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924856
Title:
Ubiquity creates useless ESR (EFI) partitio
I have applied a workaround in ubiquity that makes it ignore ESPs
smaller than 50 MB, which should fix this bug for most users, unless
some popular tool reformats the USB stick itself and creates a larger
ESP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@jibel The bug was explicitly not closed in the changelog, because this
is not the correct fix for it, just a workaround for standard install
mediums which have 5 MB size.
** Changed in: ubiquity (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you ar
Thanks for your bug report. Unfortunately, it lacks any actionable
information, because we don't know why packagekit is in a very bad
inconsistent state.
If you figure out the cause for this, please let us know.
Thanks!
** Changed in: packagekit (Ubuntu)
Status: New => Incomplete
--
You
Thank you for your bug report,
Unfortunately, there is not much we can do here - Your system ran out of
EFI variable storage place.
Your best bet is to find large EFI variables in
/sys/firmware/efi/efivars that are safe to delete and delete them. A
factory reset of the BIOS may also clear up the
Hi Sai!
That's the correct behaviour, we do want to create the ESP, and we also
do want you to create an ESP when partitioning.
The messaging is not entirely accurate on BIOS systems, as absence of
ESP is not immediately fatal, but only would be when you switch to UEFI
booting.
I think keeping t
This proposal seems somewhat incompatible with our resilient boot
specification.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923464
Title:
ideally should boot rootfs from a matching hard drive
T
** Package changed: update-manager (Ubuntu) => software-properties
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923358
Title:
Other servers doesn't display server list (Software Updater)
That said, you should be able to repopulate dbx by running sbkeysync.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924605
Title:
Grub2 menu not loading - could not create MokListXRT
To manage not
Deleting dbx is not advisable, it contains the list of revoked
certificates and binaries. The Mok* ones should be repopulated by shim
during boot, so are probably fine. You want to end up with the same
variables being back again after boot, essentially; but trigger garbage
collection in UEFI during
I don't understand what python-apt does here, it inherits zstd support
from apt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
To manage
There seems to be a bug in bionic's apt.
root@bb:/home/jak/Projects# python3 -c 'import apt_inst, apt_pkg;
apt_pkg.init();
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2_zstd1_all.deb").control.extractdata("control")'
Traceback (most recent call last):
File "", line 1, in
LookupError: Th
I have not tested hirsute in a clean container; but touch /usr/bin/zstd
makes it work, so the compressor lookup is broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compres
The fix is for Lenovo to issue a firmware update with the new dbx in
it's ro storage so it doesn't have to be in the efi vars. Seems unlikely
to happen though.
It's possible the variables are read only, which is why you can't delete
it.
I'm sorry to say, but these are firmware issues, there's not
Kernel messaging is also confusing for livepatch users which might not
have to reboot anyway
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925488
Title:
needrestart msg "The currently running kerne
Added additional verification steps for hirsute.
** Description changed:
[ Description ]
This is the codename for the release that will be 21.10
See the exception on https://wiki.ubuntu.com/StableReleaseUpdates
#distro-info-data
[ Test Case ]
-
- Verify that the following su
I verified software-properties-gtk works correctly on hirsute, and the
same stuff ddstreet did:
jak@jak-t480s:/$ dpkg -l|grep distro-info-data
Public bug reported:
APT has gained a new JSON hook protocol version, 0.2, and 0.1 is
deprecated with a warning in impish (as of apt 2.3.2)
* (incompatible change) The mode flag of arguments gained upgrade, downgrade,
reinstall modes. All of these are install
* (compatible change) The hooks org.
For details of the changes, see https://salsa.debian.org/apt-
team/apt/-/merge_requests/166
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925787
Title:
migrate advise-snap --from-apt to APT JSON ho
Please also fix the hook to accept multiple requests between the hello
and bye method. The goal has always been to start the hook just once and
then call it multiple times, and this breaks with current snapd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This has been fixed in 2.1.15 and newer versions, so starting with
hirsute. As the change is too invasive, it has not been backported to
older releases.
** Changed in: apt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
WRT your other comment: apt-transport-https is a binary package,
launchpad bugs are against source packages. Also apt-transport-https is
an empty transitional package, there is no separate https method
anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
No, that's completely unrelated. This here is firmwares not having
enough storage space. It's not a bug in shim. Potentially it can be
worked around by avoiding the mirroring of MokListX to MokListXRT, since
the information is mostly pointless to mirror.
--
You received this bug notification beca
Public bug reported:
[Impact]
We want to be able to use JSON hooks 0.2 in xenial and later releases to
display messages to users during dist-upgrade.
For xenial, we backport the JSON hook support in its entirety, whereas
for later releases, we only need to cherry-pick bugfixes and the v0.2
impro
These changes are in apt 2.3.2 which is queued for impish.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926150
Title:
[SRU] Backport JSON hooks 0.2
To manage notifications about this bug go to:
h
It's quite simply that the list in 21.04 is larger because it needs to
contain all our revoked binaries and that's why you run out of space.
Due to the pandemic, we were unable to switch signing certificates and
had to revoke all binaries via MokListX instead. Once the shard holders
can travel agai
The basic "turn the flag on" is landing in 2.3.2, I'll open other bug
reports for the backoff and server switching things I suppose.
** Changed in: apt (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: debmirror (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926120
Title:
Please merge debmirror 1:2.34 (universe) from Debian testing (main
Aside from the code being wrong - it's missing an apt_pkg.init_config(),
it also does not work with the config being setup; it needs to be
whitelisted.
So we definitely need to SRU APT. However, we are already preparing
1.2.35 at the moment for ESM enablement, I don't know if we want to
stuff both
Make sure that _apt user can read all files in /etc/apt/trusted.gpg.d
and /etc/apt/trusted.gpg and any key files you might have specified via
signed-by in sources.list.
By disabling the sandboxing, it makes it easier for an attacker that
controls the http server to make use of vulnerabilities in t
grub2-unsigned is supposed to be binary-copyable to older releases fwiw,
so it should be able to build with both fuse3 and fuse2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935659
Title:
grub2 F
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930741
Title:
20apt-esm-hook.conf is missing semicolons at end of option
To manage notifications about this bug go to
501 - 600 of 5951 matches
Mail list logo
