From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: gconf-dbus fetch failure
Date: Mon, 27 Jun 2011 14:05:40 +0100 [thread overview]
Message-ID: <1309179940.21613.299.camel@phil-desktop> (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?
Yeah, gconf-dbus is apparently stored in git nowadays.
The patch in
http://lists.linuxtogo.org/pipermail/openembedded-core/2011-June/004074.html
looks like it would probably fix this issue but doesn't seem to have
been applied.
p.
next prev parent reply other threads:[~2011-06-27 13:09 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
2011-06-27 13:05 ` Phil Blundell [this message]
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=1309179940.21613.299.camel@phil-desktop \
--to=pb@pbcl.net \
--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