public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Brian Harring <ferringb@gmail.com>
Subject: [gentoo-dev] Security/QA Spring Cleaning
Date: Sun, 21 May 2006 23:02:22 -0400	[thread overview]
Message-ID: <1148266942.19708.90.camel@localhost> (raw)

ferringb took the time to write a parser and setup a cronjob 
(every 4 hours at the half hour) to parse over our GLSA's and see what 
pkgs remain in the tree and have nothing but newer versions stable. I
did a bit of re parsing on his logfile to obtain herds & maintainers.
The list is big (very big) and like if I filed the bug in it's current
state pretty much every single one of us would probably get dozens of
mails per comment. So.. To in order to try and be nice to our mail
system and bugzilla it would be really helpful if you all could grep
the affected: field and flush old vulnerable ebuilds from the tree for
any pkgs you or your herd maintain before the tracker bug is filed.

http://gentooexperimental.org/~ferringb/reports/tree-vulnerabilities.log

In the future if you are bumping pkgs for a security bug and you are 
the last arch to push to stable. Clean up old foo up please. 
It keeps everything running smoother and faster to have less 
dead cruft in the tree.

You can use earch for this task.

wget -O /usr/local/bin/earch -q \ 
 http://dev.gentoo.org/~robbat2/earch-0.9.1 \
 && chmod +x /usr/local/bin/earch 
It helps to make it a habit to run this before repoman --pretend scan
prior to committing to the tree.

thanks in advance.

-- 
Ned Ludd <solar@gentoo.org>
All over the place
Gentoo Linux

-- 
gentoo-dev@gentoo.org mailing list



             reply	other threads:[~2006-05-22  3:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-22  3:02 Ned Ludd [this message]
2006-05-22  5:25 ` [gentoo-dev] Security/QA Spring Cleaning Robin H. Johnson
2006-05-22  5:30   ` Brian Harring
2006-05-23 20:22 ` Ned Ludd
2006-05-23 20:44   ` Brian Harring
2006-05-23 22:44     ` Thomas Cort
2006-05-23 20:51   ` Chris Gianelloni
2006-05-23 21:06     ` Brian Harring
2006-05-23 21:46       ` Chris Gianelloni
2006-05-23 22:05         ` Brian Harring
2006-05-23 22:24           ` Chris Gianelloni
2006-05-23 22:36             ` Brian Harring
2006-05-24  4:11               ` Doug Goldstein
2006-05-24 12:06                 ` Chris Gianelloni
2006-05-24 12:02               ` Chris Gianelloni
2006-05-23 21:50     ` Ned Ludd
2006-05-23 22:22       ` Chris Gianelloni
2006-05-28 18:20   ` Ned Ludd
2006-05-28 20:18     ` Robin H. Johnson
2006-05-29  1:17       ` Ned Ludd
2006-05-29 20:22     ` Chris Gianelloni
2006-06-02 13:15     ` Eldad Zack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1148266942.19708.90.camel@localhost \
    --to=solar@gentoo.org \
    --cc=ferringb@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox