Please add ebuilds for version 4.4.5.4 (released 2009-12-24) of net-firewall/shorewall and net-firewall/shorewall6. Copying the existing ebuilds for version 4.4.2.1 works fine. Reproducible: Always Steps to Reproduce:
Vieri, please let me know if you have lost interest in this package. If so, I will take over maintainership and drop the proxy tag.
(In reply to comment #1) > Vieri, please let me know if you have lost interest in this package. If so, I > will take over maintainership and drop the proxy tag. > Hi, I've been on vacation for quite a long time and haven't really had the chance to look into this, especially since 4.4.5 had a few issues. Anyway, today I checked: shorewall-4.4.6 shorewall-lite-4.4.6 and they can be version bumped from earlier ebuilds. However, I have not tested shorewall6 and currently do not have the kernel requirements for it. Tony, if you could take over maintenance you would do me a big favor. Count on me for help whenever possible. I'm interested in Shorewall but don't always have the time to keep up with the latest version. Also, it would be nice to version bump the "older branch": shorewall 4.2.11 (or, if that's too much to maintain, then remove 4.2.x from Gentoo and stick to 4.4, just like voip is doing with Asterisk 1.6 vs 1.4). If you don't have time to maintain Shorewall (now or in the future) then please let me know and I'll make an extra effort because it's a great package and Gentoo *must* have it.
At this time we should have: a) 4.4.7 in testing (keyword ~) b) 4.2.11 stable 4.4.7 (not 4.4.6) is the upstream STABLE release (4.4.6 was a development release), which should be our next candidate for keywording as stable in portage. 4.2.11 is upstream *previous* STABLE release, which we should already be seeking to keyword as stable in portage.
(In reply to comment #3) > 4.4.7 (not 4.4.6) is the upstream STABLE release (4.4.6 was a development > release), which should be our next candidate for keywording as stable in > portage. Clarification: 4.4.7 (not 4.4.6) is the upstream STABLE release, which should be our next candidate for keywording as stable in portage (after 4.2.11). 4.4.6, 4.4.5, 4.4.2, etc., were all development releases. A good strategy for us would be to try to have the upstream "previous stable" (as indicated at http://www.shorewall.net/) marked stable in portage, and to have the upstream "current stable" keyworded "~". This would minimize the burden on the maintainer, because they would only have to handle relatively infrequent stable releases, while still offering Gentoo users reasonably current versions. If the maintainers have time, they could introduce more recent upstream development versions, perhaps masked.
(In reply to comment #4) John, I agree with what you have proposed. I have CC'd you on the stabling bug that results from this approach. 4.4 ebuilds will follow once the 4.2 stabling has run its course. I would also like for a discussion on the init.d script dependencies to be resolved before I proceed.
Thanks, Tony.
It seems the "current stable" upstream is now shorewall-4.4.8 (as opposed to 4.4.7 as we had discussed). So I suppose we might as well aim for 4.4.8 (in ~arch status), once the stabilization bug (309767) is clear.
+*shorewall-4.4.10 (16 Jun 2010) + + 16 Jun 2010; <chainsaw@gentoo.org> + +files/4.4.10-underscore-not-dash.patch, +shorewall-4.4.10.ebuild: + Version bump, for bug #298301 by Magnus Kessler. +*shorewall6-4.4.10 (16 Jun 2010) + + 16 Jun 2010; <chainsaw@gentoo.org> +shorewall6-4.4.10.ebuild: + Version bump, for bug #298301 by Magnus Kessler. +*shorewall-lite-4.4.10 (16 Jun 2010) + + 16 Jun 2010; <chainsaw@gentoo.org> +shorewall-lite-4.4.10.ebuild: + Version bump, for bug #298301 by Magnus Kessler. +*shorewall6-lite-4.4.10 (16 Jun 2010) + + 16 Jun 2010; <chainsaw@gentoo.org> +shorewall6-lite-4.4.10.ebuild: + Version bump, closes bug #298301 by Magnus Kessler. Magnus, thank you for your bug report. Please file a new bug if you find any problems with the ebuilds that just got added to the portage tree. (Please wait two hours before you call emerge --sync)
