-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The following is a list of packages which are linked against libstdc++5
on some architectures and libstdc++6 on others.  This list only contains
packages from Section: base/devel/libdevel/libs/oldlibs, as the full
list contains many things waiting for other packages to transition first
.  Format is "binary-pkg (source-pkg) [broken archs]"

These packages were uploaded very early in the transition and some of
the buildds did not have the right g++ version:
  prcs [arm hppa ia64 m68k sparc]
  cssc [ia64 hppa sparc]
  libflash0 [m68k arm i386]
If you maintain one of these packages please upload a new version ASAP.


These packages were all auto-built with the right version, but the
maintainer uploaded a package with the wrong ABI:
  libmyspell3c2 (myspell) [powerpc]
  libtunepimp2 (libtunepimp) [powerpc]
Maintainers, please upload a binary NMU for these packages to fix them.
 As I understand it, even if other packages linked against the old
version of these, but used g++-4.0, only these packages need to be rebuilt.

The arm buildds seemed to have continued using an old g++ for a brief
bit in the transition.  The following packages were built incorrectly
only on arm:
  libcoin40c2 (coin2) [arm]
  libenchant1c2 (enchant) [arm]
  libdar3 (dar) [arm]
  libgc1c2 (libgc) [arm]
  librudiments0 [arm]
  libclalsadrv1 (clalsadrv) [arm]
  librlog1c2 [arm]
  libsigc++-2.0-0c2 (libsigc++-2.0) [arm]
    - already discussed this one on IRC w/ vorlon and may be rebuilt by
      this point
If you have an arm system, please bin-NMU these.

The wxwindows2.4 package was autobuilt last week and although the build
log shows g++ 4.0 was installed, a dependency on libstdc++5 was added.
I haven't discovered why yet.

Cheers,
- -Mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFC3S4c7ZPKKRJLJvMRAjsSAKC5foEWzAxx/6K9abKKthnyuf1edACfXeCE
uc/MJn8zXLo7kzXR5uzUWLQ=
=rHrT
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to