Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: current error: fetching enlightenment
Date: Thu, 13 May 2010 14:23:24 +0200	[thread overview]
Message-ID: <20100513122324.GL3370@jama> (raw)
In-Reply-To: <alpine.DEB.2.00.1005130808100.8347@lynx>

On Thu, May 13, 2010 at 08:09:03AM -0400, Robert P. J. Day wrote:
> 
>   not to sound naggy but any proposed fix for this?
> 
> On Wed, 12 May 2010, Robert P. J. Day wrote:
> 
> >
> >   just did a "git pull" followed by a bitbake fetchall and ...
> >
> > ...
> > NOTE: Update
> > svn://svn.enlightenment.org/svn/e/trunk;module=e;proto=http
> > svn: Failed to add directory 'src': an unversioned directory of the
> > same name already exists
> > NOTE: Task failed: Fetch failed: Fetch command export
> > HOME=/home/rpjday; export SSH_AUTH_SOCK=/tmp/keyring-Ll3M8v/ssh;
> > export
> > PATH=/home/rpjday/oe/angstrom-dev/sysroots/x86_64-linux/usr/bin/armv7a-angstrom-linux-gnueabi:/home/rpjday/oe/angstrom-dev/sysroots/x86_64-linux/usr/bin/armv7a-angstrom-linux-gnueabi:/home/rpjday/oe/angstrom-dev/sysroots/x86_64-linux/usr/sbin:/home/rpjday/oe/angstrom-dev/sysroots/x86_64-linux/usr/bin:/home/rpjday/oe/angstrom-dev/cross/armv7a//bin:/home/rpjday/oe/angstrom-dev/sysroots/x86_64-linux/sbin:/home/rpjday/oe/angstrom-dev/sysroots/x86_64-linux/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games;
> > /usr/bin/env svn update -r 48775 failed with signal 1, output:
> > svn: Failed to add directory 'src': an unversioned directory of the
> > same name already exists

cd /OE/downloads/svn/svn.enlightenment.org/
svn stat to check why do you have unversioned src dir here
or just remove this dir and download again

> >
> > ERROR: TaskFailed event exception, aborting
> > ERROR: Build of /home/rpjday/oe/openembedded/recipes/e17/e-wm_svn.bb
> > do_fetch failed
> > ERROR: Task 439 (/home/rpjday/oe/openembedded/recipes/e17/e-wm_svn.bb,
> > do_fetch) failed
> > NOTE: Tasks Summary: Attempted 1331 tasks of which 1331 didn't need to
> > be rerun and 1 failed.
> > ERROR: '/home/rpjday/oe/openembedded/recipes/e17/e-wm_svn.bb' failed
> 
> rday
> 
> -- 
> 
> ========================================================================
> Robert P. J. Day                               Waterloo, Ontario, CANADA
> 
>             Linux Consulting, Training and Kernel Pedantry.
> 
> Web page:                                          http://crashcourse.ca
> Twitter:                                       http://twitter.com/rpjday
> ========================================================================
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-- 
uin:136542059                jid:Martin.Jansa@gmail.com
Jansa Martin                 sip:jamasip@voip.wengo.fr 
JaMa                         



      reply	other threads:[~2010-05-13 12:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13  0:31 current error: fetching enlightenment Robert P. J. Day
2010-05-13 12:09 ` Robert P. J. Day
2010-05-13 12:23   ` Martin Jansa [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=20100513122324.GL3370@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@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