Soren,
The upstream sources come with *two* tarballs.
The nodeset tarball (with XML files) is from [1].
In the upstream open62541 project we use a git submodule for the nodeset.
For the Debian packaging we instead have a second tarball for the exact commit
of the git submodule [2].
- open62541_1.4.3.orig.tar.gz
- open62541_1.4.3.orig-nodeset.tar.gz
Both tarballs have been pushed to mentors.
The manual build should work, provided you also give it the second
nodeset-tarball.
The pristine-tar branch was created as follows:
gbp pristine-tar commit --component=nodeset ../open62541_1.4.3.orig.tar.gz
-v
The verbose output is included down below the fold.
Probably I did not redo the pristine-tar after the latest commit to main
(changing the Vcs-Git tag, no changes outside of /debian).
Rerunning the gbp pristine-tar command just now added more git-commits.
They are pushed to salsa on top of the pristine-tar branch.
With this I can run
gbp buildpackage --git-debian-branch=main
on my box without an error.
[1] https://github.com/OPCFoundation/UA-Nodeset
[2]
https://github.com/OPCFoundation/UA-Nodeset/tree/d1bb6a22125bd7cd986272b1ee98a18a91d76fff
--
Regards, Julius
gbp:debug: ['git', 'rev-parse', '--show-cdup']
gbp:debug: ['git', 'rev-parse', '--is-bare-repository']
gbp:debug: ['git', 'rev-parse', '--git-dir']
gbp:debug: ['git', 'ls-tree', '-z', 'upstream/1.4.3', '--']
gbp:debug: ['git', 'mktree', '-z']
gbp:debug: ['git', 'ls-tree', '-z', 'upstream/1.4.3', '--']
gbp:debug: Creating pristine tar commit
'../open62541_1.4.3.orig-nodeset.tar.gz' from
'f38a1be271027c8490bbce407be4f34c2397bf29'
gbp:debug: pristine-tar [] ['commit', '../open62541_1.4.3.orig-nodeset.tar.gz',
'f38a1be271027c8490bbce407be4f34c2397bf29']
gbp:debug: pristine-tar [] ['commit', '../open62541_1.4.3.orig.tar.gz',
'20bcbcfe79a001b805a52df0f3088b9868844ffc']
gbp:info: Successfully committed pristine-tar data for version 1.4.3-1 of
../open62541_1.4.3.orig.tar.gz with additional tarballs for
open62541_1.4.3.orig-nodeset.tar.gz
