unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: zimoun <zimon.toutoune@gmail.com>, 47293@debbugs.gnu.org
Subject: bug#47293: Failure of “guix lint -c archival icecat”
Date: Sun, 21 Mar 2021 15:39:11 -0400	[thread overview]
Message-ID: <878s6gl2it.fsf@netris.org> (raw)
In-Reply-To: <868s6gvb49.fsf@gmail.com>

zimoun <zimon.toutoune@gmail.com> writes:
> Indeed, there is a bug.  Because the source of ’icecat’ raises a case
> that is not handled by ’check-archival’ in (guix lint).
>
> Basically in the snippet:
>
> --8<---------------cut here---------------start------------->8---
>                  (match (lookup-content (content-hash-value hash)
>                                         (symbol->string
>                                          (content-hash-algorithm hash)))
> --8<---------------cut here---------------end--------------->8---
>
> ’lookup-content’ expect a bytevector for ’content-hash’ and in the case
> of ’icecat’, it returns #f.  Then raises the backtrace.

Icecat uses an unusual thing called a "computed origin", which means
that its source is itself built from other sources.  The only two places
in Guix where this is currently done is 'icecat' and 'linux-libre'.

See 'computed-origin-method' and 'icecat-source' in
gnu/packages/gnuzilla.scm, and 'computed-origin-method' and
'make-linux-libre-source' in gnu/packages/linux.scm.

       Mark




  reply	other threads:[~2021-03-21 19:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <86sg4puzra.fsf@gmail.com>
2021-03-21 14:05 ` bug#47293: guix lint -c archival icecat fails Luis Felipe via Bug reports for GNU Guix
2021-03-21 14:23   ` bug#47293: Failure of “guix lint -c archival icecat” zimoun
2021-03-21 19:39     ` Mark H Weaver [this message]
2021-03-25 23:25   ` bug#47293: guix lint -c archival icecat fails Ludovic Courtès

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=878s6gl2it.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=47293@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).