[Bug 2067138] [NEW] Dir::Cache=/dev/null chmods /dev/null
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 manually
apt-cache gencaches -o Dir::Cache::pkgcache=/dev/null
apt-cache gencaches -o Dir::Cache::srcpkgcache=/dev/null
apt-cache gencaches -o Dir::Cache=/dev/null
and observe that /dev/null is still correct.
[Where problems could occur]
We have eliminated writing the cache to /dev/null entirely:
--- a/apt-pkg/pkgcachegen.cc
+++ b/apt-pkg/pkgcachegen.cc
@@ -1637,6 +1637,10 @@ static DynamicMMap* CreateDynamicMMap(FileFd * const
CacheF, unsigned long Flags
static bool writeBackMMapToFile(pkgCacheGenerator * const Gen, DynamicMMap *
const Map,
std::string const )
{
+ // Do not write the file back to /dev/null or try to change its mode...
+ if (FileName == "/dev/null")
+ return true;
It's possible we may introduce issues later because something in there
does fancy bits and the cache in memory becomes invalid, but so far I
only saw that we calculate the hash in there, but we set dirty
afterwards and don't actually use the cache hash if we don't load from
disk so I think in reality this is not a problem, at least now. Just
gotta be careful to not stuff anything other than writing in there.
** Affects: apt (Ubuntu)
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/2067138
Title:
Dir::Cache=/dev/null chmods /dev/null
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2067138/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066998] Re: software update does not download updates, problem of sources, changing server does not help
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066998 Title: software update does not download updates, problem of sources, changing server does not help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2066998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066998] Re: software update does not download updates, problem of sources, changing server does not help
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066998 Title: software update does not download updates, problem of sources, changing server does not help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2066998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063094] Re: unattended-upgrades is running forever
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063094 Title: unattended-upgrades is running forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2063094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061754] Re: nullboot 0.5.1
@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 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: https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/2061754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061214] Re: [SRU] Software Sources is not compatible with deb822
@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 its own tests anymore - have to accept software-properties and force-badtest software-properties-qt as its binaries get superseded. -- 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: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066079] [NEW] cups-browsed.service should have 0s stop timeout
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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066079 Title: cups-browsed.service should have 0s stop timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2066079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775227] Re: "Create Role" and "Delete Role" buttons are missing for a domain admin user
I was looking at the status and made a mistake and changed it. Please, revert it to Triaged when possible. Thanks and sorry for the inconvenience. ** Changed in: horizon (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/1775227 Title: "Create Role" and "Delete Role" buttons are missing for a domain admin user To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1775227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
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 'apt-get update' from daily cronjob since Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
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 have an item queued to fetch in 5s we fetch it in 5s even if we received no updates from the workers to process. The queue is ordered such that all the 0 fetchAfter items come first (so as not to get stuck behind FetchAfter ones), but there may be an issue there since new owners of items can appear that can *change* the fetch after after we have inserted the item, it probably needs to be dequeued and requeued when an owner is added (or when we change FetchAfter of an owner, but I think we do there already). -- 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' from daily cronjob since Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
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' from daily cronjob since Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065528] [NEW] Ubuntu 24.04 LTS: Unreadable text in search bar in App Center with accessibility option "High Contrast"
Public bug reported: New installation of Ubuntu 24.04 LTS: When I activated the "High Contrast" accessibility option and opened the App Center, I noticed that the text in the search bar was not adequately visible. The color of the search bar background is very similar to the text color, making it illegible. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "There is text, illegible." https://bugs.launchpad.net/bugs/2065528/+attachment/5777665/+files/Screenshot%20from%202024-05-12%2010-13-23.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065528 Title: Ubuntu 24.04 LTS: Unreadable text in search bar in App Center with accessibility option "High Contrast" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2065528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065315] Re: NOBLE 24.04 Persistence is not enabled
** 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 to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2065315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 281232] Re: apt-get dist-upgrade shouldn't run when asked to upgrade between two releases
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/281232 Title: apt-get dist-upgrade shouldn't run when asked to upgrade between two releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/281232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
** Changed in: mutter (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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060721] Re: APT 2.8.0: Promote weak key warnings to errors
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2060721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060326] Re: unnattended upgrades stuck burning 100% cpu
*** 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 Ubuntu. https://bugs.launchpad.net/bugs/2060326 Title: unnattended upgrades stuck burning 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2060326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
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: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063128] Re: Upgrade from mantic to noble shows a debconf prompt
** 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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063128 Title: Upgrade from mantic to noble shows a debconf prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2063128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061214] Re: [SRU] Software Sources is not compatible with deb822
** 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: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061891] Re: Noble upgrade breaks iptables-persistent and netfilter-persistent usage
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 install persistent and disable its persistence service units. ** Changed in: ubuntu-release-upgrader (Ubuntu Noble) Status: Incomplete => Triaged ** Changed in: ubuntu-release-upgrader (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/2061891 Title: Noble upgrade breaks iptables-persistent and netfilter-persistent usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2061891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061891] Re: Noble upgrade breaks iptables-persistent and netfilter-persistent usage
** 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 also installed pre-upgrade. + [Test plan] + persistent and netfilter-persistent should remain installed, and ufw removed to preserve user config. + + [Where problems could occur] + There may be ufw reverse dependencies that could get removed. + + [Original bug report] from /var/log/dist-upgrade/apt.log: Broken ufw:amd64 Breaks on iptables-persistent:amd64 < 1.0.16 -> 1.0.20 @ii umU > - Considering iptables-persistent:amd64 -1 as a solution to ufw:amd64 5 - Added iptables-persistent:amd64 to the remove list - Conflicts//Breaks against version 1.0.16 for iptables-persistent but that is not InstVer, ignoring + Considering iptables-persistent:amd64 -1 as a solution to ufw:amd64 5 + Added iptables-persistent:amd64 to the remove list + Conflicts//Breaks against version 1.0.16 for iptables-persistent but that is not InstVer, ignoring Broken ufw:amd64 Breaks on netfilter-persistent:amd64 < 1.0.16 -> 1.0.20 @ii umU > - Considering netfilter-persistent:amd64 0 as a solution to ufw:amd64 5 - Added netfilter-persistent:amd64 to the remove list - Conflicts//Breaks against version 1.0.16 for netfilter-persistent but that is not InstVer, ignoring - MarkDelete iptables-persistent:amd64 < 1.0.16 -> 1.0.20 @ii umU > FU=0 - Fixing ufw:amd64 via remove of iptables-persistent:amd64 - MarkDelete netfilter-persistent:amd64 < 1.0.16 -> 1.0.20 @ii umU > FU=0 - Fixing ufw:amd64 via remove of netfilter-persistent:amd64 + Considering netfilter-persistent:amd64 0 as a solution to ufw:amd64 5 + Added netfilter-persistent:amd64 to the remove list + Conflicts//Breaks against version 1.0.16 for netfilter-persistent but that is not InstVer, ignoring + MarkDelete iptables-persistent:amd64 < 1.0.16 -> 1.0.20 @ii umU > FU=0 + Fixing ufw:amd64 via remove of iptables-persistent:amd64 + MarkDelete netfilter-persistent:amd64 < 1.0.16 -> 1.0.20 @ii umU > FU=0 + Fixing ufw:amd64 via remove of netfilter-persistent:amd64 ufw 0.36.2-1 add the breaks $ apt show ufw Package: ufw Version: 0.36.2-6 Priority: standard Section: admin Origin: Ubuntu Maintainer: Jamie Strandboge Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 869 kB Depends: iptables, ucf, python3:any, debconf (>= 0.5) | debconf-2.0 Suggests: rsyslog Breaks: iptables-persistent, netfilter-persistent Homepage: https://launchpad.net/ufw Task: standard Download-Size: 169 kB APT-Manual-Installed: no APT-Sources: http://phx-ad-3.clouds.archive.ubuntu.com/ubuntu noble/main amd64 Packages Description: program for managing a Netfilter firewall - The Uncomplicated FireWall is a front-end for iptables, to make managing a - Netfilter firewall easier. It provides a command line interface with syntax - similar to OpenBSD's Packet Filter. It is particularly well-suited as a - host-based firewall. + The Uncomplicated FireWall is a front-end for iptables, to make managing a + Netfilter firewall easier. It provides a command line interface with syntax + similar to OpenBSD's Packet Filter. It is particularly well-suited as a + host-based firewall. Post do-release-upgrade, iptables-persistent and netfilter-persistent are removed, which breaks any machines that relied on their configuration. ** Description changed: - [Impact] - 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 also installed pre-upgrade., removing them. + + ufw and -persistent packages both manage the firewall, hence they + conflict but they accidentally had no conflicts in jammy. + [Test plan] persistent and netfilter-persistent should remain installed, and ufw removed to preserve user config. [Where problems could occur] There may be ufw reverse dependencies that could get removed. [Original bug report] from /var/log/dist-upgrade/apt.log: Broken ufw:amd64 Breaks on iptables-persistent:amd64 < 1.0.16 -> 1.0.20 @ii umU > Considering iptables-persistent:amd64 -1 as a solution to ufw:amd64 5 Added iptables-persistent:amd64 to the remove list Conflicts//Breaks against version 1.0.16 for iptables-persistent but that is not InstVer, ignoring Broken ufw:amd64 Breaks on netfilter-persistent:amd64 < 1.0.16 -> 1.0.20 @ii umU > Considering netfilter-persistent:amd64 0 as a solution to ufw:amd64 5 Added netfilter-persistent:amd64 to the remove list Conflicts//Breaks against version 1.0.16 for netfilter-persistent but that is not InstVer, ignoring
[Bug 2060721] Re: APT 2.8.0: Promote weak key warnings to errors
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 break that a couple months down the road after we have a transition period, i.e. we can "timebomb" things by making apt treat the weak keys as expiring in August (August because we really want this sorted out by the point release when the big wave of 22.04 users upgrades). We could also introduce a new version of software-properties-common that adds PPA key refresh. We should then trigger that by apt postinst, or in the software-properties-common postinst. I do not believe we need to enforce a strict ordering relationship here, so 2.8.0 as is should technically be good to go. It's understandable that breaking existing repositories in a stable release is not optimal, however the warnings don't work as a security mechanism - we do not show you which weak keys are trusted, just which weak keys were used to sign the repository: Hence if you have a 1024R key and a 4096R that can sign a repository, but it's signed by the 4096R key now, you don't see the 1024R key, and an attacker could resign the repository with it and silently attack you. So this is something we do need to target for the first point release; we want users upgrading from 22.04 to not end up in the transitional stage where they have warnings. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2060721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060721] Re: APT 2.8.0: Promote weak key warnings to errors
** 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 series for 2.8, and this is the only change left for the 2.8 release, safe for some minor translation/test suite improvements) (This will be uploaded after the beta and may be released before noble release, as a zero day SRU or within the weeks following the release) [Impact] APT is currently just warning about keys that it should be rejecting to give Launchpad time to resign PPAs. This needs to be bumped to an error such that the crypto policy is fully implemented and we only trust keys that are still being trusted. #2055193 A warning provides some help right now to third-parties to fix their repositories, but it's not *safe*: A repository could have multiple signing keys and be signed by a good key now, then later, a previous key still in trusted.gpg.d could be revoked and we'd degrade to warnings, which, given that we update in the background automatically, the user may not see. Other fixes: - The test suite has been made less flaky in two places - Documentation translation has been unfuzzied for URL changes in 2.7.14 [Test plan] The vast regression test suite prevents regression in other components. Additional tests are: 1. (promotion to error) Take a repository that has a weak key warning, upgrade apt and check that it is an error 2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs work correctly. We don't have any tests for the test changes or the documentation translation URL unfuzzying. [Where problems could occur] apt will start to fail updates of repositories with weak signing keys, but it will have warned users about that before. Given that it is still early in the cycle, and we only enable updates for 24.04.1, this seems the right tradeoff for future security. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2060721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060256] Re: unable to upgrade 23.10
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 (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/2060256 Title: unable to upgrade 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2060256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061928] Re: 22.04 to 23.10 ubuntu upgrade (calculation) failed (Nvidia DGX Station)
** 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) failed (Nvidia DGX Station) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061928 Title: 18.04 to 20.04 ubuntu upgrade (calculation) failed (Nvidia DGX Station) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2061928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061238] Re: Unexpected Process Terminations in Ubuntu Noble Numbat (Development Branch)
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061238 Title: Unexpected Process Terminations in Ubuntu Noble Numbat (Development Branch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2061238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063952] Re: 22.04 to 23.10 upgrade fails, kubuntu-desktop is not installable.
** 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. https://bugs.launchpad.net/bugs/2063952 Title: 22.04 to 23.10 upgrade fails, kubuntu-desktop is not installable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064090] Re: Automatically installed bit not transitioned to t64 libraries
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064090 Title: Automatically installed bit not transitioned to t64 libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2064090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063897] Re: 22.04 to 23.10 upgrade fails: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages
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: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages ** 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/2063897 Title: 22.04 to 23.10 upgrade fails: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063981] Re: Noble Numbat distribution upgrade failure too many errors
** 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 errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063952] Re: Upgrade problem caused by many mistakes and broken packages.
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: + [Impact] + Upgrade of Kubuntu system from 22.04 to 23.10 fails with kubuntu-desktop not being installable. + + [Original bug report] + Upgrade problem caused by many mistakes and broken packages. Bug report 27 April 2024.in From Bas Roufs for Kubuntu developers. Mook, near Nijmegen, NL, 27 April 2024. Hello Everybody. Only a few weeks ago, I installed Kubuntu 22.04.1 LTS at my Lenovo Thinkpad X230 i5, 4GB RAM and 250 GB SSD at present. In a few weeks from now, I'll go to a computer repair shop that will add an extra SSD of 1 GB and 2 DDR 3, 1600 Mhz memory banks - with a view to getting 16 GB RAM. My idea was the following STEP 1. Prepare a system with the all the packages and languages modules I need for 10 languages - spell and grammar check, etc. STEP 2. Upgrade from Kubuntu 22.04.4 LTS to Kubuntu 24.04 LTS. However, it has become clear to me that a direct, automatic upgrade from the previous LTS to the current one is only possible after the issue of Kubuntu 24.04.1 LTS on 15 August 2024. This is way too late for me and in the middle of my holiday period. So, I have considered the option to make first an upgrade to Kubuntu 23.10, after which I would upgrade to 24.04. However, this attempt ended up in many, many complications as summarised here. STEP 3. Attempt to prepare a data only backup via Backintime or Luckybackup. However, Backintime seemingly caused complications as summarised below. STEP 3A. Attempt to prepare a system backup via Timeshift. However, this is too complicated for now - I'll start using Timeshift after getting the new 1 TB SSD. The old 250 GB SSD, I want to use for the Timeshift system-backup. My practice experience makes me clear that Timeshift is NOT AT ALL good for migration from one disk or one laptop to another. STEP 3B. Prepare migration from the smaller to the bigger SSD: via a compressed CloneZilla ISO image of the whole SSD at a Ventoy USB. Like this, I wanted to port all the packages, language modules, etc. to the bigger, new SSD. However, because of the complications summarised below, I need to make a fresh new install of, in this case, Kubuntu 24.04 LTS even before getting the hard ware upgrades: the extra SSD and RAM memory. With the language modules, packages, etc., I need to start again after fresh-installing «Noble Numbat». On the other hand, I stick to the plan to create a CloneZilla ISO: a compressed version of the contents my whole small 250 GB SDD. Like this, I want to get all the language settings, etc. to the new configuration after getting the new 1 TB SSD. STEP 3C. After getting the new SSD and RAM memory Installing the whole system and all data from the CloneZilla ISO. COMPLICATIONS EVER SINCE THURSDAY 25-04-2024. After installing Backintime, for the data only backup, the system does not 'see' anymore my 4 TB external hard disks, formatted in EXT4. Also a 2 TB USB stick formatted in FAT32 can not be used any more. Note - I am using USB 3.0 ports. So, I uninstalled again Backintime. However, this uninstallit ment action does not help. My system still does not "see" USB devices. That's why, I have copied some provisional data backups to Wetransfer. ASAP after fresh-installing Kubuntu 24.04 LTS, I'll retrieve my recent data from there. On Thursday, Kubuntu 24.04 LTS has been released. However, I do not manage to upgrade to it. That's why, I did several attempts to upgrade to Kubuntu 23.10, prior to upgrading to the newest LTS version. However, because of my ppa backports, I was not able to do an upgrade. So, I have removed the backports and also Flatpak - via the package managers at my system. However, those efforts did not help. Several attempts to upgrade to 23.10 ended up like this: «(...) bas@Camino:~$ sudo do-release-upgrade -m desktop Checking for a new Ubuntu release ERROR:root:getting the encoding failed Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeView.py", line 39, in - locale.setlocale(locale.LC_ALL, "") - File "/usr/lib/python3.10/locale.py", line 620, in setlocale - return _setlocale(category, locale) + File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeView.py", line 39, in + locale.setlocale(locale.LC_ALL, "") + File "/usr/lib/python3.10/locale.py", line 620, in setlocale + return _setlocale(category, locale) locale.Error: unsupported locale setting = Welcome to Ubuntu 23.10 'Mantic Minotaur' = The Ubuntu team is proud to announce Ubuntu 23.10 'Mantic Minotaur'.
[Bug 2063981] Re: Noble Numbat distribution upgrade failure too many errors
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 /run/log/journal/8bc63ca0b06d4ff59de1eb269b4ccb7a/system.journal corrupted or uncleanly shut down, renaming and replacing. I'd suggest running fsck. -- 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 errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063464] Re: systemd-resolved wasn't installed on upgrade from Jammy to Noble
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 Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: systemd-resolved wasn't installed on upgrade from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874272] Re: Stage "searching for obsolete software" takes a very long time (30 minutes)
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874272 Title: Stage "searching for obsolete software" takes a very long time (30 minutes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874272] Re: Stage "searching for obsolete software" takes a very long time (30 minutes)
** 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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874272 Title: Stage "searching for obsolete software" takes a very long time (30 minutes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064090] [NEW] Automatically installed bit not transitioned to t64 libraries
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 hostname init isc-dhcp-client isc-dhcp-common libeatmydata1 libwrap0 linux-base login ncurses-base ncurses-bin ncurses-term openssh-server openssh-sftp-server python-babel-localedata python3-babel python3-jinja2 python3-json-pointer python3-jsonpatch python3-jsonschema python3-markupsafe python3-pyrsistent python3-serial python3-tz ssh-import-id ubuntu-minimal ubuntu-server ubuntu-standard util-linux Broken After: base-files bash bsdutils cloud-init dash diffutils eatmydata findutils grep gzip hostname init isc-dhcp-client isc-dhcp-common libapt-pkg6.0t64 libarchive13t64 libatm1t64 libc6 libcurl3t64-gnutls libcurl4t64 libdb5.3t64 libdw1t64 libeatmydata1 libelf1t64 libevent-core-2.1-7t64 libext2fs2t64 libgdbm-compat4t64 libgdbm6t64 libglib2.0-0t64 libgnutls30t64 libgpgme11t64 libhogweed6t64 libisns0t64 libmagic1t64 libmspack0t64 libnettle8t64 libnpth0t64 libntfs-3g89t64 libnvme1t64 libparted2t64 libpng16-16t64 libpsl5t64 libreadline8t64 libssl3t64 libtirpc3t64 liburcu8t64 libuv1t64 libwrap0 libxmlsec1t64 libxmlsec1t64-openssl linux-base login ncurses-base ncurses-bin ncurses-term openssh-server openssh-sftp-server python-babel-localedata python3-babel python3-jinja2 python3-json-pointer python3-jsonpatch python3-jsonschema python3-markupsafe python3-pyrsistent python3-serial python3-tz ssh-import-id ubuntu-minimal ubuntu-server ubuntu-standard util-linux [Test plan] Launch a mantic container Upgrade to noble Check that the t64 libraries are automatically installed [Where problems could occur] Manual install requests are tried harder, but since we only hint the upgrade solver here, we don't expect this to cause any less successful install requests. ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Package changed: systemd (Ubuntu) => ubuntu-release-upgrader (Ubuntu) ** Description changed: [Impact] libraries become marked as manually installed after transitioning to t64 package names as we forgot to transition the automatically installed bit. - [Test plan] - Launch a mantic container - Upgrade to noble - Check that the t64 libraries are automatically installed - Before: - root@m:~# apt-mark showmanual + root@m:~# apt-mark showmanual base-files bash bsdutils cloud-init dash diffutils eatmydata findutils grep gzip hostname init isc-dhcp-client isc-dhcp-common libeatmydata1 libwrap0 linux-base login ncurses-base ncurses-bin ncurses-term openssh-server openssh-sftp-server python-babel-localedata python3-babel python3-jinja2 python3-json-pointer python3-jsonpatch python3-jsonschema python3-markupsafe python3-pyrsistent python3-serial python3-tz ssh-import-id ubuntu-minimal ubuntu-server ubuntu-standard - util-linux + util-linux + + Broken After: + base-files + bash + bsdutils + cloud-init + dash + diffutils + eatmydata + findutils + grep + gzip + hostname + init + isc-dhcp-client + isc-dhcp-common + libapt-pkg6.0t64 + libarchive13t64 + libatm1t64 + libc6 + libcurl3t64-gnutls + libcurl4t64 + libdb5.3t64 + libdw1t64 + libeatmydata1 + libelf1t64 + libevent-core-2.1-7t64 + libext2fs2t64 + libgdbm-compat4t64 + libgdbm6t64 + libglib2.0-0t64 + libgnutls30t64 + libgpgme11t64 + libhogweed6t64 + libisns0t64 + libmagic1t64 + libmspack0t64 + libnettle8t64 + libnpth0t64 + libntfs-3g89t64 + libnvme1t64 + libparted2t64 + libpng16-16t64 + libpsl5t64 + libreadline8t64 + libssl3t64 + libtirpc3t64 + liburcu8t64 + libuv1t64 + libwrap0 + libxmlsec1t64 + libxmlsec1t64-openssl + linux-base + login + ncurses-base + ncurses-bin + ncurses-term + openssh-server + openssh-sftp-server + python-babel-localedata + python3-babel + python3-jinja2 + python3-json-pointer + python3-jsonpatch + python3-jsonschema + python3-markupsafe + python3-pyrsistent + python3-serial + python3-tz + ssh-import-id + ubuntu-minimal + ubuntu-server + ubuntu-standard + util-linux + + + [Test plan] + Launch a mantic container + Upgrade to noble + Check that the t64 libraries are automatically installed [Where problems could occur] Manual install requests are tried harder, but since we only hint the upgrade solver here, we don't expect this to cause any less successful install requests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064090 Title: Automatically installed bit not transitioned to t64 libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2064090/+subscriptions -- ubuntu-bugs mailing list
[Bug 2063464] Re: Package wasn't installed on upgrade from Jammy to Noble
** 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 disappears. + + [Test plan] + Sadly we have so far been unable to reproduce the issue so we cannot provide a test plan to verify the fix right now. That said, the fix is the minimal "install it after marking the upgrades", so it should be obviously correct (TM). + + [Where problems could occur] + Problems could be expected around Conflicts/Breaks from or to systemd-resolved. + + systemd-resolved Provides and Conflicts with resolvconf, but it is the + only provider in the archive. systemd-resolved has no other Conflicts. + + There are no reverse-Breaks or reverse-Conflicts for systemd-resolved. + + Other dependency issues could occur if the dependencies of systemd- + resolved are unsatisfiable, however, systemd-resolved only requires + essential packages, systemd packages, and a dbus system bus. + + [Original bug report] + I just do-release-upgraded from Jammy to Noble on a pretty minimal server. After upgrade, network was fine but DNS names could not be resolved. I discovered systemd-resolved wasn't installed. I copied and installed that package manually, which immediately resolved the problem. So I assume this is a mistake in the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Apr 25 15:27:23 2024 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) - --- + --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:0:0:25766:2024-04-25 15:32:14.748564723 +:2024-04-25 15:32:14.747564766 +:/var/crash/_usr_bin_docker-compose.0.crash DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Tags: noble dist-upgrade Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-04-25 (0 days ago) UserGroups: N/A VarLogDistupgradeXorgFixuplog: - INFO:root:/usr/bin/do-release-upgrade running - INFO:root:No xorg.conf, exiting + INFO:root:/usr/bin/do-release-upgrade running + INFO:root:No xorg.conf, exiting _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063464 Title: Package wasn't installed on upgrade from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061708] Re: Yubikey stopped working after noble upgrade
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) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061708 Title: Yubikey stopped working after noble upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/archlinux-lp/+bug/2061708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063467] [NEW] needrestart should mark services as needing a restart in systemd
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 restart as needing one. ** Affects: needrestart (Ubuntu) Importance: Undecided Status: New ** Tags: rls-oo-incoming ** Tags added: 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 bug go to: https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2063467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061214] Re: [SRU] Software Sources is not compatible with deb822
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. ** Also affects: software-properties-qt (Ubuntu) Importance: Undecided Status: New ** Changed in: software-properties-qt (Ubuntu Noble) 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/2061214 Title: [SRU] Software Sources is not compatible with deb822 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062979] Re: unable to create ubuntu-noble image due to dictionaries-common config failure
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 Ubuntu. https://bugs.launchpad.net/bugs/2062979 Title: unable to create ubuntu-noble image due to dictionaries-common config failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063219] Re: mantic to noble upgrade failed
*** 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 package is unpacked early in the upgrade removing the library they need. The libssl3 is a strawman, it immediately gets solved by apt unpacking libssl3t64. I'm marking this as a duplicate of bug 2061918 where we track the bug already. ** This bug has been marked a duplicate of bug 2061918 package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063219 Title: mantic to noble upgrade failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061214] Re: Software sources not correctly updated after upgrade and/or new installs
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 deb822=True in the SoftwareProperties.__init__() supercall to enable it. -- 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: Software sources not correctly updated after upgrade and/or new installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063101] [NEW] Update apt override from important to required
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) Status: New ** Changed in: apt (Ubuntu) Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063101 Title: Update apt override from important to required To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2063101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061754] Re: nullboot 0.5.1
** 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: https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/2061754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061214] Re: Software sources not correctly updated after upgrade
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. https://bugs.launchpad.net/bugs/2061214 Title: Software sources not correctly updated after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060721] Re: APT 2.8.0: Promote weak key warnings to errors
** 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.launchpad.net/bugs/2060721 Title: APT 2.8.0: Promote weak key warnings to errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2060721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060721] Re: APT 2.8.0: Promote weak key warnings to errors
** 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 development series for 2.8, and this is the only change left for the 2.8 release, safe for some minor translation/test suite improvements) (This will be uploaded after the beta and may be released before noble release, as a zero day SRU or within the weeks following the release) [Impact] APT is currently just warning about keys that it should be rejecting to give Launchpad time to resign PPAs. This needs to be bumped to an error such that the crypto policy is fully implemented and we only trust keys that are still being trusted. #2055193 A warning provides some help right now to third-parties to fix their repositories, but it's not *safe*: A repository could have multiple signing keys and be signed by a good key now, then later, a previous key still in trusted.gpg.d could be revoked and we'd degrade to warnings, which, given that we update in the background automatically, the user may not see. Other fixes: - The test suite has been made less flaky in two places - Documentation translation has been unfuzzied for URL changes in 2.7.14 [Test plan] The vast regression test suite prevents regression in other components. Additional tests are: 1. (promotion to error) Take a repository that has a weak key warning, upgrade apt and check that it is an error 2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs work correctly. We don't have any tests for the test changes or the documentation translation URL unfuzzying. [Where problems could occur] apt will start to fail updates of repositories with weak signing keys, but it will have warned users about that before. Given that it is still early in the cycle, and we only enable updates for 24.04.1, this seems the right tradeoff for future security. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2060721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061754] Re: nullboot 0.5.1
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 bug go to: https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/2061754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061754] Re: nullboot 0.5.1
** 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 vendored dependency updates per Go MIR policy (vendor/ directory is automatically generated by go mod vendor based on go.mod); 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 there [Test plan] * Test suite passes * Deploy Azure CVM and TPM FDE * Upgrade to this new package and reboot * Boot should be successful * Double check bios_measurements_log to ensure that the newly update shim was used for boot (https://github.com/canonical/tcglog-parser/tree/master/tcglog-dump can be used to extract checksum of the shim binary used at boot and compared to the one shipped in nullboot) * CPC - build new image with nullboot preinstalled, and attempt to register and boot such an images as first time. We have set block-proposed to allow testing in noble-proposed to be carried out before migration to noble release pocket. [Where problems could occur] Resealing of Azure CVM machines could fail and they would need to be unlocked with a recovery key. -- 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: https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/2061754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061754] [NEW] nullboot 0.5.1
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 there [Test plan] * Test suite passes * Deploy Azure CVM and TPM FDE * Upgrade to this new package and reboot * Boot should be successful * Double check bios_measurements_log to ensure that the newly update shim was used for boot (https://github.com/canonical/tcglog-parser/tree/master/tcglog-dump can be used to extract checksum of the shim binary used at boot and compared to the one shipped in nullboot) * CPC - build new image with nullboot preinstalled, and attempt to register and boot such an images as first time. We have set block-proposed to allow testing in noble-proposed to be carried out before migration to noble release pocket. [Where problems could occur] Resealing of Azure CVM machines could fail and they would need to be unlocked with a recovery key. ** Affects: nullboot (Ubuntu) Importance: Undecided Status: New ** Affects: nullboot (Ubuntu Focal) Importance: Undecided Status: New ** Affects: nullboot (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: nullboot (Ubuntu Noble) Importance: Undecided Status: New ** Tags: block-proposed ** 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. + Targeted releases: + + 1. noble + 2. jammy; after/when shim 15.8 lands there + 3. focal; after/when shim 15.8 lands there [Test plan] * Test suite passes * Deploy Azure CVM and TPM FDE * Upgrade to this new package and reboot * Boot should be successful * Double check bios_measurements_log to ensure that the newly update shim was used for boot (https://github.com/canonical/tcglog-parser/tree/master/tcglog-dump can be used to extract checksum of the shim binary used at boot and compared to the one shipped in nullboot) * CPC - build new image with nullboot preinstalled, and attempt to register and boot such an images as first time. We have set block-proposed to allow testing in noble-proposed to be carried out before migration to noble release pocket. [Where problems could occur] Resealing of Azure CVM machines could fail and they would need to be unlocked with a recovery key. ** Also affects: nullboot (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nullboot (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nullboot (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/2061754 Title: nullboot 0.5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/2061754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054908] Re: gpg-wks-server pulls in postfix
*** 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. https://bugs.launchpad.net/bugs/2054908 Title: gpg-wks-server pulls in postfix To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2054908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061175] [NEW] Handle (t64) package replacements
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 install packages replacing it. We gotta do some auto_fix, auto_inst False stuff as we do not want to resolve the dependencies at this point, let the upgrader work on this. I do not believe we have to protect our choice to remove the packages here like we did for gpg-wks-server as the packages are not updatable, but I can't say I've checked. Potentially maybe just the mark_install are enough since they will inevitably result in removals anyway, but this would be easier if the removal sticks around. ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: foundations-todo ** 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/2061175 Title: Handle (t64) package replacements To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2061175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056442] Re: Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056442 Title: Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod `run/shm`: Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2056442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
** 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 to: https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060220] Re: Prevent release upgrades for users running on armhf
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060220 Title: Prevent release upgrades for users running on Raspberry Pis To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2060220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
** 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- wait-online" does no longer work with latest noble image To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2060311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060311 Title: Setting "optional: true" to overcome he timeout "Job systemd-networkd- wait-online" does no longer work with latest noble image To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2060311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060581] Re: stop shipping debian-installer package hook
** 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: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2060581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057679] Re: systemd-stub fails to boot when loaded via peimage
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 boot when loaded via peimage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2057679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054127] Re: grub-efi crashes upon `exit`
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. https://bugs.launchpad.net/bugs/2054127 Title: grub-efi crashes upon `exit` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2054127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059550] Re: autopkgtest failures on 1:5.0.3-2ubuntu3 (Noble)
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2059550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060721] Re: APT 2.8.0: Promote weak key warnings to errors
** 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 a zero day SRU or within the weeks following the release) [Impact] APT is currently just warning about keys that it should be rejecting to give Launchpad time to resign PPAs. This needs to be bumped to an error such that the crypto policy is fully implemented and we only trust keys that are still being trusted. #2055193 A warning provides some help right now to third-parties to fix their repositories, but it's not *safe*: A repository could have multiple signing keys and be signed by a good key now, then later, a previous key still in trusted.gpg.d could be revoked and we'd degrade to warnings, which, given that we update in the background automatically, the user may not see. + Other fixes: + - The test suite has been made less flaky in two places + - Documentation translation has been unfuzzied for URL changes in 2.7.14 + [Test plan] The vast regression test suite prevents regression in other components. Additional tests are: 1. (promotion to error) Take a repository that has a weak key warning, upgrade apt and check that it is an error 2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs work correctly. + We don't have any tests for the test changes or the documentation + translation URL unfuzzying. + [Where problems could occur] apt will start to fail updates of repositories with weak signing keys, but it will have warned users about that before. Given that it is still early in the cycle, and we only enable updates for 24.04.1, this seems the right tradeoff for future security. ** 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) + only change left for the 2.8 release, safe for some minor + translation/test suite improvements) (This will be uploaded after the beta and may be released before noble release, as a zero day SRU or within the weeks following the release) [Impact] APT is currently just warning about keys that it should be rejecting to give Launchpad time to resign PPAs. This needs to be bumped to an error such that the crypto policy is fully implemented and we only trust keys that are still being trusted. #2055193 A warning provides some help right now to third-parties to fix their repositories, but it's not *safe*: A repository could have multiple signing keys and be signed by a good key now, then later, a previous key still in trusted.gpg.d could be revoked and we'd degrade to warnings, which, given that we update in the background automatically, the user may not see. Other fixes: - The test suite has been made less flaky in two places - Documentation translation has been unfuzzied for URL changes in 2.7.14 [Test plan] The vast regression test suite prevents regression in other components. Additional tests are: 1. (promotion to error) Take a repository that has a weak key warning, upgrade apt and check that it is an error 2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs work correctly. We don't have any tests for the test changes or the documentation translation URL unfuzzying. [Where problems could occur] apt will start to fail updates of repositories with weak signing keys, but it will have warned users about that before. Given that it is still early in the cycle, and we only enable updates for 24.04.1, this seems the right tradeoff for future security. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2060721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060721] [NEW] APT 2.8.0: Promote weak key warnings to errors
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 or within the weeks following the release) [Impact] APT is currently just warning about keys that it should be rejecting to give Launchpad time to resign PPAs. This needs to be bumped to an error such that the crypto policy is fully implemented and we only trust keys that are still being trusted. #2055193 A warning provides some help right now to third-parties to fix their repositories, but it's not *safe*: A repository could have multiple signing keys and be signed by a good key now, then later, a previous key still in trusted.gpg.d could be revoked and we'd degrade to warnings, which, given that we update in the background automatically, the user may not see. [Test plan] The vast regression test suite prevents regression in other components. Additional tests are: 1. (promotion to error) Take a repository that has a weak key warning, upgrade apt and check that it is an error 2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs work correctly. [Where problems could occur] apt will start to fail updates of repositories with weak signing keys, but it will have warned users about that before. Given that it is still early in the cycle, and we only enable updates for 24.04.1, this seems the right tradeoff for future security. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Affects: apt (Ubuntu Noble) Importance: Undecided Status: New ** Description changed: [Impact] - APT is currently just warning about keys that it should be rejecting to give Launchpad time to resign PPAs. This needs to be bumped to an error such that the crypto policy is fully implemented and we only trust keys that are still being trusted. #2055193 + APT is currently just warning about keys that it should be rejecting to give Launchpad time to resign PPAs. This needs to be bumped to an error such that the crypto policy is fully implemented and we only trust keys that are still being trusted. #2055193 A warning provides some help right now to third-parties to fix their repositories, but it's not *safe*: A repository could have multiple signing keys and be signed by a good key now, then later, a previous key still in trusted.gpg.d could be revoked and we'd degrade to warnings, which, given that we update in the background automatically, the user may not see. [Test plan] The vast regression test suite prevents regression in other components. Additional tests are: 1. (promotion to error) Take a repository that has a weak key warning, upgrade apt and check that it is an error 2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs work correctly. + + [Where problems could occur] + apt will start to fail updates of repositories with weak signing keys, but it will have warned users about that before. Given that it is still early in the cycle, and we only enable updates for 24.04.1, this seems the right tradeoff for future security. ** 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). + [Impact] APT is currently just warning about keys that it should be rejecting to give Launchpad time to resign PPAs. This needs to be bumped to an error such that the crypto policy is fully implemented and we only trust keys that are still being trusted. #2055193 A warning provides some help right now to third-parties to fix their repositories, but it's not *safe*: A repository could have multiple signing keys and be signed by a good key now, then later, a previous key still in trusted.gpg.d could be revoked and we'd degrade to warnings, which, given that we update in the background automatically, the user may not see. [Test plan] The vast regression test suite prevents regression in other components. Additional tests are: 1. (promotion to error) Take a repository that has a weak key warning, upgrade apt and check that it is an error 2. (still valid) Check that the main Ubuntu repositories and/or resigned PPAs work correctly. [Where problems could occur] apt will start to fail updates of repositories with weak signing keys, but it will have warned users about that before. Given that it is still early in the cycle, and we only enable updates for 24.04.1, this seems the right tradeoff for future security. ** Summary changed: - Promote weak key warnings to errors + APT 2.8.0: Promote weak key warnings to errors ** Also affects: apt (Ubuntu Noble) Importance: Undecided Status: New ** Description changed:
[Bug 2060197] Re: [FFe] [HWE] fwupd-efi 1.5 and gnu-efi 3.0.18
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd-efi/+bug/2060197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060695] Re: 24.04 grub-pc cannot upgrade on mirrored software RAID root disk
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 affects: subiquity Importance: Undecided Status: New ** Changed in: grub2 (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/2060695 Title: 24.04 grub-pc cannot upgrade on mirrored software RAID root disk To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2060695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947046] Re: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary
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 https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/backports- proposed-public now for easier testing, but the priority right now I think is to get 24.04 released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947046 Title: EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1947046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060560] [NEW] Remove obsolete kernels from noble
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 found $ reverse-depends src:linux-meta-starfive No reverse dependencies found ** Affects: linux-laptop (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-meta-starfive (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-starfive (Ubuntu) Importance: Undecided Status: Fix Released ** Also affects: linux-starfive (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-meta-starfive (Ubuntu) Importance: Undecided Status: New ** Description changed: - The starfive and laptop kernels are obsolete and should be removed per - discussion with kernel team on Mattermost. + 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 found $ reverse-depends src:linux-meta-starfive No reverse dependencies found -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060560 Title: Remove obsolete kernels from noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-laptop/+bug/2060560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054127] Re: grub-efi crashes upon `exit`
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054127 Title: grub-efi crashes upon `exit` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2054127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054127] Re: grub-efi crashes upon `exit`
** 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2054127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057679] Re: systemd-stub fails to boot when loaded via peimage
** 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. https://bugs.launchpad.net/bugs/2057679 Title: systemd-stub fails to boot when loaded via peimage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2057679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
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 without session busses and issues with VNC connections are affected. I'd advise filing clear succinct reproducible issues for those cases, but I don't think there's much that can be done with this bug anymore. ** Changed in: x2goserver (Ubuntu) Status: Confirmed => Incomplete ** Changed in: snapd (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/1951491 Title: Can't run snaps: .slice/session-1.scope is not a snap cgroup To manage notifications about this bug go to: https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060197] Re: [FFe] [HWE] fwupd-efi 1.5 and gnu-efi 3.0.18
** 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. https://bugs.launchpad.net/bugs/2060197 Title: [FFe] [HWE] fwupd-efi 1.5 and gnu-efi 3.0.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd-efi/+bug/2060197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060197] [NEW] [FFe] [HWE] fwupd-efi 1.5 and gnu-efi 3.0.18
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 from Debian, going through the signing PPA for fwupd-efi. ** Affects: fwupd-efi (Ubuntu) Importance: Undecided Status: New ** Affects: gnu-efi (Ubuntu) Importance: Undecided Status: New ** Tags: noble ** Also affects: fwupd-efi (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [FFe] fwupd-efi 1.5 and gnu-efi 3.0.18 + [FFe] [HWE] fwupd-efi 1.5 and gnu-efi 3.0.18 ** Description changed: 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 from Debian, going through the + signing PPA for fwupd-efi. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd-efi/+bug/2060197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060168] Re: Prebuilt signed grub images should include f2fs and exfat modules
** 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2060168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060197] Re: [FFe] [HWE] fwupd-efi 1.5 and gnu-efi 3.0.18
** 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. https://bugs.launchpad.net/bugs/2060197 Title: [FFe] [HWE] fwupd-efi 1.5 and gnu-efi 3.0.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd-efi/+bug/2060197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1988819] Re: When apt keeps back packages due to phased updates, it should list them separately
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 would end up looking something like: Installing 5 specified packages, 10 upgrades and 30 new dependencies: - Choosing banana to satisfy foo Depends: banana | apple Removing 30 packages: - package1 ... At the moment there is no option in between full output and no output, though, and there is opposition to adding more output modes upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1988819 Title: When apt keeps back packages due to phased updates, it should list them separately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060038] [NEW] splix version 2.0.0+svn315-7fakesync1ubuntu0.22.04.1 in jammy is higher than versions in mantic and noble
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060038 Title: splix version 2.0.0+svn315-7fakesync1ubuntu0.22.04.1 in jammy is higher than versions in mantic and noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/splix/+bug/2060038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059853] Re: apt amd64 2.7.14 is missing on Ubuntu Noble?
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059853 Title: apt amd64 2.7.14 is missing on Ubuntu Noble? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2059853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059290] [NEW] RM: libtoxcore, qtox, toxic, utox - release pocket
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 libtoxcore2) * utox (for libtoxcore2) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x jak@jak-t14-g3:~/Projects/Ubuntu/ubuntu-archive-tools:main$ reverse-depends src:libtoxcore -b Reverse-Testsuite-Triggers == * qtox (for libtoxcore-dev) * utox (for libtoxcore-dev) Reverse-Build-Depends = * qtox (for libtoxcore-dev) * toxic (for libtoxcore-dev) * utox (for libtoxcore-dev) jak@jak-t14-g3:~/Projects/Ubuntu/ubuntu-archive-tools:main$ reverse-depends src:qtox No reverse dependencies found jak@jak-t14-g3:~/Projects/Ubuntu/ubuntu-archive-tools:main$ reverse-depends src:qtox -b No reverse dependencies found jak@jak-t14-g3:~/Projects/Ubuntu/ubuntu-archive-tools:main$ reverse-depends src:toxic No reverse dependencies found jak@jak-t14-g3:~/Projects/Ubuntu/ubuntu-archive-tools:main$ reverse-depends src:toxic -b No reverse dependencies found jak@jak-t14-g3:~/Projects/Ubuntu/ubuntu-archive-tools:main$ reverse-depends src:utox No reverse dependencies found jak@jak-t14-g3:~/Projects/Ubuntu/ubuntu-archive-tools:main$ reverse-depends src:utox -b No reverse dependencies found ** Affects: libtoxcore (Ubuntu) Importance: Undecided Status: New ** Tags: time-t -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059290 Title: RM: libtoxcore, qtox, toxic, utox - release pocket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtoxcore/+bug/2059290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059285] [NEW] RM: gnome-shell-pomodoro; blocks transitions
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 jak@jak-t14-g3:~/Projects/Ubuntu/ubuntu-archive-tools:main$ reverse-depends src:gnome-shell-pomodoro -b No reverse dependencies found Remove source and binaries from both pockets ** Affects: gnome-shell-pomodoro (Ubuntu) Importance: Undecided Status: New ** Tags: time-t -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059285 Title: RM: gnome-shell-pomodoro; blocks transitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-pomodoro/+bug/2059285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059282] [NEW] RM: pytest-services; fails to test on armhf, blocks libmemcached
Public bug reported:
Weird path related error:
319s ERRORS
319s _ ERROR at setup of test_mysql
_
319s
319s run_services = True
319s tmp_path_factory = TempPathFactory(_given_basetemp=None,
_trace=,
_basetemp=PosixPath('/tmp/pytest-of-root/pytest-0'), _retention_count=3,
_retention_policy='all')
319s memory_temp_dir = '/dev/shm/sr-364c4769b3ce43e29aa88f73641fdc8a-local/tmp'
319s request = >
319s
319s @pytest.fixture(scope='session')
319s def mysql_defaults_file(
319s run_services, tmp_path_factory, memory_temp_dir, request):
319s """MySQL defaults file."""
319s if run_services:
319s > cfg = tmp_path_factory.mktemp(request.session.name)
319s E ValueError: . is not a normalized and relative path
319s
319s /usr/lib/python3/dist-packages/pytest_services/mysql.py:19: ValueError
No reverse-depends:
jak@jak-t14-g3:~/Projects/Ubuntu/ubuntu-archive-tools:main$ reverse-depends
src:pytest-services
No reverse dependencies found
jak@jak-t14-g3:~/Projects/Ubuntu/ubuntu-archive-tools:main$ reverse-depends
src:pytest-services -b
No reverse dependencies found
Please let's just remove it.
** Affects: pytest-services (Ubuntu)
Importance: Undecided
Assignee: Łukasz Zemczak (sil2100)
Status: Fix Released
** Tags: time-t
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059282
Title:
RM: pytest-services; fails to test on armhf, blocks libmemcached
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pytest-services/+bug/2059282/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059277] [NEW] ngircd: RM armhf binaries
Public bug reported: Please rm armhf binaries for ngircd jak@jak-t14-g3:~/Downloads/rugged-1.7.1$ reverse-depends src:ngircd -b No reverse dependencies found jak@jak-t14-g3:~/Downloads/rugged-1.7.1$ reverse-depends src:ngircd No reverse dependencies found blocks libident ** Affects: ngircd (Ubuntu) Importance: Undecided Status: New ** Tags: time-t update-excuse ** Tags added: time-t update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059277 Title: ngircd: RM armhf binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ngircd/+bug/2059277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059275] [NEW] libgit2 vs ruby-rugged regression
Public bug reported:
ruby-rugged/1.7.1+ds-1build2
302s -{:name=>"Random J Hacker", :email=>"ha...@example.com", :time=>2017-07-07
10:28:30 +}
302s +{:name=>"Random J Hacker", :email=>"ha...@example.com", :time=>2017-07-07
12:28:30.6 +0200}
Time stamps are off .6 seconds when built with 64-bit time_t. This
is awkward because libgit2 already used an internal 64-bit time type.
** Affects: libgit2 (Ubuntu)
Importance: Undecided
Status: New
** Affects: ruby-rugged (Ubuntu)
Importance: Undecided
Status: New
** Tags: time-t update-excuse
** Summary changed:
- libgit2: ruby-rugged regression
+ libgit2 vs ruby-rugged regression
** Also affects: ruby-rugged (Ubuntu)
Importance: Undecided
Status: New
** Tags added: time-t update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059275
Title:
libgit2 vs ruby-rugged regression
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgit2/+bug/2059275/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059274] Re: dgit time_t regression
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059274 Title: dgit time_t regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dgit/+bug/2059274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059274] [NEW] dgit time_t regression
Public bug reported: on armhf, test gdr-newupstream currently fails with: 3107s ' 3107s + clog-check-1 before-new-upstream 3107s + before=before-new-upstream 3107s ++ git log --format=%aD -n1 debian/changelog 3107s + date='Tue, 26 Jun 2018 09:00:03 +0100' 3107s ++ date -R -d 'Tue, 26 Jun 2018 09:00:03 +0100' 3107s + date='Tue, 26 Jun 2018 08:00:03 +' 3107s + git show before-new-upstream:debian/changelog 3107s + m=' * Update to new upstream version 2.1.' 3107s + e='dgit test git user Tue, 26 Jun 2018 08:00:03 +' 3107s + cat - ../clog.before 3107s + clog-check-2 3107s + diff -u ../clog.expected debian/changelog 3107s --- ../clog.expected 2024-03-26 10:54:51.620658605 + 3107s +++ debian/changelog 2024-03-26 10:54:51.544657212 + 3107s @@ -2,7 +2,7 @@ 3107s 3107s* Update to new upstream version 2.1. 3107s 3107s - -- dgit test git user Tue, 26 Jun 2018 08:00:03 + 3107s + -- dgit test git user Tue, 26 Mar 2024 10:54:51 + 3107s 3107s example (2.0-2) unstable; urgency=medium 3107s 3107s + rc=1 3107s + set +x 3107s 3107s EXITING 1 3107s 3107s Most relevant logs are just before assignment rc=1 3107s Will now do cleanup etc. 3107s 3107s + pwd 3107s /tmp/autopkgtest.nu1RA0/autopkgtest_tmp/example 3107s + set +e 3107s + '[' x '!=' x ']' 3107s + '[' x/tmp/autopkgtest.nu1RA0/autopkgtest_tmp = x ']' 3107s + rm -rf /tmp/autopkgtest.nu1RA0/autopkgtest_tmp/must-clean 3107s + set -e 3107s + test 1 = 0 3107s + t-report-failure 3107s + set +x 3107s TEST FAILED 3107s cwd: /tmp/autopkgtest.nu1RA0/autopkgtest_tmp/example 3107s funcs: t-report-failure clog-check-2 main 3107s lines: 24 56 0 3107s files: tests/lib /tmp/autopkgtest.nu1RA0/build.LaH/src/tests/tests/gdr-newupstream /tmp/autopkgtest.nu1RA0/build.LaH/src/tests/tests/gdr-newupstream 3107s gzip: warning: GZIP environment variable is deprecated; use an alias or script ** Affects: dgit (Ubuntu) Importance: Undecided Status: New ** Tags: time-t -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059274 Title: dgit time_t regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dgit/+bug/2059274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059269] [NEW] RM: seahorse-nautilus; FTBFS
Public bug reported: Please remove seahorse-nautilus from the archive in noble+noble- proposed, source and binaries. It FTBFS and is blocking the time-t transition. It seems to have no reverse-dependencies: $ apt rdepends seahorse-nautilus seahorse-nautilus Reverse Depends: Breaks: nautilus (<< 3.11.92-4.1~) Breaks: nautilus (<< 3.11.92-4.1~) $ reverse-depends src:seahorse-nautilus -b No reverse dependencies found $ reverse-depends src:seahorse-nautilus $ Sadly the reverse-depends report and my removal-candidates.txt is also broken (it does not appear as a leaf there, but it also doesn't appear in the log of the tool where it logs what to keep). ** Affects: seahorse-nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: time-t -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059269 Title: RM: seahorse-nautilus; FTBFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse-nautilus/+bug/2059269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058931] Re: Please update grub 2.12-rc to 2.12 to fix critical bug with zfs - https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2041739
*** This bug is a duplicate of bug 2051999 *** https://bugs.launchpad.net/bugs/2051999 ** This bug has been marked a duplicate of bug 2051999 Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058931 Title: Please update grub 2.12-rc to 2.12 to fix critical bug with zfs - https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2041739 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2058931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058932] [NEW] RM: pyfltk and rdeps, FTBFS
Public bug reported: pyfltk fails to build from source, blocks libfltk-gl1.3t64 let's investigate reverse-depends: jak@jak-t14-g3:~/Projects/Ubuntu/Scratch$ reverse-depends src:pyfltk Reverse-Recommends == * mrcal (for python3-fltk) Reverse-Depends === * python3-gl-image-display (for python3-fltk) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x jak@jak-t14-g3:~/Projects/Ubuntu/Scratch$ reverse-depends src:pyfltk -b No reverse dependencies found $ apt-cache showsrc python3-gl-image-display | grep Package Package: gl-image-display jak@jak-t14-g3:~/Projects/Ubuntu/Scratch$ reverse-depends src:gl-image-display -b No reverse dependencies found jak@jak-t14-g3:~/Projects/Ubuntu/Scratch$ reverse-depends src:gl-image-display Reverse-Recommends == * mrcal (for python3-gl-image-display) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x ** Affects: gl-image-display (Ubuntu) Importance: Undecided Status: New ** Affects: pyfltk (Ubuntu) Importance: Undecided Status: New ** Also affects: gl-image-display (Ubuntu) Importance: Undecided Status: New ** Description changed: - pyfltk fails to build from source, let's investigate reverse-depends: + pyfltk fails to build from source, blocks libfltk-gl1.3t64 + let's investigate reverse-depends: jak@jak-t14-g3:~/Projects/Ubuntu/Scratch$ reverse-depends src:pyfltk Reverse-Recommends == * mrcal (for python3-fltk) Reverse-Depends === * python3-gl-image-display (for python3-fltk) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x jak@jak-t14-g3:~/Projects/Ubuntu/Scratch$ reverse-depends src:pyfltk -b No reverse dependencies found $ apt-cache showsrc python3-gl-image-display | grep Package Package: gl-image-display - jak@jak-t14-g3:~/Projects/Ubuntu/Scratch$ reverse-depends src:gl-image-display -b No reverse dependencies found - jak@jak-t14-g3:~/Projects/Ubuntu/Scratch$ reverse-depends src:gl-image-display + jak@jak-t14-g3:~/Projects/Ubuntu/Scratch$ reverse-depends src:gl-image-display Reverse-Recommends == * mrcal (for python3-gl-image-display) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058932 Title: RM: pyfltk and rdeps, FTBFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gl-image-display/+bug/2058932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058851] Re: RM: ignition-gazebo ignition-gui ignition-launch ignition-rendering ignition-sensors
Without -b it looks the same just noisier :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058851 Title: RM: ignition-gazebo ignition-gui ignition-launch ignition-rendering ignition-sensors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ignition-gazebo/+bug/2058851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058851] Re: RM: ignition-gazebo ignition-gui ignition-launch ignition-rendering ignition-sensors
$ ( grep-dctrl -FVersion 0ubuntu -a -P ignition- /var/lib/apt/lists/*Sources -nsPackage | sort -u ) | tee /dev/stderr | sort -u | xargs -IA reverse-depends -b src:A ignition-gazebo ignition-gui ignition-launch ignition-rendering ignition-sensors Reverse-Build-Depends = * ignition-launch (for libignition-gazebo-dev) Reverse-Build-Depends = * ignition-gazebo (for libignition-gui-dev) * ignition-launch (for libignition-gui-dev) No reverse dependencies found Reverse-Build-Depends = * ignition-gazebo (for libignition-rendering-dev) * ignition-gui (for libignition-rendering-ogre1-dev) * ignition-sensors (for libignition-rendering-ogre1-dev) * ignition-sensors (for libignition-rendering-ogre2-dev) No reverse dependencies found -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058851 Title: RM: ignition-gazebo ignition-gui ignition-launch ignition-rendering ignition-sensors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ignition-gazebo/+bug/2058851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058851] [NEW] RM: ignition-gazebo ignition-gui ignition-launch ignition-rendering ignition-sensors
Public bug reported: These are Ubuntu-specific and broken, we can't fix ignition-rendering easily even, it has weird C++ build failures and seemingly undefined macros. ** Affects: ignition-gazebo (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: ignition-gui (Ubuntu) Importance: Undecided Status: New ** Affects: ignition-launch (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: ignition-rendering (Ubuntu) Importance: Undecided Status: New ** Affects: ignition-sensors (Ubuntu) Importance: Undecided Status: New ** Also affects: ignition-gazebo (Ubuntu) Importance: Undecided Status: New ** Also affects: ignition-gui (Ubuntu) Importance: Undecided Status: New ** Also affects: ignition-launch (Ubuntu) Importance: Undecided Status: New ** Also affects: ignition-sensors (Ubuntu) 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/2058851 Title: RM: ignition-gazebo ignition-gui ignition-launch ignition-rendering ignition-sensors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ignition-gazebo/+bug/2058851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
Uploaded procps with the file; leaving gamemode task open because maybe dynamic enhancements there still make some sense in 24.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
I'm agreeing with desktop in following Fedora to bump to 1048576, the precedence makes this safe, and this I consider this a bug fix for crashing software and not a feature request. ** Changed in: procps (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: procps (Ubuntu) Status: Triaged => In Progress ** Changed in: procps (Ubuntu) Status: In Progress => Fix Committed ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
Subscribing Canonical desktop team to get their input. Basically the ask is to ship this file: https://src.fedoraproject.org/rpms/systemd/blob/f39/f/10-map-count.conf I believe if we do it should be shipped in procps; or possibly, gamemode should set that option? ** Also affects: procps (Ubuntu) Importance: Undecided Status: New ** Also affects: gamemode (Ubuntu) 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/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2057792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058803] [NEW] RM: src:yrmcds; FTBFS, leaf
Public bug reported:
This needs fixes for time_t:
* No change rebuild against libgoogle-perftools4t64, libtcmalloc-
minimal4t64.
* Remove manual libgoogle-perftools4 dependency.
but FTBFS due to header changes, so please kill it
In file included from cybozu/ip_address.cpp:3:
cybozu/ip_address.hpp:51:10: error: ‘uint32_t’ in namespace ‘std’ does not name
a type; did you mean ‘wint_t’?
51 | std::uint32_t v6scope() const {
| ^~~~
| wint_t
cybozu/ip_address.cpp: In member function ‘bool
cybozu::ip_address::operator==(const cybozu::ip_address&) const’:
cybozu/ip_address.cpp:99:9: error: ‘v6scope’ was not declared in this scope
99 | if( v6scope() != rhs.v6scope() ) return false;
| ^~~
cybozu/ip_address.cpp:99:26: error: ‘const class cybozu::ip_address’ has no
member named ‘v6scope’
99 | if( v6scope() != rhs.v6scope() ) return false;
| ^~~
make[1]: *** [: cybozu/ip_address.o] Error 1
make[1]: *** Waiting for unfinished jobs
In file included from cybozu/tcp.hpp:7,
from cybozu/tcp.cpp:3:
cybozu/ip_address.hpp:51:10: error: ‘uint32_t’ in namespace ‘std’ does not name
a type; did you mean ‘wint_t’?
51 | std::uint32_t v6scope() const {
| ^~~~
| wint_t
In file included from ./cybozu/tcp.hpp:7,
from src/counter/counter.hpp:8,
from src/counter/counter.cpp:3:
./cybozu/ip_address.hpp:51:10: error: ‘uint32_t’ in namespace ‘std’ does not
name a type; did you mean ‘wint_t’?
51 | std::uint32_t v6scope() const {
| ^~~~
| wint_t
In file included from ./cybozu/tcp.hpp:7,
from src/counter/counter.hpp:8,
from src/counter/stats.hpp:7,
from src/counter/stats.cpp:3:
./cybozu/ip_address.hpp:51:10: error: ‘uint32_t’ in namespace ‘std’ does not
name a type; did you mean ‘wint_t’?
51 | std::uint32_t v6scope() const {
| ^~~~
| wint_t
jak@jak-t14-g3:~/Projects/Ubuntu/Scratch$ reverse-depends src:yrmcds
No reverse dependencies found
jak@jak-t14-g3:~/Projects/Ubuntu/Scratch$ reverse-depends src:yrmcds -b
No reverse dependencies found
** Affects: yrmcds (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- RM: yrmcds; FTBFS, leaf
+ RM: src:yrmcds; FTBFS, leaf
** Description changed:
- This needs fixes for time_t but FTBFS due to header changes, so please
- kill it
+ This needs fixes for time_t:
- In file included from cybozu/ip_address.cpp:3:
- cybozu/ip_address.hpp:51:10: error: ‘uint32_t’ in namespace ‘std’ does not
name a type; did you mean ‘wint_t’?
-51 | std::uint32_t v6scope() const {
- | ^~~~
- | wint_t
- cybozu/ip_address.cpp: In member function ‘bool
cybozu::ip_address::operator==(const cybozu::ip_address&) const’:
- cybozu/ip_address.cpp:99:9: error: ‘v6scope’ was not declared in this scope
-99 | if( v6scope() != rhs.v6scope() ) return false;
- | ^~~
[Bug 2058734] [NEW] RM: apt-verify; not fit for purpose, not installable
Public bug reported: Please remove apt-verify from the archive. It overrides APT's repository verification mechanism, and hence APT has gained a Conflicts: to it to prevent people from installing it. ** Affects: apt-verify (Ubuntu) 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/2058734 Title: RM: apt-verify; not fit for purpose, not installable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-verify/+bug/2058734/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058648] Re: Support upgrades from unmerged 22.04 - was: package libc6 2.35-0ubuntu3.6 [modified: usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/README.hesiod.
** Changed in: glibc (Ubuntu) Status: Incomplete => 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.35-0ubuntu3.6 [modified: usr/share/doc/libc6/NEWS.Debian.gz usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/README.hesiod.gz usr/share/doc/libc6/changelog.Debian.gz usr/share/lintian/overrides/libc6] failed to install/upgrade: new libc6:amd64 package pre-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2058648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
