[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: DUCK -the Debian Url Checker



On 06/11/12 21:08, Axel Beckert wrote:
> Hi Simon,
Hi Axel,
> 
> Simon Kainz wrote:
>> as I had some problems in the past finding upstream sources and
>> homepages, I hacked up some scripts to monitor and display the results
>> of the Upstream Homepage entries in the package control files.
>>
>> Please take a look at http://debian.tugraz.at/duck/
> 
> Very cool! And I like that name! :-)
> 
>> Currently the job runs once a day and the results are displayed. Maybe
>> this is of some use for some maintainers and/or developers.
> 
> Indeed!
> 
>> One can also search for specific maintainers.
> 
> Could you also treat uploaders like maintainers (or similar, i.e. add
> some [U] flag if someone is just an Uploader as seen elsewhere in
> Debian)? That would help people who are also active in teams but don't
> help to maintain all packages in the team.
> 

ok, I'll think about that - good idea.

> Another thing I noticed:
> http://debian.tugraz.at/duck/?maintainer=pkg-wml-maintainers@lists.alioth.debian.org
> -- if I click on the link the ftp directory shows up perfectly in my
> browser. Any idea why it's regarded as broken?

Umm, yes - that is a false positive: FTP return 226/227, which tells me
the file transfer was successful (
http://en.wikipedia.org/wiki/List_of_FTP_server_return_codes ). I
treated codes >200 as "warning", so it showed up in the list - sorry,
I'll fix this.

> 
> Michal already suggested to check also debian/copyright. I would also
> love to see to have Vcs-*, at least Vcs-Browser checked. Actually
> today I noticed a package where the Vcs repo location moved and is no
> more uptodate (mssh FWIW).

Code for VCS-* is already there ( in fact, I started with this some
weeks ago). I definitly will incorporate VCs-* check results in the
list. Also I'm working on code for links found in Description: fields.


> 
> Anyway, already now this is a great service!
> 

Thanks !
> 		Regards, Axel

Cheers, Simon


Reply to: