Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Packages that fail to be downloaded
Date: Wed, 1 Jan 2014 06:41:26 +0200	[thread overview]
Message-ID: <20140101044126.GF4263@tarshish> (raw)
In-Reply-To: <CAPFcPTJtoK3p0kseX-kQ7wNUyh5A+T7fwVETc89UcANmZZzJxw@mail.gmail.com>

Hi Mau,

On Tue, Dec 31, 2013 at 11:58:25PM +0200, Mau Z wrote:
> The following package downloads fail:
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >>> vim 699f8d8f096d Downloading
> Reason :   ERROR 404: Not Found.
> 
> >>> >>> python-nfc 142 Downloading
> Reason :   ERROR 404: Not Found.
> 
> >>> dvb-apps 83c746462ccb Downloading
> Reason :   ERROR 404: Not Found.

I had no problem downloading any of the above. Do you have Mercurial and Bzr 
installed on your system?

> >>> mxml 2.7 Downloading
> Reason :   Server does not answer......
> (http://ftp.easysw.com/pub/mxml/2.7/mxml-2.7.tar.gz)

This URL has changed in version 2013.08 (commit dc6d9070b). What version of 
Buildroot are you using?

> >>> xinetd 2.3.15 Downloading
> failed: Connection timed out.

www.xinetd.org is not responding here also. But automatic fall back to 
sources.buildroot.net works.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2014-01-01  4:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-31 21:58 [Buildroot] Packages that fail to be downloaded Mau Z
2014-01-01  4:41 ` Baruch Siach [this message]
2014-01-01 12:58   ` Mau Z
2014-01-01 13:06     ` Baruch Siach
2014-01-02  9:10   ` Thomas Petazzoni
2014-01-02 12:45     ` Thomas De Schampheleire

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=20140101044126.GF4263@tarshish \
    --to=baruch@tkos.co.il \
    --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