Bug#811565: [uscan] git mode: allow for scanning repositories without tags

[Michael Stapelberg]

I think the git HTTP transport does never allow shallow clones. You can use
the git transport protocol (also with GitHub), but note that the git
transport protocol is not authenticated (whereas https is, of course).

So, I think the solution is to only use --depth=1 for git:// URLs.

For GitHub, I’d recommend first translating https URLs into git URLs, then
(later) use the GitHub API.

On Fri, Aug 11, 2017 at 6:51 AM, Osamu Aoki <osamu at debian.org> wrote:

> Hi,
>
> On Thu, Aug 10, 2017 at 09:37:33AM +0200, Michael Stapelberg wrote:
> > Here’s an example: https://github.com/Debian/dh-make-golang/. The
> corresponding
>
> Tested ...
>
> $ git clone --depth=1 --bare https://github.com/Debian/dh-make-golang/ boo
> Cloning into bare repository 'boo'...
> remote: Counting objects: 13, done.
> remote: Compressing objects: 100% (12/12), done.
> remote: Total 13 (delta 0), reused 6 (delta 0), pack-reused 0
> Unpacking objects: 100% (13/13), done.
> $ git clone --depth=1 --bare http://git.ao2.it/tweeper.git foo
> Cloning into bare repository 'foo'...
> fatal: dumb http transport does not support shallow capabilities
> $ git clone  --bare http://git.ao2.it/tweeper.git foo
> Cloning into bare repository 'foo'...
> $
>
> Interesting.  So not all site can work with shallow checkout.
>
> This reminds me of problems I had with git-archive, too.
>
> Before coding further, let me check and test all these sites.
>
>
> Osamu
>
>
>


-- 
Best regards,
Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20170811/50e8d8e2/attachment-0001.html>