openSUSE:Obs git known issues

Known Issues and Workarounds regarding the OBS to Git migration

The main page is here. To learn about the new git packaging workflow visit the dedicated page. To learn more about the specifics for Leap see packaging for Leap.

Issues are generally reported and tracked at:

• https://github.com/openSUSE/openSUSE-git
• https://src.opensuse.org/adamm/autogits

We will try to document known workarounds here.

Creating PR from one pool branch to another directly fails (#129)

If you are a regular user (non-collaborator), you go to /pool/somepackage and select factory branch as source and leap-16.0 as target, the UI will fail with a permission issue.

Workaround

Fork to home and then create a PR from there to leap-16.0

Gitea doesn't allow LFS push with AGit workflow (#97)

This is being worked on upstream: https://github.com/go-gitea/gitea/issues/34583

Workaround

Use standard fork and create a PR from that. See git-obs workflow

Renaming package might lead to "broken" package (#142)

If a user wants to rename a package, it is necessary to do:

1. Rename the repository in https://src.opensuse.org/mcepl/<old-module>/settings, rename the directory in the checkout, and edit .git/config to reflect new URLs and new name of the module
2. Change the URL in .gitmodules file of the super-project via editing the file, or use: git submodule set-url [--] <patch> <newurl>), and run git submodule update --init <new-module>
3. check that tarball is LFS (run git lfs pull)
4. rm -r .git/modules/<old-module>
5. create a new commit in the superproject covering all these changes (git add -A .)

Strange git history

Sometime around April 2024 commits created by the git-obs-bridge had a parent and were getting merged into the relevant code-stream branch but then the changes from OBS are coming from an orphan branch. No action is required. It's an importer issue, which will be fixed when everything got imported into git. Branches will be fixed during migration.