[Pkg-fonts-devel] fontforge upload to unstable

Vasudev Kamath vasudev at copyninja.info
Sat Aug 27 17:34:50 UTC 2016

Hi all,

I'm planning to upload new fontforge to unstable soon. There has been
following packages failing ¹ thanks to Adam for generating it. Here I
checked 2 failing fonts

1. ttf-goudybookletter (now fonts-goudybookletter) it stops at building
   italic font and does not return not sure what really is going wrong.
2. fonts-okolaks fails due to missing build scripts, the font does fail
   now also during build but error is unnoticed probably because old
   fontforge ignored missing files and returned without doing
   anything. But newer one tries to ask user (even with fontforge-nox)
   and fails to open display and errors out.
   The okolaks font build issue has been already mentioned to Gurkan in
   another mail I hope he will have a look at this font.
3. fonts-pecita build failure is known and reported upstream. Upstream
   promised the fix (and IIUC something is already merged ) I hope next
   upstream release should fix it.

Other issues needs to be reported to individual packages as bugs.

I'm just wondering if its right to directly upload it to unstable or
first file bug against failing packages give them some time and then
upload to unstable (this is what is being followed by many maintainers
like gcc and openssl). Any suggestions?.

And yeah any objections for uploading newer fontforge to unstable :-) ?.

¹ https://angband.pl/tmp/ff10/failed/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 800 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-fonts-devel/attachments/20160827/1dd24537/attachment.sig>

More information about the Pkg-fonts-devel mailing list