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

Bug#1015123: latex-cjk-chinese-arphic: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity



Some observations:

Going back to fontforge version 20201107~dfsg-4 and its dependencies, I notice the following warning message:

21900/1114292:          
  Add extrema...
  Simplifying outlines...
NaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creationNaN value in spline creation22000/1114292:                                                                                                        
  Add extrema...        
  Simplifying outlines...

A more recent version of Fontforge will just let the application hang.

I will have to contact upstream to figure out what is causing this.

-- 
Danai


On Sun, 17 Jul 2022 at 16:15, Danai SAE-HAN (韓達耐) <danai.saehan@gmail.com> wrote:
Very interesting; font bkai gets stuck during the fontforge compilation at 21900/1114292 and stays at 100% CPU usage.  Other fonts seem fine.
This requires a bit more investigating.  My gut tells me the recent fontforge upload has a regression somewhere.

-- 
Danai

On Sat, 16 Jul 2022 at 22:42, Danai SAE-HAN (韓達耐) <danai.saehan@gmail.com> wrote:
Thanks Lucas, I'll look at it tonight.

On Sat, 16 Jul 2022, 22:04 Lucas Nussbaum, <lucas@debian.org> wrote:
Source: latex-cjk-chinese-arphic
Version: 1.24
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):
> Reading subfont definition file `/usr/share/texlive/texmf-dist/fonts/sfd/ttf2pk/Unicode.sfd'...
> Writing extended font definition file `c70bsmi.fdx'...
>
> # Remove the *.enc files; they're not used.
> ( cd build/bsmi00lp && rm -f *.enc )
>
> # Create a Type1 font map.
>
> # Create entries for the font definition file
> # `c00bsmi.fd' (which uses UBig5 encoding).
>
> # Create entries for the font definition file
> # `c70bsmi.fd' (which uses Unicode encoding).
>
> touch build-stamp.bsmi
> 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/latex-cjk-chinese-arphic_1.24_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.


Reply to: