From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0002684]: Fakeroot 1.9 again
Date: Wed, 26 Mar 2008 06:25:35 -0700 [thread overview]
Message-ID: <ca9dd8b6d63d7eec85f22f0e5c6355f6@busybox.net> (raw)
A NOTE has been added to this issue.
======================================================================
http://busybox.net/bugs/view.php?id=2684
======================================================================
Reported By: Graol
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 2684
Category: Architecture Specific
Reproducibility: always
Severity: block
Priority: normal
Status: assigned
======================================================================
Date Submitted: 03-26-2008 03:45 PDT
Last Modified: 03-26-2008 06:25 PDT
======================================================================
Summary: Fakeroot 1.9 again
Description:
Fakeroot 1.9 has disappeared again from the official debian repository, and
the 1.9.3 version fails to compile (on architecture x86_64).
======================================================================
----------------------------------------------------------------------
hmoffatt - 03-26-08 06:08
----------------------------------------------------------------------
Please provide details of the failure, ie a log. It builds fine for me on
amd64.
----------------------------------------------------------------------
Graol - 03-26-08 06:20
----------------------------------------------------------------------
The server I used to work on not available anymore (reconfigured for
release). I forgot to save the log, but it said something like "applying a
patch to fakeroot 1.9.3... Trunk failure 1 on 1 etc... ## trunk failures in
##".
Despite modifying the /etc/apt/sources.list, a make still got the fakeroot
package from the official debian repo instead of snapshot.debian.net
----------------------------------------------------------------------
hmoffatt - 03-26-08 06:25
----------------------------------------------------------------------
buildroot doesn't use your /etc/apt/sources.list - it fetches the source
directly using wget. If yours didn't go to snapshot.debian.net then it
isn't up to date.
Issue History
Date Modified Username Field Change
======================================================================
03-26-08 03:45 Graol New Issue
03-26-08 03:45 Graol Status new => assigned
03-26-08 03:45 Graol Assigned To => buildroot
03-26-08 06:08 hmoffatt Note Added: 0005994
03-26-08 06:20 Graol Note Added: 0006004
03-26-08 06:25 hmoffatt Note Added: 0006014
======================================================================
next reply other threads:[~2008-03-26 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 13:25 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-27 22:44 [Buildroot] [buildroot 0002684]: Fakeroot 1.9 again bugs at busybox.net
2008-03-27 15:37 bugs at busybox.net
2008-03-26 21:20 bugs at busybox.net
2008-03-26 13:56 bugs at busybox.net
2008-03-26 13:20 bugs at busybox.net
2008-03-26 13:08 bugs at busybox.net
2008-03-26 10:45 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=ca9dd8b6d63d7eec85f22f0e5c6355f6@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