Re: DUCK Status update, RFC
On Wed, Jan 2, 2013 at 10:49 PM, Simon Kainz wrote:
> I added the checks for SVN repos, which now leads to ~2700 binary
> packages with issues.
> To link to a specific package(from PTS), you may now use
> the parameter package=<packagename> like this:
> I am currently thinking about a way to check (amongst other vcs systems)
> git repos, without cloning the full repo - maybe just fetch some file
> from inside the repo? Someone has some idea how this might be done?
> Basically bandwith is no issue, but it seems a bit overkill to me, to
> _really_ check out git repos.
For the ssh:// URLs (with any VCS), you should list an error since
those aren't public.
For the git:// URLs and Vcs-Git http/https URLs it looks like git
ls-remote is the command to use:
git ls-remote git://git.debian.org/collab-maint/duck.git
For mercurial you can use hg id:
hg id http://hg.icculus.org/icculus/aquaria/
For bzr can use bzr info or package and use the ping plugin:
bzr info lp:bzr
For CVS you can do this:
cvs -d ':pserver:email@example.com:/cvs/webwml' ls .
Couldn't find anything for darcs but it often uses http/https so just
check as per usual I guess.
Also, please check the Vcs-Browser headers if you aren't already.