Hi,

So this doesn't actually affect the package in Wheezy, since that builds
and works just fine with the version of dovecot in Wheezy.

And the dovecot version that this build failed with shouldn't be able to
transition to testing until this bug is fixed, due to the versioned dep
on this package which should block that until they both can move.

Normally a binNMU would be enough to fix that, but the 2.0 -> 2.1 bump
of dovecot means that sourceful changes will be needed for this one.
Upstream knows about it, and has a tentative patch, but it's so far
untested.  He's a little shocked at this happening so close to the
freeze, but we'll try to get an update out for this as soon as we can.

 Ron


On Mon, Jun 04, 2012 at 11:51:40PM +0200, Lucas Nussbaum wrote:
> Source: dovecot-antispam
> Version: 2.0+20120225-2
> Severity: serious
> Tags: wheezy sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20120604 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part:
> > cc -DHAVE_CONFIG_H -I/usr/include/dovecot/ -I/usr/include/dovecot/src/ 
> > -I/usr/include/dovecot/src/lib/ -I/usr/include/dovecot/src/lib-storage/ 
> > -I/usr/include/dovecot/src/lib-mail/ -I/usr/include/dovecot/src/lib-imap/ 
> > -I/usr/include/dovecot/src/lib-dict/ -I/usr/include/dovecot/src/lib-index/ 
> > -I/usr/include/dovecot/src/imap/ -o dovecot-version dovecot-version.c
> > ./dovecot-version > dovecot-version.h
> >   CC   antispam-storage.o
> > antispam-storage.c:3:26: fatal error: antispam-storage-2.1.c: No such file 
> > or directory
> > compilation terminated.
> > make[1]: *** [antispam-storage.o] Error 1
> 
> The full build log is available from:
>    
> http://people.debian.org/~lucas/logs/2012/06/04/dovecot-antispam_2.0+20120225-2_unstable.log
> 
> 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!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
> 
> 



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to