New Shorewall structure: - shorewall base package - shorewall-shell traditional compiler - shorewall-perl new compiler - shorewall-lite Reproducible: Always
Created attachment 116237 [details] shorewall-3.9.1 ebuild
Created attachment 116238 [details] shorewall-shell-3.9.1 ebuild
Created attachment 116240 [details] shorewall-perl-3.9.1 ebuild
Created attachment 116241 [details] shorewall-lite-3.9.1 ebuild
Proposing new ebuilds for the upcoming 4.0.0 release. These ebuilds are currently based on the Beta4 packages but can easily be updated to use the stable 4.0.0 as soon as it comes out. The following is commented out because I don't know how to avoid cyclic dependencies (if anyone could help out...): #RDEPEND="|| ( # >=net-firewall/shorewall-shell-4.0.0 # >=net-firewall/shorewall-perl-4.0.0 # )" (Gentoo users are invited to test Shorewall-4.0.0-Beta with these ebuilds and report back your experiences to the shorewall-devel mailing list. For better feedback in case of encountering errors you should also grab the latest revision from Shorewall's SVN.)
Created attachment 121927 [details] shorewall-4.0.0-Beta4 ebuild
Created attachment 121928 [details] shorewall-lite-4.0.0-Beta4 ebuild
Created attachment 121929 [details] shorewall-shell-4.0.0-Beta4 ebuild
Created attachment 121931 [details] shorewall-perl-4.0.0-Beta4 ebuild
I would also like to request the removal of shorewall-perl-3.9.0 from portage.
Created attachment 123920 [details] 4.0-aware net-firewall/shorewall-3.4.4 ebuild I think that RDEPEND="!net-firewall/shorewall-common !net-firewall/shorewall-shell !net-firewall/shorewall-perl" should be added to all shorewall ebuilds in portage. The 3.4.4 ebuild is proposed here. Please also refer to http://bugs.gentoo.org/show_bug.cgi?id=182544
Created attachment 123922 [details] net-firewall/shorewall-4.0.0 ebuild (Beta 7) dummy ebuild (now "shorewall" should not exist anymore; only shorewall-common, -perl and -shell)
Created attachment 123923 [details] net-firewall/shorewall-common-4.0.0 (Beta 7) new ebuild
Created attachment 123925 [details] net-firewall/shorewall-lite-4.0.0 (Beta 7)
Created attachment 123927 [details] net-firewall/shorewall-perl-4.0.0 (Beta 7)
Created attachment 123928 [details] net-firewall/shorewall-shell-4.0.0 (Beta 7)
Shorewall will be split into shorewall-common, shorewall-shell and shorewall-perl. shorewall-lite will remain as such.
Created attachment 124117 [details] net-firewall/shorewall-common-4.0.0 (RC1) Release Candidate 1 available. Also minor ebuild fix regarding download URL. The other ebuilds should be manually edited and make sure that: MY_P_BETA="-RC1" Unmerge previous betas, if any, before emergeing RC1.
Created attachment 125677 [details] net-firewall/shorewall-common-4.0.0 (stable release) Stable 4.0.0 has been released. All proposed ebuilds should be changed to reflect: MY_P_TREE="4.0" # stable MY_P_BETA="" # stable or experimental The attached shorewall-common ebuild has also a few fixes.
shorewall-common Version 4.0.0 Installed cp: stat "/usr/local/portage/net-firewall/shorewall-common/files/shorewall-r2" sikertelen: Nincs ilyen f**l vagy k**yvt** * * ERROR: net-firewall/shorewall-common-4.0.0 failed. * Call stack: * ebuild.sh, line 1648: Called dyn_install * ebuild.sh, line 1083: Called qa_call 'src_install' * ebuild.sh, line 44: Called src_install * shorewall-common-4.0.0.ebuild, line 48: Called die * * doinitd failed * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/net-firewall/shorewall-common-4.0.0/temp/build.log'. * This ebuild is from an overlay: '/usr/local/portage/'
cp: cannot stat `/usr/local/portage/net-firewall/shorewall-common/files/shorewall-r2': No such file or directory
(In reply to comment #21) > cp: cannot stat > `/usr/local/portage/net-firewall/shorewall-common/files/shorewall-r2': No such > file or directory > Just copy over files/shorewall-r2 from /usr/portage/net-firewall/shorewall-common to /usr/local/portage/net-firewall/shorewall-common.
(In reply to comment #22) > Just copy over files/shorewall-r2 from > /usr/portage/net-firewall/shorewall-common to I meant /usr/portage/net-firewall/shorewall...
4.0.1 is out (netmon pretty please)
Created attachment 126468 [details] net-firewall/shorewall-4.0.1 ebuild (stable)
Created attachment 126469 [details] net-firewall/shorewall-common-4.0.1 (stable) Minor changes (less einfo). -shell and -perl are trivial (version bump)
4.0.2 has been released. Would be nice to have it go into portage and 3.4 stabilized.
Finally made it into the tree Added you to metadata so you can pick up any dev and pester him to bump ebuilds if I'm not there or slacking or whatever ;)
Thanks Markus. I'm reopening this bug instead of opening another one because it's directly related to these new ebuilds. ---- # emerge -pv shorewall These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] net-firewall/shorewall-shell-4.0.3 69 kB [ebuild N ] net-firewall/shorewall-common-4.0.3 USE="doc" 2,395 kB [ebuild N ] net-firewall/shorewall-4.0 0 kB [blocks B ] <net-firewall/shorewall-4.0.0 (is blocking net-firewall/shorewall-common-4.0.3, net-firewall/shorewall-shell-4.0.3) Total: 3 packages (3 new, 1 block), Size of downloads: 2,464 kB ---- If I edit shorewall-common, shorewall-shell and shorewall-perl ebuilds and change: DEPEND="... !<net-firewall/shorewall-4.0.0" to DEPEND="... !<net-firewall/shorewall-4.0" the blocking issue is solved. ---- # emerge -pv shorewall shorewall-perl These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] net-firewall/shorewall-shell-4.0.3 69 kB [ebuild N ] net-firewall/shorewall-common-4.0.3 USE="doc" 2,395 kB [ebuild N ] net-firewall/shorewall-4.0 0 kB [ebuild N ] net-firewall/shorewall-perl-4.0.3 98 kB Total: 4 packages (4 new), Size of downloads: 2,562 kB
corrected :) thankies
Did you guys ever thought of a sceenario where shorewall already is installed? merc ~ # emerge -ua shorewall These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] net-firewall/shorewall-4.0 [3.4.6] [ebuild N ] net-firewall/shorewall-shell-4.0.3 [ebuild N ] net-firewall/shorewall-common-4.0.3 USE="-doc" [blocks B ] <net-firewall/shorewall-4.0 (is blocking net-firewall/shorewall-common-4.0.3, net-firewall/shorewall-shell-4.0.3) !!! Error: The above package list contains packages which cannot be installed !!! at the same time on the same system. For more information about Blocked Packages, please refer to the following section of the Gentoo Linux x86 Handbook (architecture is irrelevant): http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked I know "blocked" generally mean to first unmerge the old package first but shorewall docs stress that uninstall of 3.4.6 is not neccesarry before upgrade, so why on Gentoo?
Reopening due to a typo in shorewall-perl ebuild: DEPEND="net-firewall/iptables sys-apps/iproute2 dev-lang/perl !<et-firewall/shorewall-4.0" ^^ needs to be "net". --- Joakim, I haven't found a simple way to do this in an ebuild. If someone can please take a look at it. The DEPEND restriction above is to avoid downgrades that don't unmerge shorewall >4.0. An alternative I suggested previously is to add: RDEPEND="!net-firewall/shorewall-common !net-firewall/shorewall-shell !net-firewall/shorewall-perl" to all pre-4.0 shorewall ebuilds. So then one can also remove !<net-firewall/shorewall-4.0 from DEPEND in the post-4.0 ebuilds and that would get rid of your error message.
> I know "blocked" generally mean to first unmerge the old package first but > shorewall docs stress that uninstall of 3.4.6 is not neccesarry before upgrade, > so why on Gentoo? We make use of the splitted packages as upstream does now. And if you want to use the "new" package, you have to unmerge the older one. No way around that. It's also a good reminder that people should look again at their configs.
