From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/check: don; t conflict with release archive
Date: Fri, 25 Aug 2023 09:07:46 +0200 [thread overview]
Message-ID: <87ledzd2gt.fsf@48ers.dk> (raw)
In-Reply-To: <20230824212810.4166630-1-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Thu, 24 Aug 2023 23:28:10 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> In commit ee93213d18bc (package/check: fix compile issue due to missing
> source file), we switched from using the released tarball, to using the
> autogenerated tarball from github.
> However, that means that the filename of the archive did not change,
> while its content did change. The hash was promptly updated, but that
> means that the archive we cachec on s.b.o (and possibly the one users
> may also already have locally) will not match the new hash (and
> conversely).
> So we switch to using the sha1-hash of the commit conrresponding to the
> tag.
> Reported-by: Peter Korsgaard <peter@korsgaard.com>
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> Cc: Waldemar Brodkorb <wbx@openadk.org>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-25 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 21:28 [Buildroot] [PATCH] package/check: don; t conflict with release archive Yann E. MORIN
2023-08-25 7:07 ` Peter Korsgaard [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=87ledzd2gt.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.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.
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.