From: Peter Korsgaard <peter@korsgaard.com>
To: Romain Naour via buildroot <buildroot@buildroot.org>
Cc: Romain Naour <romain.naour@smile.fr>
Subject: Re: [Buildroot] [PATCH] package/checksec: fix download
Date: Wed, 20 Nov 2024 21:59:56 +0100 [thread overview]
Message-ID: <87h681tycz.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20241030212700.2517051-1-romain.naour@smile.fr> (Romain Naour via buildroot's message of "Wed, 30 Oct 2024 22:27:00 +0100")
>>>>> "Romain" == Romain Naour via buildroot <buildroot@buildroot.org> writes:
> checksec-2.7.1.tar.gz archive was replaced or regenerated by upstream
> sometime between the 22 September 2024 [1] and the 29 September 2024
> [2].
> diffoscope report no changes in extracted files exept a different
> top directory name (checksec.sh-2.7.1/checksec-2.7.1):
> --- checksec-2.7.1.tar.gz a0d7a444d4603fb3d62fa25ef678e544ef39fa7b3c9bd5d22f1a8c526152cdde
> +++ checksec-2.7.1.tar.gz eba0616f4033385d6093608a2a2aad3c2debb847d6778c87346f89c80946684f
> Files identical despite different names
> --- checksec-2.7.1/ChangeLog
> +++ checksec.sh-2.7.1/ChangeLog
> Use the git hash of the 2.7.1 release to use a different archive name
> than the checksec-2.7.1.tar.gz archive previously released.
> [1] https://gitlab.com/buildroot.org/buildroot/-/jobs/7888799855
> [2] https://gitlab.com/buildroot.org/buildroot/-/jobs/7948006849
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/7948006849
> Signed-off-by: Romain Naour <romain.naour@smile.fr>
Committed to 2024.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-11-20 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 21:27 [Buildroot] [PATCH] package/checksec: fix download Romain Naour via buildroot
2024-10-31 12:51 ` Thomas Petazzoni via buildroot
2024-11-20 20:59 ` 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=87h681tycz.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=romain.naour@smile.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.