Version bump request to maintain "sync" between Shorewall and Shorewall 6 In my case, I run Shorewall and Shorewall6, for IPv4 and IPv6 respectively. The Shorewall package just "bumped" to 4.6.6.1 I am unable to upgrade my system to Shorewall 4.6.6.1 because Shorewall6 is still at 4.5.21.9. Emerge tosses this error: emerge --ask --update --newuse --with-bdeps=y @world These are the packages that would be merged, in order: Calculating dependencies... done! WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: net-firewall/shorewall:0 (net-firewall/shorewall-4.6.6.1:0/0::gentoo, ebuild scheduled for merge) conflicts with =net-firewall/shorewall-4.5.21.9 required by (net-firewall/shorewall6-4.5.21.9:0/0::gentoo, installed) ^ ^^^^^^^^ Nothing to merge; quitting.
You ought to switch to net-firewall/shorewall as all of the different shorewall lite/ipv6 packages have been merged into that.
Jeroen: Your statement in Comment 1 is almost correct. An accurate statement might be: The functionality has been merged into "net-firewall/shorewall-4.6.6.1". Please note: There is no corresponding error message when users that were using separate "shorewall" and "shorewall6" packages, and then they try to "emerge --update" to the current "net-firewall/shorewall-4.6.6.1". Please ask the package maintainer of "net-firewall/shorewall-4.6.6.1" to add an "emerge" message telling the user about this change after displaying the error that I posted here. That type of message would have stopped me from filing this bug report. I did the upgrade to "net-firewall/shorewall-4.6.6.1" tonight after backing up my "shorewall6" configurations and running "emerge --depclean shorewall6". Then I used Shorewall's own tools to merge the configuration differences as prompted at the end of the "emerge" process" for "net-firewall/shorewall-4.6.6.1". The entire process of combining all the Shorewall configuration changes, based on working through the merge feature of "dispatch-conf", should be done very carefully "by hand".
Hi Jeff, I am currently proxy maintaining net-firewall/shorewall and was the one who integrated the split packages back into one package (see bug 522278 for reasons). I understand your problem and while testing I experienced the same "bad" UE. But from my knowledge (and I bothered the people in #gentoo-dev-help multiple times regarding this problem) there is nothing we can do: All the ebuild phases are running *after* you pressed "y" to confirm to process with the upgrade, see http://devmanual.gentoo.org/ebuild-writing/functions/ But emerge will stop like you have shown before the first phase (pkg_pretend) has the chance to be called. That's because we have to set a block for shorewall-core (a previous base component) in the new net-firewall/shorewall package. Well, we could remove the block from the DEPENDs and check in pkg_pretend where we are able to show a nice error message, but this would be "the wrong way" I was told. We could have created a Gentoo news item for that but I was told, too, that there is no need for a news item, because the block message says everything the user needs to know, i.e. "net-firewall/shorewall don't support any of the previous split packages" so that the user will dig into the new package and will find out that the other packages are now combined into that one... If you have any idea/suggestion how to display a message or improve the situation please tell me.
For what it's worth, a news item for this would have been a good thing. For several weeks, I was waiting for new shorewall6 package to appear, until I lost patience and looked into bugzilla. Is this really the kind of user experience you want your users to have? The mentioned block message doesn't really say anything useful to a user who is used to have shorewall and shorewall6 packages in sync and has no idea that you have decided to merge them.
@ Jeff and Andrej: We finally added a news item, see bug 546952.
