From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0003374]: download path for lockfile-progs_0.1.11.tar.gz invalid
Date: Tue, 20 May 2008 02:42:51 -0700 [thread overview]
Message-ID: <403abc707a9e00fd21dc119626f2ac57@busybox.net> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=3374
======================================================================
Reported By: sgleissner
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 3374
Category: Architecture Specific
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 05-20-2008 02:42 PDT
Last Modified: 05-20-2008 02:42 PDT
======================================================================
Summary: download path for lockfile-progs_0.1.11.tar.gz
invalid
Description:
(buildroot version 20080519)
When running "make" for buildroot, the make process can not download the
file lockfile-progs_0.1.11.tar.gz from
http://ftp.debian.org/debian/pool/main/l/lockfile-progs/lockfile-progs_0.1.11.tar.gz
and the build process stops. On the debian server, the file is no longer
available.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
05-20-08 02:42 sgleissner New Issue
05-20-08 02:42 sgleissner Status new => assigned
05-20-08 02:42 sgleissner Assigned To => buildroot
======================================================================
reply other threads:[~2008-05-20 9:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=403abc707a9e00fd21dc119626f2ac57@busybox.net \
--to=bugs@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