Re: Cleaning salsa build cache before a new build
Hi,
Le 02/10/2025 à 08:52, Andrey Rakhmatullin a écrit :
On Thu, Oct 02, 2025 at 01:58:46AM +0200, Vincent Danjean wrote:
I found my problem: after fixing my initial mistake, I force-push all branches.
But I forgot to force-push tags. And upstream/3.7.8 was pointing to the previous (wrong) state.
I don't think it's related.
Kind of, nevertheless, because "gbp export-orig" relies on the tag if pristine-tar is not enabled.
Without this issue, I would never realized there was a problem in my setup and my packages repos.
My $HOME/.gbp.conf has been last changed in 2010...
So, "git branch -a --list -v" shows me exactly the same state as the one on salsa CI
But "gbp export-orig --tarball-dir=..." leads to different tarballs on salsa CI and locally
In the (locally) cloned repo from salsa
You probably have pristine-tar enabled globally, as I hinted in my previous email and as is relatively clear from your commands.
You were totally right and I missed your previous advice.
This would have saved me lot of time. My bad.
Many thanks for your help
Regards
Vincent
Reply to: