Hi, I wanted to work on my packages again... failed with an error, went to see if someone had already reported the same : yes... and it's me. ent.
Here is a simple session showing how to reproduce the failure: $ gbp clone https://salsa.debian.org/ocaml-team/elpi $ cd elpi $ gbp import-orig --uscan gbp:info: Cloning from 'https://salsa.debian.org/ocaml-team/elpi' gbp:info: Launching uscan... Newest version of elpi on remote site is 3.4.5, local version is 3.4.3 => Newer package available from: => https://github.com/LPCIC/elpi/archive/refs/tags/v3.4.5.tar.gz Successfully symlinked ../v3.4.5.tar.gz to ../elpi_3.4.5.orig.tar.gz. gbp:info: Using uscan downloaded tarball ../elpi_3.4.5.orig.tar.gz What is the upstream version? [3.4.5] gbp:info: Importing '../elpi_3.4.5.orig.tar.gz' to branch 'upstream/latest'... gbp:info: Source package is elpi gbp:info: Upstream version is 3.4.5 gbp:error: Import of ../elpi_3.4.5.orig.tar.gz failed: Couldn't commit to 'pristine-tar' with upstream '143112a9fe70b23d66d7d8b7da11cb12965c206f': tar: This does not look like a tar archive tar: Exiting with failure status due to previous errors error: excessively large binary delta for /tmp/pristine- tar.ssLYm7XX9J/origtarball (Please consider filing a bug report.) pristine-tar: failed to generate delta gbp:error: Error detected, Will roll back changes. gbp:info: Rolling back branch upstream/latest by resetting it to 3d3ad30dc66e6df2465594610d2e3e2af6b23ffd gbp:info: Rolling back branch pristine-tar by resetting it to 4350b5792b78268da97cd6dc3d37513b4a7d18b3 gbp:error: Rolled back changes after import error. Again I can confirm that tar is quite happy with elpi_3.4.5.orig.tar.gz, so I don't understand what the problem actually is. Cheers, J.Puydt
