Dan Čermák

> > @majamassarini @lachmanfrantisek I am not sure if I understood #2099, but afaik there is no project out there that is actually using OBS as its upstream version control...

I have submitted osc to epel for CentOS 9, so I hope that the CI should be passing now. How should we proceed from here?

This appears to be caused by some sphinx bug. The failure is reproducible with doxygen 1.9.7 and Sphinx 7.0.1 but not with Sphinx 7.1.2 (implemented via https://src.fedoraproject.org/rpms/python-sphinx/pull-request/56) nor with Sphinx...

That's great news, thanks a lot!

Thanks for giving the analyzer a try @pythiankerr! I have tried to enable building the container for multiple architectures in #162. Could you please try to pull the container image...

> There are a few other places to touch. Please follow this PR as an example: https://github.com/emacs-lsp/lsp-mode/pull/4283/files Should be done now

We've had a thought with @danishprakash about how this could be implemented. A very simple way would be to change the loop in https://github.com/containers/image/blob/6caf212454493ef1979393c398ac705aebb393a6/signature/policy_eval.go#L281 to accept a signature if at...

Yet another inconsistency: if you instead use `curl --user ${CREDENTIALS} -X PUT ${OBS}/source/${project}/${package}/${filename}?rev=repository -d "something in here"` then you will get neither a status nor a revision back, but this:...

> Repository only uploads (`rev=repository`) do not create a revision at all, so you only get the srcmd5 back. That makes sense, but of which object do I get the...

Let me rephrase that: is the returned `srcmd5` the hash of the file that I just uploaded or the package in the new "dirty" state or of the package in...