| 1 |
This email is mostly for Swift and gizmo, but anyone can have their input. |
| 2 |
|
| 3 |
I've been running a SELinux system for the last month or so since I've |
| 4 |
uploaded the massive work done by Swift and gizmo. There was one major |
| 5 |
bug we noticed right away, and Swift got it, namely bugs #355745 and |
| 6 |
#356533 --- dups. After that, it looks pretty clean. |
| 7 |
|
| 8 |
I'm think we should go for stabilization --- I'm not sure how since the |
| 9 |
arch teams are going to say they really can't test this for us, and as |
| 10 |
they did with other packages, will probably defer the judgment back to |
| 11 |
us. If we do, we should take this responsibility very seriously because |
| 12 |
the arch teams, if nothing else, are a double check on our work. |
| 13 |
|
| 14 |
So far I see only a few bugs that need addressing still in bugzilla. |
| 15 |
(The bug reports are a bit disorganized because of how they were |
| 16 |
assigned. We're going to be assigning selinux bugs to |
| 17 |
selinux@g.o for easy lookup.) |
| 18 |
|
| 19 |
I think these are blockers to stabilization. Any others you want to add |
| 20 |
to the list? |
| 21 |
|
| 22 |
#355675 - No brainer. I'll test the patch there this afternoon and put |
| 23 |
it on the tree later if it works. |
| 24 |
|
| 25 |
#346563 - sounds like a profile problem, but I'm not sure its valid |
| 26 |
|
| 27 |
-- |
| 28 |
Anthony G. Basile, Ph.D. |
| 29 |
Gentoo Developer |
Archives