From: "Gábor Boskovits" <boskovits@gmail.com>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: Guix <guix-devel@gnu.org>
Subject: Re: WIP gnu: poetry: Update to 1.0.3.
Date: Mon, 3 Feb 2020 19:20:36 +0100 [thread overview]
Message-ID: <CAE4v=pjxnY5SK0D7jKL9v4vPKx=EUzLkWkhqE2dL4ywa-b8qeg@mail.gmail.com> (raw)
In-Reply-To: <20200203153122.llccmfho2fwtr7o7@rafflesia>
Hello,
Tanguy Le Carrour <tanguy@bioneland.org> ezt írta (időpont: 2020.
febr. 3., H, 16:31):
>
> Dear Guix,
>
> I'm working on updating Poetry to version 1.0.3 and I have a problem
> with the version of a dependency.
>
> Poetry now depends on python-keyring >=20.0.0,<21.0.0. In Guix we
> have python-keyring 21.0.0, so it does not work once installed!
>
> What am I supposed to do?
>
> I see 3 different ways out of this:
> - patch the package to make it use our version (I tried but failed [1]);
> - ask upstream to update dependencies;
> - declare a new package python-keyring-20.0.0 and use it as an input.
Asking upstream to update would be great.
>
> [1]: attempt to patch setup.py
> - (arguments `(#:tests? #f)) ; tests depend on dbus service
> + (arguments
> + `(#:tests? #f ;; Pypi does not have tests.
> + #:phases
> + (modify-phases %standard-phases
> + (add-after 'unpack 'change-dependencies
> + (lambda _
> + ;; Guix has version 21.0.0 of python-keyring
> + (invoke "sed" "-i" "-e"
> + "s/keyring>=20.0.1,<21.0.0/keyring>=20.0.1,<22.0.0/"
> + "setup.py")
> + #t)))))
>
What did not work in this case?
Also, do you think that you could replace invoke sed with substitute*?
> Any help welcome!
>
> --
> Tanguy
>
Best regards,
g_bor
--
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21
next prev parent reply other threads:[~2020-02-03 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 15:31 WIP gnu: poetry: Update to 1.0.3 Tanguy Le Carrour
2020-02-03 18:20 ` Gábor Boskovits [this message]
2020-02-04 8:48 ` Tanguy Le Carrour
2020-02-05 17:13 ` Tanguy Le Carrour
2020-02-19 16:40 ` Tanguy Le Carrour
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='CAE4v=pjxnY5SK0D7jKL9v4vPKx=EUzLkWkhqE2dL4ywa-b8qeg@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=tanguy@bioneland.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.