Our last messages crossed.
There is something strange with your repository (at least zmat):
$ gbp clone git@salsa.debian.org:pkg-octave-team/zmat.git
gbp:info: Cloning from 'git@salsa.debian.org:pkg-octave-team/zmat.git'
$ cd zmat
$ gbp export-orig
gbp:info: Creating /var/data/rlaboiss/debian/PKGS/zmat/zmat_0.9.8.orig.tar.gz
gbp:error: Can not find pristine tar commit for archive 'zmat_0.9.8.orig.tar.gz'
sorry for the confusions - still learning the process
this is what I did for the pristine-tar branch - I first download
the upstream release tarball at
https://github.com/fangq/zmat/releases/tag/v0.9.8
with a file name of zmat-0.9.8.tar.gz, and then run the command
gbp pristine-tar commit /path/to/zmat-0.9.8.tar.gz
to add the pristine-tar branch.
As I mentioned earlier, the zmat_0.9.8.orig.tar.gz file linked in my .dsc is a modified version of the upstream release.
I suppose I can do one of two things to fix this:
1. delete the pristine-tar branch, and reimport the (modified upstream tarball) "zmat_0.9.8.orig.tar.gz" that matches my .dsc
2. delete the pristine-tar branch, rename unmodified upstream tarball from zmat-0.9.8.tar.gz to zmat_0.9.8.orig.tar.gz and import that file to pristine-tar.
Please let me know which one is the proper next step.
thanks for your patience!
Best,
Rafael
* Qianqian Fang <fangqq@gmail.com> [2020-06-19 09:09]:
On 6/19/20 2:42 AM, Rafael Laboissière wrote:
Note that the "upstream" branch is lacking in the zmat repository.
Also, the "pristine-tar" branch is lacking in all three
repositories.
Finally, as I wrote in a previous message, the tags "debian/*" should not be present for now. They should appear only after the package has been uploaded and accepted in unstable.
Please, fixed the above issues, otherwise it will be impossible to use the repositories in a git-buildpackage normal workflow.
thanks, it looks like I did not enable pristine-tar in my gbp.conf. now the missing branches are all added, and debian/* are all deleted:
$octave-jsonlab$ git branch -a * master pristine-tar upstream remotes/origin/HEAD -> origin/master remotes/origin/master remotes/origin/pristine-tar remotes/origin/upstream $octave-jsonlab$ git tag -l upstream/2.0
$zmat$ git branch -a * master pristine-tar upstream remotes/origin/HEAD -> origin/master remotes/origin/master remotes/origin/pristine-tar remotes/origin/upstream $zmat$ git tag -l upstream/0.9.8
$octave-jnifti$ git branch -a * master pristine-tar upstream remotes/origin/HEAD -> origin/master remotes/origin/master remotes/origin/pristine-tar remotes/origin/upstream $octave-jnifti$ git tag -l upstream/0.6
let me know if this looks ok.
Qianqian
if you have time, please take a look and let me know if any changes you want me to make - I want to briefly mention two things:
1. the above 3 toolboxes have dependencies - octave-jsonlab requires zmat, and octave-jnifti requires the above two.
2. the only major warning I have right now is that the jnifti-demos subpackage in octave-jnifti contains only docs files, so lintian gives the below warning:
W: jnifti-demos: empty-binary-package
please let me know if this is something that should be fixed.
In the meantime, I will read the web pages on how to move forward from here.
Before looking into the packages, I will wait until you fix the layout problems I mentioned above.
In addition, I am also preparing another 4 new packages. Once they are ready, I will follow up with you on the repo settings if I need you to change permission.
Ok.
Rafael