All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5846] New: Extra slash added to last slash in URL
Date: Fri,  4 Jan 2013 09:43:05 +0000 (UTC)	[thread overview]
Message-ID: <bug-5846-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=5846

           Summary: Extra slash added to last slash in URL
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: g at maral.me
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


This happens in 2012.11, I dunno about the older versions.

I noticed this with a few of my packages, but most recently with a custom
kernel tar file url.

For example, I have the following URL in my .config file:

BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="https://github.com/raspberrypi/linux/archive/rpi-3.6.y.tar.gz"

While make-ing, buildroot adds an extra slash to the URL and tries to download 
"https://github.com/raspberrypi/linux/archive//rpi-3.6.y.tar.gz" instead; this
results in an error (at least if the target server does some redirection
kung-fu like github does).

Example Output:

>>> linux custom Downloading
--2013-01-04 01:30:29-- 
https://github.com/raspberrypi/linux/archive//rpi-3.6.y.tar.gz
Resolving github.com... 207.97.227.239
Connecting to github.com|207.97.227.239|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://nodeload.github.com/raspberrypi/linux/tar.gz//rpi-3.6.y
[following]
--2013-01-04 01:30:30-- 
https://nodeload.github.com/raspberrypi/linux/tar.gz//rpi-3.6.y
Resolving nodeload.github.com... 207.97.227.252
Connecting to nodeload.github.com|207.97.227.252|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2013-01-04 01:30:30 ERROR 404: Not Found.

--2013-01-04 01:30:30--  http://sources.buildroot.net//rpi-3.6.y.tar.gz
Resolving sources.buildroot.net... 176.9.16.109
Connecting to sources.buildroot.net|176.9.16.109|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2013-01-04 01:30:31 ERROR 404: Not Found.

make: ***
[/home/gamaral/development/mm-buildroot/output/build/linux-custom/.stamp_downloaded]
Error 1

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2013-01-04  9:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04  9:43 bugzilla at busybox.net [this message]
2013-01-13 19:40 ` [Buildroot] [Bug 5846] Extra slash added to last slash in URL bugzilla at busybox.net

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=bug-5846-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.