all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 50809-done@debbugs.gnu.org
Subject: bug#50809: tla2tools fails to build
Date: Mon, 27 Sep 2021 14:26:29 +0200	[thread overview]
Message-ID: <8735pqqgf9.fsf@nckx> (raw)
In-Reply-To: <87czowyo8h.fsf@gmail.com>

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

Andrew,

Thanks for reporting this!  Fixed in Guix commit 86d316b.

> I tried the obvious fix of putting in the correct hash

Obvious maybe, but not much of a fix, as you discovered: what 
mishappened to change the hash in the first place?  Anything bad? 
Would it happen again next week?

> expected hash: 
> 1hhx8gmn81k8qrkx4p7ppinmygxga9fqffd626wkvhjgg2ky8lhs

This hash corresponds to tlaplus commit 6932e19.

> actual hash: 
> 0xqp2ayn3knmdcs5h1sb70rf1adirg2i4igl0y2r0mlx4wwlma2h

This hash corresponds to tlaplus commit 875bf8f.

> Given that the current tag v1.8.0 is from 2021-09-14 while ~git 
> blame~ says that tla2tools hasn't been touched since 2021-04-15, 
> something weird is definitely going on.

Upstream has moved the v1.8.0 ‘tag’ by *eighty-seven* commits! 
Probably more.  Why??  Are they nihilistic hellraisers?  Probably 
not: according to [0]
1.8.0 is not a proper release.  Oops.  Let's give them the benefit 
of the doubt.

If it still moves after the release, and if I don't forget, I'll 
file a bug.

Closing this one,

T G-R

[0]: https://github.com/tlaplus/tlaplus/releases/

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

      reply	other threads:[~2021-09-27 13:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26  4:02 bug#50809: tla2tools fails to build Andrew Patterson
2021-09-27 12:26 ` 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=8735pqqgf9.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=50809-done@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.