Package: git-debpush
Version: 13.11
Severity: wishlist

src:gnome-desktop (among others) has an empty (0 byte) .gitmodules at 
top level. I'm assuming this means that upstream previously used 
submodules, decided they were not the right answer, and did the 
necessary amount of `git rm -r` to stop using them, but did not go as 
far as also deleting the resulting 0-byte metadata file. I've 
successfully uploaded projects in this situation with dgit in the past: 
because there are no actual submodules, they pass the "git tree == 
result of unpacking .dsc" check.

When I tried uploading src:gnome-desktop with `git debpush`, the tool 
complained about the apparent existence of submodules, but when I told 
it to ignore the potential problem:

git-debpush: check failed: git submodule(s) detected; these are not supported 
('submodule' check)
git-debpush: proceed anyway? (y/N) y
git-debpush: fetching from https://salsa.debian.org/gnome-team/gnome-desktop to 
check existing state
...

everything seems to have gone well, uploading version 44.3-4 via 
tag2upload job ID 500.

Would it be possible to skip this check if .gitmodules is completely 
empty (0 bytes)?

(Perhaps even if it exists but contains only whitespace? But that's 
probably harder to achieve, since it would require dgit/git-debpush to 
actually look at and understand the file contents, not just the 
filesystem metadata.)

Thanks,
    smcv

Reply via email to