From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] seatd: Update URL and hash.
Date: Fri, 31 Mar 2023 10:40:59 +0200 [thread overview]
Message-ID: <ZCacm7MVKdnnHPa+@pengutronix.de> (raw)
In-Reply-To: <21b19ed7-9f0e-4319-8125-0ec2cf1f50bc@t2data.com>
On Fri, Mar 24, 2023 at 06:44:00PM +0100, Christian Melki wrote:
> On 3/24/23 07:51, Michael Olbrich wrote:
> > On Fri, Mar 24, 2023 at 07:47:10AM +0100, Michael Olbrich wrote:
> >> On Thu, Mar 23, 2023 at 09:04:48PM +0100, Christian Melki wrote:
> >>> For unknown reasons, seatd tarball changed it's hash for
> >>> the same version. Fortunately, I had an old copy of seatd
> >>> and could compare. No differences noted (please double check).
> >>> I chalk this down to a rebuild of tarballs or something.
> >>> Anyway. I changed URL to the github mirror just in case.
> >>> Also, hopefully less fidgety with the tarballs.
> >>>
> >>> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> >>> ---
> >>> rules/seatd.make | 4 ++--
> >>> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>>
> >>> diff --git a/rules/seatd.make b/rules/seatd.make
> >>> index 64876313a..5df69ac91 100644
> >>> --- a/rules/seatd.make
> >>> +++ b/rules/seatd.make
> >>> @@ -16,10 +16,10 @@ PACKAGES-$(PTXCONF_SEATD) += seatd
> >>> # Paths and names
> >>> #
> >>> SEATD_VERSION := 0.7.0
> >>> -SEATD_MD5 := 922b8a4ca4dfdb1f43a294db9e77bcf7
> >>> +SEATD_MD5 := a326424b2fccf8d6ae630063ba735aa1
> >>
> >> Please add the new hash (space separated list). This way either hash is
> >> accepted. This helps those with the old file in their local cache.
> >>
> >>> SEATD := seatd-$(SEATD_VERSION)
> >>> SEATD_SUFFIX := tar.gz
> >>> -SEATD_URL := https://git.sr.ht/~kennylevinsen/seatd/archive/$(SEATD_VERSION).$(SEATD_SUFFIX)
> >>> +SEATD_URL := https://github.com/kennylevinsen/seatd/archive/refs/tags/$(SEATD_VERSION).$(SEATD_SUFFIX)
> >
> > Oh, and git.sr.ht is the official upstream. So I'd like to keep that URL.
> > Any reason for the change?
> >
> > Michael
> >
>
> None other than I don't like release tarballs that change hashes for no
> apparent reason. Much like buildroot triggered mitm attack warnings, so
> did my brain. :)
>
> If github reverts their gzip changes and git.sr.ht picks it up, then
> we'd be back to the original hash again. gleh.
>
> I think just drop this. Now that I know the real cause behind hash
> changes, I'm much less inclined to change anything.
I've added the new hash to SEATD_MD5. Now both tarballs work.
Michael
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2023-03-31 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 20:04 Christian Melki
2023-03-24 6:47 ` Michael Olbrich
2023-03-24 6:51 ` Michael Olbrich
2023-03-24 17:44 ` Christian Melki
2023-03-31 8:40 ` Michael Olbrich [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=ZCacm7MVKdnnHPa+@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox