From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: proper way to report fetch failure?
Date: Thu, 26 Jul 2012 07:20:41 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1207260717280.8530@oneiric> (raw)
to stock up on tarballs, i just ran:
$ bitbake -c fetchall world
and got:
NOTE: package kbd-1.15.2-r3: task do_fetch: Started
WARNING: Failed to fetch URL
http://kernel.org/pub/linux/utils/kbd/kbd-1.15.2.tar.bz2, attempting
MIRRORS if available
...
and, sure enough, that current tarball is not at that location:
http://kernel.org/pub/linux/utils/kbd/
is there a proper way to report this?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2012-07-26 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 11:20 Robert P. J. Day [this message]
2012-07-26 13:29 ` proper way to report fetch failure? Richard Purdie
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=alpine.DEB.2.02.1207260717280.8530@oneiric \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox