From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] knock: Fix build failure due to missing README file.
Date: Mon, 16 Dec 2013 16:55:01 +0100 [thread overview]
Message-ID: <871u1cssdm.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <52AF2051.7080806@imgtec.com> (Vicente Olivert Riera's message of "Mon, 16 Dec 2013 15:46:25 +0000")
>>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes:
Hi,
> But you need to mirror it first. The version we have right know works
> because you have this tarball in the buildroot mirrors:
> http://sources.buildroot.net//knock-7666f2e86e18d482eaad5fe1fea46d87d80b0555.tar.gz
> If you try to get that file from git, it fails with:
>>>> knock 7666f2e86e18d482eaad5fe1fea46d87d80b0555 Downloading
> --2013-12-16 15:40:52--
> https://github.com/jvinet/7666f2e86e18d482eaad5fe1fea46d87d80b0555/tarball/knock-7666f2e86e18d482eaad5fe1fea46d87d80b0555.tar.gz
> Resolving github.com... 192.30.252.130
> Connecting to github.com|192.30.252.130|:443... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2013-12-16 15:40:53 ERROR 404: Not Found.
> So, in order to bump the version you need to put the new tarball in
> the mirrors first.
Ahh, I somehow dropped the project name ('knock') from the github macro
when I fixed the revision.
Sorry about that, fixed in git.
> --
> Vincent
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-12-16 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 12:26 [Buildroot] [PATCH v3] knock: Fix build failure due to missing README file Vicente Olivert Riera
2013-12-12 14:27 ` Peter Korsgaard
2013-12-12 22:29 ` Arnout Vandecappelle
2013-12-12 22:50 ` Peter Korsgaard
2013-12-13 9:33 ` Vicente Olivert Riera
2013-12-13 9:58 ` Peter Korsgaard
2013-12-16 14:39 ` Vicente Olivert Riera
2013-12-16 15:14 ` Peter Korsgaard
2013-12-16 15:46 ` Vicente Olivert Riera
2013-12-16 15:50 ` Vicente Olivert Riera
2013-12-16 15:55 ` Peter Korsgaard [this message]
2013-12-16 16:38 ` Vicente Olivert Riera
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=871u1cssdm.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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