Re: Guix build output insufficient

[Ricardo Wurmus <rekado@elephly.net>]

Hi Pjotr,

> On latest
>
>   ./pre-inst guix package -i something
>
> The new color scheme is nice for output. But I miss the old build
> logs. How do I get them back?

The build logs are stored by the daemon.  You can get their location by
doing

    guix build --log-file something

Note also that “guix build something” still has the same behaviour as
before.  If you want “guix package” to print build logs you need to pass
“--verbose”.

I realize that ’--verbose’ and ’--verbosity=LEVEL’ appear to collide.
We should remove the latter because all it changes is the daemon
verbosity, which isn’t very helpful in most cases.

> Also when I got the hash wrong I did not display the new hash value.
> And -K does not show the tmp location. E.g.
>
>   ./pre-inst-env guix package -p ~/opt/gdc -i gdc --substitute-urls="https://berlin.guixsd.org  https://mirror.hydra.gnu.org" -K
>  (...)
>
>   Build failed: /gnu/store/85salmra99rwz6ifpmswvd9kc5cl69gv-gdc-7a5dbd1.drv - 1 r:sha256 hash mismatch for output path `/gnu/store/wk3sm5krg5srrdivfsjvsz5snd2nqipg-gdc-7a5dbd1'
>   expected: 0i0yrcpqrbghq1ddp2zbqq4anl3z5l9fp9b7kblf40642pbdg49d
>   actual:
>   -guix package: error: build failed: build of `/gnu/store/wp5wr8f4xnc69amc1g8mfb7ypipx5gz0-gdc-v2.082.0-rc.1.drv' failed

Yes, this looks like a bug.  Not sure why this happens.  Thanks for
reporting it.

--
Ricardo