Thanks, it helps the salsa pipeline. But it fails right after, because the git content is too different from the tarball of 1.0.20...
I guess there is no easy way to make this pipeline work before the release of 1.1.0. I tend to think that our issues come from the remote tracking of upstream's git in the debian one. In the other packages I'm involved in, we only use `gbp import-orig` to get new upstream content, while keeping the pristine-tar branch in sync. I understand that the situation is very specific for xournalpp, as you wanted to get ready for the upcoming release, but maybe in the future it'd be easier to stick to the classical git-buildpackage workflow? That being said, if you have another workflow that work (on salsa also), I'd be glad to learn new tricks ;) I'm not very well connected to the xournal world. Do you have any hint of when the next release will occur? Thx, Mt
