From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 65774@debbugs.gnu.org
Subject: bug#65774: python updater clears inputs, leaves propagated-inputs empty
Date: Wed, 06 Sep 2023 01:15:58 -0400 [thread overview]
Message-ID: <87tts77ugh.fsf@gmail.com> (raw)
Hi,
I've had the Python updater produce this when attempting to update
fontmake:
gnu/packages/fontutils.scm:780:2: warning: fontmake: 'propagated-inputs'
field not found; leaving it unchanged
gnu/packages/fontutils.scm:780:2: warning: fontmake: expected
'propagated-inputs' value: (python-attrs python-fontmath
python-fonttools python-glyphslib python-ufo2ft python-ufolib2)
--8<---------------cut here---------------start------------->8---
modified gnu/packages/fontutils.scm
@@ -779,16 +779,16 @@ (define-public psautohint-font-data
(define-public fontmake
(package
(name "fontmake")
- (version "3.4.0")
+ (version "3.7.1")
(source (origin
(method url-fetch)
(uri (pypi-uri "fontmake" version ".zip"))
(sha256
(base32
- "0fc5c9csjpy1aa4c03p7nvjgls5wjplhmmf42n0cmvrlh6cm7wl3"))))
+ "0ib7fvwgwazm7qfj4a3rkqkb40xfbj40rnvsmkvl2isg2ky3vg9m"))))
(build-system python-build-system)
- (inputs (list python-fontmath python-glyphslib))
- (native-inputs (list unzip python-setuptools-scm))
+ (inputs (list))
+ (native-inputs (list zip))
(home-page "https://github.com/googlefonts/fontmake")
(synopsis
"Compile fonts from sources (UFO, Glyphs) to binary (OpenType, TrueType)")
--8<---------------cut here---------------end--------------->8---
The choice of using inputs here was conscious, as it is a command, not a
library. Perhaps it could check if the name starts with 'python-' or
not? It's a bit 'magic', but it would help.
--
Thanks,
Maxim
next reply other threads:[~2023-09-06 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 5:15 Maxim Cournoyer [this message]
2023-09-06 17:18 ` bug#65774: python updater clears inputs, leaves propagated-inputs empty Sergio Pastor Pérez
2023-09-06 18:38 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tts77ugh.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=65774@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).