From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9796] New: source-check broken for Github downloads
Date: Fri, 07 Apr 2017 09:37:18 +0000 [thread overview]
Message-ID: <bug-9796-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9796
Bug ID: 9796
Summary: source-check broken for Github downloads
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: thomas.petazzoni at free-electrons.com
CC: buildroot at uclibc.org
Target Milestone: ---
source-check doesn't work for Github downloads it seems, see for example the
Linux kernel download for the raspberrypi_defconfig:
$ make raspberrypi_defconfig
$ make source-check
[...]
Spider mode enabled. Check if remote file exists.
--2017-04-07 08:00:27--
https://github.com/raspberrypi/linux.git/linux-935c7ce84c982a26f567a03a58a1537424569938.tar.gz
Resolving github.com (github.com)... 192.30.253.112, 192.30.253.113
Connecting to github.com (github.com)|192.30.253.112|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
Remote file does not exist -- broken link!!!
Spider mode enabled. Check if remote file exists.
--2017-04-07 08:00:27--
http://sources.buildroot.net/linux-935c7ce84c982a26f567a03a58a1537424569938.tar.gz
Resolving sources.buildroot.net (sources.buildroot.net)... 176.9.16.109
Connecting to sources.buildroot.net (sources.buildroot.net)|176.9.16.109|:80...
connected.
HTTP request sent, awaiting response... 404 Not Found
Remote file does not exist -- broken link!!!
Some source-check fails because the kernel is not available. But in practice,
if you do a build, it can download the kernel perfectly fine:
$ make linux-extract
>>> linux 935c7ce84c982a26f567a03a58a1537424569938 Downloading
Doing full clone
Cloning into 'linux-935c7ce84c982a26f567a03a58a1537424569938'...
remote: Counting objects: 5514757, done.
remote: Compressing objects: 100% (4789/4789), done.
remote: Total 5514757 (delta 3516), reused 11 (delta 11), pack-reused 5509948
Receiving objects: 100% (5514757/5514757), 1.55 GiB | 12.32 MiB/s, done.
Resolving deltas: 100% (4579570/4579570), done.
Checking connectivity... done.
Checking out files: 100% (56709/56709), done.
warning: refname '935c7ce84c982a26f567a03a58a1537424569938' is ambiguous.
Git normally never creates a ref that ends with 40 hex characters
because it will be ignored when you just specify 40-hex. These refs
may be created by mistake. For example,
git checkout -b $br $(git rev-parse ...)
where "$br" is somehow empty and a 40-hex ref is created. Please
examine these refs and maybe delete them. Turn this message off by
running "git config advice.objectNameWarning false"
>>> linux 935c7ce84c982a26f567a03a58a1537424569938 Extracting
gzip -d -c
/home/thomas/buildroot/dl/linux-935c7ce84c982a26f567a03a58a1537424569938.tar.gz
| tar --strip-components=1 -C
/home/thomas/buildroot/buildroot/output/build/linux-935c7ce84c982a26f567a03a58a1537424569938
-xf -
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-04-07 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 9:37 bugzilla at busybox.net [this message]
2017-04-08 8:28 ` [Buildroot] [Bug 9796] source-check broken for Github downloads bugzilla at busybox.net
2017-04-08 8:30 ` [Buildroot] [Bug 9796] source-check broken for Git downloads bugzilla at busybox.net
2017-04-08 8:35 ` bugzilla at busybox.net
2017-05-10 20:04 ` bugzilla at busybox.net
2017-05-10 21:39 ` bugzilla at busybox.net
2017-05-12 15:55 ` bugzilla at busybox.net
2017-05-13 13:13 ` 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-9796-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox