** Description changed:
- The noble update picked up those dependencies on armhf due to t64
- mangling changes in the C++ symbols, and is now uninstallable.
+ [ Impact ]
+
+ The noble packagekit update[1] to fix LP: #2086773 picked up those
+ dependencies on armhf due to t64 mangling changes in the C++ symbols,
+ and is now uninstallable:
+
+ ubuntu@n-armhf:~$ sudo apt install packagekit
+ Reading package lists... Done
+ Building dependency tree... Done
+ Reading state information... Done
+ Some packages could not be installed. This may mean that you have
+ requested an impossible situation or if you are using the unstable
+ distribution that some required packages have not yet been created
+ or been moved out of Incoming.
+ The following information may help to resolve the situation:
+
+ The following packages have unmet dependencies:
+ packagekit : Depends: libapt-pkg6.0t64 (>= 2.8.2) but 2.7.14build2 is to be
installed
+ E: Unable to correct problems, you have held broken packages.
+
+ The planned fix is to remove apt 2.8.2 from noble-proposed (done),
+ rebuild packagekit (this bug), and release that.
+
+
+ 1. https://launchpad.net/ubuntu/+source/packagekit/1.2.8-2ubuntu1
+
+
+ [ Test Plan ]
+
+ On a noble armhf system, install packagekit from noble-proposed. It must
+ not pull in other non-packagekit packages from noble-proposed.
+
+ [ Where problems could occur ]
+
+ This is a no-change rebuild. Like all SRUs, it's always built with the
+ proposed pocket enabled, but this time the newer apt 2.8.2 is not there,
+ so that dependency will not be picked up. That being said, the risk is
+ the same that an unintended dependency from noble-proposed will be
+ picked up, but the test plan specifically checks for that.
+
+ [ Other Info ]
+
+ This is fixing a regression introduced by the release of
+ https://launchpad.net/bugs/2086773 to updates, where even though it was
+ noticed that the excuses page was flagging packagekit to be depending on
+ apt from proposed, it was incorrectly deemed irrelevant by me
+ (@ahasenack) at the time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/2091714
Title:
packagekit noble update uninstallable on armhf, depends on libapt-
pkg6.0t64 (>= 2.8.2) from proposed
Status in packagekit package in Ubuntu:
Invalid
Status in packagekit source package in Noble:
Fix Committed
Bug description:
[ Impact ]
The noble packagekit update[1] to fix LP: #2086773 picked up those
dependencies on armhf due to t64 mangling changes in the C++ symbols,
and is now uninstallable:
ubuntu@n-armhf:~$ sudo apt install packagekit
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
packagekit : Depends: libapt-pkg6.0t64 (>= 2.8.2) but 2.7.14build2 is to be
installed
E: Unable to correct problems, you have held broken packages.
The planned fix is to remove apt 2.8.2 from noble-proposed (done),
rebuild packagekit (this bug), and release that.
1. https://launchpad.net/ubuntu/+source/packagekit/1.2.8-2ubuntu1
[ Test Plan ]
On a noble armhf system, install packagekit from noble-proposed. It
must not pull in other non-packagekit packages from noble-proposed.
[ Where problems could occur ]
This is a no-change rebuild. Like all SRUs, it's always built with the
proposed pocket enabled, but this time the newer apt 2.8.2 is not
there, so that dependency will not be picked up. That being said, the
risk is the same that an unintended dependency from noble-proposed
will be picked up, but the test plan specifically checks for that.
[ Other Info ]
This is fixing a regression introduced by the release of
https://launchpad.net/bugs/2086773 to updates, where even though it
was noticed that the excuses page was flagging packagekit to be
depending on apt from proposed, it was incorrectly deemed irrelevant
by me (@ahasenack) at the time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2091714/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
