Source: dovecot-antispam
Version: 2.0+20171229-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20250429 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> 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
> In file included from antispam-storage.c:1:
> dovecot-version.h:17:49: fatal error: antispam-storage-2.4.c: No such file or 
> directory
>    17 | #define ANTISPAM_STORAGE                        
> "antispam-storage-2.4.c"
>       |                                                 
> ^~~~~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> make[1]: *** [Makefile:37: antispam-storage.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2025/04/29/dovecot-antispam_2.0+20171229-1.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250429;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250429&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Reply via email to