From: Jesse Gibbons <jgibbons2357@gmail.com>
To: 35893@debbugs.gnu.org
Subject: bug#35893: guix import json does not specify input package's output when provided in the json
Date: Fri, 24 May 2019 18:49:29 -0600 [thread overview]
Message-ID: <20190524184929.771a67b7@gmail.com> (raw)
I'm trying to generate a package definition from the following json:
{
"name" : "pysolfc",
"version" : "2.6.4",
"source" : "https://github.com/shlomif/PySolFC/archive/pysolfc-2.6.4.tar.gz"
"build-system" : "python",
"home-page" : "https://pysolfc.sourceforge.io/",
"synopsis" : "Solitaire Collection, Written in Python",
"description" : "PySol Fan Club Edition (PySolFC) is a collection of more than 1000 solitaire card games. It is a fork of PySol Solitaire.",
"license" : "GPL-3.0+",
"inputs" : ["python2:tk"],
"propagated-inputs" : ["python2-six"]
}
==========
When I run guix import json pysolfc.json >> pysolfc.scm and define the
output as a public package, I get the following:
(define-module (custom packages pysolfc)
#:use-module (guix packages)
#:use-module (guix download)
#:use-module (guix build-system python)
#:use-module (guix licenses))
(define-public pysolfc
(package
(name "pysolfc")
(version "2.6.4")
(source
(origin
(method url-fetch)
(uri (string-append
"https://github.com/shlomif/PySolFC/archive/pysolfc-"
version
".tar.gz"))
(sha256
(base32
"17r9mbn4fj6kbxhllsab74gfjac0j2mjdwkkwaxp6cqpy4dss3z8"))))
(build-system python-build-system)
(inputs
`(("python2" ,(@ (gnu packages python) python-2))))
(propagated-inputs
`(("python2-six"
,(@ (gnu packages python-xyz) python2-six))))
(home-page "https://pysolfc.sourceforge.io/")
(synopsis
"Solitaire Collection, Written in Python")
(description
"PySol Fan Club Edition (PySolFC) is a collection of more than 1000 solitaire card games. It is a fork of PySol Solitaire.")
(license gpl3+))
)
====================
When I try to build this I get the following error:
import _tkinter # If this fails your Python may not be configured
for Tk ModuleNotFoundError: No module named '_tkinter'
====================
Conclusion: guix import json doesn't specify the output required by the
json.
next reply other threads:[~2019-05-25 0:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 0:49 Jesse Gibbons [this message]
2019-06-07 21:17 ` bug#35893: guix import json does not specify input package's output when provided in the json Ludovic Courtès
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=20190524184929.771a67b7@gmail.com \
--to=jgibbons2357@gmail.com \
--cc=35893@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).