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

Bug#1013548: 3270font: FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1



Source: 3270font
Version: 2.3.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> for f in build/*f; do fontlint -i 98 $f || exit 1; done
> Copyright (c) 2000-2022. See AUTHORS for Contributors.
>  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
>  with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE.
>  Version: 20220308
>  Based on sources from 2022-06-16 10:08 UTC-D.
> Internal Error: Attempt to unget two characters
> CHECKING     build/3270-Regular.otf
> CHECKING  98 Self-intersecting glyph (issue #2) when FontForge is able to
>              correct this (overrides general setting)
> ERROR      2 Self-intersecting glyph
> ERROR      5 Missing points at extrema
> FAIL         build/3270-Regular.otf
> 
> make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/3270font_2.3.1-1_unstable.log

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