[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1015092: marked as done (fonts-ocr-a: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Thu, 19 Jan 2023 07:20:45 +0100
with message-id <8b533e73c4f64844ef756cad4326656e@phys.ethz.ch>
and subject line fonts-ocr-a: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
has caused the Debian Bug report #1015092,
regarding fonts-ocr-a: FTBFS: 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 owner@bugs.debian.org
immediately.)


-- 
1015092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015092
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: fonts-ocr-a
Version: 1.0-10
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20220716 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> Making OCRABold
> Internal Error (overlap): Mismatched intersection.
>  (577.44,660.73)->(596.484,629.212) ends at (-999999,-999999) while (596.484,629.212)->(597.837,624.513) starts at (596.484,629.212)
> Internal Error (overlap): Winding number did not return to 0 when y=629.212
> Internal Error (overlap): Winding number did not return to 0 when y=629.212
> Internal Error (overlap): Winding number did not return to 0 when y=629.212
> Internal Error (overlap): Winding number did not return to 0 when y=629.212
> Internal Error (overlap): Winding number did not return to 0 when y=629.212
> Internal Error (overlap): Winding number did not return to 0 when y=629.212
> Internal Error (overlap): Winding number did not return to 0 when y=629.212
> Internal Error (overlap): Winding number did not return to 0 when y=629.212
> Internal Error (overlap): Neither needed nor unneeded (596.484,629.212)->(596.484,629.212)
> Internal Error (overlap): Humph. This monotonic leads nowhere (426.041,758.838)->(436.173,759.665).
> Internal Error (overlap): couldn't find a needed exit from an intersection
> Internal Error (overlap): couldn't find a needed exit from an intersection
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2022/07/16/fonts-ocr-a_1.0-10_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220716&fusertaguser=lucas@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 marking 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 --- this has been a problem in fontforge and fixed with the recent sid upload
--- End Message ---
Reply to: