Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: jiaying.song.cn@windriver.com, openembedded-devel@lists.openembedded.org
Cc: changqing.li@windriver.com
Subject: Re: [PATCH][meta-oe][scarthgap] xmlsec1: fix do_fetch error
Date: Fri, 18 Oct 2024 09:34:45 -0700	[thread overview]
Message-ID: <b83eb7f4-63e8-47b4-982c-4fbf6ffabb43@gmail.com> (raw)
In-Reply-To: <20241018061416.2483243-1-jiaying.song.cn@windriver.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 1545 bytes --]

On 10/17/24 11:14 PM, jiaying.song.cn@windriver.com wrote:
> From: Jiaying Song <jiaying.song.cn@windriver.com>
> 
> Change the SRC_URI to the correct value due to the following error:
> 
> WARNING: xmlsec1-native-1.3.4-r0 do_fetch: Failed to fetch URL http://www.aleksey.com/xmlsec/download/xmlsec1-1.3.4.tar.gz, attempting MIRRORS if available
> 


I have sent a patch [1] which switches SRC_URI to use github releases
which should avoid these issues and should be backport worthy, please 
look into that patch and test it out on scarthgap

[1] 
https://lore.kernel.org/openembedded-devel/20241018162512.3304078-1-raj.khem@gmail.com/T/#u

> Signed-off-by: Jiaying Song <jiaying.song.cn@windriver.com>
> ---
>   meta-oe/recipes-support/xmlsec1/xmlsec1_1.3.4.bb | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta-oe/recipes-support/xmlsec1/xmlsec1_1.3.4.bb b/meta-oe/recipes-support/xmlsec1/xmlsec1_1.3.4.bb
> index 7639209e19..a3e66c96df 100644
> --- a/meta-oe/recipes-support/xmlsec1/xmlsec1_1.3.4.bb
> +++ b/meta-oe/recipes-support/xmlsec1/xmlsec1_1.3.4.bb
> @@ -12,7 +12,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=352791d62092ea8104f085042de7f4d0"
>   
>   SECTION = "libs"
>   
> -SRC_URI = "http://www.aleksey.com/xmlsec/download/${BP}.tar.gz \
> +SRC_URI = "https://www.aleksey.com/xmlsec/download/older-releases/${BP}.tar.gz \
>              file://fix-ltmain.sh.patch \
>              file://change-finding-path-of-nss.patch \
>              file://makefile-ptest.patch \

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2613 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]

      reply	other threads:[~2024-10-18 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18  6:14 [PATCH][meta-oe][scarthgap] xmlsec1: fix do_fetch error jiaying.song.cn
2024-10-18 16:34 ` Khem Raj [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=b83eb7f4-63e8-47b4-982c-4fbf6ffabb43@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=changqing.li@windriver.com \
    --cc=jiaying.song.cn@windriver.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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