Subject: Subject: python3-apt: undefined symbol: _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceEmmPKcm

From: Jeffrey Cliff <[email-masked]>
Date: Wed, 4 Dec 2024 11:23:03 -0600

Package: python3-apt
X-Debbugs-CC: jeff cliff<[email-masked]>
Severity: important

# reportbug reportbug

results in

Traceback (most recent call last):
  File "/usr/bin/reportbug", line 40, in <module>
    from reportbug import utils
  File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 45, in <module>
    import apt
  File "/usr/lib/python3/dist-packages/apt/__init__.py", line 21, in <module>
    import apt_pkg
ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-312-x86_64-linux-gnu.so:
undefined symbol:
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceEmmPKcm,
version APTPKG_6.0

[ie reportbug is broken and doesn't run at all]

any packages removed/added via either apt on the commandline or aptitude
*do* seem to get added/removed but with a similar warning

ie apt installing bb results in

...
Get:7 https://repo.jing.rocks/devuan/merged unstable/main amd64 bb
amd64 1.3rc1-13 [1,002 kB]
Get:8 https://repo.jing.rocks/devuan/merged unstable/main amd64
libdecor-0-plugin-1-gtk amd64 0.2.2-2 [22.7 kB]
Fetched 2,649 kB in 2s (1,174 kB/s)
Traceback (most recent call last):
  File "/usr/bin/apt-listchanges", line 5, in <module>
    from apt_listchanges.apt_listchanges import main
  File "/usr/lib/python3/dist-packages/apt_listchanges/apt_listchanges.py",
line 36, in <module>
    import apt_pkg
ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-312-x86_64-linux-gnu.so:
undefined symbol:
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE10_M_replaceEmmPKcm,
version APTPKG_6.0
...

note: i don't have cython3 installed

cython3:
  Installed: (none)
  Candidate: 3.0.11+dfsg-1+b1

devuan: excalibur/ceres
kernel: linux (libre)+a few patches: Linux wicksell
6.12.0-gnu-librelibre-c23-gnm #2 SMP PREEMPT_DYNAMIC Fri Nov 29
15:14:29 CST 2024 x86_64 GNU/Linux

/etc/apt/sources.list was
deb https://repo.jing.rocks/devuan/merged unstable main
deb-src https://repo.jing.rocks/devuan/merged unstable main

tried adding

deb https://repo.jing.rocks/devuan/merged ceres main
deb-src https://repo.jing.rocks/devuan/merged ceres main

no change

---

From: Mark Hindley <[email-masked]>
Date: Wed, 4 Dec 2024 21:23:07 +0000

Jeffrey

Thanks for this.

Andreas,

I wonder if this is because Debian's python3-apt here has been built against their
more recent apt.

I think we are going to have to keep more closely aligned wrt Debian apt
versions to avoid this.

What do you think?

Best wishes

Mark

---

From: B Stack <[email-masked]>
Date: Wed, 4 Dec 2024 16:39:53 -0500

Is this somehow separate from upstream bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088262 ?

B. Stack

---

From: Mark Hindley <[email-masked]>
Date: Wed, 4 Dec 2024 21:46:50 +0000

Control: tags -1 debian
Control: upstream -1 https://bugs.debian.org/1088262 

> Is this somehow separate from upstream bug

No!

> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088262 ?

I was just looking for a matching Debian bug and couldn't find it.

Thanks!

So, Jeffrey,  

It looks as it version 2.9.2 uploaded to Debian today should fix it.

Can you try and report back?

Thanks

Mark

---

From: Jeffrey Cliff <[email-masked]>
Date: Wed, 4 Dec 2024 19:14:39 -0600

Downloaded source to 2.9.2 via git clone of
https://salsa.debian.org/apt-team/python-apt
debuilded it using debuild -us -uc -b
installed using dpkg -i resulting deb file
and this issue no longer presents itself

--
------------------------------------------------------------------------------------------------
End the campaign to Cancel Richard Stallman - go to stallmansupport.org !
------------------------------------------------------------------------------------------------

---

From: Andreas Messer <[email-masked]>
Date: Thu, 5 Dec 2024 09:17:08 +0100

Hi,

> and this issue no longer presents itself

Thank you for the feedback! 

@Mark: So I assume there is no hurry to re-package the next apt version.
(I'll probaly do this today anyways) Currently I would like to stick
with tracking the Debian testing branch when re-packaging for our unstable
branch since I already had some experience with diverging versions on 
Debian unstable & testing during feature freeze.

And Btw, thanks to Mark & B Stack sorting this out.

Cheers,
Andreas

-- 
gnuPG keyid: 8C2BAF51
fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51