Re: DUCK Status update, RFC
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 01/02/13 17:38, schrieb Paul Wise:
> 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.
>
> Cool.
>
>> To link to a specific package(from PTS), you may now use
>>
>> the parameter package=<packagename> like this:
>>
>> http://zidpc9027.tugraz.at/duck/index.php?package=xtermset
>
> Great!
>
>> 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.
You
>
> 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
> http://doc.bazaar.canonical.com/plugins/en/ping-plugin.html
>
> For CVS you can do this:
>
> cvs -d ':pserver:anonymous@anonscm.debian.org:/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.
>
Thank you!! I'll integrate as many VCSs as i can.
Concerning VCS-Browser: It basically works, but i get killed off after
some requests, seems to be some kind of connection rate limiting or
some clever iptables rule. I'm currently talking with the alioth admin
team to resolve this issue.
Simon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlDlglMACgkQEtt57sR2O6XkbgCeIQo2675yNjS70iGPQQiZsQEq
3EoAoImmlwVUUIa/288DTCERk3T+cWTh
=0lj7
-----END PGP SIGNATURE-----
Reply to: