Issue 2255 - cvs co -c is not working anymore
Summary: cvs co -c is not working anymore
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Upgrade (show other issues)
Version: current
Hardware: All All
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-22 10:43 UTC by Martin Hollmichel
Modified: 2003-12-06 14:52 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Martin Hollmichel 2001-11-22 10:43:07 UTC
user mh doesn't have <Module> access to .
Comment 1 Unknown 2001-11-22 18:33:32 UTC
Hi,

I am finding the same behavior on the staging server as well as
production. After testing on other sites which also are running
version 1.1, it appears to be a core product issue. 
A ticket has been entered (pcn6638) to address this issue as quickly
as possible.

Thank you
Kat
Comment 2 Martin Hollmichel 2001-11-22 18:56:36 UTC
Unfortunatly I tested only the checkout of CVSROOT on the staging
server and not the cvs co -c command. Sorry for that.

Comment 3 Unknown 2001-11-26 06:45:05 UTC
Kat will own this issue to track from support. Re-assigning
Comment 4 Unknown 2001-11-27 18:35:50 UTC
Really re-assigning this time!
Comment 5 Unknown 2001-11-29 03:02:56 UTC
Wednesday last, changed were made to the database permissions on
stage01 in a first attempt with our operations department to enable
Module access without success.

Our cvs developer is now looking into this issue to further
investigate the differences between the past and present versions of
the rpm and the interaction with the permissioning system to address
the problem as quickly as possible.

Kat 
Comment 6 Unknown 2001-12-01 02:05:06 UTC
This problem was traced to an error in the helm install. The
permission VersionControl-Module is now available to be added to all
roles by the domain admin, but is not wet by default. I have already
added this permission to the roles Domain Admin, Developer, and
Project Owner.

Comment 7 stx123 2002-06-01 00:16:52 UTC
Martin, in preparation of the upcoming upgrade I would like to 
cleanup the existing bugs in subcomponent "upgrade".
Please verify and close.
Comment 8 Martin Hollmichel 2002-06-11 08:23:41 UTC
verified and closed