Package sources gets step by step migrated from OBS to src.opensuse.org (github). As the source is no longer on OBS, it can’t be branched. Instead you need to fork the project on github, make your changes and merge your request.
I only work on this sort of thing at the console level.
Geany is now in Git. For that, you need to use “osc fork”.
MTP is still in OBS and should still work with “osc branch”.
Well, osc and GH both on CLI — instead OBS on GUI (web browser) here at mine, so far — is too heavy for me. I am sadly not into it. Using OBS just for very basic needs has been easy. But the current workflow looks not to be made for non-Pros…
Additionally: does this actually mean that OBS will become obsolete/deprecated in the future?
We are moving source management to Git. We are not moving the build out of OBS — projects will continue to be built in OBS.
OK, so I still could add and use additional repos (as some others do). But my current workflow (just branching some specific packages from other repos instead of adding/using whole repos and then changing vendor to the package there) doesn’t seem to work for me any more due to my lack of skills (osc, GH: CLI…). What a pity!
No guarantee of accuracy.
I mean, the build via that annoying git only works via the console.
Maybe it works somehow via src.opensuse.org as well.
In my opinion, there isn’t any proper documentation either. (I know what’s coming next: ‘But it’s written there and there.’ I stand by my opinion anyway.)
The whole thing has become so complicated and also much more time-consuming than before that I’m glad I can use it via the console.
(Please, no arguments or comments like ‘it’s sooo much better’. I’ve had that discussion so many times. I’m still absolutely convinced that it isn’t. For me, it has zero added value.)
I’m just going to assume that soon all repos will run via Git.
You can still do it via the GUI with MTP.
With Geany, you’ll have to get to grips with OSC fork.
But that’s when the real work and time-wasting begins. Once it’s working with OSC, it’s almost as fast as before. Provided you’ve found where the package is actually built in OBS.
Hmm.
Normally, you go to the web GUI at https://build.opensuse.org/package/show/devel:libraries:c_c++/libmtp, which displays
There, you then click on ‘Branch’.
Or you go to your home repo, click on ‘branch’ there, and then specify the repo ‘devel:libraries:c_c++’ and the package ‘libmtp’.
‘8 derivative packages’ simply means that 8 others have already branched it.
I don’t know what the link is for.
With Git, you would either just need to enter
osc fork devel:libraries:c_c++ libmtp or
osc fork devel:libraries:c_c++ libmtp --target-project=home:.
In the console, that is.
And then an osc co home: libmtp
That’s exactly what I don’t know. I tried it once, but it never worked.
Running osc fork devel:libraries:c_c++ libmtp --target-project=home:your_name
in the console works.
After that, you’ll be able to see it in your repo in OBS.
Well, yes. But in that case, I don’t even need osc at all because I can do it directly in OBS GUI. The questions holds for cases like geany which are already managed by SCM (https://src.opensuse.org/GNOME/geany#factory in that case).
Well, osc is needed then. I would like to avoid it. Of course, I could learn and use some basic commands — but I would rather like to avoid it and do it all by GUI in https://build.opensuse.org/ and https://src.opensuse.org/ solely.
Is there any chance that it could be possible in the future?
But you do not use many osc commands, maybe only:
osc vc - to write the changelog file
osc ci -n - to transfer it from you Computer to the OBS
osc up - to get the OBS with your Computer to the same level
