Hi Dirk, how does testing builds work with this new git-backend? Usually, I branch a package in OBS, do updates, send it back to my branch and see if it builds fine on all archs and relevant code-streams. Sometimes I even try out the resulting rpms, in case I need to verify some fix. And only once I'm satisfied, do I issue an SR. How does something like this work with the new git-based model? It seems to only actually start building something, once I've created the final SR/PR to Factory. But what if it gets approved before I could test out things or other codestreams/archs have finished building, that Factory doesn't care about? Thanks, Martin On 6/26/24 2:29 PM, Dirk Müller via openSUSE Factory wrote:
Hi,
for a while src.opensuse.org has been serving git-converted history of openSUSE Tumbleweed packages. We recently switched that to SHA256 which is the git format chosen for package maintenance in git going forward. We are aware of many unsolved issues but are afraid to miss some others. Therefore I'd like to invite you to opt in maintaining some of your existing packages in git and help us find and resolve issues in the tooling (osc, and maybe anything else you're using).
The way on how to do that is documented in https://opensuse.github.io/scm-staging/user_guide.html#contributor-guide
This is a bot that forwards PRs from one place to SRs in the other place. This is a migration helper, it's not supposed to stay that way, so don't focus on this part too much. the interesting part is learning what else you need over today in making the "local packaging experience as good or better" with package sources stored in git.
feel free to report the issues or chat about them on https://github.com/openSUSE/openSUSE-git/discussions
Looking forward to your feedback and issues raised.
Thanks, Dirk