Bug 217875

Summary: cvs-import script is unable to create new modules
Product: [Fedora] Fedora Reporter: Neil Horman <nhorman>
Component: 915resolutionAssignee: Jeremy Katz <katzj>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: extras-qa
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: 2006-12-04 20:06:46 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:
Attachments:
Description Flags
patch to fix cvs-import script none

Description Neil Horman 2006-11-30 15:51:32 UTC
Description of problem:
cvs-import.sh script is unable to create new modules

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1.import a new package to fedora extras
2.
3.
  
Actual results:
if the module doesn't yet exist in cvs, the import will fail

Expected results:
import should create the new module before checking it out.

Additional info:

This is occuring because the cvs-import.sh script adds the name of the module
being imported to the modules file, and then immediately greps for the name of
the module in that file as s test to see if it needs to create the module in
cvs.  Since we just added the name, this check will always erroneously decide
that the module already exists.

I haven't completely tested the attached patch yet, but I think something like
this should fix the issue

Comment 1 Neil Horman 2006-11-30 15:51:33 UTC
Created attachment 142484 [details]
patch to fix cvs-import script

Comment 2 Jeremy Katz 2006-12-04 20:06:46 UTC
No, it's not added to modules until after it sees it's not there already. 
Adding new packages is working for everyone else, so I think you're hitting
something else.  Please actually provide details of the failure you're seeing
and report them to the infrastructure ticketing system
(http://fedoraproject.org/wiki/Infrastructure/Tickets)