This bug was fixed in the package python-apt - 2.7.7ubuntu3
---
python-apt (2.7.7ubuntu3) noble; urgency=medium
* No-change rebuild without proposed (LP: #2077685)
* Mirror list updates.
-- Julian Andres Klode Fri, 23 Aug 2024 09:52:34
+0200
** Changed in: python-apt (Ubuntu
Update verified.
root@55d22e9f8666:/# apt update
Hit:1 http://ports.ubuntu.com/ubuntu-ports noble InRelease
Get:2 http://ports.ubuntu.com/ubuntu-ports noble-updates InRelease [126 kB]
Hit:3 http://ports.ubuntu.com/ubuntu-ports noble-proposed InRelease
Get:4 http://ports.ubuntu.com/ubuntu-ports nob
Hello Chris, or anyone else affected,
Accepted python-apt into noble-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/python-
apt/2.7.7ubuntu3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
This is a time_t transition issue most likely, the symbols files was not
updated for 64-bit time_t, and hence all the time_t symbols will now
depend on the build version on armhf.
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Noble)
St
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
I've set the phasing of python-apt to 0.
Now, of course, we have the most annoying kind of regression to untangle
- any rebuild of python-apt in -proposed will *also* exhibit this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
