On Tue, Oct 14, 2008 at 6:14 PM, Abhishek Dasgupta wrote:

Hi all,

I've created a web based report [1] from running namcap on the [community] tree. The design is inspired by lintian reports [2] (I am not much of a designer anyway :) )

There's a script which makes the namcap.log by traversing the community tree, then another python script cooks it up into HTML. Since namcap is quite verbose, I created some tags corresponding to the namcap warnings/errors (like: bad-backups => Backup entries should not have preceeding slashes). The packages have been listed by the namcap tag. Right now there's no view of what tags a particular package has, but I plan to add it sometime in the future. There's also an RSS feed for each tag.

[1]: http://abhidg.mine.nu/arch/namcap-reports [2]: http://lintian.debian.org

This is really cool! How long does it take to parse all of community? -- Callan Barrett

Callan Barrett wrote:

On Tue, Oct 14, 2008 at 6:14 PM, Abhishek Dasgupta wrote:

...

Hi all,

I've created a web based report [1] from running namcap on the [community] tree. The design is inspired by lintian reports [2] (I am not much of a designer anyway :) )

There's a script which makes the namcap.log by traversing the community tree, then another python script cooks it up into HTML. Since namcap is quite verbose, I created some tags corresponding to the namcap warnings/errors (like: bad-backups => Backup entries should not have preceeding slashes). The packages have been listed by the namcap tag. Right now there's no view of what tags a particular package has, but I plan to add it sometime in the future. There's also an RSS feed for each tag.

[1]: http://abhidg.mine.nu/arch/namcap-reports [2]: http://lintian.debian.org

This is really cool! How long does it take to parse all of community?

Good work. I am a bit disappointed about the number of packages without license information, especially due to the amount of work BaSh (and others?) put into fixing this. Allan

On Tue, Oct 14, 2008 at 2:44 PM, Abhishek Dasgupta wrote:

Thanks to all of you for your comments! As Xavier suggested, the reports are now for all the repos except testing. I didn't add testing because there would be package name duplication in the log which would confuse the script. Right now there's no way to distinguish between the packages from the different repos, though.

Nice job :) I think testing is not so important, these packages end up in core or extra anyway. But a way to distinguish is indeed a good idea!

On Tue, Oct 14, 2008 at 4:11 PM, Aaron Griffin wrote:

I'm with Callan and Xavier here - this is awesome.

Sure! Now, if only it could be possible to filter by maintainer...

2008/10/14 Aaron Griffin :

On Tue, Oct 14, 2008 at 6:11 AM, Xavier wrote:

...

On Tue, Oct 14, 2008 at 12:43 PM, Callan Barrett wrote:

...

This is really cool! How long does it take to parse all of community?

Indeed, maybe it could be extended to core and extra, and maybe testing too? That is, all official repos available through abs.

I'm with Callan and Xavier here - this is awesome.

awesome++ wood love to see this integrated in Dev Dashboard and AUR -- Roman Kyrylych (Роман Кирилич)

On Tue, Oct 14, 2008 at 7:14 PM, Abhishek Dasgupta wrote:

Hi all,

I've created a web based report [1] from running namcap on the [community] tree. The design is inspired by lintian reports [2] (I am not much of a designer anyway :) )

There's a script which makes the namcap.log by traversing the community tree, then another python script cooks it up into HTML. Since namcap is quite verbose, I created some tags corresponding to the namcap warnings/errors (like: bad-backups => Backup entries should not have preceeding slashes). The packages have been listed by the namcap tag. Right now there's no view of what tags a particular package has, but I plan to add it sometime in the future. There's also an RSS feed for each tag.

[1]: http://abhidg.mine.nu/arch/namcap-reports [2]: http://lintian.debian.org

What happened with this? I was really looking forward to seeing something like this go official. Hopefully something did go ahead and I've completely missed it! -- Callan Barrett

2008/11/30 Abhishek Dasgupta :

...

What happened with this? I was really looking forward to seeing something like this go official. Hopefully something did go ahead and I've completely missed it!

Today, I wrote a Makefile to automate the report generation, ABS checkout, etc. Otherwise there's not been much change... I've not yet added support for the new tags (mandir incorrect, and optdepends checking which are supported by namcap 2.2). I don't have sufficient django-fu to port it to a django based site, but it can be safely put in a folder and made to run with a cronjob.

Happy new year to everyone! namcap-reports is set to run everyday at 1000 UTC now, I'll be producing a graph of errors/warnings after a fortnight or so. I've also separated out most of the HTML into template files. namcap-reports now requires a configuration file where the output and template directories can be specified. Previously everything used to take place in the code folder itself. -- Abhishek