https://rpm-software-management.github.io/mock/feature-hermetic-buildsYes, thanks for the link. I think this didn't exist when I started working on my script to do rebuilds, so I just gather the rpms reported by koji to have been used for the original build and call 'createrepo_c' on the directory and point mock to that. This works fine… But having support for using a lockfile natively in mock is nice.
Yes. This is several months old.
Pavel added it during his work on Konflux. And this feature will
be used in Konflux.
Though, the process described in that link seems incomplete.
Can you elaborate? Or you can reach Pavel off-list to discuss the
usage.
# we want to build this package srpm=your-package.src.rpmWhere does the $srpm come from? The process of creating the srpm from dist-git involves running the spec, i.e. already calling "untrusted" code. How is that part handled?
"mock --buildsrpm" or "fedpkg srpm". I am not sure. In Konflux creating SRPM is separate step. So SRPM is granted from previous step.
Pavel may provide more details later when he recovers from
illness.
Yet another build system in fedora-infra? Can the rebuilderd be adjusted that it submits builds to Copr?That is a good question. Does copr support running a build with a specified "$lockfile", i.e. with a fixed set of nvra's? It would also have to download those rpms from koji, since they are not available on mirrors.
No. Copr does not support it, because no one asked for that and there was no use-case. When you open RFE we can discuss what it would requires and when we can put it in our plan.
Or you can use Konflux that will use this natively. But Konflux
is very immature now.
rebuilderrd is an complete project that does things in its own way. It turned out to be not-very-complicated to teach it to use a build script that does the build locally.
Building 30k packages locally? With frequent updates for lots of them. Does it scale?
-- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
