Hi Jiri, On Thu, 2025-02-27 at 08:05 +0100, Jiri Slaby wrote:
The price is IMO not so high. Have you actually tried this all yet?
The fact that I will have to leave the terminal and manually navigate to the project page in my web browser and retrieve the git URL is a major step backwards in my opinion. Plus, I can no longer collect and assemble packages in my own home project to build and test them there. For larger package stacks, it's an indispensable feature of OBS that I can build and test a collection of packages in my home project and even create a repository from there in order to submit them in a batch. If this feature becomes unavailable because of the transition to Gitea, larger stack updates will become impossible unless there is a different way of creating such staging setups. Furthermore, there are many small nuisances that still exist such that folders and temporary files are not automatically ignored but can accidentally get committed and the fact that commit messages are not constructed from the changes file, so that I have copy them manually. I have the impression that the easy of use and flexibility of OBS is vastly underestimated here so that some people think it can be easily replaced by Gitea. Coming from the Debian world myself, I learned to appreciate the power of OBS really fast as it's much more flexible than Debian's rather simple network of buildds (build servers) which don't support building packages for custom projects in your own home. There is just one set of builders and a system to track package sources while OBS has multiple sources and multiple builders to create multiple repos. This is hugely more useful.
With osc, I often hit its limits. For example have you ever tried to find out who and _why_ added/changed/(and the hardest part in osc: removed) a line in a .spec file (i.e. find a .spec revision and also corresponding .changes one)? git blame/show is lovely. osc blame/cat is often hopeless.
I have never had to use this feature, to be honest. Those are features that I need when maintaining complex source code but not when keeping track of spec files, tarballs and patches.
Not talking about git branch, stash, amend and many other features ;).
Same applies here. I have never had the urge to use these features in OBS, despite the fact that I am actively using these all the time when hacking on upstream projects like the kernel. I have to admit the more the Gitea conversion nears, the more I am convinced that Gitea is not the right tool for the job.
Well guys, if you propose a change, you ought to start with a _Motivation_!
Yes, but the change should not mean that you lose a lot of features from OBS that made the whole build system in openSUSE so superior in the first place. Adrian