You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
to have the package available in another project (because it is required for dependency or it should be build in a different environment or for different platform).
With scmsync managed package I get an error:
tumbleweed-pkg~/b/neovim$ osc branch openSUSE:Factory par_text home:mcepl:neovim
BuildService API error: failed to branch: <status code="404">
<summary>_link: no such file</summary>
<details>404 _link: no such file</details>
</status>
tumbleweed-pkg~/b/neovim$
Any ideas?
Versions
Operating system: Tumbleweed
Packages: local build from the master branch (currently tag 1.3.0).
To Reproduce
Steps to reproduce the behavior:
see above
Expected behavior
somehow the package becomes present in the other package as well
The text was updated successfully, but these errors were encountered:
for one we will definitive not supporting source merge mechanism of native OBS packages together with git managed sources.
I wonder why you even try to use it, because you may not know that a package is actually git managed?
In that case we should just report an error message pointing to an explanation how to work with gitea instead IMHO.
What we need to find is a tool/workflow how one can setup easily a test build env after ones has forked a package in any git server IMHO.
This is solved by openSUSE/open-build-service#14752 for packages you convert from now on and on build.o.o also for packages that have been converted previously.
Describe the bug
With a regular (OSC managed) package I can do
to have the package available in another project (because it is required for dependency or it should be build in a different environment or for different platform).
With scmsync managed package I get an error:
Any ideas?
Versions
To Reproduce
Steps to reproduce the behavior:
Expected behavior
somehow the package becomes present in the other package as well
The text was updated successfully, but these errors were encountered: