On Thu, Jan 03, 2019 at 10:45:12AM +0100, Guido Günther wrote: > What's your checkout command on the other machine? Did you specify the > components. Please don't omit the commands you're using for import and > export
import: gbp import-orig --pristine-tar ../opencv_3.4.5+dfsg.orig.tar.xz --component contrib export (where the tarball is imported): ~/D/o/opencv ❯❯❯ git st HEAD detached at 922bf8f32 nothing to commit, working tree clean ~/D/o/opencv ❯❯❯ pristine-tar checkout opencv_3.4.5+dfsg.orig-contrib.tar.xz pristine-tar: successfully generated opencv_3.4.5+dfsg.orig-contrib.tar.xz ~/D/o/opencv ❯❯❯ pristine-tar checkout opencv_3.4.5+dfsg.orig.tar.xz pristine-tar: successfully generated opencv_3.4.5+dfsg.orig.tar.xz export (remote): It's quite strange that I cannot reproduce this problem anymore on the commit in question. @Mattia: Are you able to reproduce this problem? I can checkout the tarball from both git: a0bd84b30b388b9811bc300e9a62801cf89c8966 git: 922bf8f325761abecfcd8171ab490fba4e821c58 which yield the same tarball c41c9e5892e3d1fa15c0a8016cd5e84c 1.xz c41c9e5892e3d1fa15c0a8016cd5e84c 2.xz even if they points to different id: --- a/opencv_3.4.5+dfsg.orig.tar.xz.id +++ b/opencv_3.4.5+dfsg.orig.tar.xz.id @@ -1 +1 @@ -a67d0acc9952eb94c9dc0f50eb1f73777695418e +a18a03170473e1773e1f571e561441bc83a3861e