Bug#1069880: bullseye-pu: package cpu/1.4.3-14~deb11u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: ***@packages.debian.org
Usertags: pu
Control: block 1067439 with -1
Control: affects -1 + src:cpu

[ Reason ]
The last QA upload four years ago fixed a FTBFS (multiple definitions of
a global variable) by replacing that variable with an extern declaration
and zero definitions. This didn't result in a linker error (missing
symbol) because it happens in a plugin library and thus is only detected
at runtime when the plugin gets loaded (i.e. always).
So let's ship the plugin with *one* definition of the global variable
;-)

[ Impact ]
cpu stays unusable, but nobody noticed that for the last 4 years and two
stable releases ...

[ Tests ]
Added a smoketest autopkgtest that detects the current failure.

[ Risks ]
We can't make the current situation much worse ;-)

[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[x] the issue is verified as fixed in bookworm-pu

[ Changes ]
* Actually provide a definition of globalLdap. (Closes: #1067439)
* Add smoke test.

[ Other info ]
n/a

Andreas

[Debian Bug Tracking System]

Post by Andreas Beckmann
block 1067439 with -1

Bug #1067439 {Done: Andreas Beckmann <***@debian.org>} [cpu] cpu: undefined symbol globalLdap in libcpu_ldap.so on Debian 12
1067439 was not blocked by any bugs.
1067439 was not blocking any bugs.
Added blocking bug(s) of 1067439: 1069880

Post by Andreas Beckmann
affects -1 + src:cpu

Bug #1069880 [release.debian.org] bullseye-pu: package cpu/1.4.3-14~deb11u1
Added indication that 1069880 affects src:cpu

[Debian Bug Tracking System]

tag -1 confirmed

Bug #1069880 [release.debian.org] bullseye-pu: package cpu/1.4.3-14~deb11u1
Added tag(s) confirmed.

[Jonathan Wiltshire]

Control: tag -1 confirmed

Post by Andreas Beckmann
The last QA upload four years ago fixed a FTBFS (multiple definitions of
a global variable) by replacing that variable with an extern declaration
and zero definitions. This didn't result in a linker error (missing
symbol) because it happens in a plugin library and thus is only detected
at runtime when the plugin gets loaded (i.e. always).
So let's ship the plugin with *one* definition of the global variable
;-)

Please go ahead.

Thanks,