From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/rp-pppoe: update tarball URL
Date: Fri, 16 Jan 2026 22:26:53 +0100 [thread overview]
Message-ID: <aWqs4r1FGNf5CH_L@windsurf> (raw)
In-Reply-To: <20260114173925.1877799-1-bernd@kuhls.net>
On Wed, Jan 14, 2026 at 06:39:25PM +0100, Bernd Kuhls wrote:
> The project moved its repo to codeberg.org:
> https://dianne.skoll.ca/pipermail/rp-pppoe/2025q3/000663.html
>
> Updated tarball hash after verifying that no files changed, only the
> directory name changed from rp-pppoe-4.0/ to rp-pppoe/
>
> Fixes:
> https://autobuild.buildroot.net/results/5ff/5fff21a4150a5f668d43830591e21b660299ed9d/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Applied, thanks!
> -sha256 17d45712778f2bf6b0859ff610a3dacd24bc4462e9f53bb1466d47af391701d3 rp-pppoe-4.0.tar.gz
> +sha256 459904065fd4a70c927757d84cc7b4ef70946a707fa1b83f16246f925158b13e 4.0.tar.gz
It would have been nice to find a solution that allowed to have a
better tarball name, but I couldn't find a quick solution, so I
applied as-is. And anyway, having a different tarball name is needed
to not have clashes on the hash value.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-01-16 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 17:39 [Buildroot] [PATCH 1/1] package/rp-pppoe: update tarball URL Bernd Kuhls
2026-01-16 21:26 ` Thomas Petazzoni via buildroot [this message]
2026-01-28 17:24 ` Arnout Vandecappelle 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=aWqs4r1FGNf5CH_L@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=thomas.petazzoni@bootlin.com \
/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.