From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Sasha Shashkevich <alex@stunpix.com>,
bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH v2] bb/fetch2: fixes copying of file://dir; subdir=foo, bug 6128 and bug 6129
Date: Wed, 09 Mar 2016 22:42:06 +0000 [thread overview]
Message-ID: <1457563326.2804.192.camel@linuxfoundation.org> (raw)
In-Reply-To: <48D48E72-F0D1-4705-BDB2-ED59E44F0354@stunpix.com>
On Wed, 2016-03-09 at 18:54 +0200, Sasha Shashkevich wrote:
> > On Mar 9, 2016, at 18:15, Alexander Shashkevich <alex@stunpix.com>
> > wrote:
> >
> > When in SRC_URI appears file://dir;subdir=foo unpacker copies 'dir'
> > to ${WORKDIR}, not
> > ${WORKDIR}/foo as it should be.
> >
> > These changes are fixing following bugs as well:
> > Bug 6128 - Incorrect wildcard unpack behaviour in fetcher
> > Bug 6129 - Local directories unpack to a different location than
> > local files
> >
> > Signed-off-by: Alexander Shashkevich <alex@stunpix.com>
> > --
>
> Changes were tested on 1.8 and 2.0 branches for core-image-sato and
> meta-sdk images.
>
> Additional changes since last sent patch:
>
> - New test cases were added to cover absolute paths in SRC_URI for
> local files.
> - Fixed recipe nativesdk-qemu-helper_1.0.bb: it was based on
> incorrect copying behavior which had been changed by this patch.
>
> Please review my changes.
Could you have a look at master please? I already took one of your
earlier patches which I followed with a changes to correctly handle
absolute paths:
http://git.yoctoproject.org/cgit.cgi/poky/commit/bitbake/lib?id=2a73181
33bbd64f5dcb2ddf400229d4627925580
I wasn't convinced the behaviour in the qemu-helper recipe was
incorrect. If you still believe it is, I'm happy to consider that.
I'm also very interested in getting some updated test cases in.
Cheers,
Richard
next prev parent reply other threads:[~2016-03-09 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 16:15 [PATCH v2] bb/fetch2: fixes copying of file://dir; subdir=foo, bug 6128 and bug 6129 Alexander Shashkevich
2016-03-09 16:54 ` Sasha Shashkevich
2016-03-09 22:42 ` Richard Purdie [this message]
2016-03-10 14:30 ` Sasha Shashkevich
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=1457563326.2804.192.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex@stunpix.com \
--cc=bitbake-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 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.