From: Thomas Huth <huth@tuxfamily.org>
To: "J. Neuschäfer" <j.neuschaefer@gmx.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/frotz: update package hash for verion 2.54
Date: Sun, 25 Aug 2024 07:49:40 +0200 [thread overview]
Message-ID: <20240825074940.6de3b82b@fedora> (raw)
In-Reply-To: <20240824-frotz-v1-1-05b86b9e6038@gmx.net>
Am Sat, 24 Aug 2024 23:11:29 +0200
schrieb J. Neuschäfer <j.neuschaefer@gmx.net>:
> Recently, hash checks have been failing for frotz-2.54.tar.bz2.
> Fortunately, the old version can still be downloaded from
> sources.buildroot.org:
>
> $ wget -q https://sources.buildroot.net/frotz/frotz-2.54.tar.bz2
> $ sha256sum frotz-2.54.tar.bz2
> bdf9131e6de49108c9f032200cea3cb4011e5ca0c9fbdbf5b0c05f7c56c81395 frotz-2.54.tar.bz2
>
> Diffing the old and current unpacked tarballs shows that the change is benign
> and appears to be due to a change in GitLab's tarball generation:
>
> diff -ru frotz-2.54/Makefile frotz-2.54-new/Makefile
> --- frotz-2.54/Makefile 2022-04-14 08:47:41.000000000 +0200
> +++ frotz-2.54-new/Makefile 2022-04-14 08:47:41.000000000 +0200
> @@ -261,7 +261,7 @@
> GIT_DATE = $(shell git show -s --format=%ci)
> else
> GIT_HASH = 5a86de2f0799bde12699a0189ea12be8c96194a5
> -GIT_HASH_SHORT = 5a86de2
> +GIT_HASH_SHORT = 5a86de2f
> GIT_DATE = 2022-04-13 23:47:41 -0700
> endif
> export CFLAGS
Hi!
Thanks for your investigation! But since likely nobody beside me was using
this package, and I also don't need it anymore, I already suggested another
way of "fixing" this problem:
https://gitlab.com/buildroot.org/buildroot/-/commit/ed2d440a08aba129a737705b2ac4231d
Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-25 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 21:11 [Buildroot] [PATCH] package/frotz: update package hash for verion 2.54 J. Neuschäfer via buildroot
2024-08-25 5:49 ` Thomas Huth [this message]
2024-08-25 13:43 ` J. Neuschäfer via buildroot
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=20240825074940.6de3b82b@fedora \
--to=huth@tuxfamily.org \
--cc=buildroot@buildroot.org \
--cc=j.neuschaefer@gmx.net \
/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.