Bug 425808 - [RFE] version 4.5 of Nmap has been released, repos still have 4.2
Summary: [RFE] version 4.5 of Nmap has been released, repos still have 4.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nmap
Version: 8
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Tomas Smetana
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-16 04:05 UTC by John L. Greco
Modified: 2008-01-15 22:52 UTC (History)
0 users

Fixed In Version: 4.52-1.fc8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-15 22:52:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description John L. Greco 2007-12-16 04:05:31 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.10) Gecko/20071128 Fedora/2.0.0.10-2.fc8 Firefox/2.0.0.10

Description of problem:
Version 4.5 of nmap was recently released though the repositories still have 4.20.  Nmap's default gui has also been changed from NmapFE to Zenmap, though NmapFE appears to be provided by the package nmap-frontend.

Version-Release number of selected component (if applicable):
nmap-4.20-6.fc8

How reproducible:
Always


Steps to Reproduce:
1.  Nothing really to reproduce, just an upgrade request.  Sorry if I'm not doing this properly.

Actual Results:


Expected Results:


Additional info:

Comment 1 Tomas Smetana 2007-12-17 07:27:07 UTC
Thanks for noting me.  I have more urgent issues to solve first so please be
patient.

Comment 2 Fedora Update System 2008-01-11 22:27:52 UTC
nmap-4.52-1.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update nmap'

Comment 3 Fedora Update System 2008-01-15 22:52:40 UTC
nmap-4.52-1.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.