Hi,
fontmake and the dependencies has been updated:
* fontmake 1.8.0: https://salsa.debian.org/fonts-team/fontmake
* glyphslib 3.1.4: https://salsa.debian.org/fonts-team/glyphslib
* mutatormath 2.1.2: https://salsa.debian.org/fonts-team/mutatormath
* fontmath 0.4.9:
Hi,
Replying inline:
On Thu, Dec 13, 2018 at 10:00:46AM -0500, Jeremy Bicha wrote:
> I think I've done all of these today (or earlier) except for:
>
> ufo2ft 2.5: the build requires skia-pathops. Did you want to work on
> packaging that too?
This is not an requirement as far as the source code
On Fri, Nov 30, 2018 at 3:24 AM Yao Wei wrote:
> I would like to RFS the following packages to close this bug, as I am
> non-uploading DD:
>
> * fontmake 1.6.1: https://salsa.debian.org/fonts-team/fontmake
> * ufo2ft 2.5.0: https://salsa.debian.org/fonts-team/ufo2ft
> * fonttools 3.32.0:
On Fri, Nov 30, 2018 at 07:04:53AM -0500, Jeremy Bicha wrote:
> Please check that you have git pushed the upstream and pristine-tar
> branches for that list.
Ouch.
Uploaded, Please check.
Yao Wei
signature.asc
Description: PGP signature
On Fri, Nov 30, 2018 at 3:24 AM Yao Wei wrote:
> I would like to RFS the following packages to close this bug, as I am
> non-uploading DD:
>
> * fontmake 1.6.1: https://salsa.debian.org/fonts-team/fontmake
> * ufo2ft 2.5.0: https://salsa.debian.org/fonts-team/ufo2ft
> * fonttools 3.32.0:
Hi,
I would like to RFS the following packages to close this bug, as I am
non-uploading DD:
* fontmake 1.6.1: https://salsa.debian.org/fonts-team/fontmake
* ufo2ft 2.5.0: https://salsa.debian.org/fonts-team/ufo2ft
* fonttools 3.32.0: https://salsa.debian.org/fonts-team/fonttools
* defcon
James Godfrey-Kittle wrote:
> Your error is the same as in the original email. The error "Glyph
> psili cannot be in both @MC_top and @MC_topleft" I believe was fixed
> by https://github.com/googlei18n/ufo2ft/pull/276, and should not occur
> with ufo2ft >= 2.3.0.
Great, thank you! So, we have a
Aha! I didn't have the correct versions of the dependencies as packaged in sid.
Your error is the same as in the original email. The error "Glyph
psili cannot be in both @MC_top and @MC_topleft" I believe was fixed
by https://github.com/googlei18n/ufo2ft/pull/276, and should not occur
with ufo2ft
Am Montag, den 26.11.2018, 09:19 -0800 schrieb James Godfrey-Kittle:
> > Yes, according to https://packages.debian.org/fontmake both Buster and
> Sid are packaging fontmake 1.6.1. I also tried with the latest version
> on Github (1.8.0) and got no error.
Well, then something is still odd on the
James Godfrey-Kittle wrote:
> Hm, I'm unable to reproduce this error with fontmake 1.6.1 and the
> latest version of FiraCode from https://github.com/tonsky/FiraCode.
Is this with the fontmake version packaged in Debian?
- Fabian
Hm, I'm unable to reproduce this error with fontmake 1.6.1 and the
latest version of FiraCode from https://github.com/tonsky/FiraCode. My
output:
$ fontmake -g FiraCode.glyphs
INFO:fontmake.font_project:Building master UFOs and designspace from
Glyphs source
INFO:glyphsLib.classes:Parsing
Hi James,
Am Dienstag, den 20.11.2018, 09:22 -0800 schrieb James Godfrey-Kittle:
> with some component of fontmake; it's worth posting an issue on Github
> to have it triaged (I was planning to do this soon when I have time).
yes, please!
Thanks,
- Fabian
signature.asc
Description: This is
On 2018-11-20 10:22 a.m., James Godfrey-Kittle wrote:
> It's possible that this font actually contains illegal feature syntax,
> which is still accepted by Glyphs. Or of course it could be an issue
> with some component of fontmake; it's worth posting an issue on Github
> to have it triaged (I
It's possible that this font actually contains illegal feature syntax,
which is still accepted by Glyphs. Or of course it could be an issue
with some component of fontmake; it's worth posting an issue on Github
to have it triaged (I was planning to do this soon when I have time).
Hi,
Yao Wei wrote:
> Sorry for the late reply, here was me testing to build Fira Code after
> bumping fontmake:
*sigh* this doesn't look too promising. Do you have any idea which package
is responsible for this error?
Thanks,
- Fabian
Hi,
Sorry for the late reply, here was me testing to build Fira Code after
bumping fontmake:
INFO:fontmake.font_project:Building master UFOs and designspace from Glyphs
source
INFO:glyphsLib.classes:Parsing "FiraCode.glyphs" file into
INFO:fontmake.font_project:Building OTF for FiraCode-Regular
Hi,
Yao Wei wrote:
> While newer version is ready, I found that building Fira Code needs the
> dependencies under fontmake to be bumped, hence this bug is kept
> unresolved.
could you please tell me what exactly needs to be updated in order to
build fonts-firacode with fontmake?
Thanks!
-
Hi Jeremy,
Jeremy Bicha wrote:
> 3.1 is not a trivial update since our glyphdata handling will need to
> be redone (debian/rules, debian/copyright and we probably need a
> glyphsinfo update).
I have seen some progress in the salsa GIT repo recently. Is there
anything still missing to have this
Hi,
While newer version is ready, I found that building Fira Code needs the
dependencies under fontmake to be bumped, hence this bug is kept unresolved.
Yao Wei
On Tue, Oct 30, 2018 at 17:27 Fabian Greffrath wrote:
> Hi Jeremy,
>
> Jeremy Bicha wrote:
> > 3.1 is not a trivial update since our
Jeremy Bicha wrote:
> 3.1 is not a trivial update since our glyphdata handling will need to
> be redone (debian/rules, debian/copyright and we probably need a
> glyphsinfo update).
Okay, thanks!
- Fabian
On Mon, Oct 15, 2018 at 11:09 AM Fabian Greffrath wrote:
> > This has been fixed upstream in glyphslib:
> > https://github.com/googlei18n/glyphsLib/pull/428
>
> any chance to get glyphslib >= 3.1.1 into Debian in the near future?
3.1 is not a trivial update since our glyphdata handling will need
Hi there,
> This has been fixed upstream in glyphslib:
> https://github.com/googlei18n/glyphsLib/pull/428
any chance to get glyphslib >= 3.1.1 into Debian in the near future?
- Fabian
signature.asc
Description: This is a digitally signed message part
Control: reassign -1 glyphslib
Control: found -1 3.0.2-3
Control: tags -1 + fixed-upstream
This has been fixed upstream in glyphslib:
https://github.com/googlei18n/glyphsLib/pull/428
- Fabian
signature.asc
Description: This is a digitally signed message part
I filed this upstream here:
https://github.com/googlei18n/fontmake/issues/445
Package: fontmake
Version: 1.4.0-2
Severity: normal
Hi fontmake mates,
the following happens when I try to rebuild fonts-firacode from its
glyphs source. I have absolutely no clue what that means. Could you
probably have a look, please?
$ fontmake -g FiraCode.glyphs
25 matches
Mail list logo
