All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Brulebois <cyril.brulebois@ariadnext.com>
To: openembedded-devel@lists.openembedded.org
Cc: gumstix-users@lists.sourceforge.net
Subject: Re: fakeroot 1.14.5 source is missing
Date: Sat, 30 Jul 2011 13:04:43 +0200	[thread overview]
Message-ID: <4E33E54B.2010304@ariadnext.com> (raw)
In-Reply-To: <201107301242.41215.schnitzeltony@gmx.de>

Hi,

Andreas Mueller <schnitzeltony@gmx.de> (30/07/2011):
> Hi guys,
> 
> I tried to build an image based on gumstix overo-2011 branch [1] but the sources 
> for fakeroot 1.14.5 can not be downloaded.
> 
> ERROR: fakeroot-native-1.14.5: 
> ftp://ftp.debian.org/debian/pool/main/f/fakeroot/fakeroot_1.14.5.orig.tar.bz2 
> cannot check archive integrity
> 
> In [2] I saw that it is it is not there ( anymore ? ).

pointing to packages which are in unstable or testing feels very wrong.
New versions can come up at any time in unstable, and (if some
constraints are satisfied), can move to testing and overwrite what was
there before. (But pointing to packages in stable would buy you several
years.)

If you need to point to such a package anyway, I'd suggest considering
snapshot.debian.org, which should retain all packages. For example:
  http://snapshot.debian.org/package/fakeroot/1.14.5-1/

http://snapshot.debian.org/archive/debian/20101205T211007Z/pool/main/f/fakeroot/fakeroot_1.14.5.orig.tar.bz2

As a consequence, the URL to the original tarball includes a date
(meaning “fakeroot as seen in Debian as of $date), but I guess that
won't cause any issue.

If you have more Debian-related questions, feel free to ask.

Cheers,
-- 
Cyril Brulebois
Support AriadNEXT
0 825 590 003



  reply	other threads:[~2011-07-30 11:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-30 10:42 fakeroot 1.14.5 source is missing Andreas Mueller
2011-07-30 11:04 ` Cyril Brulebois [this message]
2011-07-30 11:12 ` Andreas Mueller
2011-07-30 15:14   ` Tom Rini
2011-07-30 21:30     ` Khem Raj
2011-07-30 15:27   ` Koen Kooi

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=4E33E54B.2010304@ariadnext.com \
    --to=cyril.brulebois@ariadnext.com \
    --cc=gumstix-users@lists.sourceforge.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.