GNU bug report logs -
#53184
mycli unmet dependency on python-pyperclip
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 53184 in the body.
You can then email your comments to 53184 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#53184
; Package
guix
.
(Tue, 11 Jan 2022 10:14:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Rostislav Svoboda <rostislav.svoboda <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Tue, 11 Jan 2022 10:14:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
The command was:
$ guix upgrade mycli
The following package will be upgraded:
mycli (dependencies or package changed)
substitute: updating substitutes from 'https://ci.guix.gnu.org'...
0.0%guix substitute: warning: ci.guix.gnu.org: connection failed:
Connection timed out
substitute:
The following derivations will be built:
/gnu/store/hxisvawd8dwrazxqxbiqgddprwbgphkw-profile.drv
/gnu/store/vfp2fv1qsixc7f9x6n1pj8z49a6jh48n-mycli-1.24.1.drv
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 0.0%
building /gnu/store/vfp2fv1qsixc7f9x6n1pj8z49a6jh48n-mycli-1.24.1.drv...
\ 'sanity-check' phasebuilder for
`/gnu/store/vfp2fv1qsixc7f9x6n1pj8z49a6jh48n-mycli-1.24.1.drv' failed
with exit code 1
build of /gnu/store/vfp2fv1qsixc7f9x6n1pj8z49a6jh48n-mycli-1.24.1.drv failed
View build log at
'/var/log/guix/drvs/vf/p2fv1qsixc7f9x6n1pj8z49a6jh48n-mycli-1.24.1.drv.bz2'.
cannot build derivation
`/gnu/store/hxisvawd8dwrazxqxbiqgddprwbgphkw-profile.drv': 1
dependencies couldn't be built
guix upgrade: error: build of
`/gnu/store/hxisvawd8dwrazxqxbiqgddprwbgphkw-profile.drv' failed
The build log says:
...
validating 'mycli'
/gnu/store/6azf9r02qsslp8yx1kmgnv2gpqfpc409-mycli-1.24.1/lib/python3.9/site-packages
...checking requirements: ERROR: mycli==1.24.1 (pyperclip 1.6.4
(/gnu/store/q1l7qm1lqiz9i58xw6ya7rc4cjpvfjwy-python-pyperclip-1.6.4/lib/python3.9/site-packages),
Requirement.parse('pyperclip>=1.8.1'), {'mycli'})
error: in phase 'sanity-check': uncaught exception:
%exception #<&invoke-error program: "python" arguments:
("/gnu/store/nwwr89v2vyg1hs48i49m083vhczsgh3m-sanity-check.py"
"/gnu/store/6azf9r02qsslp8yx1kmgnv2gpqfpc409-mycli-1.24.1/lib/python3.9/site-packages")
exit-status: 1 term-signal: #f stop-signal: #f>
phase `sanity-check' failed after 0.1 seconds
command "python"
"/gnu/store/nwwr89v2vyg1hs48i49m083vhczsgh3m-sanity-check.py"
"/gnu/store/6azf9r02qsslp8yx1kmgnv2gpqfpc409-mycli-1.24.1/lib/python3.9/site-packages"
failed with status 1
(Full build log is in the attachment)
Could you fix it please? Thanks
Bost
[p2fv1qsixc7f9x6n1pj8z49a6jh48n-mycli-1.24.1.drv.bz2 (application/octet-stream, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53184
; Package
guix
.
(Tue, 11 Jan 2022 10:46:03 GMT)
Full text and
rfc822 format available.
Message #8 received at 53184 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Rostislav Svoboda schreef op di 11-01-2022 om 11:12 [+0100]:
> /gnu/store/6azf9r02qsslp8yx1kmgnv2gpqfpc409-mycli-
> 1.24.1/lib/python3.9/site-packages
> ...checking requirements: ERROR: mycli==1.24.1 (pyperclip 1.6.4
> (/gnu/store/q1l7qm1lqiz9i58xw6ya7rc4cjpvfjwy-python-pyperclip-
> 1.6.4/lib/python3.9/site-packages),
> Requirement.parse('pyperclip>=1.8.1'), {'mycli'})
It would seem that if python-pyperclip is upgraded, the build would
succeed.
Greetings,
Maxime.
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53184
; Package
guix
.
(Tue, 11 Jan 2022 10:53:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 53184 <at> debbugs.gnu.org (full text, mbox):
> 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
guix install: error: profile contains conflicting entries for python-pyperclip
guix install: error: first entry: python-pyperclip <at> 1.6.4
/gnu/store/q1l7qm1lqiz9i58xw6ya7rc4cjpvfjwy-python-pyperclip-1.6.4
guix install: error: second entry: python-pyperclip <at> 1.6.4
/gnu/store/b6fr579v3cg944n84lxv1k2hnqfwyssp-python-pyperclip-1.6.4
guix install: error: ... propagated from mycli <at> 1.24.1
hint: Try upgrading both `python-pyperclip' and `mycli', or remove one
of them from the profile.
And at this point I decided to write a bug report instead of wasting
time with ad hoc workaround(s).
Bost
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53184
; Package
guix
.
(Tue, 11 Jan 2022 11:01:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 53184 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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.
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53184
; Package
guix
.
(Tue, 11 Jan 2022 11:19:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 53184 <at> debbugs.gnu.org (full text, mbox):
> If it does, there's some serious and weird bug in the guix daemon's
> build isolation code.
I wonder how and why the mycli got installed without having it's
dependency, the python-pyperclip installed in the first place.
Bost
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53184
; Package
guix
.
(Tue, 11 Jan 2022 14:44:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 53184 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Rostislav Svoboda <rostislav.svoboda <at> gmail.com> writes:
> I wonder how and why the mycli got installed without having it's
> dependency, the python-pyperclip installed in the first place.
I think, that's because pyperclip is needed in "sanity-check" phase and
we didn't had this before the big merge.
--
Garbage In -- Gospel Out.
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53184
; Package
guix
.
(Tue, 11 Jan 2022 14:47:01 GMT)
Full text and
rfc822 format available.
Message #23 received at 53184 <at> debbugs.gnu.org (full text, mbox):
> I think, that's because pyperclip is needed in "sanity-check" phase and
> we didn't had this before the big merge.
I'm rather new to guix... big merge what with what?
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53184
; Package
guix
.
(Tue, 11 Jan 2022 15:08:02 GMT)
Full text and
rfc822 format available.
Message #26 received at 53184 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Rostislav Svoboda <rostislav.svoboda <at> gmail.com> writes:
>> I think, that's because pyperclip is needed in "sanity-check" phase and
>> we didn't had this before the big merge.
>
> I'm rather new to guix... big merge what with what?
Oh, I'm sorry and welcome to guix!
What I called "the big merge" was the merge of the "core-updates" branch
with master some weeks ago.
See e.g. https://guix.gnu.org/manual/en/guix.html#Submitting-Patches for
a description of the branches master,staging and core-updates.
--
Wir haben alle zwei Leben: Das zweite beginnt,
wenn wir realisieren, dass wir nur ein Leben haben.
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#53184
; Package
guix
.
(Wed, 12 Jan 2022 11:50:02 GMT)
Full text and
rfc822 format available.
Message #29 received at 53184 <at> debbugs.gnu.org (full text, mbox):
It works now. We can close this bug. Thank you for fixing it.
Reply sent
to
Leo Famulari <leo <at> famulari.name>
:
You have taken responsibility.
(Wed, 12 Jan 2022 18:44:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Rostislav Svoboda <rostislav.svoboda <at> gmail.com>
:
bug acknowledged by developer.
(Wed, 12 Jan 2022 18:44:02 GMT)
Full text and
rfc822 format available.
Message #34 received at 53184-done <at> debbugs.gnu.org (full text, mbox):
On Wed, Jan 12, 2022 at 12:48:26PM +0100, Rostislav Svoboda wrote:
> It works now. We can close this bug. Thank you for fixing it.
Anybody can close the bug by sending a message to
<53184-done <at> debbugs.gnu.org>, like I am doing now.
This is described here:
https://debbugs.gnu.org/server-control.html
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 10 Feb 2022 12:24:10 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 46 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.