Summary: | net-firewall/shorewall-4.4.10 removed, no stable 4.x version now available | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andy Dalton <andy.dalton> |
Component: | Current packages | Assignee: | Constanze Hausner (RETIRED) <constanze> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | netmon, rentorbuy |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andy Dalton
2011-01-24 12:39:46 UTC
I agree. shorewall-3.x should be removed from the tree anyway because it's obsolete. A 4.4 version should be marked stable. However, my personal choice is to emerge the latest 4.4 even if it's ~. (In reply to comment #0) > Greetings, > > On 23 January, the previously stable net-firewall/shorewall-4.4.10 was removed > from portage, the Changelog states "Version bump; Cleaned up old versions". > Unfortunately, none of other 4.x versions of shorewall are marked stable; Looking at the removed ebuilds, I cannot find any carrying stable keywords, so removing them is fine. Maybe you put ~amd64 into your package.accept_keywords/package.keywords? If so, you may want to upgrade to the newly added version. Hi, I cleaned the version up yesterday and I only removed unstable versions. As you can see here: http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-firewall/shorewall/shorewall-4.4.10.ebuild?view=markup all arches were unstable in 4.4.10 prior to my removal. As I agree, that we definably need a newer stable version, I also filed a stabilizing request yesterday, which you can see here: http://bugs.gentoo.org/show_bug.cgi?id=352532 |