From: Philippe De Swert <philippedeswert@scarlet.be>
To: openembedded-devel@openembedded.org
Subject: Re: SVN fetcher behaviour
Date: Fri, 05 Oct 2007 19:22:24 +0300 [thread overview]
Message-ID: <1191601344.17230.22.camel@localhost.localdomain> (raw)
In-Reply-To: <F38DEABE0E171746B133C1ABBD142D97071112B2@radmail.Radstone.Local>
Hello all,
On Thu, 2007-10-04 at 11:57 +0100, Martyn Welch wrote:
> It is failing to download gconf-dbus using "gconf-dbus_svn.bb". It seems
> that the script does not specify a revision and it therefore trying to
> download revision 1. This fails.
>
> I have managed to get the script to continue buy hacking the script to
> get it to download the current revision (608), by adding "rev=608" to
> the SRC_URI.
I ran into a similar problem recently and it seems you need to edit
../org.openembedded.dev/conf/distro/include/sane-srcdates.inc or make
sure it is included in your distro.
> I've looked at
> http://www.openembedded.org/user-manual&dpage=src_uri_variable, which
> (under "SVN") describes the behaviour of the svn fetcher. This doesn't
> seem to specify what the default behaviour of the svn fetcher is when no
> revision is specified, I'd assumed it would be the "head", though I am
> now having some doubt.
I think this should be the default behaviour, unfortunately it is not.
The expected behaviour is fetch the latest revision and build it but it
dies not. I think ib general it is a great improvement for managing svn
revisions, but it sucks at building the latest and newest.
Cheers,
Philippe
next prev parent reply other threads:[~2007-10-05 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 10:57 SVN fetcher behaviour Martyn Welch
2007-10-04 11:27 ` Koen Kooi
2007-10-05 16:22 ` Philippe De Swert [this message]
2007-10-05 17:02 ` Hans Henry von Tresckow
2007-10-05 19:56 ` Leon Woestenberg
2007-10-05 20:40 ` Hans Henry von Tresckow
2007-10-08 8:25 ` Richard Purdie
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=1191601344.17230.22.camel@localhost.localdomain \
--to=philippedeswert@scarlet.be \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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