Package: git-debrebase Version: 14.9 When using the recommended salsa-ci script from https://diziet.dreamwidth.org/20851.html , then the builds will start to fail when it was finally possible to get all patches upstreamed.
Let us have a look at the problematic part in the CI script: - git-debrebase make-patches # make an orig tarball using the upstream tag, not a gbp upstream/ tag # https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/541 - git-deborig If no patch could be extracted from the git branch (because all of them were upstreamed - yeah!!!), make-patches will print: No (more) patches to export. This is a failure, according to the git-debrebase script - even when it would be a goal which every Debian package should try to achieve. The git-debrebase script will return a 255 error in this situation. Because of this return value, the CI will stop the processing - git-deborig will therefore never run. The whole CI run will then stop with an error like: /usr/bin/bash: line 260: cd: /builds/whatever/foobar/debian/output: No such file or directory When git-debrebase wants to become a viable option then it should not force anyone to switch back-and-forth between git-debrebase and git-merge based workflow whenever a Debian package switches between (long standing) patches and when not needing patches at all.
