Re: tracking new Dapper and Debian sid versions of certain packages

On Sun, Nov 06, 2005 at 04:05:58PM +0100, Herv? Cauwelier wrote:

> Shot - Piotr Szotkowski wrote:
> >What I'm looking for is a way to get notified when one of these packages
> >changes in Dapper, changes in sid or reaches Dapper for the first time.
>
> For Debian, you can subscribe using the Package Tracking System, see for
> instance :
> http://packages.qa.debian.org/z/zope2.7.html>
> Using the form on the middle-left hand, you could be notified when a new
> revision is uploaded, when a report is filed or changed, etc. (see the
> advanced mode).
>
> I'll let our fellow administrators answer if there's such a tool for
> Ubuntu, or when it will be available! ;-)

Well, there is the dapper-changes mailing list (and I think theres
another one for autosyncs from debian)

It'd be *all* packages and somewhat high-traffic, but you could filter
it.

Cheers,
-- Shot
--
I hate leaving Windows 95 boxes publically accessible, so shifting even to
NT is a blessing in some ways. At least I can reboot them remotely in a sane
manner, rather than having to send them malformed packets. -- _BOFHJournal_
====================== http://shot.pl/hovercraft/ === http://shot.pl/1/125/ ===

Re: tracking new Dapper and Debian sid versions of certain packages

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Shot - Piotr Szotkowski wrote:

> Hello.
>
> Thanks, Herv? and Trent, for your prompt replies!
>
> Herv? Cauwelier:
>
>
>>For Debian, you can subscribe using the Package Tracking System
>
>
> This seems to be a very nice tool. It would be great
> if something like this was available in Ubuntu. :o)
>
> I also subscribed to the Dapper Changes
> RSS feed[1], will see how intensive it is.
>
> [1] http://www.ubuntulinux.nl/files/dapper.xml>
> Cheers,
> -- Shot
>

You could always subscribe to the changes lists, and run a filter that
sends all messages to /dev/null unless it contains the names of those
specific packages in the subject. This can be done server side with
procmail or locally on your email client (you'd notice a lot less of the
overhead doing it server side).