From: Maxime Devos <maximedevos@telenet.be>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 53326@debbugs.gnu.org
Subject: bug#53326: snap: Fails to build (hash mismatch)
Date: Thu, 20 Jan 2022 19:37:54 +0100 [thread overview]
Message-ID: <e1df8e9940d7d9c52b2186839a809e6315a35f4c.camel@telenet.be> (raw)
In-Reply-To: <87o849fadb.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
Nicolas Goaziou schreef op di 18-01-2022 om 14:21 [+0100]:
> Hello,
>
> Maxime Devos <maximedevos@telenet.be> writes:
>
> > Since 'snap' has a history of mutating tags in-place, maybe it would
> > would be a good idea to replace (string-append "v" version) with the
> > actual commit string (and not a tag name), to avoid future breakage
> > and help "guix time-machine" users?
>
> AFAIK, this is the first time it happens for this project. I'd rather
> keep tags for now and revisit that decision if it happens again.
>
> WDYT?
Personally, I would change to commits after the first time it happens,
to avoid having to keep count.
Anyway, I asked upstream <https://github.com/jmoenig/Snap/issues/2966>
whether this will happen again. Let's wait for a response?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-01-20 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 20:13 bug#53326: snap: Fails to build (hash mismatch) Ivan Vilata i Balaguer
2022-01-17 23:41 ` Nicolas Goaziou
2022-01-18 8:02 ` Maxime Devos
[not found] ` <87o849fadb.fsf@nicolasgoaziou.fr>
2022-01-20 18:37 ` Maxime Devos [this message]
2022-01-20 23:10 ` Nicolas Goaziou
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=e1df8e9940d7d9c52b2186839a809e6315a35f4c.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=53326@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).