public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <basile@opensource.dyc.edu>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] SELinux bughunt
Date: Fri, 22 Jul 2011 06:37:43 -0400	[thread overview]
Message-ID: <4E2952F7.9070702@opensource.dyc.edu> (raw)
In-Reply-To: <20110721100629.GA23460@siphos.be>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 07/21/2011 06:06 AM, Sven Vermeulen wrote:
> Hi guys,
> 
> The SELinux bugs are "piling" up but most of them are resolved and I'd like to
> use the STATUS field to keep track of which bugs are actually still open...
> 
> Considering the available states in the status field in bugzilla, I think it
> is a nice idea to say:
> 
>   UNCONFIRMED = reported, not taken up
>   CONFIRMED   = reported and considered valid
>   IN_PROGRESS = taken up by a developer, fix might be available (ask developer)
>   RESOLVED    = fix available, waiting QA. Fix might be in hardened-dev.git
>                 or another overlay
>   VERIFIED    = fix available and accepted. Fix might be in ~arch
>   FIXED       = fix available and in portage tree "arch" status
> 
> I know it looks like some bureaucratic nonesense for some, but at least that
> allows poor developers like me to see which bugs are still open for grabs,
> which are awaiting stabilization, which still needs to be pushed to portage
> tree, etc.
> 
> Considering the above (but also recent updates and fixes), the following
> bugs need to be altered. Perhaps someone can take care of this for me?
> 
> #283274 - Mark as FIXED
> #134129 - Mark as WONTFIX (we do not support SELinux and PPC)
> #274239 - Mark as FIXED
> #306393 - Mark as VERIFIED
> #257111 - Mark as VERIFIED
> #275085 - Mark as RESOLVED
> #211374 - Mark as IN_PROGRESS
> #368795 - Mark as RESOLVED
> #365761 - Mark as CONFIRMED
> #370765 - Mark as RESOLVED NEEDINFO + comment that the bug needs to be reopened then
> #371831 - Mark as RESOLVED
> #369089 - Mark as VERIFIED
> #371425 - Mark as VERIFIED
> #374991 - Mark as FIXED
> #375475 - Mark as CONFIRMED
> #375617 - Mark as IN_PROGRESS
> #373381 - Mark as CONFIRMED
> 
> Thanks in advance.
> 
> Wkr,
> 	Sven Vermeulen

I'll get them.



- -- 
Anthony G. Basile, Ph. D.
Chair of Information Technology
D'Youville College
Buffalo, NY 14201
(716) 829-8197
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEAREIAAYFAk4pUvcACgkQl5yvQNBFVTUjUwCff769Pq00bDYBgmWSqhnLxFVN
POEAnj1UsjVzPS4k61W+IVElkK1L8k/0
=J3Sv
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2011-07-22 10:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21 10:06 [gentoo-hardened] SELinux bughunt Sven Vermeulen
2011-07-21 13:47 ` Chris Richards
2011-07-21 13:55   ` Sven Vermeulen
2011-07-22 10:37 ` Anthony G. Basile [this message]
2011-07-22 14:27   ` d hee
2011-07-22 15:08     ` Sven Vermeulen
2011-07-22 18:07       ` d hee
2011-07-22 19:33         ` Anthony G. Basile
2011-07-23 20:54           ` d hee
2011-07-24  1:30             ` Mike Edenfield
2011-07-26  7:06               ` d hee
2011-07-24 12:16             ` Magnus Granberg
2011-07-24 20:29               ` d hee
2011-07-26  6:45                 ` d hee
2011-07-26 15:19   ` d hee

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=4E2952F7.9070702@opensource.dyc.edu \
    --to=basile@opensource.dyc.edu \
    --cc=gentoo-hardened@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