Requesting STABILIZATION of net-firewall/shorewall-{common,perl,shell,lite}-4.0.15 and REMOVAL of <net-firewall/shorewall-{common,perl,shell,lite}-4.0.15 Reproducible: Always
stabilization... it's a bit too fast. We have policy: ebuilds should sit in ~arch for one month. So I'll try not to forget about this, but if I do, just ping this bug and we CC archs. Thank you for you help.
ping ;-) Letting you CC whenever you want to.
Thank you, Vieri for notification. arch teams, please do it. Old ebuilds removed.
amd64/x86 stable
None of those is keyworded on alpha: -lite-4.0.15 -perl-4.0.15 Want us to keyword them and stabilize in a month? Or just stabilize -common and -shell?
(In reply to comment #5) > None of those is keyworded on alpha: > -lite-4.0.15 > -perl-4.0.15 keyword and stabilize in a month, please.
ppc64 done
ppc done
How about putting in net-firewall/shorewall-4.2.8 into the tree and getting that stabilized since it can handle ip6 also.
(In reply to comment #9) > How about putting in net-firewall/shorewall-4.2.8 into the tree and getting > that stabilized since it can handle ip6 also. shorewall-4.2.8 will hopefully be added to the tree soon. However, the fact that 4.2 supports ipv6 does not imply that it should be stabilized (the portage tree already has previous 4.2 versions with ipv6). In fact, 4.2 has had many subsequent releases and patch fixes lately for several bugs. Anyway, if you disagree, please open a specific bug report. This bug is only for STABLEREQ'ing 4.0.15 which is still in progress.
Stable for HPPA.
Sparc, please action bug #309767 instead. Thank you.