'guix pull' error while updating from 1.0.0

  • Done
  • quality assurance status badge
Details
4 participants
  • Giovanni Biscuolo
  • jg
  • Ludovic Courtès
  • Maxim Cournoyer
Owner
unassigned
Submitted by
jg
Severity
normal
J
J
jg wrote on 14 May 2019 00:12
Reporting a bug
(address . bug-guix@gnu.org)
7ae28ff01e1c669c69d1ba4c1f7ab5bd@fossilfreecanada.ca
Hi there,

The program told me to write to you about this.

error: You found a bug: the program
'/gnu/store/3p3p50xmgp21xfd6hvxkyn69v5lmbk5y-compute-guix-derivation'
failed to compute the derivation for Guix (version:
"a430a3501a6d3a565cb78e04a8dbb3ab846ec5fc"; system: "x86_64-linux";
host version: "1.0.0"; pull-version: 1).
Please report it by email to

Regards,
Javier
L
L
Ludovic Courtès wrote on 14 May 2019 10:07
(address . jg@fossilfreecanada.ca)(address . 35723@debbugs.gnu.org)
87h89x31dq.fsf@gnu.org
Hello,

jg@fossilfreecanada.ca skribis:

Toggle quote (9 lines)
> The program told me to write to you about this.
>
> error: You found a bug: the program
> '/gnu/store/3p3p50xmgp21xfd6hvxkyn69v5lmbk5y-compute-guix-derivation'
> failed to compute the derivation for Guix (version:
> "a430a3501a6d3a565cb78e04a8dbb3ab846ec5fc"; system: "x86_64-linux";
> host version: "1.0.0"; pull-version: 1).
> Please report it by email to

I’ve tried to reproduce the issue with:

guix pull -p ./test --commit=a430a3501a6d3a565cb78e04a8dbb3ab846ec5fc

but I didn’t hit the bug.

Did you have any useful hints above the “You found a bug” message, such
as a backtrace?

Could you try running ‘guix pull’ again?

Thanks for your report,
Ludo’.
L
L
Ludovic Courtès wrote on 14 May 2019 10:13
control message for bug #35723
(address . control@debbugs.gnu.org)
87bm053141.fsf@gnu.org
retitle 35723 'guix pull' error while updating from 1.0.0
G
G
Giovanni Biscuolo wrote on 15 May 2019 09:55
Re: bug#35723: guix pull error (was Reporting a bug)
(address . 35723@debbugs.gnu.org)
877easdueb.fsf@roquette.mug.biscuolo.net
Hello,

Ludovic Courtès <ludo@gnu.org> writes:

[...]

Toggle quote (6 lines)
> I’ve tried to reproduce the issue with:
>
> guix pull -p ./test --commit=a430a3501a6d3a565cb78e04a8dbb3ab846ec5fc
>
> but I didn’t hit the bug.

(was not strictly needed but) I confirm that I didn' hit the bug also :-)

my two cents, Gio'

[...]

--
Giovanni Biscuolo

Xelera IT Infrastructures
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEERcxjuFJYydVfNLI5030Op87MORIFAlzbxd0ACgkQ030Op87M
ORL1fQ//aRT1AXWY9384gywwjAp6ql9sQ81Fz+Uf5xu8WSGPTmh/4WCmnYjEGv9Y
jEpIQaJZxtgOQxyvGXyRxokenyAVH81A5DdN7zgTYg3mNQ+CUBALyFjBFCBTaQQh
8PSEyGNUSjxYF1Phq0/RJoPN7VHg/19RAnmAV3t2bh3XvMZShx8zheJIQvsxmOla
MBqpguZBOHSkKPpzFKf2scQYGram4lZdI8p0EsFkuFIS1pda9De2P7e8h0Rm/X8n
4CZE0UIgJNpEq+AlIiLotVJipAAf5wrBmRnLts/ZzI/EwV532z34dfSqVVI4QUmF
vY1LOAEetGVWhaYdrwa7FPvLMhiwul0HCABakYmL9FxaJ3dypDHSjkJw/o68m3OQ
g7Ak5QYTdaLlFvO0tXo9wpuokNMmJRotVk04w/dXMjV7QSr2Jd6SslCu1FQYimoo
1vuQcv6jfs2pbXqm0Cil2Ys1maFA/84xFxQGetjS2noOe8Qc7OFOQCDCQ/z9ejW5
xCfPpDffg5r4WGusmeAMt2BWNc5ojV4hnXOzYCTo361G3ze/n8/svrFR4zEwS/Gj
9l7rj6VF3chXsz0uLfwDZ1C3LcuSF7mppMObTpaOAmFL9Lk/6YvY8H4ZobvZXEn/
WxwkuSt7n9tXwa2JKdk8RtNpPOa/X4gAcjdcwDoDWe4eTVaMWI8=
=YPWq
-----END PGP SIGNATURE-----

M
M
Maxim Cournoyer wrote on 18 Aug 2021 02:58
Re: bug#35723: 'guix pull' error while updating from 1.0.0
(name . Giovanni Biscuolo)(address . g@xelera.eu)
87im03y3fm.fsf_-_@gmail.com
Hello,

Giovanni Biscuolo <g@xelera.eu> writes:

Toggle quote (18 lines)
> Hello,
>
> Ludovic Courtès <ludo@gnu.org> writes:
>
> [...]
>
>> I’ve tried to reproduce the issue with:
>>
>> guix pull -p ./test --commit=a430a3501a6d3a565cb78e04a8dbb3ab846ec5fc
>>
>> but I didn’t hit the bug.
>
> (was not strictly needed but) I confirm that I didn' hit the bug also :-)
>
> my two cents, Gio'
>
> [...]

I'm closing this old forgotten issue, as people were not able to
reproduce and we're now at version 1.3.0.

Thanks for the report!

Maxim
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 35723@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 35723
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch