[Bug 2102720] Re: Failure: The 3.0 solver produced a worse result

2025-03-21 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 2.9.34 --- apt (2.9.34) unstable; urgency=medium [ Julian Andres Klode ] * Fix uploads to errors.ubuntu.com with whoopsie: - zstd: The compressor level should be -6, not -19 - edsp: Add functionality to only write relevant packages

[Bug 2102720] Re: Failure: The 3.0 solver produced a worse result

2025-03-20 Thread Julian Andres Klode
Fix in https://salsa.debian.org/apt-team/apt/-/merge_requests/466 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2102720 Title: Failure: The 3.0 solver produced a worse result To manage notification

[Bug 2102720] Re: Failure: The 3.0 solver produced a worse result

2025-03-17 Thread Julian Andres Klode
** Changed in: apt (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** 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/2102720 Title: Failure: The 3.

[Bug 2102720] Re: Failure: The 3.0 solver produced a worse result

2025-03-16 Thread Julian Andres Klode
Maybe I should print some message in apt when I generate a report for https://discourse.ubuntu.com/t/evaluating-the-new-apt-solver- in-25-04/55618 But in released versions apport doesn't prompt for bug reports but you get the whoopsie error reports, so not sure. -- You received this bug notif

[Bug 2102720] Re: Failure: The 3.0 solver produced a worse result

2025-03-15 Thread Jeremy BĂ­cha
breezy is broken in Ubuntu 25.04 so I installed it locally. That still didn't work but we're building the new breezy and rust-pyo3 today so maybe that helps. Thanks for reading through the log. Except for the apport popup, there was no indication of anything that wasn't working correctly on the us

[Bug 2102720] Re: Failure: The 3.0 solver produced a worse result

2025-03-15 Thread Julian Andres Klode
Ah I think you have a hold (or pin) on brz; and the new solver now considers "brz" as obsolete because the candidate version is not installable anymore, and then tries to prefer to satisfiy libdpkg-perl Suggests bzr by installing bzr (it does not want to end up with Suggests getting broken by upg

[Bug 2102720] Re: Failure: The 3.0 solver produced a worse result

2025-03-15 Thread Julian Andres Klode
Alright I made a silly mistake when I patched the "don't detect manually installed package as obsolete"; the calls were interleaved. So we see the "libdpkg-perl Suggests bzr" *before* we see "brz" as installed and set the flag in the solver state. Turns out I gotta loop twice; who knew? ** Changed