From: Danny Milosavljevic <dannym@scratchpost.org>
To: swedebugia <swedebugia@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: Packaging ufw
Date: Sat, 10 Nov 2018 22:25:59 +0100 [thread overview]
Message-ID: <20181110222559.28ad2d00@scratchpost.org> (raw)
In-Reply-To: <bab3a3bb-102c-3caa-778e-b6acd0b827b3@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 2269 bytes --]
Hi,
On Sat, 10 Nov 2018 21:42:38 +0100
swedebugia <swedebugia@riseup.net> wrote:
> I need help.
>
> It fails with
>
> starting phase `install'
> running "python setup.py" with command "install" and parameters
> ("--prefix=/gnu/store/v8kzgqs1jdfg7wzqr9c02719ada6x8bm-ufw-0.35"
> "--single-version-externally-managed" "--root=/" "--root=/")
> Found
> '/gnu/store/8assqq8vmmvn09cysg5nm3kf2075hvxd-iptables-1.6.2/sbin/iptables'
> version '1.6.2\n''
> usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
> or: -c --help [cmd1 cmd2 ...]
> or: -c --help-commands
> or: -c cmd --help
>
> error: option --single-version-externally-managed not recognized
>
> This option comes from the python-build-system.
Yes, and it elaborates (in guix/guix/build/python-build-system.scm):
>;; Pip behaves a bit different then easy_install: it always executes
>;; "setup.py" with the option "--single-version-externally-managed" set. This
>;; makes setuptools' "install" command run the original "install" command
>;; instead of the "easy_install" command, so no .pth file (and no site.py)
>;; will be created. The "site-packages" directory only contains the package
>;; and the related .egg-info directory.
>;;
>;; This is exactly what we need for Guix and this is what we mimic in the
>;; install phase below.
>(define* (install #:key outputs (configure-flags '()) use-setuptools?
> #:allow-other-keys)
> "Install a given Python package."
> (let* ((out (assoc-ref outputs "out"))
> (params (append (list (string-append "--prefix=" out))
> (if use-setuptools?
^---- Aha!
> ;; distutils does not accept these flags
>
> (list "--single-version-externally-managed"
> "--root=/")
> '())
> configure-flags)))
> (call-setuppy "install" params use-setuptools?)
> #t))
Try specifying
(arguments
`(#:use-setuptools? #f))
in the package.
But if ufw doesn't use "--single-version-externally-managed", that implies
that ufw is not available on PyPI. Weird.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-11-10 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-10 16:01 Packaging ufw swedebugia
2018-11-10 18:19 ` swedebugia
2018-11-10 18:24 ` Brett Gilio
2018-11-10 20:42 ` swedebugia
2018-11-10 21:25 ` Danny Milosavljevic [this message]
2018-11-10 18:30 ` Pierre Neidhardt
-- strict thread matches above, loose matches on Subject: below --
2018-11-11 1:30 Jeremiah
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=20181110222559.28ad2d00@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=swedebugia@riseup.net \
/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).