On Mon, 2022-02-07 at 10:16 +0100, Alexander Kanavin wrote: > Signed-off-by: Alexander Kanavin <[email protected]> > --- > ...-do-not-force-RHEL-7-specific-build-.patch | 30 +++++++++++++++++++ > meta/recipes-devtools/git/git_2.35.1.bb | 3 +- > 2 files changed, 32 insertions(+), 1 deletion(-) > create mode 100644 > meta/recipes-devtools/git/git/0001-config.mak.uname-do-not-force-RHEL-7-specific-build-.patch > > diff --git > a/meta/recipes-devtools/git/git/0001-config.mak.uname-do-not-force-RHEL-7-specific-build-.patch > > b/meta/recipes-devtools/git/git/0001-config.mak.uname-do-not-force-RHEL-7-specific-build-.patch > new file mode 100644 > index 0000000000..e0f702f327 > --- /dev/null > +++ > b/meta/recipes-devtools/git/git/0001-config.mak.uname-do-not-force-RHEL-7-specific-build-.patch > @@ -0,0 +1,30 @@ > +From 3b2505435bc6f982226eff84bad6bf9a36381573 Mon Sep 17 00:00:00 2001 > +From: Alexander Kanavin <[email protected]> > +Date: Mon, 7 Feb 2022 10:13:15 +0100 > +Subject: [PATCH] config.mak.uname: do not force RHEL-7 specific build > settings > + > +This breaks reproducibility as git builds on centos 7 use > +different flags than git builds on other host distros. > + > +Upstream-Status: Inappropriate [upstream needs to check compiler and > component versions properly]
I'm struggling a bit with the Inappropriate patch status. I can't help wonder if we should have something like "NeedsRework" to illustrate something where the patch itself isn't appropriate but the issue itself should be handled upstream? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#161457): https://lists.openembedded.org/g/openembedded-core/message/161457 Mute This Topic: https://lists.openembedded.org/mt/88968013/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
