Re: Bug#173824: Not good.

[Aaron Hall <lisps@vitaphone.net>]

[cc'd to Alexander as requested]

On Mon, 6 Jan 2003, Alexander Hvostov wrote:

> On Mon, 2003-01-06 at 09:51, Matt Zimmerman wrote:

[large snips]

> > You can get all of this information by subscribing to debian-devel-changes,
> > which receives a message with a copy of the .changes file for every upload
> > (at least accepted uploads).  The .changes file format is trivial to parse.
>
> That, on the other hand, I can do.

I (and I'm sure many others) do something similiar, checking
debian-devel-changes for changes to installed packages for this reason.
Here's the procmail recipe I use for such:

# catch debian-devel-changes mails, and weed out those we aren't
# interested in

:0
* ^X-Mailing-List.*debian-devel-changes@lists.debian.org
{
        # PKG_FILE is a file with the names of all installed
        # packages, one per line
        PKG_FILE=$HOME/lib/package_regexs

        # The "Binary:" line contains the binary packages
        # the update covers
        IN_PKGS = `sed -n '/^Binary: /s/Binary: //p'`

        :0:
        * ? echo $IN_PKGS | egrep -f $PKG_FILE
        $MAILDIR/L-deb-changes

        :0 E
        /dev/null
}

PKG_FILE is generated out of cron, and looks like this:

(^| )adduser( |$)
(^| )ae( |$)
(^| )analog( |$)
(^| )apache( |$)
(^| )apache-common( |$)
(^| )apache-ssl( |$)
(^| )apt( |$)

...and so on. I'm not claiming it's good, just that it works for me, and
maybe it will help someone else. Heaven knows I've gotten enough good
from Debian. :)

(If someone does have ideas for improve it, I'd love to know. I'm sure
it could be made more efficient, for example.)

Thanks,
Aaron

-- 
Aaron Hall           :              Sleep, where is thy sting?
ahall@vitaphone.net  :              Bed, where is thy victory?
                     :                            -- Insomnia? Me?