From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-12-28
Date: Mon, 31 Dec 2018 00:01:24 +0100 [thread overview]
Message-ID: <87tviusjp7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <87o994vweq.fsf@tkos.co.il> (Baruch Siach's message of "Sat, 29 Dec 2018 23:46:21 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> Hi Peter,
> Thomas Petazzoni writes:
>> m68k | whois-5.3.2 | NOK |
>> http://autobuild.buildroot.net/results/c139030e8383027dc679cfc59feddad426919900
>> |
> This is a transient issue with the snapshot.debian.org server. However,
> the sources.buildroot.net fallback doesn't work either:
> --2018-12-27 19:51:56-- http://sources.buildroot.net/whois/whois_5.3.2.tar.xz
> Resolving sources.buildroot.net
> (sources.buildroot.net)... 104.25.211.19, 104.25.210.19,
> 2606:4700:20::6819:d213, ...
> Connecting to sources.buildroot.net (sources.buildroot.net)|104.25.211.19|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2018-12-27 19:51:56 ERROR 404: Not Found.
> And indeed the whois tarball is not there even though version 5.3.2 is
> in Buildroot since July, and is included in the 2018.11 release. What
> went wrong?
I'm not quite sure. I have explicitly added the 2018.11.x branch to the
list of branches to run 'make source' on and manually triggered a run,
and the file is now there.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-12-30 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-12-28 Thomas Petazzoni
2018-12-29 21:46 ` Baruch Siach
2018-12-30 23:01 ` Peter Korsgaard [this message]
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=87tviusjp7.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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