Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] BUGREPORT: fakeroot version 1.9.6
Date: Mon, 01 Dec 2008 10:09:05 +0100	[thread overview]
Message-ID: <87k5akfej2.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <347d9b1b0811291152j89fbf69l55053f78054da2d5@mail.gmail.com> (Alexander Voropay's message of "Sat\, 29 Nov 2008 22\:52\:54 +0300")

>>>>> "Alexander" == Alexander Voropay <alec@sensi.org> writes:

Hi,

 Alexander> There is no such version on the fakeroot page:

 Alexander> http://ftp.debian.org/debian/pool/main/f/fakeroot/

 Alexander> Can anyone correct this ?

Yes, I've fixed it in r24200 to use the stable links to
snapshot.debian.net instead.

 Alexander> P.S. There is fakeroot-ng and most distributives use it.

 Alexander> http://sourceforge.net/projects/fakerootng

Ahh, that looks interesting - I'll take a look.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2008-12-01  9:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-29 19:52 [Buildroot] BUGREPORT: fakeroot version 1.9.6 Alexander Voropay
2008-12-01  9:09 ` Peter Korsgaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-01  4:44 Allen
2008-12-01  9:10 ` Peter Korsgaard

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=87k5akfej2.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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