GNU bug report logs - #50809
tla2tools fails to build

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Tobias Geerinckx-Rice <me <at> tobias.gr>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#50809: closed (tla2tools fails to build)
Date: Mon, 27 Sep 2021 13:48:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Mon, 27 Sep 2021 14:26:29 +0200
with message-id <8735pqqgf9.fsf <at> nckx>
and subject line Re: tla2tools fails to build
has caused the debbugs.gnu.org bug report #50809,
regarding tla2tools fails to build
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
50809: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=50809
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Andrew Patterson <andrewpatt7 <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: tla2tools fails to build
Date: Sun, 26 Sep 2021 00:02:29 -0400

[Message part 3 (text/plain, inline)]

tla2tools fails to build with a hash mismatch:

[log-tla2tools-1.8.0-current (text/plain, attachment)]

[Message part 5 (text/plain, inline)]

I tried the obvious fix of putting in the correct hash, but then 
it failed with a patch failure:

[log-tla2tools-1.8.0-correct-hash (text/plain, attachment)]

[Message part 7 (text/plain, inline)]

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.  I could continue to try 
and hack this into working, but I don't know how I would make sure 
this doesn't happen again, and I would prefer if whoever wrote 
this originally (apparently Mike Gerwitz or Ludovic Courtès?) 
could at least help.

-- 
Andrew Patterson

[Message part 8 (message/rfc822, inline)]

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: 50809-done <at> debbugs.gnu.org
Subject: Re: tla2tools fails to build
Date: Mon, 27 Sep 2021 14:26:29 +0200

[Message part 9 (text/plain, inline)]

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/

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.