[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
mismatch of source tar ball hash
From: |
Marco van Hulten |
Subject: |
mismatch of source tar ball hash |
Date: |
Sun, 28 Oct 2018 12:23:33 +0100 |
Hi—
When I try to install calcurse, the hash of the downloaded file is
different from the one specified in the package:
address@hidden ~$ guix package --fallback -i calcurse
The following package will be installed:
calcurse 4.3.0
/gnu/store/a77ap0vw0fnsz138paby8w55rlcd58zi-calcurse-4.3.0
The following derivations will be built:
/gnu/store/r44sbjgn7gxwl3nxvlnq6946zc05xq0f-profile.drv
/gnu/store/xzvmj17kgc5z97czlw5nrz7afb47cjyh-ca-certificate-bundle.drv
/gnu/store/wazkm772ssqj81w9npbfi9531s41rh4w-glib-schemas.drv
/gnu/store/kwqvdmcpqrqg1q2gk6zc83c50x8w8198-gtk-icon-themes.drv
/gnu/store/fad05ars0k7lnis4pys6bc5n2mrwywqj-xdg-mime-database.drv
/gnu/store/dkr1dg622dyaphw66zy2lrb925pkfz0y-xdg-desktop-database.drv
/gnu/store/9zqzgm8gybh8a8w05g4151k7bk3wkv7x-fonts-dir.drv
/gnu/store/4ccc9liswa27f56867fnsg4xl657irpg-info-dir.drv
/gnu/store/35zb2h95ssn189i8y43z54b6jqmngwsp-gtk-im-modules.drv
/gnu/store/6abn78c8wa5dkks4pnig5i2mijj0f3lf-manual-database.drv
0.3 MB will be downloaded:
/gnu/store/a77ap0vw0fnsz138paby8w55rlcd58zi-calcurse-4.3.0
substitution of /gnu/store/a77ap0vw0fnsz138paby8w55rlcd58zi-calcurse-4.3.0
failed
building
/gnu/store/ya1v2nv0mq8dzkcik64inlyxxk3skz3h-calcurse-4.3.0.tar.gz.drv...
downloading from http://calcurse.org/files/calcurse-4.3.0.tar.gz...
sha256 hash mismatch for
/gnu/store/873m2xbqxndbhcdfrngpsj7cwflm48d0-calcurse-4.3.0.tar.gz:
expected hash: 16jzg0nasnxdlz23i121x41pq5kbxmjzk52c5d863rg117fc7v1i
actual hash: 11q0r4dbi8vca22x3q1ad07nr1gs4y17cgnplbjzmmz9r9x0h8m2
build of /gnu/store/ya1v2nv0mq8dzkcik64inlyxxk3skz3h-calcurse-4.3.0.tar.gz.drv
failed
View build log at
'/var/log/guix/drvs/ya/1v2nv0mq8dzkcik64inlyxxk3skz3h-calcurse-4.3.0.tar.gz.drv.bz2'.
\guix package: error: build failed: build of
`/gnu/store/r44sbjgn7gxwl3nxvlnq6946zc05xq0f-profile.drv' failed
Should I contact the calcurse people to ask if the file could have been
changed? Or is there a better hypothesis explaining this issue?
—Marco
- mismatch of source tar ball hash,
Marco van Hulten <=