From: jemy.zhang at gmail.com <jemy.zhang@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/1] download url broken if url include '+'
Date: Tue, 5 Nov 2019 17:04:47 +0800 [thread overview]
Message-ID: <20191105090448.99235-1-jemy.zhang@gmail.com> (raw)
From: "Jemy Zhang" <jemy.zhang@gmail.com>
While downloading pacakges, the `SITE_METHOD` will be prefixed to the download url of the main package, but the extra download url would not be. If the `SITE URL` accidentally includes '+', url link before '+' would be parsed as `SITE METHOD` by dl-wrapper, and the url broken.
Take `android-tools` package for example:
```
ANDROID_TOOLS_SITE = https://launchpad.net/ubuntu/+archive/primary/+files
ANDROID_TOOLS_EXTRA_DOWNLOADS = android-tools_$(ANDROID_TOOLS_VERSION)-3ubuntu41.debian.tar.gz
```
while build the android-tools package, `ALL_DOWNLOADS` will be expended as:
```
for p in https+https://launchpad.net/ubuntu/+archive/primary/+files/android-tools_4.2.2+git20130218.orig.tar.xz https://launchpad.ne
t/ubuntu/+archive/primary/+files/android-tools_4.2.2+git20130218-3ubuntu41.debian.tar.gz; do \
if test ! -e /mnt/fileroot/jun.zhang/buildroot-git/buildroot/dl/android-tools/`basename $p` ; then \
echo ">>> android-tools 4.2.2+git20130218 Downloading" ; \
break ; \
fi ; \
done
```
Notice that there's no 'https+' prefixed to the url, `SITE_METHOD` missing.
and while downloading package, url corrupted:
>--2019-11-05 14:10:29-- http://archive/primary/+files/android-tools_4.2.2+git20130218-3ubuntu41.debian.tar.gz
Jemy Zhang (1):
fix corrupted download url of extra packages
package/pkg-generic.mk | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
2.22.0
next reply other threads:[~2019-11-05 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 9:04 jemy.zhang at gmail.com [this message]
2019-11-05 9:04 ` [Buildroot] [PATCH 1/1] fix corrupted download url of extra packages jemy.zhang at gmail.com
2019-11-08 17:28 ` Yann E. MORIN
2019-11-08 22:26 ` jemy zhang
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=20191105090448.99235-1-jemy.zhang@gmail.com \
--to=jemy.zhang@gmail.com \
--cc=buildroot@busybox.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