From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dl-wrapper: Fix urlencode option never being sent to backend
Date: Mon, 10 Dec 2018 17:50:54 +0100 [thread overview]
Message-ID: <20181210165054.GH3383@scaer> (raw)
In-Reply-To: <671b136857f0b184e19f2f5452c1e764766bf912.camel@vitec.com>
Damien, All,
On 2018-12-10 08:03 +0000, Damien Th?bault spake thusly:
> On Fri, 2018-12-07 at 18:35 +0100, Yann E. MORIN wrote:
> > On 2018-12-07 12:41 +0000, Damien Th?bault spake thusly:
> > > The urlencode parameter is lost in dl-wrapper, because we try to
> > > get it
> > > from backend instead of backend_urlencode.
> > >
> > > We must get the urlencode information from backend_urlencode.
> >
> > What is this trying to fix, actually? We have no download issue in
> > the autobuilders, as far as I can see... Do you have a test-case to
> > share?
> I have a build configured with a primary site and
> BR2_PRIMARY_SITE_ONLY=y that failed to download libopenssl patches from
> the mirror.
OK, makes sense, thanks for the feedback. :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-12-10 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 12:41 [Buildroot] [PATCH] dl-wrapper: Fix urlencode option never being sent to backend Damien Thébault
2018-12-07 17:35 ` Yann E. MORIN
2018-12-10 8:03 ` Damien Thébault
2018-12-10 8:13 ` Thomas Petazzoni
2018-12-10 16:50 ` Yann E. MORIN [this message]
2018-12-09 16:18 ` Thomas Petazzoni
2018-12-16 19:46 ` 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=20181210165054.GH3383@scaer \
--to=yann.morin.1998@free.fr \
--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