On Tue, Dec 05, 2023 at 11:15:40PM +0100, Robin Jarry wrote: > Nilesh Patra, Dec 05, 2023 at 20:44: > > You should have the permissions now for this repo. LMK if there's still > > an issue. > > Thanks I managed to push everything needed. However, the CI fails for some > obscure reason now: > > https://salsa.debian.org/go-team/packages/golang-sourcehut-rockorager-go-jmap/-/jobs/5005483 > > $ GBP_CONF_FILES=:debian/gbp.conf gbp buildpackage > --git-no-pristine-tar --git-ignore-branch --git-ignore-new > --git-export-dir=/tmp/export --git-no-overlay > --git-tarball-dir=/nonexistent --git-cleaner=/bin/true > --git-builder='dpkg-buildpackage -S -d --no-sign' > gbp:info: Tarballs 'golang-sourcehut-rockorager-go-jmap_0.4.4.orig.tar.gz' > not found at '/nonexistent' > gbp:error: upstream is not a valid branch > > Do you have a clue? It seems related to my change in debian/gbp.conf I have a vague idea, and I'm not really keep to dig into it as this is not /really/ important. I am able to repro if I `git clone` the repository and try to run the command or try to run `gbp export-orig` | $ gbp export-orig | gbp:error: upstream is not a valid branch This is because a simple clone does not checkout the upstream branch. Once I checkout this, the error goes away. My hunch is that the CI is trying to do something like this, atleast as per the CI logs: | Fetching changes with git depth set to 20... | Reinitialized existing Git repository in /builds/go-team/packages/golang-sourcehut-rockorager-go-jmap/.git/ My understanding is that we can maybe ignore the CI here. Best, Nilesh
Attachment:
signature.asc
Description: PGP signature