[core-updates] font-gnu-freefont fails to build

  • Done
  • quality assurance status badge
Details
2 participants
  • Jack Hill
  • Marius Bakke
Owner
unassigned
Submitted by
Jack Hill
Severity
normal
J
J
Jack Hill wrote on 24 Apr 2020 16:33
(address . bug-guix@gnu.org)
alpine.DEB.2.20.2004241025370.5735@marsh.hcoop.net
Hi Guix,

On the current core-updates branch, font-gnu-freefont fails to build with
the attatched build log.

Based on the messages about syntax errors, it looks like gnu-freefont is
not compatible with python3, and instead needs python2.

However, we already try to do this in the package definition:

;; replace python 3 with python 2
;; python 3 support commits aren't yet released in 20120503
;; so freefont needs python 2 support in fontforge
(native-inputs `(("fontforge" ,(package (inherit fontforge)
(inputs `(("python-2" ,python-2)
,@(package-inputs fontforge)))))))


Best,
Jack
Attachment: 657ynripn8j0kma5ziz9qyk37fqfg2-font-gnu-freefont-20120503.drv.log
M
M
Marius Bakke wrote on 24 Apr 2020 18:20
87h7x8g8j1.fsf@devup.no
Jack Hill <jackhill@jackhill.us> writes:

Toggle quote (8 lines)
> Hi Guix,
>
> On the current core-updates branch, font-gnu-freefont fails to build with
> the attatched build log.
>
> Based on the messages about syntax errors, it looks like gnu-freefont is
> not compatible with python3, and instead needs python2.

A new version of GNU FreeFont that supports Python 3 is slated for later
this year. Meanwhile I fixed this by providing an older FontForge in
commit 4affa9182d93c77505c40e95964b8ab9d436298b.

Thanks!
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl6jEdIACgkQoqBt8qM6
VPqJkwf/fuDaOig/nXcGU2nATyk8y9Gm2zOzvUsjEAn+FuEypxzNemwqetDmosd7
9UhQQQKb79dtlvmGNzW5YDnk/Z/gzuotKNHrLA/nfEYINXN/B4CUKOOnEv9LZJRT
bMrnVLL5jI1pU1TTdKZKWId34KrDD67yaWJxkvzu4VaMjAOpdpJF6i2P3faCBJWS
UsbZRR0Wrp7JAHmXcBcV7TvguTw07xyO1vc5V3s5wTozh/IpYiE/YpZ/EZlmKwi+
NKn9ArK/OESIESvyeoRqZ4RYAMkdQM/wuD3ij7HXQJaEQUUP1CfaR8x2vblsUEAp
fl674y0nkXlX27hspu9u1/IRZjd6AQ==
=bsaY
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 40819@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 40819
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch