All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Berger <gmane@reliableembeddedsystems.com>
To: poky@pokylinux.org
Subject: Re: No rootfs for beagleboard after bernard 5.0
Date: Fri, 13 May 2011 00:38:15 +0300	[thread overview]
Message-ID: <iqhk07$fpf$1@dough.gmane.org> (raw)
In-Reply-To: <1305192197.30391.490.camel@rex>

Hi Darren/Richard,

Thanks for the hints.
... but the problem is even more interesting.
For some strange reason I can't get a valid .tar.bz from the URL which
is in the recipe.

What helped was to grab it from somewhere else:

diff --git a/meta/recipes-devtools/distcc/distcc_2.18.3.bb
b/meta/recipes-devtools/distcc/distcc_2.18.3.bb
index b6b7b78..f5ae761 100644
--- a/meta/recipes-devtools/distcc/distcc_2.18.3.bb
+++ b/meta/recipes-devtools/distcc/distcc_2.18.3.bb
@@ -11,7 +11,7 @@ RRECOMMENDS_${PN} = "avahi-daemon"

 # Upstream change this patch periodically so store locally
 # http://0pointer.de/public/distcc-avahi.patch
-SRC_URI = "http://distcc.samba.org/ftp/distcc/distcc-${PV}.tar.bz2 \
+SRC_URI =
"ftp://ftp.slackware.at/slackware-10.2/source/d/distcc/distcc-${PV}.tar.bz2\
            file://distcc-avahi.patch;patch=1 \
           file://default \
           file://distccmon-gnome.desktop \

Regards,

Robert

..."Gott gebe mir die Gelassenheit, Dinge hinzunehmen, die ich nicht
ändern kann, den Mut, Dinge zu ändern, die ich ändern kann und die
Weisheit, das eine von dem anderen zu unterscheiden." (Friedrich
Christoph Oetinger 1702-1782)

My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1




  reply	other threads:[~2011-05-12 21:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 20:51 No rootfs for beagleboard after bernard 5.0 Robert Berger
2011-05-11 23:07 ` Darren Hart
2011-05-12  9:23   ` Richard Purdie
2011-05-12 21:38     ` Robert Berger [this message]
2011-05-12 21:44       ` Gary Thomas

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='iqhk07$fpf$1@dough.gmane.org' \
    --to=gmane@reliableembeddedsystems.com \
    --cc=poky@pokylinux.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.