From: Nathan Dehnel <ncdehnel@gmail.com>
To: help-guix@gnu.org
Subject: "invalid input: python"
Date: Wed, 4 Mar 2020 23:56:57 -0600 [thread overview]
Message-ID: <CAEEhgEvFdPw6cxz0-5fQ85zk5JVwdVFH7xwVo0e+oJk4ebwysg@mail.gmail.com> (raw)
(define-public ladish
(package
(name "ladish")
(version "ladish-1")
(source
(origin
(method git-fetch)
(uri
(git-reference
(url "https://github.com/LADI/ladish.git")
(commit version)))
(file-name (git-file-name name version))
(sha256
(base32
"0cmmpz87cs2j15d5jbzffx24gqlgrcq0465k3qx12ai9mbi6lbf0"))))
(build-system waf-build-system)
(arguments
'(#:python ,python-2))
(inputs
`(("alsa-lib" ,alsa-lib)
("jack2" ,jack-2)
("dbus" ,dbus)
("e2fsprogs" ,e2fsprogs)
("expat" ,expat)
("glib" ,glib)
("dbus-glib" ,dbus-glib)
("gtk+" ,gtk+)))
(home-page "http://ladish.org/")
(synopsis "LADI Session Handler")
(description "LADI Session Handler or simply ladish is a session
management system for JACK applications on GNU/Linux. Its aim is to
allow you to have many different audio programs running at once, to
save their setup, close them down and then easily reload the setup at
some other time. ladish doesn't deal with any kind of audio or MIDI
data itself; it just runs programs, deals with saving/loading
(arbitrary) data and connects JACK ports together. It can also be used
to move entire sessions between computers, or post sessions on the
Internet for download.")
(license gpl2)))
bash-5.0$ guix package -i ladish
WARNING: (cadence): `expat' imported from both (guix licenses) and
(gnu packages xml)
guix package: error: cadence.scm:142:2: package `ladish@ladish-1' has
an invalid input: ("python" (unquote python-2))
What am I doing wrong? This seems no different from how e.g.
non-sequencer package is doing it.
next reply other threads:[~2020-03-05 5:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 5:56 Nathan Dehnel [this message]
2020-03-05 6:08 ` "invalid input: python" Tobias Geerinckx-Rice
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEEhgEvFdPw6cxz0-5fQ85zk5JVwdVFH7xwVo0e+oJk4ebwysg@mail.gmail.com \
--to=ncdehnel@gmail.com \
--cc=help-guix@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.