Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
	 Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	 Richard Purdie <richard.purdie@linuxfoundation.org>,
	 "Burton, Ross" <ross.burton@intel.com>
Subject: Re: [URGENT] Daisy is broken
Date: Thu, 23 Oct 2014 11:30:55 -0700	[thread overview]
Message-ID: <5449495F.4030904@intel.com> (raw)
In-Reply-To: <CAP9ODKq2070AmmM9E4h+KWmnLM2k0H1uFG_VgD3Fg7EN2bM3BQ@mail.gmail.com>

On 10/23/2014 11:19 AM, Otavio Salvador wrote:
> Hello,
>
> Today some backports were done in Daisy. It seems it had no test
> before pushing the stuff to the Git repository as it fails with:
>
> ERROR: Function failed: Fetcher failure for URL:
> 'file://Makefiles-ptest.patch'. Unable to fetch URL from any source.
> ERROR: Logfile of failure stored in:
> .../build/tmp/work/x86_64-linux/openssl-native/1.0.1j-r0/temp/log.do_fetch.9860
>
> Looking at the commit it didn't remove the patches from source neither
> added the new ones. No test done before pushing to the official tree.
>
> Please fix it ASAP and be more careful next time, however pushed it.
>
This appears to be my fault, I asked RP to use the daisy-next branch 
this morning after I had completed some tests, what appears to have 
happened is I had not finished the push to what I asked RP to pull, 
found the "git push" sitting on a cmdline waiting for a Enter press!

I have pushed the correct set of patches into the daisy-next branch, 
which will await another round on the Autobuilder and/or RP's time to 
pull it to daisy.

Apologies to all for this.

Sau!



      reply	other threads:[~2014-10-23 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23 18:19 [URGENT] Daisy is broken Otavio Salvador
2014-10-23 18:30 ` Saul Wold [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=5449495F.4030904@intel.com \
    --to=saul.wold@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@intel.com \
    /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