From: "Matthew" <matthew.zeng@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>
Subject: Re: [OE-core] [PATCH 1/2] quilt: do not test patch-wrapper as it is not enabled
Date: Wed, 15 Apr 2020 14:35:03 -0400 [thread overview]
Message-ID: <87y2qwfvhk.fsf@windriver.com> (raw)
In-Reply-To: <20200324213647.20829-1-alex.kanavin@gmail.com>
Can we get an update regarding the status of this patch? It is to fix https://bugzilla.yoctoproject.org/show_bug.cgi?id=13841 which the target milestone is set to 3.1 M4.
Thanks,
Matthew
Alexander Kanavin <alex.kanavin@gmail.com> writes:
> Upstream only enables the test if --with-patch-wrapper
> was supplied to ./configure, and so should we.
>
> Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
> ---
> meta/recipes-devtools/quilt/quilt.inc | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/recipes-devtools/quilt/quilt.inc b/meta/recipes-devtools/quilt/quilt.inc
> index d6d06c049c..d2db079e0b 100644
> --- a/meta/recipes-devtools/quilt/quilt.inc
> +++ b/meta/recipes-devtools/quilt/quilt.inc
> @@ -71,6 +71,9 @@ do_install_ptest() {
> tar -c --exclude=mail.test --exclude=delete.test test/ | ( cd ${D}${PTEST_PATH} && tar -xf - && chmod 777 test)
> cp ${WORKDIR}/Makefile ${D}${PTEST_PATH}
> cp ${WORKDIR}/test.sh ${D}${PTEST_PATH}
> +
> + # This is specifically excluded when --with-patch-wrapper is absent during ./configure
> + rm ${D}${PTEST_PATH}/test/patch-wrapper.test
> }
>
> PACKAGES += "guards guards-doc"
--
Mingde (Matthew) Zeng
next prev parent reply other threads:[~2020-04-15 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 21:36 [PATCH 1/2] quilt: do not test patch-wrapper as it is not enabled Alexander Kanavin
2020-03-24 21:36 ` [PATCH 2/2] ptest: further bump RAM in qemu Alexander Kanavin
2020-04-15 18:35 ` Matthew [this message]
2020-04-15 18:40 ` [OE-core] [PATCH 1/2] quilt: do not test patch-wrapper as it is not enabled Alexander Kanavin
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=87y2qwfvhk.fsf@windriver.com \
--to=matthew.zeng@windriver.com \
--cc=alex.kanavin@gmail.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 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.