Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Samuel Martin <s.martin49@gmail.com>,
	linux-amarula@amarulasolutions.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/2] package/armadillo: temporarily update the site URL
Date: Tue, 3 Sep 2024 22:10:13 +0200	[thread overview]
Message-ID: <20240903221013.3e5d61af@windsurf> (raw)
In-Reply-To: <20240901064509.3505801-1-dario.binacchi@amarulasolutions.com>

On Sun,  1 Sep 2024 08:45:08 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:

> Following an email exchange with Conrad Sand, one of the maintainers of
> the project, I learned that version 9.900.2 has been moved to
> https://sourceforge.net/projects/arma/files/retired/.
> 
> This patch fixes the package download error, waiting for a subsequent
> patch that will restore the previous URL to bump to a more recent
> version.
> 
> Adding the .RETIRED suffix to the downloaded tarball generated the
> following error:
> 
> armadillo-9.900.2.tar.xz.RETIRED: OK (sha256: d78658c9442addf7f718eb05881150ee3ec25604d06dd3af4942422b3ce26d05)
> >>> armadillo 9.900.2 Extracting  
> buildroot/dl/armadillo/armadillo-9.900.2.tar.xz.RETIRED | buildroot/output/host/bin/tar --strip-components=1 -C buildroot/output/build/armadillo-9.900.2   -xf -
> /bin/bash: line 1: buildroot/dl/armadillo/armadillo-9.900.2.tar.xz.RETIRED: Permission denied
> buildroot/output/host/bin/tar: This does not look like a tar archive
> buildroot/output/host/bin/tar: Exiting with failure status due to previous errors
> make[1]: *** [package/pkg-generic.mk:213: buildroot/output/build/armadillo-9.900.2/.stamp_extracted] Error 2
> 
> which required the addition of ARMADILLO_EXTRACT_CMDS to be fixed.
> 
> Finally, it was also necessary to modify the tarball's hash.
> 
> Fixes:
> - http://autobuild.buildroot.org/results/d4e9e7b453960a4f62a199344b30b729a4f235bc
> 
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
> Changes v1 -> v2:
>   - Don't bump to 10.1.0 but update the URL site to continue to download and
>     build the current version (e. g. 9.900.2).

Thanks, series applied to master:

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2024-09-03 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-01  6:45 [Buildroot] [PATCH v2 1/2] package/armadillo: temporarily update the site URL Dario Binacchi
2024-09-01  6:45 ` [Buildroot] [PATCH v2 2/2] DEVELOPERS: add Dario Binacchi for armadillo Dario Binacchi
2024-09-18 20:29   ` Peter Korsgaard
2024-09-03 20:10 ` Thomas Petazzoni via buildroot [this message]
2024-09-18 20:29 ` [Buildroot] [PATCH v2 1/2] package/armadillo: temporarily update the site URL Peter Korsgaard

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=20240903221013.3e5d61af@windsurf \
    --to=buildroot@buildroot.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=s.martin49@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox