On 3/12/25 12:45 PM, Miroslav Suchý wrote:
Dne 11. 03. 25 v 10:36 dop. Panu Matilainen napsal(a):
It's exactly for reasons like this that rpm will not even try to
automatically setup the signing - it has no way of knowing what the
right thing is.
Mock has it's own signing plugin, rpm wont interfere with it:
https://rpm-software-management.github.io/mock/Plugin-Sign
Hmm, but this plugin is not enabled by default. And it is not even
enabled in Copr where packages are signed after Mock finishes and passed
to obs-sign.
Can you provide a Copr project with RPM 6.0 build that I can try (I did
not find it in the Change document)?
We don't provide any "official" builds for any version, but
https://copr.fedorainfracloud.org/coprs/pmatilai/rpm-snapshot/ is
~daily-weekly builds of rpm git master branch, currently in pre-6.0. I
run this on my laptop at all times, so it's not expected to eat anybodys
kittens for breakfast but of course, approach with caution.
mock and copr seem to be working fine, but it's possible I'm not testing
some specific thing that does actually break with this.
Just realized there are a couple of clarifications to be made as to what
exactly is enforced: the enforced signature checking only concerns
installations (including update/reinstall) through transactions. 'rpm -i
foo.src.rpm' is not affected, nor is querying packages.
- Panu -
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
