From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] cdrtools-native: Don't set uid/gid during install
Date: Wed, 13 Nov 2019 21:28:01 +0000 [thread overview]
Message-ID: <b7cf9efa-6caf-c2f2-40ff-e84205f6e4ea@intel.com> (raw)
In-Reply-To: <20191112223119.47941-2-paul@betafive.co.uk>
On 12/11/2019 22:31, Paul Barker wrote:
> +++ b/meta/recipes-devtools/cdrtools/cdrtools-native/0001-Don-t-set-uid-gid-during-install.patch
ERROR: cdrtools-native-3.01a31+really3.01-r0 do_fetch: Fetcher failure:
Unable to find file file://0001-Don-t-set-uid-gid-during-install.patch
anywhere. The paths that were searched were:
/home/ross/Yocto/poky/meta/recipes-devtools/cdrtools/cdrtools-3.01a31+really3.01/poky
/home/ross/Yocto/poky/meta/recipes-devtools/cdrtools/cdrtools/poky
/home/ross/Yocto/poky/meta/recipes-devtools/cdrtools/files/poky
/home/ross/Yocto/poky/meta/recipes-devtools/cdrtools/cdrtools-3.01a31+really3.01/
/home/ross/Yocto/poky/meta/recipes-devtools/cdrtools/cdrtools/
/home/ross/Yocto/poky/meta/recipes-devtools/cdrtools/files/
/home/ross/Yocto/poky/meta/recipes-devtools/cdrtools/cdrtools-3.01a31+really3.01/x86-64
/home/ross/Yocto/poky/meta/recipes-devtools/cdrtools/cdrtools/x86-64
/home/ross/Yocto/poky/meta/recipes-devtools/cdrtools/files/x86-64
/home/ross/Yocto/poky/meta/recipes-devtools/cdrtools/cdrtools-3.01a31+really3.01/
/home/ross/Yocto/poky/meta/recipes-devtools/cdrtools/cdrtools/
/home/ross/Yocto/poky/meta/recipes-devtools/cdrtools/files/
/home/ross/Yocto/downloads/
Put it in /cdrtools/ not cdrtool-native.
> +Upstream-status: Inappropriate [native]
As the pedantic patchtest says, Upstream-Status.
Ross
next prev parent reply other threads:[~2019-11-13 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 22:31 [PATCH 0/1] cdrtools-native: Don't set uid/gid during install Paul Barker
2019-11-12 22:31 ` [PATCH 1/1] " Paul Barker
2019-11-13 21:28 ` Ross Burton [this message]
2019-11-13 21:32 ` Paul Barker
2019-11-12 23:02 ` ✗ patchtest: failure for " Patchwork
2019-11-12 23:31 ` Paul Barker
2019-11-13 0:47 ` Mittal, Anuj
2019-11-14 13:09 ` Paul Barker
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=b7cf9efa-6caf-c2f2-40ff-e84205f6e4ea@intel.com \
--to=ross.burton@intel.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