Thanks for the bug report, McSinyx, and the first tests, Sebastian!
On 31.03.2023 12:09, Sebastian Crane wrote:
On Thu, Mar 30, 2023 at 05:47:19PM +0900, McSinyx wrote:
I am wondering about the difference between the following outputs:
https://api.reuse.software/info/trong.loang.net/~cnx/rub https://xong.loang.net/log/reuse/7
I was able to reproduce this in a local instance of the API. This is the output:
$ docker run --rm reuse-api-worker-runner https://trong.loang.net/~cnx/rub Cloning into '/project'... fatal: dumb http transport does not support shallow capabilities reuse.project - WARNING - could not find supported VCS # SUMMARY
- Bad licenses:
- Deprecated licenses:
- Licenses without file extension:
- Missing licenses:
- Unused licenses:
- Used licenses:
- Read errors: 0
- Files with copyright information: 0 / 0
- Files with license information: 0 / 0
Congratulations! Your project is compliant with version 3.0 of the REUSE Specification :-)
The clone command looks like the following (more or less):
git clone --depth 1 https://trong.loang.net/~cnx/rub
The clone fails because a shallow clone isn't supported. Therefore, the /project directory is empty.
So your server only seems to support the "Dumb HTTP" protocol and not Smart HTTP or Git protocols [1]. This honestly is the first time this issue occurred, and we have a number of repos from self-hosted Git forges.
Would it be possible for you to enable one of the other protocols on your server?
Otherwise, we'd have to tweak the API worker to not attempt a shallow clone (which saves *a lot* of bandwidth and time) if only the dumb protocol is present [2]. However, unless someone contributes to this, that may take a while as we have other priorities currently.
Best, Max
[1]: https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
[2]: https://git.fsfe.org/reuse/api-worker/src/branch/master/docker-image/check-g...