bug#41044: [guix 1.1.0] guix pull failed

bug#41044: [guix 1.1.0] guix pull failed

[wensheng xie]

[-- Attachment #1: Type: text/plain, Size: 3192 bytes --]

The log in console:
root@guix ~# guix pull
Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
Building from this channel:
  guix      https://git.savannah.gnu.org/git/guix.git 1463079
Computing Guix derivation for 'x86_64-linux'... -Backtrace:
In srfi/srfi-1.scm:
   592:29 19 (map1 ((#<package libtasn1@4.14 7fa636bd5f20> "out") (#<package libidn2@2.2.0 7fa63e8ba9a0> "out") (?) ?))
   592:29 18 (map1 ((#<package libidn2@2.2.0 7fa63e8ba9a0> "out") (#<package nettle@3.5.1 7fa63d8a7630> "out") (?) ?))
   592:29 17 (map1 ((#<package nettle@3.5.1 7fa63d8a7630> "out") (#<package zlib@1.2.11 7fa635bc3420> "out") (# #) ?))
   592:29 16 (map1 ((#<package zlib@1.2.11 7fa635bc3420> "out") (#<package gmp@6.1.2 7fa63e72e370> "out") (#<p?> ?) ?))
   592:29 15 (map1 ((#<package gmp@6.1.2 7fa63e72e370> "out") (#<package guile3.0-git@0.3.0 ./guix/packages.sc?> ?) ?))
   592:29 14 (map1 ((#<package guile3.0-git@0.3.0 ./guix/packages.scm:893 7fa635457210> "out") (#<package guil?> ?) ?))
   592:29 13 (map1 ((#<package guile3.0-bytestructures@1.0.7 ./guix/packages.scm:893 7fa6354574d0> "out") (#<p?> ?) ?))
   592:29 12 (map1 ((#<package guile3.0-json@3.5.0 ./guix/packages.scm:893 7fa635c3e160> "out") (#<package gui?> ?) ?))
   592:29 11 (map1 ((#<package guile3.0-ssh@0.12.0 7fa63e1d2210> "out") (#<package guile3.0-sqlite3@0.1.0 ./gu?> ?) ?))
   592:29 10\(map1 ((#<package guile3.0-sqlite3@0.1.0 ./guix/packages.scm:893 7fa6354578f0> "out") (#<<compute?> ?) ?))
   592:29  9 (map1 ((#<<computed-file> name: "guix-core" gexp: #<gexp (begin (use-modules (srfi srfi-26) (ice-?> ?) ?))
   592:29  8|(map1 ((#<<computed-file> name: "guix-extra" gexp: #<gexp (begin (use-modules (srfi srfi-26) (ice?> ?) ?))
   592:17  7/(map1 ((#<<computed-file> name: "guix-packages-base" gexp: #<gexp (begin (use-modules (srfi srfi-?> ?) ?))
In ./guix/store.scm:
   1255:8  6 (call-with-build-handler #<procedure build-accumulator (continue store things mode)> _)
  1975:24  5 (run-with-store #<store-connection 256.99 7fa6403256c0> _ #:guile-for-build _ #:system _ #:target _)
In ./guix/gexp.scm:
    691:8  4 (_ _)
In ./guix/store.scm:
   1811:8  3 (_ _)
  1846:38  2 (_ #<store-connection 256.99 7fa6403256c0>)
In ./guix/derivations.scm:
   926:17  1 (derivation #<store-connection 256.99 7fa6403256c0> _ _ _ #:system _ #:env-vars _ #:inputs _ #:sources _ ?)
In ./guix/store.scm:
   1034:9  0 (_ #<store-connection 256.99 7fa6403256c0> _ #vu8(68 101 114 105 118 101 40 91 40 34 111 117 116 34 # ?) ?)

./guix/store.scm:1034:9: Throw to key `srfi-34' with args `(#<condition &store-protocol-error [message: "error parsing derivation `/gnu/store/7vs0arx5s6whljvbbb5rky4mbrs61f85-icu4c-datetime-regression.patch.drv': expected string `)'" status: 1] 7fa6368f3f30>)'.
guix pull: error: You found a bug: the program '/gnu/store/d5j5nl4jd10dbbpyw0rpqxbadnj7dxcc-compute-guix-derivation'
failed to compute the derivation for Guix (version: "1463079a2dc855df2274a2429dd48adc4d31ffdb"; system: "x86_64-linux";
host version: "8a0b02c248a9877812cce29641bb1843cb77ea19"; pull-version: 1).
Please report it by email to <bug-guix@gnu.org>.


[-- Attachment #2: Type: text/html, Size: 4965 bytes --]

bug#41044: [guix 1.1.0] guix pull failed

[Ludovic Courtès]

Hi,

wensheng xie <xiewensheng@hotmail.com> skribis:

> ./guix/store.scm:1034:9: Throw to key `srfi-34' with args `(#<condition &store-protocol-error [message: "error parsing derivation `/gnu/store/7vs0arx5s6whljvbbb5rky4mbrs61f85-icu4c-datetime-regression.patch.drv': expected string `)'" status: 1] 7fa6368f3f30>)'.

Could you check the contents of the file above?  It seems to be corrupt,
which could be the result of a hard disk corruption, possibly due to
hardware issues.

Thanks in advance,
Ludo’.

bug#41044: [guix 1.1.0] guix pull failed

[zimoun]

Dear,

Since

> The problem is solved by doing 'guix pull' again.

and

>> Could you check the contents of the file above?  It seems to be corrupt,
>> which could be the result of a hard disk corruption, possibly due to
>> hardware issues.

the issue was on the user side.  Therefore, closing.


All the best,
simon