On Sun, 1 Feb 2009 01:23:40 +0100 Michelle Konzack <linux4michelle@tamay-dogan.net> wrote: > > I'll have to see about a smaller icon - or maybe just pinch the Debian > > swirl RSS logo. (The one used by > > http://ftp-master.debian.org/rss/removals.rss etc.) I'll rename it for > > the location already specified in the feeds so it'll just appear. > > I have not found the Icon, so I have included my one... Thanks - been at work all day, should have mentioned that I wouldn't get around to that until Sunday. > > An extra feed we probably need is per-package as well as the content > > gained from parsing the logs. i.e. > > > > To track single packages in Crush: > > http://devel.debian.tamay-dogan.net/rss.php?action=fetch&what=crush&package=PKG > > where PKG is a single source package name. > > <http://devel.debian.tamay-dogan.net/rss.php?action=rss&what=crush&package=apt> > <http://devel.debian.tamay-dogan.net/rss.php?action=rss&what=crush&package=debian-archive-keyring> > > But currently I have problems detecting whether a build was successfully > or not... At the "apt" build it fails, but it works for the > "debian-archive-keyring"... That's correct - if I'm reading it right. The apt build currently has failed and the debian-archive-keyring build was OK. > > That could allow individual Debian maintainers watch feeds for their > > own packages. If you really want to, that could be tied into dd-list > > and feeds provided via maintainer name for all their packages and we > > could put a link to that feed on the DDPO pages: > > http://qa.debian.org/developer.php?login=codehelp@debian.org > > e.g. > > http://devel.debian.tamay-dogan.net/rss.php?action=fetch&what=crush&login=$LOGIN > > http://devel.debian.tamay-dogan.net/rss.php?action=fetch&what=grip&login=$LOGIN > > OK, but this make the thing realy more complex and resources consuming > because I have to know, which source is associated with which maintainer. dd-list does all that for you. Pass it the source package name and it gives you the list of maintainers and uploaders which then need parsing into an array or something similar. That does mean having devscripts installed. $ dd-list apt APT Development Team <deity@lists.debian.org> apt Luca Bruno <lethalman88@gmail.com> apt (U) Daniel Burrows <dburrows@debian.org> apt (U) Eugene V. Lyubimkin <jackyf.devel@gmail.com> apt (U) Christian Perrier <bubulle@debian.org> apt (U) Otavio Salvador <otavio@debian.org> apt (U) Michael Vogt <mvo@debian.org> apt (U) dd-list itself is a perl script. Of course, what you need is almost the reverse - to look up the login and get the list of packages in Crush relevant to that login. dd-list actually relies on apt-cache to do the work. In perl, I'd use the Parse::Debian::Packages module which is actually a very trivial module and very fast. The Packages file is always up to date so it would be a good way of getting whatever data isn't directly obtainable from the build log. http://www.emdebian.org/emdebian/dists/$suite/main/binary-$ARCH/Packages There are probably other ways of getting the data you would need for this. Feel free to mark this as a wishlist or RFE and see if others can give you simpler ways of obtaining the data once the rest of the process is working. > In the successfull build I have > > Maintainer: Daniel Kobras <kobras@debian.org> > Changed-By: Neil Williams <codehelp@debian.org> > > but how can I get the maintainer of non-successfull builds? >From the source package name (which you already have) and dd-list or the Packages file. > > A link to the search results for the package would be good too: > > For Crush: (assume always arm for now) > > http://www.emdebian.org/packages/search.php?package=ucf&arch=arm > > For Grip: > > http://www.emdebian.org/grip/search.php?package=ucf&arch=arm > > OK Added... Excellent, thank you. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
pgp8aATOGLP75.pgp
Description: PGP signature