Re: Freeze break request: kernel builders
On Thu, Sep 1, 2022 at 8:55 PM Kevin Fenzi <kevin(a)scrye.com> wrote:
So, last week I managed to break bkernel01 kernel builder (and we have
been using just 02 since then). There were 2 issues:
1. I switched rawhide to use systemd-nspawn for isolation instead of
chroot and this broke kernel builds due to (
https://github.com/rpm-software-management/mock/issues/140 )
2. pesign in f36 had some issues with unlocking the smart cards.
( https://bugzilla.redhat.com/show_bug.cgi?id=2122777 )
The pesign maintainers fixed issue 2 this morning and I tested the
workaround I have for issue 1 in mock on bkernel01.
So, what I would like to do now is:
* upgrade bkernel02 to the same pesign version as on 01 along with
moving it to f36 (like 01 is).
* Push a commit in ansible to adjust mock config for the workaround for
issue 1 above.
+1s or further questions?
+1
kevin
_______________________________________________
infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
To unsubscribe send an email to infrastructure-leave(a)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/infrastructure@lists.fedora...
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue