Your message dated Tue, 29 Apr 2014 12:22:39 +0200
with message-id <1914774.Ljt63qJYkI@madagaskar>
and subject line Re: Something is still wonky
has caused the Debian Bug report #745233,
regarding libgmp10: Wrong shlibs information after 6.0.0 adds new symbols
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
745233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: libhogweed2
version: 2.7.1-2
severity: serious

Hi,

The new nettle upload contains a version of libhogweed2 which uses symbols
from the new version (6.0.0) of libgmp10, but it doesn't have a versioned
dependency. This means it's possible to install libhogweed2 with an older
version of libgmp10, but this doesn't work.

This also makes builds fail:

https://buildd.debian.org/status/fetch.php?pkg=samba&arch=i386&ver=2%3A4.1.7%2Bdfsg-1&stamp=1397911283

Cheers,

Ivo

--- End Message ---
--- Begin Message ---
Version: gmp/2:6.0.0+dfsg-2.3

> Hi, it seems something is still wonky. As bug 746216, which describes
> the exact problem, has been merged with this bug, I would like to reopen it.
> 
> My package qpdfview failed to build on kfreebsd-i386, mips, and powerpc
> (so far kfreebsd-amd64 and mipsel builds have not yet started) with the
> log tail:
> 
> //usr/lib/i386-kfreebsd-gnu/libhogweed.so.2: undefined reference to
> `__gmpz_limbs_modify'

The bug is fixed in gmp, but nettle and other packages still need to be 
rebuilt to get the right dependencies.

Still, I'm not sure why not all autobuilders use the latest version from sid 
anyway.

-- 
Magnus Holmgren
Debian Developer

--- End Message ---

Reply via email to