← Back to team overview

debcrafters-packages team mailing list archive

[Bug 2099829] Autopkgtest regression report (libcanberra/0.30-17ubuntu1.1)

 

All autopkgtests for the newly accepted libcanberra (0.30-17ubuntu1.1) for oracular have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/47.0-1ubuntu4.4 (arm64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/oracular/update_excuses.html#libcanberra

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/2099829

Title:
  libcanberra-gtk3-0t64 remains installed in oracular/plucky

Status in apt package in Ubuntu:
  Invalid
Status in libcanberra package in Ubuntu:
  Fix Released
Status in libcanberra source package in Oracular:
  Fix Committed
Status in libcanberra source package in Plucky:
  Fix Released

Bug description:
  [Impact]
  People upgrading from noble are stuck on the no-longer-available libcanberra-gtk3-0t64 (which has been changed back to libcanberra-gtk3-0 in oracular).

  This is in turn causes them to have an unsupported package installed,
  and the new apt solver is producing a "worse result" because it
  notices and tries to replace it.

  The issue for oracular users meanwhile is the lack of security support
  for the t64 package they are stuck on, in case a security update
  happens.

  [Test plan]
  Upgrade from noble to oracular or take an upgraded system, run apt dist-upgrade and see libcanberra-gtk3-0 being installed.

  [Where problems could occur]
  There could be typos or something in theory. The solver could go mad in anger. But it seems pretty unrealistic.

  [Other info]
  The transitional package is Architecture: any and Multi-Arch: same to force the upgrade across architectures, it can't be Architecture: all as then it would only enforce the upgrade for the native architecture.

  [Original bug report]

  The error appeared during an attempt to install supertuxkart

  ProblemType: AptSolver
  DistroRelease: Ubuntu 25.04
  Package: apt 2.9.30ubuntu1
  ProcVersionSignature: Ubuntu 6.12.0-15.15-generic 6.12.11
  Uname: Linux 6.12.0-15-generic x86_64
  ApportVersion: 2.31.0+git20250220-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Feb 23 19:46:11 2025
  ErrorMessage:

  InstallationDate: Installed on 2023-12-23 (428 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
  SourcePackage: apt
  Title: Failure: The 3.0 solver produced a worse result
  UpgradeStatus: Upgraded to plucky on 2025-02-11 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2099829/+subscriptions