All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: gconf-dbus fetch failure
Date: Fri, 24 Jun 2011 12:20:25 +0100	[thread overview]
Message-ID: <1308914425.20015.155.camel@rex> (raw)
In-Reply-To: <4E043FEF.8080107@linux.intel.com>

On Fri, 2011-06-24 at 00:42 -0700, Darren Hart wrote:
> It seems there is a problem with the subversion repository for gconf-dbus. Are others seeing this as well, or this perhaps a local networking issue?
> 
> ERROR: Logfile of failure stored in: /build/poky/timeline/qemux86/tmp/work/x86_64-linux/gconf-dbus-native-2.16.0+svnr705-r0/temp/log.do_fetch.19184
> Log data follows:
> | NOTE: Fetch svn://developer.imendio.com/svn/gconf-dbus;module=trunk;proto=http
> | NOTE: Fetch svn://developer.imendio.com/svn/gconf-dbus;module=trunk;proto=http
> | svn: OPTIONS of 'http://developer.imendio.com/svn/gconf-dbus/trunk': could not connect to server (http://developer.imendio.com)
> |  ERROR: Function 'Fetcher failure for URL: 'svn://developer.imendio.com/svn/gconf-dbus;module=trunk;proto=http'. Unable to fetch URL svn://developer.imendio.com/svn/gconf-dbus;module=trunk;proto=http from any source.' failed
> 

Its a known issue and we are currently relying on the mirror to provide
this file. We have a plan to get this addressed (drop gconf-dbus in
favour of gconf).

Cheers,

Richard




  reply	other threads:[~2011-06-24 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24  7:42 gconf-dbus fetch failure Darren Hart
2011-06-24 11:20 ` Richard Purdie [this message]
2011-06-27 13:05 ` Phil Blundell
2011-06-27 13:08   ` 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=1308914425.20015.155.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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.