Bug 621950

Summary: Review Request: sockettest - A java tool for socket testing
Product: [Fedora] Fedora Reporter: PRABIN KUMAR DATTA <linux.n.pkd>
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: low    
Version: rawhideCC: aquini, fedora-package-review, notting
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-08-06 23:12:30 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:

Description PRABIN KUMAR DATTA 2010-08-06 15:31:04 UTC
Spec URL: http://prabindatta.fedorapeople.org/SPECS/sockettest.spec
SRPM URL: http://prabindatta.fedorapeople.org/SRPMS/sockettest-3.0-2.fc13.src.rpm
Description: A java tool for socket testing. It can create both TCP and UDP client or server. It can be used to test any server or client that uses TCP or UDP
protocol to communicate. 

koji scratch build:
(tested twice)
https://koji.fedoraproject.org/koji/taskinfo?taskID=2385110
https://koji.fedoraproject.org/koji/taskinfo?taskID=2385134 (tested again)

Comment 1 PRABIN KUMAR DATTA 2010-08-06 19:09:15 UTC
koji scratch build:
(updated)
http://koji.fedoraproject.org/koji/taskinfo?taskID=2386019

Comment 2 Rafael Aquini 2010-08-06 23:12:30 UTC
Prabin,

I'm closing this as it bug duplicates https://bugzilla.redhat.com/show_bug.cgi?id=484051

Please, talk to the first submitter of this package if you are planning to proceed with this review. Therefore, as a new packager you gonna need a sponsor before you really get into the packagers group. Take a look at the following link to understand this policy:

https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group

Regards

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