All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Müller" <schnitzeltony@gmx.de>
To: "Patches and discussions about the oe-core layer"
	<openembedded-core@lists.openembedded.org>
Subject: Re: dropbear build build fails
Date: Thu, 1 Sep 2011 23:00:08 +0200	[thread overview]
Message-ID: <201109012300.08901.schnitzeltony@gmx.de> (raw)
In-Reply-To: <201109012227.49280.schnitzeltony@gmx.de>

On Thursday, September 01, 2011 10:27:49 PM Andreas Müller wrote:
> Hi
> 
> build after fresh git pull & fresh tmpdir fails for dropbear:
> 
> NOTE: package dropbear-0.52-r3: task do_fetch: Started
> ERROR: Function 'Fetcher failure for URL: 'file://dropbear-configuration-
> file.patch'. Unable to fetch URL file://dropbear-configuration-file.patch
> from any source.' failed
> ERROR: Logfile of failure stored in: /home/Superandy/tmp/oe-core-
> eglibc/work/armv7a-angstrom-linux-gnueabi/dropbear-0.52-
> r3/temp/log.do_fetch.12169
> 
> Log data follows:
> | DEBUG: Trying PREMIRRORS
> | DEBUG: Trying Upstream
> | ERROR: Function 'Fetcher failure for URL: 'file://dropbear-configuration-
> 
> file.patch'. Unable to fetch URL file://dropbear-configuration-file.patch
> from any source.' failed
> NOTE: package dropbear-0.52-r3: task do_fetch: Failed
> 
> There was a change yesterday
> 
> commit 48dcb8fc7b669b27160dde33079f40551853702b
> Author: Xiaofeng Yan <xiaofeng.yan@windriver.com>
> Date:   Wed Aug 31 10:48:11 2011 +0800
> 
>     dropbear: Change the path to find configuration file and add a
> configuration file for dropbear
> ...
> 
> In folder dropbear-0.52 is a file configure.patch. Is that a typo or is it
> me?
> 
It looks that file://dropbear-configuration-file.patch is simply missing. How about 
an INC_PR to save from further quiet breaks?

Andreas



      reply	other threads:[~2011-09-01 21:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01 20:27 dropbear build build fails Andreas Müller
2011-09-01 21:00 ` Andreas Müller [this message]

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=201109012300.08901.schnitzeltony@gmx.de \
    --to=schnitzeltony@gmx.de \
    --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 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.