So the context you miss is that os-prober runs each time update-grub
runs on the system still.
The use case here is a highly unusual setup where another OS is directly
installed to a LUKS partition instead of using LVM on top of LUKS, and
one needs to balance whether this is a feature we care
$ reverse-depends -c main libgo23
Reverse-Depends
===
* libgo-14-dev
Packages without architectures listed are reverse-dependencies in: amd64,
arm64, armhf, i386, ppc64el, s390x
$ reverse-depends -c main libgo-14-dev
$ reverse-depends -c main lib32go-14-dev
$ reverse-depends -c main
Public bug reported:
All our architectures are supported by the standard Go toolchain, we
should demote the alternative gcc toolchain to universe, this includes
at least
libgo23 libgo-14-dev lib32go-14-dev libx32go-14-dev lib32go23 libx32go23
Possibly others but all the gccgo compilers
Untagging this, the patch could land via patch pilot, but this is not
really a high priority item.
** Tags removed: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/530252
Title:
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
** Changed in: glibc (Ubuntu Noble)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: glibc (Ubuntu Oracular)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
** Also affects: ubuntu-release-upgrader (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects:
Moving this to the pp cycle as no replacement has appeared yet, so we
can look at it again in 5-6 months.
** Tags removed: rls-oo-incoming
** Tags added: rls-pp-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: rls-oo-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063467
Title:
needrestart should mark services as needing a restart in systemd
To manage notifications about this
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
** Tags removed: rls-oo-incoming
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think this is more a misunderstanding here, but the "workaround" is
the right solution for this issue.
Specifically, unattended-upgrades is exactly designed to give you less
preferable upgrades because the others are reserved for manual upgrades
(i.e. -security vs -updates). That is, the
I'd suggest raising this with the Debian maintainer in their bug
tracker, but this doesn't seem like a good thing to deviate on for a
community-maintained package, it seems more vital that it be kept
uptodate (currently it's synced automatically from Debian, then it would
need manual work) and I
I tend to agree with zhjs; even if we could force it, cross-grading
ncurses-bin could get hairy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067228
Title:
ncurses/i386 autopkgtest failure
To
** Summary changed:
- [FFe] [HWE] fwupd-efi 1.6 and gnu-efi 3.0.18
+ [SRU] [HWE] fwupd-efi 1.6 and gnu-efi 3.0.18
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060197
Title:
[SRU] [HWE] fwupd-efi
** Tags added: foundations-todo
** 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 Ubuntu.
https://bugs.launchpad.net/bugs/2067886
Title:
Not being able to upgrade to 24.04 is (now) bug 2067886.
Also for 23.10 the bug was fixed in December in noble-proposed but the
SRU team never bothered releasing it in the 6 months and it got
overriden by a security update which also has been sitting around in
proposed since March now.
--
You
Public bug reported:
[Impact]
Upgrades for users with XFS /boot are wrongly blocked for noble as the
workaround for mantic hasn't been removed.
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
This is not an issue in the LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2039172
Title:
grub 2.12~rc1 fails to load files from large directories on XFS
To manage notifications about this bug
Sorry mawk is not actually essential, so in either case you miss a
Depends. Actually a PreDepends.
I do not believe a PreDepends: awk would work but I'm not sure - does it
require all awks to be configured or just one is the question.
--
You received this bug notification because you are a
The issue here is that apt is forced to remove libreadline8 to allow installing
libreadline8t64. The user has gawk installed which has the higher priority for
awk.
gawk is not essential so it doesn't have the immediate handling of an essential
package.
The python3-uno package uses awk in its
Public bug reported:
[Impact]
Upgrades to noble chmod /dev/null 644, breaking use of the device on multi-user
systems for non-root.
[Test plan]
1. do-release-upgrade mantic -> noble
2. check that /dev/null remains 666
[Where problems could occur]
[Details]
This is a regression of the fix for
Public bug reported:
[Impact]
If you set Dir::Cache or Dir::Cache::pkgcache to /dev/null, /dev/null is
chmodded as we chmod the cache file to 666. This is a semi-common pattern to
not use a cache, and breaks user scripts.
[Test plan]
1. autopkgtests run the large integration test suite
2. run
And sorry likewise, you also configured i386 which is only available on
archive.ubuntu.com and its mirrors.
So you can either drop that, why do you want i386 on arm?
Or you need to add Architectures: i386 to the archive.ubuntu.com
sources, and Architectures: arm64 to the ports.ubuntu.com ones.
This is to be expected, you have configured a mirror but you are using
an arm64 machine, which is only served by ports.ubuntu.com.
** Changed in: update-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
We're still going to need a couple more snapshots of backtraces - it's
important to check if we ever return from pkgDepCache::MarkInstall()
because I do not see an infinite loop in unattended-upgrades
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@jbicha can you provide input into why you removed the block-proposed
tag? This was breaking provisioning new CVM instances and it's not clear
to me that Azure has a new matching encrypt-cloud-image deployed that
would fix that issue.
--
You received this bug notification because you are a
@mfo The only autopkgtest regressions the bot mentioned and that are
visible still, are the ones I flagged earlier (albeit I don't know to
whom). That's software-properties-qt/unknown failing which is to be
expected - software-properties-qt got reabsorbed into this source
package so it cannot run
Public bug reported:
cups-browsed can hang at shutdown in a busy network, but there's nothing
important that requires it to have an ordered shutdown, so just set the
timeout to 0 to kill it immediately.
** Affects: cups (Ubuntu)
Importance: Undecided
Status: New
--
You received
So if you turn on Debug::pkgAcquire::Worker you should probably see it
fail after a @ Queue: Action combined for
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2003851
Title:
occasional hanging
The important point to note is that fetchAfter==0 is the default case if
we did not get retries, so every non-retried item has that value and we
don't want to cycle it. The loop's purpose is to find the smallest
timeout to wait for, as an _optimization_ to the select() call below,
such that if we
We're going to need to fix this properly rather than busy cycle the
queues outside the select loop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2003851
Title:
occasional hanging 'apt-get update'
** Package changed: grub2 (Ubuntu) => casper (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065315
Title:
NOBLE 24.04 Persistence is not enabled
To manage notifications about this bug go
Acknowledge. We need to identify a key package and see whether it
changes suites compared to the os-release. Usually that's base-files on
Debian.
I'll add this to my apt 3.0 UX improvements list.
** Changed in: apt (Ubuntu)
Status: Invalid => Triaged
** Tags added: foundations-todo
--
Removing the block-proposed tag for oracular
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060721
Title:
APT 2.8.0: Promote weak key warnings to errors
To manage
*** This bug is a duplicate of bug 2063094 ***
https://bugs.launchpad.net/bugs/2063094
** This bug has been marked a duplicate of bug 2063094
unattended-upgrades is running forever
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
bubblewrap should be won't fix per comment #91 from jjohansen
** Changed in: bubblewrap (Ubuntu)
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/2046844
Title:
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: Nick Rosbrook (enr0n) => (unassigned)
** Tags removed: rls-nn-incoming
** Tags added: rls-nn-notfixing
--
You received this bug notification because you
** Tags removed: 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/2061214
Title:
[SRU] Software Sources is not compatible with deb822
To manage notifications about this bug go to:
If users had installed both, any configuration made by ufw would have
been persisted by the -persistent packages and hence would be restored
by it.
They inadvertently had no Conflicts relationship declared, but sure
enough conflicted in practice.
There doesn't seem to be a reason why you'd
** Description changed:
- Upgrade from Jammy to Noble breaks iptables-persistent and netfilter-
- persistent firewall configuration if ufw is also installed pre-upgrade.
+ [Impact]
+ Upgrade from Jammy to Noble breaks iptables-persistent and
netfilter-persistent firewall configuration if ufw is
The same caveat applies to -updates, but there is a question of whether
we should ship 2.8.0 as this or make 2.8.0 different, I did not push a
tag for it yet.
i.e. given that this is a stable release update that will break PPAs
users currently have warnings for, it might make sense to make it
** Description changed:
- ⚠️ Only land this in the release pocket after PPAs have been resigned
+ ⚠️ Only land this in the release/updates pocket after PPAs have been
+ resigned
(This bumps the apt version to 2.8.0. APT uses the odd/even number
system, with 2.7.x being the development
Name resolution is broken here, hence we can't find a mirror for mantic
to upgrade to.
2024-04-05 02:42:24,073 DEBUG s='http' n='pl.archive.ubuntu.com'
p='/ubuntu//dists/mantic/Release' q='' f=''
2024-04-05 02:42:24,395 DEBUG error from httplib: ''
** Changed in: ubuntu-release-upgrader
** Summary changed:
- ubuntu upgrade (calculation) failed (Nvidia DGX Station)
+ 22.04 to 23.10 ubuntu upgrade (calculation) failed (Nvidia DGX Station)
** Summary changed:
- 22.04 to 23.10 ubuntu upgrade (calculation) failed (Nvidia DGX Station)
+ 18.04 to 20.04 ubuntu upgrade (calculation)
Please report individual crash reports for software that is crashing and
shipped by Ubuntu, and raise any crashes in 3rd party applications with
them. This is not an upgrade bug.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification
** Summary changed:
- 22.04 to 23.10 upgrade fails to keep kubuntu-desktop installed
+ 22.04 to 23.10 upgrade fails, kubuntu-desktop is not installable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed in git
** Also affects: ubuntu-release-upgrader (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You seem to be running a desktop machine, but you have removed the
ubuntu-desktop meta packages, hence it is trying to run in server mode.
Please install ubuntu-desktop and then retry the upgrade.
** Summary changed:
- Distro upgrade isn't working, PPA-'s removed
+ 22.04 to 23.10 upgrade fails:
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063981
Title:
Noble Numbat distribution upgrade failure too many
Hello,
what I could extract from all the text is that the upgrade from 22.04 to
23.10 failed because kubuntu-desktop is not installable.
I can reproduce this issue, and I'll just note that this is working fine when
trying the same with 24.04 (when it is turned on).
** Description changed:
+
Given that files disappear that we just unpacked this makes me believe
your file system is broken. I can see hanging kernel tasks in your
journal at the top, but it's too truncated. journald also is corrupted:
Apr 27 21:05:17 username systemd-journald[64573]: File
Fix committed in ubuntu/main
** Summary changed:
- Package wasn't installed on upgrade from Jammy to Noble
+ systemd-resolved wasn't installed on upgrade from Jammy to Noble
** No longer affects: systemd (Ubuntu)
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Fix
https://code.launchpad.net/~juliank/ubuntu-release-upgrader/+git/ubuntu-
release-upgrader/+merge/465148 speeds this up by roughly 35x for the
default lxc container. For larger upgrades, the speed up should probably
be even faster.
--
You received this bug notification because you are a member of
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
[Impact]
libraries become marked as manually installed after transitioning to t64
package names as we forgot to transition the automatically installed bit.
Before:
root@m:~# apt-mark showmanual
base-files
bash
bsdutils
cloud-init
dash
diffutils
eatmydata
findutils
grep
gzip
** Description changed:
- I just do-release-upgraded from Jammy to Noble on a pretty minimal
- server.
+ [Impact]
+ Upgrades from jammy to noble sometimes end up without systemd-resolved being
installed, breaking networking as the system already migrated to resolved in
jammy and now it
I don't recommend running with pcscd, it's much more stable to run with
direct access, but I do not know why it doesn't seem to work for you, it
certainly does for me.
It failing with pcscd is nice, it not telling us why and how to fix it
is bad UX though.
** Changed in: gnupg2 (Ubuntu)
Public bug reported:
bluca wrote:
> There is already an interface (property to set) to mark units for
need-restart or need-reload, and then a command to restart or reload
anything that is marked (systemctl reload-or-restart. --marked)
We should use the interface to mark the services we did not
Yeah sorry folks this was a bit awkward, to avoid respinning other
images we temporarily spun out software-properties-qt into its own
package (0.99.48.1) and fixed it there, and hence there was no bug
closure or anything. This will fold back into the main package in a
zero-day SRU in 0.99.49.
**
I'm unsubscribing as I only did a no-change rebuild. I'd generally
advise against using LC_ALL=C in any setting however, it's generally a
bad idea and you should use LC_ALL=C.UTF-8 instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 2061918 ***
https://bugs.launchpad.net/bugs/2061918
The issue here is undeclared dependencies on libglib2.0-0 in snapd /
deb2snap conversion packages, in this case, thunderbird, causing it to
fail to install, because an empty libglib2.0-0 transitional
The last comment made me realize we are talking about the Qt frontend
here, and yes, sure, we only ever implemented deb822 for the Gtk
frontend and the Dbus backend.
The Qt frontend needs to gain a deb822 entry editor dialog, possibly
some rendering fixes for deb822 source entries, and swap on
Public bug reported:
APT is currently overriden from required to important, this is causing
it not to be installed by default when bootstrapping with mmdebstrap.
** Affects: apt (Ubuntu)
Importance: Undecided
Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061754
Title:
nullboot 0.5.1
To manage notifications about this bug go to:
Please attach a tarball of your /etc/apt/sources.list and
/etc/apt/sources.list.d
** Changed in: software-properties (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: apt (Ubuntu Noble)
Status: New => Triaged
** Changed in: apt (Ubuntu Noble)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Tags added: block-proposed block-proposed-noble
** Tags removed: block-proposed-noble
** Description changed:
+ ⚠️ Only land this in the release pocket after PPAs have been resigned
+
(This bumps the apt version to 2.8.0. APT uses the odd/even number
system, with 2.7.x being the
Gauthier verified it still boots fine on CVM, hooray
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061754
Title:
nullboot 0.5.1
To manage notifications about this
** Changed in: nullboot (Ubuntu Noble)
Status: New => Fix Committed
** Description changed:
[Impact]
- new upstream release; usual dependency updates per Go MIR policy; aligning
with snapd 2.62; and support for shim 15.8 per the secboot dependency update.
+ new upstream release; usual
Public bug reported:
[Impact]
new upstream release; usual dependency updates per Go MIR policy; aligning with
snapd 2.62; and support for shim 15.8 per the secboot dependency update.
Targeted releases:
1. noble
2. jammy; after/when shim 15.8 lands there
3. focal; after/when shim 15.8 lands
*** This bug is a duplicate of bug 2060578 ***
https://bugs.launchpad.net/bugs/2060578
This was fixed in u-r-u in bug 2060578
** No longer affects: ubuntu-release-upgrader (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
We should do something like:
for package in cache:
if package.is_installed and :
replacement =
replacement.mark_install(auto_fix=False, auto_inst=False)
replacement.mark_remove(auto_fix=False)
To hint the solver to remove the installed pre-t64 packages and
jammy to mantic is not a particular interesting upgrade path, it's opt-
in only, so if nobody is interested in a mantic fix we shouldn't block
the jammy LTS fix for it. jammy users will be upgrading to noble and not
be affected by a mantic regression.
--
You received this bug notification
** Tags removed: 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/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a snap cgroup
To manage notifications about this bug go
So I think we should extend this to some more important packages in main
that were dropped in noble, but otherwise +1. And you do get the
obsolete package prompt in the end anyway.
** Tags removed: rls-nn-incoming
** Tags added: foundations-todo
--
You received this bug notification because you
** Tags removed: rls-nn-incoming
** Tags added: 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/2060311
Title:
Setting "optional: true" to overcome he timeout "Job systemd-networkd-
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-24.04
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Milestone: None => ubuntu-24.04
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: 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/2060581
Title:
stop shipping debian-installer package hook
To manage notifications about this bug go to:
This bug needs verification for mantic, added tags.
** Tags added: verification-needed verification-needed-mantic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057679
Title:
systemd-stub fails to
This bug needs verification for mantic, added tags.
** Tags removed: foundations-todo
** Tags added: verification-needed verification-needed-mantic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I cannot comment on what is happening here, but the patch is still there
and hasn't changed. If you delete /boot/grub/grub.cfg it would run os-
prober again or give a sensible error for what's happening.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sponsored, thanks
** Changed in: lxc (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/2059550
Title:
autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)
To
** Description changed:
(This bumps the apt version to 2.8.0. APT uses the odd/even number
system, with 2.7.x being the development series for 2.8, and this is the
only change left for the 2.8 release)
(This will be uploaded after the beta and may be released before noble
release, as
Public bug reported:
(This bumps the apt version to 2.8.0. APT uses the odd/even number
system, with 2.7.x being the development series for 2.8, and this is the
only change left for the 2.8 release)
(This will be uploaded after the beta and may be released before noble
release, as a zero day SRU
If I stage it there, I get shouted at for binary copying gnu-efi
unnecessarily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060197
Title:
[FFe] [HWE] fwupd-efi 1.5 and gnu-efi 3.0.18
To manage
Is it possible the 22.04 install was setup using legacy dm-raid format?
The legacy dm-raid format does not include a header so it looks like a
raw ext2 to grub and it can "embed" there (as it will see the ext2 on
either disk at boot).
Anyway, reassigning to subiquity for triaging.
** Also
Hi Gerald,
2.12 updates for stable releases should happen some time after the 24.04
release, early unsigned backports are in
https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/backports-build
I was hoping we'd have signed backports in the
Public bug reported:
The starfive and laptop kernels are obsolete, on mantic release version
still, and should be removed per discussion with kernel team on
Mattermost.
$ reverse-depends src:linux-starfive # some reverse-depends bug
$ reverse-depends src:linux-laptop
No reverse dependencies
** Also affects: grub2-unsigned (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: grub2-unsigned (Ubuntu Noble)
Importance: Medium
Assignee: Mate Kukri (mkukri)
Status: Fix Committed
--
You received this bug notification because you are a member of
** Changed in: grub2-unsigned (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/2054127
Title:
grub-efi crashes upon `exit`
To manage notifications about
** Also affects: grub2-unsigned (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: grub2-unsigned (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the bug report, unfortunately this has become quite
convoluted and I've identified at least 3 different strands of
discussion in here that are not related.
Some stuff, like "runuser" in a cron job is clearly never going to work,
but I don't know how the other two instances - sessions
** Patch added: "fwupd-efi-1.5.diff"
https://bugs.launchpad.net/ubuntu/+source/fwupd-efi/+bug/2060197/+attachment/5761554/+files/fwupd-efi-1.5.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
A new version of fwupd-efi has been released, adding support for
riscv64, as well as fixing some bugs. It requires gnu-efi 3.0.18. We'd
like to ship these in noble release; presumably we are going to end up
having to SRU them as well.
These are practically speaking syncs
** Changed in: grub2-unsigned (Ubuntu)
Status: New => 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/2060168
Title:
Prebuilt signed grub images should include f2fs and exfat modules
** Patch added: "gnu-efi-3.0.18.diff"
https://bugs.launchpad.net/ubuntu/+source/fwupd-efi/+bug/2060197/+attachment/5761553/+files/gnu-efi-3.0.18.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Geekley I personally agree and would go a lot further and hide even most
dependencies (you don't really care which libraries you are installing,
just about choices made, e.g. if there's an a | b dependency it should
tell you that it picked a).
So if you want to think about it that terse mode
Public bug reported:
This package cannot be upgraded, we're going to need a mantic SRU and an
ubuntu1 for noble.
** Affects: splix (Ubuntu)
Importance: High
Assignee: Till Kamppeter (till-kamppeter)
Status: New
--
You received this bug notification because you are a member
You may have heard about the xz-utils backdoor, compromised binaries
have been removed and replaced with older ones, and a partial amd64
rebuild is ongoing.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Please remove these packages from the release pocket,
jak@jak-t14-g3:~/Projects/Ubuntu/ubuntu-archive-tools:main$ reverse-depends
src:libtoxcore
Reverse-Depends
===
* qtox (for libtoxcore2)
* toxic (for
Public bug reported:
This is not compatible with the proposed gnome-shell 46 - depends gnome-
shell (<< 46~); has failing autopkgtest and no reverse depends:
jak@jak-t14-g3:~/Projects/Ubuntu/ubuntu-archive-tools:main$ reverse-depends
src:gnome-shell-pomodoro
No reverse dependencies found
1 - 100 of 4809 matches
Mail list logo