unofficial mirror of 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <>
To: Vishakh Kumar <>
Subject: bug#56091: Possible hash mismatch in barrier 2.4.0
Date: Sun, 19 Jun 2022 17:28:53 +0200	[thread overview]
Message-ID: <87v8sw3bws@nckx> (raw)
In-Reply-To: <>

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


Thanks for reporting this.

Vishakh Kumar 写道:
> I think this is a case where the hash in the package description
> might be wrong?

What usually (though, mercifully, rarely) happens is that the hash 
is correct at the time of packaging, then upstream goes and moves 
a perfectly good git tag instead of making a new one, and the hash 
becomes wrong in retrospect.

This case was different: the original packager correctly ran ‘guix 
hash -rx .’ on their clone of the barrier git repository, but did 
not first check out the submodules and was unaware that these 
affect the hash.  I don't think the original package ever built, 
or at least fail to see how it could have.

Fixed on master[0].

Closing, but could you guix pull & confirm that it works for you?

Kind regards,



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

      reply	other threads:[~2022-06-19 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-19  6:25 bug#56091: Possible hash mismatch in barrier 2.4.0 Vishakh Kumar
2022-06-19 15:28 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]

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:

  List information:

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

  git send-email \
    --in-reply-to=87v8sw3bws@nckx \ \ \ \ \ \

* 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

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).