Source: gap-polycyclic
Version: 2.16-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> dpkg-source: warning: ignoring deletion of file doc/chap6.html, use 
> --include-removal to override
> dpkg-source: warning: ignoring deletion of file doc/chap7.txt, use 
> --include-removal to override
> dpkg-source: warning: ignoring deletion of file doc/chap3.txt, use 
> --include-removal to override
> dpkg-source: info: building gap-polycyclic in 
> gap-polycyclic_2.16-1.debian.tar.xz
> dpkg-source: info: building gap-polycyclic in gap-polycyclic_2.16-1.dsc
>  debian/rules binary
> mkdir -p debian/gaproot/pkg
> ln -s ../../.. debian/gaproot/pkg/Polycyclic
> gap -q -l 'debian/gaproot;/usr/share/gap' < tst/testall.g | tee debian/gap.tst
> true
> Architecture: x86_64-pc-linux-gnu-default64-kv8
> 
> testing: debian/gaproot/pkg/Polycyclic/tst/AddToIgs.tst
>      154 ms (61 ms GC) and 14.7MB allocated for AddToIgs.tst
> testing: debian/gaproot/pkg/Polycyclic/tst/bugfix.tst
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/gap-polycyclic_2.16-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221220&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