From: Maxime Devos <maximedevos@telenet.be>
To: Rostislav Svoboda <rostislav.svoboda@gmail.com>
Cc: 53184@debbugs.gnu.org
Subject: bug#53184: mycli unmet dependency on python-pyperclip
Date: Tue, 11 Jan 2022 11:00:15 +0000 [thread overview]
Message-ID: <c687bfeb623ff2353deedfa2aefc1022fefff35d.camel@telenet.be> (raw)
In-Reply-To: <CAEtmmewEti7K_kAKcS3E=9nXYGd=2-ru1nPP8u7nj=_Fc64r1g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
Rostislav Svoboda schreef op di 11-01-2022 om 11:51 [+0100]:
> > It would seem that if python-pyperclip is upgraded, the build would
> > succeed.
>
> Hmm maybe. I tried:
>
> $ guix install python-pyperclip
> The following package will be installed:
> python-pyperclip 1.6.4
I mean updating the version of python-pyperclip packaged in Guix,
e.g. with "./pre-inst-env guix refresh -u python-pyperclip"
(assuming that works), not the python-pyperclip in the profile.
The version of pyperclip in some profile does not have any
impact on whether the build of a depedent of pyperclip succeeds.
If it does, there's some serious and weird bug in the guix daemon's
build isolation code.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-01-11 11:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 10:12 bug#53184: mycli unmet dependency on python-pyperclip Rostislav Svoboda
2022-01-11 10:45 ` Maxime Devos
2022-01-11 10:51 ` Rostislav Svoboda
2022-01-11 11:00 ` Maxime Devos [this message]
2022-01-11 11:17 ` Rostislav Svoboda
2022-01-11 14:42 ` Michael Rohleder
2022-01-11 14:46 ` Rostislav Svoboda
2022-01-11 15:06 ` Michael Rohleder
2022-01-12 11:48 ` Rostislav Svoboda
2022-01-12 18:43 ` Leo Famulari
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=c687bfeb623ff2353deedfa2aefc1022fefff35d.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53184@debbugs.gnu.org \
--cc=rostislav.svoboda@gmail.com \
/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).