unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Luke Dashjr <luke@dashjr.org>
Cc: 55273@debbugs.gnu.org
Subject: bug#55273: failed to compute the derivation for Guix (version: "b80ca672de936a76368de6e6ea0b28505e74d420"; system: "x86_64-linux";
Date: Fri, 06 May 2022 22:14:26 +0200	[thread overview]
Message-ID: <bec0a1f8bbb102dba367f2af4cea266a7dc52c7e.camel@telenet.be> (raw)
In-Reply-To: <f72f8a56bd046073b58540e0875afaec7a27b6c2.camel@telenet.be>

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

retitle 55273 guile-git is irreproducible and libgit2 fails to build
thanks

Maxime Devos schreef op vr 06-05-2022 om 21:40 [+0200]:
> I can't reproduce locally.

Looking further, it appears to be libgit2@1.3.0 (a dependency of guile-
git) that fails to build:

$ guix build libgit2 --check -c8 --no-grafts
> [...]
> refs::reflog::messages..............
> refs::reflog::reflog..................
> refs::rename...........
> refs::revparse.................F
> 
>   1) Failure:
> refs::revparse::date [/tmp/guix-build-libgit2-1.3.0.drv-
> 0/source/tests/refs/revparse.c:31]
>   Function call succeeded: error
>   no error, expected non-zero return
> 
> error: in phase 'check': uncaught exception:
> %exception #<&invoke-error program: "./libgit2_clar" arguments: ("-v"
> "-Q") exit-status: 1 term-signal: #f stop-signal: #f> 
> phase `check' failed after 42.3 seconds
> command "./libgit2_clar" "-v" "-Q" failed with status 1
> builder for `/gnu/store/r6b9r9bx0k0yhgsf23689n404cyv7xkm-libgit2-
> 1.3.0.drv' failed with exit code 1
> de bouw van /gnu/store/r6b9r9bx0k0yhgsf23689n404cyv7xkm-libgit2-
> 1.3.0.drv mislukte
> Bekijk de bouwlog op
> '/var/log/guix/drvs/r6/b9r9bx0k0yhgsf23689n404cyv7xkm-libgit2-
> 1.3.0.drv.gz'.
> guix build: fout: build of
> `/gnu/store/r6b9r9bx0k0yhgsf23689n404cyv7xkm-libgit2-1.3.0.drv'
> failed

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-05-06 20:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 13:33 bug#55273: failed to compute the derivation for Guix (version: "b80ca672de936a76368de6e6ea0b28505e74d420"; system: "x86_64-linux"; Luke Dashjr
2022-05-06 17:57 ` Maxime Devos
2022-05-06 17:58   ` Maxime Devos
2022-05-06 18:49     ` Luke Dashjr
2022-05-06 19:40       ` Maxime Devos
2022-05-06 20:14         ` Maxime Devos [this message]
2022-05-06 20:23           ` Maxime Devos
2022-05-07 23:42         ` Luke Dashjr
2022-05-06 18:09   ` Maxime Devos
2022-05-06 18:23     ` bug#55273: guile-git@0.5.2 (irreproducibly?) fails to build and output is non-deterministic Maxime Devos
2022-07-12 14:08       ` bug#55273: guile-git is not reproducible Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bec0a1f8bbb102dba367f2af4cea266a7dc52c7e.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=55273@debbugs.gnu.org \
    --cc=luke@dashjr.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).