From: Joshua Watt <jpewhacker@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] oeqa: Run diffoscop on saved output
Date: Tue, 11 Feb 2020 21:14:31 -0600 [thread overview]
Message-ID: <20200212031435.792802-1-JPEWhacker@gmail.com> (raw)
Adds recipes to build the diffoscope tool and run it when the OEQA
reproducible build test saves output to a local path. This should make
it much easier to debug reproducible build issues from the autobuilder,
since the published output can be easily viewed on the website.
Joshua Watt (4):
python: Add libarchive-c recipe
python: Add magic recipe
recipes-support: Add diffoscope recipe
oeqa: reproducible: Run diffoscope on saved output
meta/conf/distro/include/maintainers.inc | 3 +++
meta/lib/oeqa/selftest/cases/reproducible.py | 24 +++++++++++++------
.../python/python3-libarchive-c_2.9.bb | 17 +++++++++++++
.../python/python3-magic_0.4.15.bb | 19 +++++++++++++++
.../diffoscope/diffoscope_136.bb | 15 ++++++++++++
5 files changed, 71 insertions(+), 7 deletions(-)
create mode 100644 meta/recipes-devtools/python/python3-libarchive-c_2.9.bb
create mode 100644 meta/recipes-devtools/python/python3-magic_0.4.15.bb
create mode 100644 meta/recipes-support/diffoscope/diffoscope_136.bb
--
2.23.0
next reply other threads:[~2020-02-12 3:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 3:14 Joshua Watt [this message]
2020-02-12 3:14 ` [PATCH 1/4] python: Add libarchive-c recipe Joshua Watt
2020-06-10 3:17 ` [OE-core] " Yu, Mingli
2020-02-12 3:14 ` [PATCH 2/4] python: Add magic recipe Joshua Watt
2020-02-12 3:14 ` [PATCH 3/4] recipes-support: Add diffoscope recipe Joshua Watt
2020-02-14 6:34 ` Khem Raj
2020-02-14 13:15 ` Joshua Watt
2020-02-14 14:18 ` Richard Purdie
2020-02-14 14:31 ` Khem Raj
2020-02-12 3:14 ` [PATCH 4/4] oeqa: reproducible: Run diffoscope on saved output Joshua Watt
2020-02-12 3:28 ` [PATCH 0/4] oeqa: Run diffoscop " akuster808
2020-02-15 11:07 ` Richard Purdie
2020-02-16 18:27 ` Joshua Watt
2020-02-17 11:02 ` Richard Purdie
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=20200212031435.792802-1-JPEWhacker@gmail.com \
--to=jpewhacker@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.