Ok. So, as far as I can tell, python3-apt on armhf *and only* on armhf
gets a versioned dependency on libapt-pkg6.0t64 (>=
$THE_VERSION_IT_BUILT_AGAINST). It's unclear to me what is causing this
behaviour; the symbols file for that library in the apt source looks
unremarkable, and there's no weird architecture-specific wrangling that
I can see in the rules.
I have verified that a no-change rebuild of python-apt in an archive
containing noble-updates but *not* noble-proposed will generate a
package that has correct dependencies on armhf. Thus, we should be able
to build in a PPA and binary-copy the result to noble-proposed (and then
release into -updates from there).
I'm aware that there are special considerations around building a
package in a PPA to be binary-copied into the main archive, but I'm not
familiar with setting up a suitable build archive. I shall coordinate
with others on the SRU/Archive teams to get this happening.
** Changed in: python-apt (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/2077685
Title:
python3-apt_2.7.7ubuntu2 uninstallable on armhf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2077685/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
