<2d7646c54be061caf7635da748d35dc8@riseup.net>this build: https://builds.sr.ht/~raingloom/job/1212401 triggered by this commit: https://git.sr.ht/~raingloom/thesis/commit/868582e02a68601383583df11bb9322b4383d330 has two sources on the CI, which results in two clones, which obviously fails, because the directory already exists. If there is no branch suffix, the problem seems to disappear: https://builds.sr.ht/~raingloom/job/1212409 Is this a bug? It definitely seems like one, but I'd like to make sure.
<441545ed-aebc-48bd-8721-7393590fe86d@bitfehler.net>
<2d7646c54be061caf7635da748d35dc8@riseup.net>
(view parent)
On 5/4/24 11:12 PM, raingloom@riseup.net wrote: > this build: https://builds.sr.ht/~raingloom/job/1212401 > triggered by this commit: > https://git.sr.ht/~raingloom/thesis/commit/868582e02a68601383583df11bb9322b4383d330 > has two sources on the CI, which results in two clones, which obviously > fails, because the directory already exists. > > If there is no branch suffix, the problem seems to disappear: > https://builds.sr.ht/~raingloom/job/1212409 > > Is this a bug? It definitely seems like one, but I'd like to make sure. Yeah, it looks like it. I recommend you remove the branch suffix for now, as it just points to your default branch anyway. I'll submit a fix for this soon. Cheers, Conrad