From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <georgi.georgiev@woodward.com>
Cc: <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Yocto [thud], [zeus] do_fetch and do_unpack failures with offline/online svn build! #yocto #python
Date: Mon, 17 Feb 2020 13:47:18 +0000 [thread overview]
Message-ID: <20200217134718.GT104502@korppu> (raw)
In-Reply-To: <0704a68acba44839865cb31e22e584db@Kemp-ExMb1.woodward.com>
On Mon, Feb 17, 2020 at 01:35:02PM +0000, Georgi Georgiev via Lists.Yoctoproject.Org wrote:
> Hi Mikko,
> Your patch is upstreamed and...It is actually released. If you see the error output you will see your codeline. I decided to try with your old version but the result is the same. Can you say something for the previous issue I have about offline build.
> It seem svn is not very well supported by yocto.
Ah, indeed.
svn is supported and for me it's working quite well. It has some issues
like download cache locking when multiple recipes include the same URLs.
Where possible, I've switched to using http fetcher with tar balls and large
binary blobs in svn, but there one needs to remember to include version
details into file names...
-Mikko
next prev parent reply other threads:[~2020-02-17 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 12:56 [yocto] Yocto [thud], [zeus] do_fetch and do_unpack failures with offline/online svn build! #yocto #python Georgi Georgiev
2020-02-17 13:03 ` Mikko Rapeli
2020-02-17 13:35 ` Georgi Georgiev
2020-02-17 13:47 ` Mikko Rapeli [this message]
2020-02-18 7:25 ` Georgi Georgiev
2020-02-18 9:00 ` Mikko Rapeli
-- strict thread matches above, loose matches on Subject: below --
2020-02-05 16:57 Georgi Georgiev
2020-01-31 12:02 georgi.georgiev
2020-01-31 12:13 ` [yocto] " Mikko Rapeli
2020-01-31 18:33 ` Khem Raj
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=20200217134718.GT104502@korppu \
--to=mikko.rapeli@bmw.de \
--cc=georgi.georgiev@woodward.com \
--cc=yocto@lists.yoctoproject.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.