From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Andrei Gherzan <andrei@gherzan.com>,
openembedded <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [dunfell][PATCH 1/2] bitbake: fetch2: fix handling of `\` in file:// SRC_URI
Date: Tue, 31 Aug 2021 14:03:36 +0100 [thread overview]
Message-ID: <78fde0d5a1bb9b74efd8da33a9cf8d7949df6ccd.camel@linuxfoundation.org> (raw)
In-Reply-To: <b052a428-da00-4a55-9027-65828171b1f6@www.fastmail.com>
On Tue, 2021-08-31 at 13:45 +0100, Andrei Gherzan wrote:
> Hey,
>
> On Tue, 24 Aug 2021, at 16:25, Andrei Gherzan wrote:
> > On Tue, 24 Aug 2021, at 15:24, Richard Purdie wrote:
> > > On Tue, 2021-08-24 at 04:20 -1000, Steve Sakoman wrote:
> > > > On Mon, Aug 23, 2021 at 3:53 AM Andrei Gherzan <andrei@gherzan.com> wrote:
> > > > >
> > > > > From: Leif Middelschulte <leif.middelschulte@klsmartin.com>
> > > > >
> > > > > Using backslashes in file:// URIs was broken.
> > > > > Either the resolver would fail or the subsequent `cp` command.
> > > > > Try to avoid this by putting the filenames into quotes.
> > > > >
> > > > > Fixes https://bugzilla.yoctoproject.org/show_bug.cgi?id=8161
> > > > >
> > > > > (Bitbake rev: aa857fa2e9cf3b0e43a9049b04ec4b0b3c779b11)
> > > >
> > > > Patches for bitbake should be sent to: bitbake-devel@lists.openembedded.org
> > > >
> > > > I tried applying this patch, but found that it caused errors on the autobuilder:
> > > >
> > > > https://errors.yoctoproject.org/Errors/Build/129189/
> > > >
> > >
> > > We dropped wildcard support in master but that is still present in dunfell. That
> > > means we can't quote things as we are relying on expansion of the wildcards for
> > > some SRC_URIs. This could be difficult to fix with the compatibility constraints
> > > of an older release funfortunately :/.
> >
> > Got it now. That's going to be painful indeed. I can't think of an easy
> > way out of this either.
>
> Can you guys think of a way forward with this? Or shall we just drop it and consider it unsupported?
The only idea I had was to see if wildcards were in the name and only quote it
if not. I'm not sure we ever have had backslashes working though so it has
always been unsupported until the fix in master afaict.
Cheers,
Richard
prev parent reply other threads:[~2021-08-31 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 13:52 [dunfell][PATCH 1/2] bitbake: fetch2: fix handling of `\` in file:// SRC_URI Andrei Gherzan
2021-08-23 13:52 ` [dunfell][PATCH 2/2] Use the label provided when formating a dos partition Andrei Gherzan
2021-08-24 14:20 ` [OE-core] [dunfell][PATCH 1/2] bitbake: fetch2: fix handling of `\` in file:// SRC_URI Steve Sakoman
2021-08-24 14:24 ` Richard Purdie
2021-08-24 15:25 ` Andrei Gherzan
[not found] ` <169E47906AF45A5C.6361@lists.openembedded.org>
2021-08-31 12:45 ` Andrei Gherzan
2021-08-31 13:03 ` Richard Purdie [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=78fde0d5a1bb9b74efd8da33a9cf8d7949df6ccd.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=andrei@gherzan.com \
--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