[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#33419: guix package is not showing that the checksum is mismatching
From: |
Ludovic Courtès |
Subject: |
bug#33419: guix package is not showing that the checksum is mismatching |
Date: |
Mon, 19 Nov 2018 21:30:46 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Hello,
Björn Höfling <address@hidden> skribis:
> $ guix package -u guix-tools
> substitute: updating list of substitutes from 'https://berlin.guixsd.org'...
> 0
> [..]
> building
> /gnu/store/vy3s1y7bv1w6d8gmp5b10xppy9skbgkd-guix-tools-0.1.0-2.4f17b79-checkout.drv...
> build of
> /gnu/store/vy3s1y7bv1w6d8gmp5b10xppy9skbgkd-guix-tools-0.1.0-2.4f17b79-checkout.drv
> failed
> View build log at
> '/var/log/guix/drvs/vy/3s1y7bv1w6d8gmp5b10xppy9skbgkd-guix-tools-0.1.0-2.4f17b79-checkout.drv.bz2'.
> -guix package: error: build failed: build of
> `/gnu/store/iwma3gq778n32mqz6y7277g67nvx1abb-guix-tools-0.1.0-2.4f17b79.drv'
> failed
[...]
> $ guix build guix-tools
>
> HEAD is now at 4f17b79 gdev: Add more package to environment.
> environment variable `PATH' unset
> output path
> `/gnu/store/s399g9f1k19v01rs992w5dl6aif87har-guix-tools-0.1.0-2.4f17b79-checkout'
> should have r:sha256 hash
> `1j4q43hk7jrys7zsmws37g6w7babzshfdb1s5myl7qwr3mcx6hnf', instead has
> `0b61q29915b4i6adidx3zixnx3m0zp58rjbfa9byqcz13szznc52'
> build of
> /gnu/store/vy3s1y7bv1w6d8gmp5b10xppy9skbgkd-guix-tools-0.1.0-2.4f17b79-checkout.drv
> failed
> View build log at
> '/var/log/guix/drvs/vy/3s1y7bv1w6d8gmp5b10xppy9skbgkd-guix-tools-0.1.0-2.4f17b79-checkout.drv.bz2'.
> cannot build derivation
> `/gnu/store/iwma3gq778n32mqz6y7277g67nvx1abb-guix-tools-0.1.0-2.4f17b79.drv':
> 1 dependencies couldn't be built
> guix build: error: build failed: build of
> `/gnu/store/iwma3gq778n32mqz6y7277g67nvx1abb-guix-tools-0.1.0-2.4f17b79.drv'
> failed
>
>
> Is it intended that this build-failure detail is not shown? I suppose
> not. At least in a log it should be shown.
I suspect you’re running an “old” guix-daemon, aren’t you?
Could you try again with an up-to-date daemon (and client)? The code
that prints hash mismatch errors when talking to recent daemons is in
(guix status).
Thanks,
Ludo’.