Bug 217875 - cvs-import script is unable to create new modules
Summary: cvs-import script is unable to create new modules
Alias: None
Product: Fedora
Classification: Fedora
Component: 915resolution   
(Show other bugs)
Version: rawhide
Hardware: All Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2006-11-30 15:51 UTC by Neil Horman
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-12-04 20:06:46 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch to fix cvs-import script (794 bytes, patch)
2006-11-30 15:51 UTC, Neil Horman
no flags Details | Diff

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:

Steps to Reproduce:
1.import a new package to fedora extras
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

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