Hello,

On Sat, Jan 09, 2010 at 11:35:30AM +0100, Lucas Nussbaum wrote:
> Source: dico
> Version: 2.0-7
> Severity: serious
> User: [email protected]
> Usertags: qa-ftbfs-2010-01-08 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part:
> > /bin/bash ../libtool --tag=CC   --mode=link gcc -DSYSCONFIG=\"/etc\" 
> > -DLOCALSTATEDIR=\"/var\" -DDICO_MODDIR=\"/usr/lib/dico\" 
> > -DDEFAULT_VERSION_INCLUDE_DIR=\"/usr/share/dico/2.0/include\" 
> > -DDEFAULT_INCLUDE_DIR=\"/usr/share/dico/include\" 
> > -DDEFAULT_PREPROCESSOR="\"/usr/bin/m4 -s\"" -g -O2  -Wl,--as-needed -o 
> > dicod accesslog.o acl.o alias.o auth.o capa.o cmdline.o commands.o 
> > config-format.o config-gram.o config-lex.o dbtext.o dicod.o gsasl.o ident.o 
> > lang.o lev.o loader.o main.o markup.o mime.o ostream.o pp.o regex.o 
> > server.o stat.o stratcl.o udb.o xidle.o xversion.o ../lib/libxdico.a 
> > ../gnu/libgnu.a ../lib/libextra.a ../lib/libdico.la ../lib/libdicosasl.a 
> > -lgsasl -lltdl   -lrt -lnsl -ldl 
> > libtool: link: cannot find the library `/usr/lib/libgcrypt.la' or unhandled 
> > argument `/usr/lib/libgcrypt.la'
> > make[5]: *** [dicod] Error 1
> 
> The full build log is available from:
>    http://people.debian.org/~lucas/logs/2010-01-08/dico_2.0-7_lsid64.buildlog
> 
> A list of current common problems and possible solutions is available at 
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
---end quoted text---

Last successful build of dico on amd64: 
https://buildd.debian.org/fetch.cgi?pkg=dico;ver=2.0-7;arch=amd64;stamp=1260645968

didn't pull the libgcrypt* packages in the first place.

I see that the new version of libgsasl7 (1.4.0-1) depends on libgcrypt11,

maybe libgsasl7-dev should depend on libcrypt11-dev ?

-- 
 ‎أحمد المحمودي (Ahmed El-Mahmoudy)
  Digital design engineer
 GPG KeyID: 0xEDDDA1B7 (@ subkeys.pgp.net)
 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7



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

Reply via email to