First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 18428
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Martin Holzer (RETIRED) <mholzer@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Thomas Schuetz <tsc12@gmx.de>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 18428 depends on: Show dependency tree
Bug 18428 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2003-03-29 10:56 0000 
I just wanted to build an ebuild for guarddog and found it by accident under
net-misc. 
Guarddog is a firewall-utility and really belongs to net-firewall, doesn't it? 
And there is already an ebuild for the very stable version 2.0.0. I know it
works fine 
on i386, the ebuild for nearly half a year and there are no bugs in the
database. 
Couldn't the 2.0.0.ebuild unmasked? I think, there's just nobody at the moment,
who 
takes care of this ebuild.

------- Comment #1 From Martin Holzer (RETIRED) 2003-05-01 07:19:01 0000 ------- 
moved

you can now mark it stable.

------- Comment #2 From Daniel Black 2003-05-07 00:28:11 0000 ------- 
I think the guarddog ebuilds require a SLOT="0" line. All versions are a
continued development 
on the same product with no consistancies. Guarddog 2.1.4 works with the same
ebuild as 
2.0.0. 2.1.4 is still listed as a development version by the author. I also
have found guarddog to 
be very stable on 2.0.0. Picky note sorry but ChangeLog top line still reflects
former location 
net-misc.
First Last Prev Next    No search results available      Search page      Enter new bug