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
On Tue, Oct 14, 2008 at 6:14 PM, Abhishek Dasgupta abhidg@gmail.com 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.
This is really cool! How long does it take to parse all of community?
On Tue, Oct 14, 2008 at 12:43 PM, Callan Barrett wizzomafizzo@gmail.com 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.
On Tue, Oct 14, 2008 at 6:11 AM, Xavier shiningxc@gmail.com wrote:
On Tue, Oct 14, 2008 at 12:43 PM, Callan Barrett wizzomafizzo@gmail.com 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.
On Tue, Oct 14, 2008 at 4:11 PM, Aaron Griffin aaronmgriffin@gmail.com wrote:
I'm with Callan and Xavier here - this is awesome.
Sure! Now, if only it could be possible to filter by maintainer...
On Tue, Oct 14, 2008 at 07:08:27PM +0200, bardo wrote:
On Tue, Oct 14, 2008 at 4:11 PM, Aaron Griffin aaronmgriffin@gmail.com wrote:
I'm with Callan and Xavier here - this is awesome.
Sure! Now, if only it could be possible to filter by maintainer...
Thanks! I've added the core, extra and community tags to the reports with a bit of javascript to allow toggling between the repositories.
I'm working on adding listing by maintainer, the thing is what should the URLs contain? The email or the name of the maintainer? In case of email while for most it is OK, some maintainers have encoded their email to evade spam bots, so it can't be used as is. If I use names then the URLs can become long (and what happens if there are accented characters in the name?).
While I can use numerical indexing (like in archlinux.de), it is unintuitive, so I would prefer some other approach (if there's any).
2008/10/14 Aaron Griffin aaronmgriffin@gmail.com:
On Tue, Oct 14, 2008 at 6:11 AM, Xavier shiningxc@gmail.com wrote:
On Tue, Oct 14, 2008 at 12:43 PM, Callan Barrett wizzomafizzo@gmail.com 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
On Sun, Oct 19, 2008 at 9:21 PM, Roman Kyrylych roman.kyrylych@gmail.com wrote:
2008/10/14 Aaron Griffin aaronmgriffin@gmail.com:
On Tue, Oct 14, 2008 at 6:11 AM, Xavier shiningxc@gmail.com wrote:
On Tue, Oct 14, 2008 at 12:43 PM, Callan Barrett wizzomafizzo@gmail.com 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
Yeah, it doesn't sound like it's resource hungry. I'd love to see this running on the main website.
Callan Barrett wrote:
On Tue, Oct 14, 2008 at 6:14 PM, Abhishek Dasgupta abhidg@gmail.com 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.
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
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.
On Tue, Oct 14, 2008 at 06:43:49PM +0800, Callan Barrett wrote:
This is really cool! How long does it take to parse all of community?
Generating namcap.log for core, extra and community took three minutes on my desktop (core 2). After that, the report generation takes a second or two.
I also fixed the RSS pubDate to be that of namcap.log's modification time, as that makes more sense.
On Tue, Oct 14, 2008 at 2:44 PM, Abhishek Dasgupta abhidg@gmail.com 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 7:14 PM, Abhishek Dasgupta abhidg@gmail.com 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.
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!
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.
2008/11/30 Abhishek Dasgupta abhidg@gmail.com:
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.
aur-general@lists.archlinux.org