Your message dated Mon, 26 May 2025 02:33:00 +0300
with message-id <aDOorIzBNwRQMuw3@localhost>
and subject line Re: Bug#1103062: unidic-mecab: FTBFS in testing/i386: E: Build
killed with signal TERM after 150 minutes of inactivity
has caused the Debian Bug report #1103062,
regarding unidic-mecab: FTBFS in testing/i386: E: Build killed with signal TERM
after 150 minutes of inactivity
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.)
--
1103062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unidic-mecab
Version: 3.1.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20250414 ftbfs-trixie
Hi,
During a rebuild of all packages in testing (trixie), your package failed
to build on i386.
Relevant part (hopefully):
> dh_installdocs
> dh_installchangelogs
> dh_perl
> dh_link
> dh_strip_nondeterminism
> dh_compress
> dh_fixperms
> dh_missing
> dh_installdeb
> dh_gencontrol
> dh_md5sums
> debian/rules override_dh_builddeb
> make[1]: Entering directory '/build/reproducible-path/unidic-mecab-3.1.1'
> dh_builddeb -- -Zxz -Sextreme -z9 -Sextreme
> dpkg-deb: building package 'unidic-mecab' in
> '../unidic-mecab_3.1.1-1_all.deb'.
> E: Build killed with signal TERM after 150 minutes of inactivity
The full build log is available from:
http://qa-logs.debian.net/2025/04/14/unidic-mecab_3.1.1-1_testing-i386.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250414;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250414&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.
--- End Message ---
--- Begin Message ---
On Mon, Apr 14, 2025 at 01:42:43PM +0200, Lucas Nussbaum wrote:
> Source: unidic-mecab
> Version: 3.1.1-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20250414 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in testing (trixie), your package failed
> to build on i386.
>
>
> Relevant part (hopefully):
> > dh_installdocs
> > dh_installchangelogs
> > dh_perl
> > dh_link
> > dh_strip_nondeterminism
> > dh_compress
> > dh_fixperms
> > dh_missing
> > dh_installdeb
> > dh_gencontrol
> > dh_md5sums
> > debian/rules override_dh_builddeb
> > make[1]: Entering directory '/build/reproducible-path/unidic-mecab-3.1.1'
> > dh_builddeb -- -Zxz -Sextreme -z9 -Sextreme
> > dpkg-deb: building package 'unidic-mecab' in
> > '../unidic-mecab_3.1.1-1_all.deb'.
> > E: Build killed with signal TERM after 150 minutes of inactivity
>...
I can see how this might fail on 32-bit, expecially with a slow cpu.
But that does not really matter since binary-all packages do not have to
be buildable on architectures other than amd64.
cu
Adrian
--- End Message ---
