mass RC-bug filing? deps on libart-2.0-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
in libart-2.0-dev 2.3.16-3, libart lost their shlibs version....
(do people actually test their packages when switching to a new
build system? Especially for libs where the shlibs system is important).
seb128 tells me this will be fixed RSN...
Anyhow, this is nasty, since versions >= 2.3.8 actually _do_ introduce
new functions/symbols which newer stuff use and therefore this is a
problem.
I just noticed openoffice.org-bin being affected and looked whether
other packages are, too....
$ grep-available -FDepends libart-2.0 | grep Package > l
$ $ for p in `cat l | sed -e s/"Package: "//`; do if apt-cache show $p |
grep -q libart-2.0-2 && ! apt-cache show $p | grep -q "libart-2.0-2 (>=
2.3.8)"; then echo $p; fi; done
This affects dozen of packages....
This is still running. I'll follow-up with exact results :)
Is (mass-)filing serious bugs against those pkgs ok?
(adding build-conflicts against that libart version and rebuilding with
the fixed one)
/me hides from the release people...
Grüße/Regards,
René
- --
.''`. René Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' rene@debian.org | GnuPG-Key ID: 248AEB73
`- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAfszD+FmQsCSK63MRAmnfAJ9bOQT2yXGHWzBvSWvEvQ/gZ9HZ6ACeOLUG
G/8A242RNyf/CpkM5QfX9oE=
=igaR
-----END PGP SIGNATURE-----
Reply to: