From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Randy MacLeod <randy.macleod@windriver.com>,
Khem Raj <raj.khem@gmail.com>,
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core][PATCH v10 1/5] rpm-sequoia-crypto-policy: New recipe
Date: Wed, 12 Feb 2025 05:35:24 +0100 [thread overview]
Message-ID: <bd635513-bf80-471e-984b-1d04e82f4b15@gmail.com> (raw)
In-Reply-To: <1822D4A7D4324BD6.32551@lists.openembedded.org>
2025. 02. 10. 12:17 keltezéssel, Zoltan Boszormenyi via lists.openembedded.org írta:
> 2025. 02. 10. 10:03 keltezéssel, Alexander Kanavin írta:
>> On Sat, 8 Feb 2025 at 08:24, Zoltán Böszörményi <zboszor@gmail.com> wrote:
>>> +Assume that the policies are good as they are committed.
>>> +The CI for fedora-crypto-policies ensures this.
>>> +
>>> +Upstream-Status: Inappropriate [Yocto specific]
>> The patch as it is is indeed not suitable, but perhaps you can open a
>> ticket, describe the issue, and see if upstream would be willing to
>> take a configuration option instead?
>>
>> We generally ask that Inappropriate patches still come with ticket
>> links, so upstreams are aware of the problems we face. Sometimes
>> solutions come out of that, and if not
>> this documents their response.
The upstream discussion happened, my patches were
merged into fedora-crypto-policies. v12 series is on its way.
prev parent reply other threads:[~2025-02-12 4:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 7:24 [OE-core][PATCH v10 1/5] rpm-sequoia-crypto-policy: New recipe Zoltán Böszörményi
2025-02-08 7:24 ` [OE-core][PATCH v10 2/5] rpm-sequoia: New recipe for version 1.7.0 Zoltán Böszörményi
2025-02-08 7:24 ` [OE-core][PATCH v10 3/5] rpm: Set SEQUOIA_CRYPTO_POLICY in wrapped tools Zoltán Böszörményi
2025-02-08 7:24 ` [OE-core][PATCH v10 4/5] dnf: " Zoltán Böszörményi
2025-02-08 7:24 ` [OE-core][PATCH v10 5/5] oeqa/selftest/cases/signing.py: Re-enable self-test Zoltán Böszörményi
2025-02-10 9:03 ` [OE-core][PATCH v10 1/5] rpm-sequoia-crypto-policy: New recipe Alexander Kanavin
2025-02-10 11:17 ` Böszörményi Zoltán
[not found] ` <1822D4A7D4324BD6.32551@lists.openembedded.org>
2025-02-12 4:35 ` Böszörményi Zoltán [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=bd635513-bf80-471e-984b-1d04e82f4b15@gmail.com \
--to=zboszor@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=randy.macleod@windriver.com \
--cc=richard.purdie@linuxfoundation.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.