[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: github repo with submodules: non usable source tarball



Hello,

On 25/06/2025 15:31, Hugh McMaster wrote:
On 25/06/2025 5:38 pm, Jerome BENOIT wrote:
I am considering to package a software stored at GitHub.
It is under active development and it builds well in Sid.
However it appears that its source tarball at GitHub does not
contain all the necessary material: its submodules are not included.
This issue seems to be an old GitHub issue. Whatever.
I am wondering how we can grab its source tarball with uscan(1).
The best solution I come with is to write a script that would git-clone
with the option `--recurse-submodule` the git repo and then build a
source ball from this. However this approach sounds heavy to me.
Is there any better way ? Any example of a package with such an issue
is welcome.

uscan has supported git repositories with submodules since v2.25.11 (testing/unstable only).

This is great.


See [1] for usage.


On a up-to-date Sid schroot environment, the following `watch` file

====8><-----------------------------------------------------------------------------------
version=4
opts=mode=git,gitmode=shallow,gitmodules,date=%Y%m%d,pretty=0.0+git%cd.%h,pgpmode=none \
https://github.com/styluslabs/Write.git heads/master
------------------------------><8=========================================================

ends up with the following error message

uscan info: Downloading upstream package: Write.git master
fatal: /usr/lib/git-core/git-submodule cannot be used without a working tree.
uscan die: 1 at /usr/share/perl5/Devscripts/Uscan/Output.pm line 77.


Is a package bug or local misconfiguration ?


Cheers,
Jerome


Hugh

[1] https://manpages.ubuntu.com/manpages/questing/man1/uscan.1.html



--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calculus@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


Reply to: