Bug 538299

Summary: Review Request: openvas-client - Client component of Open Vulnerability Assessment (OpenVAS) Server
Product: [Fedora] Fedora Reporter: Stjepan Gros <stjepan.gros>
Component: Package ReviewAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: fedora-package-review, huzaifas, notting, pahan, roysjosh, xavier
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-06 21:17:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 538297    
Bug Blocks:    

Description Stjepan Gros 2009-11-18 07:30:29 UTC
Spec URL: http://www.zemris.fer.hr/~sgros/stuff/fedora/openvas/openvas-client.spec
SRPM URL: http://www.zemris.fer.hr/~sgros/stuff/fedora/openvas/openvas-client-2.0.5-1.fc11.src.rpm
Description:
OpenVAS-Client is a client component that is used to access and control
OpenVAS server. It is also used to perform analysis task of results
provided by the server component.

Comment 1 Huzaifa S. Sidhpurwala 2009-12-22 11:02:19 UTC
*** Bug 541494 has been marked as a duplicate of this bug. ***

Comment 2 Pavel Alexeev 2010-01-02 16:58:32 UTC
For new package you shouldn't use vendor tag for desktop-file.
https://fedoraproject.org/wiki/Packaging/Guidelines#desktop-file-install_usage

Also missing BR glib. Build package failed - http://koji.fedoraproject.org/koji/taskinfo?taskID=1898860

Comment 3 Joshua Roys 2010-01-04 16:51:32 UTC
OpenVAS 3.0.0 was released recently.

Comment 4 Stjepan Gros 2010-02-06 21:17:50 UTC
I'm closing this bug report since it is superseded by a new major release. Desktop and BR I'll fix in next iteration.

*** This bug has been marked as a duplicate of bug 562470 ***