Hi Scott, Scott Bradnick via openSUSE Factory <factory@lists.opensuse.org> writes:
On Wed, 2023-07-19 at 11:28 +0200, Dan Čermák via openSUSE Factory wrote:
Dear packagers for openSUSE Tumbleweed,
we have been working on a prototype that allows you to maintain your packages in git (similarly to Fedora's dist git) on src.opensuse.org instead of on OBS. Contributions to the package are then handled via pull requests on src.opensuse.org which get automatically forwarded as submitrequests on OBS.
This is currently just a prototype and we are looking for testers and general feedback. So if you want to participate as a maintainer, please check the full guide here: https://opensuse.github.io/scm-staging/user_guide.html
tl;dr; you'll have to convert the develpackage to use `<scmsync>` from src.opensuse.org/pool and everything else should "just work".
FAQ:
- Where can I report issues or provide feedback? https://github.com/openSUSE/scm-staging/issues (for bugs) or https://github.com/openSUSE/scm-staging/discussions (for general feedback)
- Is this how the future of packaging in openSUSE is going to look like? Maybe, maybe not. This is currently just a test drive and its outcome will influence the way forward.
- Will submitrequests to my develpackage still work? Sadly no, branching a git maintained package on OBS does not work. Please indicate in the description of your package that users should contribute on src.opensuse.org instead.
- Which tools do I need? Just git, git-lfs and osc (at least version 1.2.0 is recommended for service runs to work)
Looking forward to your feedback!
Dan
I have a few questions as I try to give this a go :)
1. what's the intention behind the https://src.opensuse.org/rpm area? I see a package in /pool ("Updated 2 weeks ago") but it's less up-to-date than the /rpm fork ("Updated 20 hours ago"). I see most any package I maintain that's been updated in the not-too-distant-past like this.
2. Under "Contributor Guide" it says "1. Install the `git-scm-bridge`" - is this supposed to to `obs-scm-bridge`? Seems so, but maybe I just don't have a repo which offers `git-scm-bridge` up.
3. Also under "Contributor Guide", for "4. Add the fork ..." - the code block shows `git remote add fork gitea@src.opensuse.org/$username/$pkg_name` but that doesn't work when you later do `git push fork` since I had to change it to: `gitea@src.opensuse.org:$username/$pkg_name`. I _think_ that's the general convention when SSH in involved, but I'm not a git expert.
2 and 3 have been fixed, thanks for spotting that! Cheers, Dan -- Dan Čermák <dcermak@suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstrasse 146 90461 Nürnberg Germany (HRB 36809, AG Nürnberg) Managing Director/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman