On Fri, 2025-02-28 at 18:14 +0100, Adrian Schröter wrote:
On Freitag, 28. Februar 2025, 17:51:13 CET Atri Bhattacharya wrote:
* How do I branch a package on the git pool and build it simultaneously for multiple openSUSE versions? For example, to check if a change I make for TW does not end up causing build failures for the package on Leap 15.6 or so on?
the repository configuration of your project (devel, home or whatever) is independend from where the project or package sources come from.
So, nothing really is changing here, you can still build against any targets from the same source.
This was my hope too, but for example, after I clone locally <https://src.opensuse.org/badshah400/argparse>, which is a fork from <https://src.opensuse.org/clibs/argparse>, `osc build` no longer works: ``` ~> osc build WARNING: Using EXPERIMENTAL support for git scm. The functionality may change or disappear without a prior notice! Couldn't map git branch 'master' to a project ~> osc build openSUSE_Factory x86_64 WARNING: Using EXPERIMENTAL support for git scm. The functionality may change or disappear without a prior notice! Couldn't map git branch 'master' to a project ``` Where is the corresponding OBS branch project created? Or what am I doing wrong?
not be causing some new build failures for package B? Currently, I can branch a package X from obs://devel:libraries:c_c++ into home:FOO:TestRepo and another package Y, say, from obs://science into the same home:FOO:TestRepo to test if Y plays nicely with changes in make in X. Is this still possible using packages from git pool?
You have at least two options
1. you can still setup a classic OBS project and just link the wanted packages together. Using old style _link files. Or you just add the git repo url in the <scmsync> element of the package meta, it will automatically follow.
2. if you have multiple packages from the same git project and you plan to submit them together later, it might make sense to fork the git project and build that one in your staging project.
Please note that you can also limit the package sources you want to build there using the onlybuild parameter optional, eg: http....?onlybuild=gcc&onlybuild=glibc
OK, thanks. Will try this out. Best wishes, -- Atri