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 9371] New: openssl: download failes with "Only allow downloads from primary download site" + local server
Date: Thu, 20 Oct 2016 09:49:29 +0000	[thread overview]
Message-ID: <bug-9371-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 9371
           Summary: openssl: download failes with "Only allow downloads
                    from primary download site" + local server
           Product: buildroot
           Version: 2016.08
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: johanderycke at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

We have " Only allow downloads from primary download site" enabled and have a
local webserver with all needed packages on it.
For openssl some patches are added to "OPENSSL_PATCH" (eg.
https://gitweb.gentoo.org/repo/gentoo.git/plain/dev-libs/openssl/files/openssl-1.0.2d-parallel-build.patch?id=c8abcbe8de5d3b6cdd68c162f398c011ff6e2d9d)

Our server has this file available but wget fails because of the "?" in the
name.

Any suggestions on a working workaround?

Best regards,

Johan

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2016-10-20  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20  9:49 bugzilla at busybox.net [this message]
2016-10-21 20:30 ` [Buildroot] [Bug 9371] openssl: download failes with "Only allow downloads from primary download site" + local server bugzilla at busybox.net
2016-10-23 12:55 ` 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-9371-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.