On 09.01.23 12:39, Miroslav Suchý wrote: > Dne 09. 01. 23 v 7:12 Thorsten Leemhuis napsal(a): >> I tried a few (three? four?) years ago and there were iirc three >> showstoppers back then. I'm sure I wrote them down somewhere, but I >> can't find it right now. 🙁 But I think I remember one: >> >> It iirc (and afaik back then) was not possible to build packages and >> test them before their publication. Is that possible these days? I >> occasionally do something stupid, that's why I fire up the x86_64 builds >> in qemu locally these days before publishing a build. > > TIMWTDI > > 1) If you are using pull request then you can use Packit > https://packit.dev/ > Packit build the code in PR in new Copr project and links results from PR. > > 2) If you are not using PR and want to share a results before you push > it, you can create project, e.g., thorsten-testing, and configure it > that is requires some other repo (your upstream project) and all build > in thorsten-testing can use package from some-other-repo and your builds > in thorsten-testing will not impact some-other-repo. > > Generally speaking: creating project is cheap task and you can > create/delete project on daily basis. Either I'm missing something or your explanation is missing one important detail: can I rename a project once I tested the newly built packages so that users of my repos get the latest packages with the next "dnf update" without doing anything? Ciao, Thorsten _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-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/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
