From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001819]: buildroot 20071226 tries to fetch non-existant fakeroot
Date: Thu, 27 Dec 2007 00:35:06 -0800 [thread overview]
Message-ID: <e50c5e7384d81283b7d42e51151872bf@busybox.net> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=1819
======================================================================
Reported By: alexking
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1819
Category: Other
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
======================================================================
Date Submitted: 12-27-2007 00:35 PST
Last Modified: 12-27-2007 00:35 PST
======================================================================
Summary: buildroot 20071226 tries to fetch non-existant
fakeroot
Description:
While trying to build a system with buildroot, it tries to fetch fakeroot
1.8.2, which is not a current version and isn't available in the Debian
mirrors.
1.5.10 is in etch, and 1.8.10 is current in testing/unstable.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
12-27-07 00:35 alexking New Issue
12-27-07 00:35 alexking Status new => assigned
12-27-07 00:35 alexking Assigned To => buildroot
======================================================================
next reply other threads:[~2007-12-27 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 8:35 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-12-27 8:49 [Buildroot] [buildroot 0001819]: buildroot 20071226 tries to fetch non-existant fakeroot bugs at busybox.net
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=e50c5e7384d81283b7d42e51151872bf@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