From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14396] New: GIthub schema is broken
Date: Fri, 26 Nov 2021 15:13:58 +0000 [thread overview]
Message-ID: <bug-14396-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14396
Bug ID: 14396
Summary: GIthub schema is broken
Product: buildroot
Version: 2021.08.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: okitain@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
Github seems to have adopted a new schema for releases: instead of:
https://github.com/<user>/<project>/archive/<version>/<project>-<version>.tar.gz
it's now:
https://github.com/<user>/<project>/archive/refs/tags/<version>.tar.gz
which is then redirected to a location containing <project>-<version>.tar.gz.
This effectively breaks at least jsmn and gtest, but probably all github
packages.
Steps to reproduce:
1. Download a fresh Buildroot, e.g. the master branch.
2. make menuconfig and select gtest
3. In menuconfig: disable BR2_BACKUP_SITE
3. make source
This results in GTest download failing with error 404:
wget --passive-ftp -nd -t 3 -O
'/home/user/projects/buildroot/output/build/.gtest-1.11.0.tar.gz.FcavV0/output'
'https://github.com/google/googletest/archive/release-1.11.0/gtest-1.11.0.tar.gz'
--2021-11-26 18:12:27--
https://github.com/google/googletest/archive/release-1.11.0/gtest-1.11.0.tar.gz
Location:
https://codeload.github.com/google/googletest/tar.gz/release-1.11.0/gtest-1.11.0
[following]
--2021-11-26 18:12:27--
https://codeload.github.com/google/googletest/tar.gz/release-1.11.0/gtest-1.11.0
Connecting to proxy.elvees.com (proxy.elvees.com)|192.168.1.15|:3128...
connected.
Proxy request sent, awaiting response... 404 Not Found
2021-11-26 18:12:28 ERROR 404: Not Found.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2021-11-26 15:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 15:13 bugzilla [this message]
2021-11-27 12:03 ` [Buildroot] [Bug 14396] GIthub schema is broken bugzilla
2021-11-27 20:28 ` bugzilla
2021-11-27 21:12 ` bugzilla
2021-11-27 21:32 ` bugzilla
2021-11-27 21:54 ` bugzilla
2021-11-27 22:14 ` bugzilla
2021-11-28 8:39 ` bugzilla
2021-11-28 15:52 ` bugzilla
2021-11-28 16:28 ` bugzilla
2021-11-28 16:49 ` bugzilla
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-14396-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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