shorewall-{common,shell,perl,lite} 4.0.5 version bump request Reproducible: Always
Looks like 4.0.5 is buggy and requires patches which are not yet taken into account in the ebuilds. So I think that we can wait for 4.0.6 instead of patchng from upstream errata.
4.0.6 is out, there is also a patched 4.0.6-2 version but it seem to only concern Debian and Ubunto. Please bump as current one in portage tree seem t have some problems and a lot of bugs are fixed with this one. It now also say to fully integrate the split of compilers.
Created attachment 137467 [details] shorewall-common-4.0.6 new ebuild
Created attachment 137468 [details] shorewall-lite-4.0.6 new ebuild
Created attachment 137470 [details] shorewall-perl-4.0.6 new ebuild with upstream patch
Created attachment 137471 [details] shorewall-shell-4.0.6 new ebuild
new ebuilds for shorewall suite 4.0.6 (upstream now makes it easy to keep up with patches - see shorewall-perl)
bump! please give us a merry Christmas ;-)
patch level in shorewall-perl-4.0.6 needs to be changed to -3
version bump the proposed 4.0.6 ebuilds to 4.0.7 and set the MY_P_PATCH variable to "". Future releases won't even need it but it doesn't hurt to leave it there just in case.
and will this ever make it into the tree or do have to keep up with bumping our overlay???
(In reply to comment #10) > version bump the proposed 4.0.6 ebuilds to 4.0.7 and set the MY_P_PATCH > variable to "". Future releases won't even need it but it doesn't hurt to leave > it there just in case. > Actually, -perl-4.0.7 and -shell-4.0.7 do need MY_P_PATCH and it set to ".2", it seem upstream have from - to . marking patch level. It's a pity this havent got into the tree yet though.
(In reply to comment #12) > Actually, -perl-4.0.7 and -shell-4.0.7 do need MY_P_PATCH and it set to ".2", > it seem upstream have from - to . marking patch level. MY_P_PATCH is not necessary anymore "because" upstream started using . instead of -. So the only thing to do is a simple version bump, eg. shorewall-perl-4.0.7.2.ebuild, etc.
(In reply to comment #13) > (In reply to comment #12) > > Actually, -perl-4.0.7 and -shell-4.0.7 do need MY_P_PATCH and it set to ".2", > > it seem upstream have from - to . marking patch level. > > MY_P_PATCH is not necessary anymore "because" upstream started using . instead > of -. So the only thing to do is a simple version bump, eg. > shorewall-perl-4.0.7.2.ebuild, etc. > Well if you do that then emerge complain of missing dependency shorewall-common-4.0.7.2 and if you rename shorewall-common it cannot find source as there is no shorewall-common-4.0.7.2.tar.bz2 file ;-(
Seems that nobody of developers currently uses this package. But seems that you are interested in this package so I suggest that somebody of you stepped up to maintain it. That means you provide ebuilds, I commit them and you fix bugs if any arise :) If you are interested, then please, update and test another time ebuilds to the state they are ready to be bumped and attach patch (to the latest version in the tree) here.
(In reply to comment #15) > Seems that nobody of developers currently uses this package. But seems that you > are interested in this package so I suggest that somebody of you stepped up to > maintain it. That means you provide ebuilds, I commit them and you fix bugs if > any arise :) If you are interested, then please, update and test another time > ebuilds to the state they are ready to be bumped and attach patch (to the > latest version in the tree) here. hi. Jokey added my name to the Changelog and alsol suggested proxy maintenance but we never got to do it. Anyway, theebuilds on this page can be bumped to 4.0.8 which is the latest version available. I use shorewall regularly at work so I can provide some feedback (although I don't use *all*of its features). But this should be enough to keep this package updated in portage. If you require a patch to the latest ebuild in the tree and not the ebuilds I attached here, then I'll be glad to provide them tomorrow (if time permits, from office).
added to CVS, please test and report back :)
(In reply to comment #17) > added to CVS, please test and report back :) emerges 4.0.8 fine. MY_P_PATCH not necessary for now. So I guess you can close this bug. Thanks. ;-)
Thank you for reporting back, Viery. I think we can leave cleaning MY_P_PATCH for next update. :) FIXED.
