Hello Neil,
Am 2009-01-31 08:01:17, schrieb Neil Williams:
> 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...
> 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"...
> It is harder to track single packages in Grip - that would need to get
> data from the Packages.gz file as well as the buildlog.
For now I try to get Crush running... One thing after one... ;-)
> It could also be good if, wherever the content does relate to a single
> package, each item would contain a link to the Emdebian patch sets which
> can be generated from the source package name:
>
> $base="http://buildd.emdebian.org/svn/browser/current/target/trunk";;
> $url="$base/$initial/$srcpackage/trunk/";
OK included...
> 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.
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?
I have found only your E-Mail by greping for
dpkg-buildpackage: source changed by
> (There will be quite a few empty feeds from that method though.)
>
> 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...
Thanks, Greetings and nice Day/Evening
Michelle Konzack
Systemadministrator
24V Electronic Engineer
Tamay Dogan Network
Debian GNU/Linux Consultant
--
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
<http://www.tamay-dogan.net/> <http://www.can4linux.org/>
Michelle Konzack Apt. 917 ICQ #328449886
+49/177/9351947 50, rue de Soultz MSN LinuxMichi
+33/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com)
Attachment:
signature.pgp
Description: Digital signature