Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Arnout Vandecappelle <arnout@rnout.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH/next 2/4] package/matchbox-fakekey: switch to gz tarball
Date: Wed,  7 Jan 2026 18:48:20 +0100	[thread overview]
Message-ID: <20260107174820.224342-1-arnout@rnout.be> (raw)
In-Reply-To: <20251205190034.1839192-2-bernd@kuhls.net>

In reply of:
> Switched _SOURCE to .gz, upstream does not provide bz2 tarballs anymore.
> 
> No autobuild errors recorded due to previous download error with
> matchbox-lib.
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Applied to 2025.02.x and 2025.11.x. Thanks

> ---
>  package/matchbox-fakekey/matchbox-fakekey.hash | 2 +-
>  package/matchbox-fakekey/matchbox-fakekey.mk   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/package/matchbox-fakekey/matchbox-fakekey.hash b/package/matchbox-fakekey/matchbox-fakekey.hash
> index 3627b13913..03fcfef6d3 100644
> --- a/package/matchbox-fakekey/matchbox-fakekey.hash
> +++ b/package/matchbox-fakekey/matchbox-fakekey.hash
> @@ -1,3 +1,3 @@
>  # Locally computed
> -sha256  4e2fdc9bc20df469d53885c40e104122140131e06d4c184902070ec0b0f2ca9f  libfakekey-0.3.tar.bz2
> +sha256  d282fa6481a5b85f71e36e8bad4cfa938cc8eaac4c42ffa27f9203ac634813f4  libfakekey-0.3.tar.gz
>  sha256  3271662131760e9b30dd92495a0ea0b598fc457798cc67948947365299dd607d  src/libfakekey.c
> diff --git a/package/matchbox-fakekey/matchbox-fakekey.mk b/package/matchbox-fakekey/matchbox-fakekey.mk
> index 99921ef8e7..4f32cd9378 100644
> --- a/package/matchbox-fakekey/matchbox-fakekey.mk
> +++ b/package/matchbox-fakekey/matchbox-fakekey.mk
> @@ -5,7 +5,7 @@
>  ################################################################################
>  
>  MATCHBOX_FAKEKEY_VERSION = 0.3
> -MATCHBOX_FAKEKEY_SOURCE = libfakekey-$(MATCHBOX_FAKEKEY_VERSION).tar.bz2
> +MATCHBOX_FAKEKEY_SOURCE = libfakekey-$(MATCHBOX_FAKEKEY_VERSION).tar.gz
>  MATCHBOX_FAKEKEY_SITE = \
>  	http://git.yoctoproject.org/cgit/cgit.cgi/libfakekey/snapshot
>  MATCHBOX_FAKEKEY_LICENSE = GPL-2.0+
> -- 
> 2.47.3
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-01-07 17:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05 19:00 [Buildroot] [PATCH/next 1/4] package/matchbox-lib: bump version to 1.14 Bernd Kuhls
2025-12-05 19:00 ` [Buildroot] [PATCH/next 2/4] package/matchbox-fakekey: switch to gz tarball Bernd Kuhls
2026-01-07 17:48   ` Arnout Vandecappelle via buildroot [this message]
2025-12-05 19:00 ` [Buildroot] [PATCH/next 3/4] package/matchbox-keyboard: " Bernd Kuhls
2026-01-07 17:48   ` Arnout Vandecappelle via buildroot
2025-12-05 19:00 ` [Buildroot] [PATCH/next 4/4] package/matchbox-panel: fix build Bernd Kuhls
2026-01-07 17:48   ` Arnout Vandecappelle via buildroot
2025-12-27 23:17 ` [Buildroot] [PATCH/next 1/4] package/matchbox-lib: bump version to 1.14 Thomas Petazzoni 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=20260107174820.224342-1-arnout@rnout.be \
    --to=buildroot@buildroot.org \
    --cc=arnout@rnout.be \
    --cc=bernd@kuhls.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox