From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 3451] New: fakeroot package: wrong FAKEROOT_SITE variable
Date: Wed, 9 Mar 2011 12:10:30 +0000 (UTC) [thread overview]
Message-ID: <bug-3451-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=3451
Summary: fakeroot package: wrong FAKEROOT_SITE variable
Product: buildroot
Version: 2010.11
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Outdated package
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: hector.oron at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Hello,
FAKEROOT_SITE points to the wrong URL within buildroot fakeroot package.
The following patch fixes this issue:
diff -Naur buildroot-2010.11/package/fakeroot//fakeroot.mk
buildroot-2010.11.fix/package/fakeroot//fakeroot.mk
--- buildroot-2010.11/package/fakeroot//fakeroot.mk 2010-11-30
15:52:43.000000000 +0000
+++ buildroot-2010.11.fix/package/fakeroot//fakeroot.mk 2011-03-09
12:01:14.636006340 +0000
@@ -5,7 +5,7 @@
#############################################################
FAKEROOT_VERSION:=1.9.5
FAKEROOT_SOURCE:=fakeroot_$(FAKEROOT_VERSION).tar.gz
-FAKEROOT_SITE:=http://snapshot.debian.net/archive/2008/04/27/debian/pool/main/f/fakeroot/
+FAKEROOT_SITE:=http://snapshot.debian.org/archive/debian/20080427T000000Z/pool/main/f/fakeroot/
FAKEROOT_LIBTOOL_PATCH=NO
define FAKEROOT_PATCH_FAKEROOT_IN
Cheers,
-- Hector Oron
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-03-09 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 12:10 bugzilla at busybox.net [this message]
2011-03-13 20:30 ` [Buildroot] [Bug 3451] fakeroot package: wrong FAKEROOT_SITE variable bugzilla 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=bug-3451-163@https.bugs.busybox.net/ \
--to=bugzilla@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