Closed
Bug 27297
Opened 25 years ago
Closed 21 years ago
cvs release requires write acccess to repository
Categories
(mozilla.org Graveyard :: Server Operations, task, P3)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jgmyers, Assigned: drew.streib)
Details
Using cvs-mirror.mozilla.org, I'm getting:
> cvs release -d ucvibm
? .deps
You have [0] altered files in this repository.
Are you sure you want to release (and delete) directory `ucvibm': yes
cvs-1.10.8 [server aborted]: "release" requires write access to the repository
This makes no sense; I should not need write access to the repository in order
to do a cvs release.
Comment 1•25 years ago
|
||
This is cvs client issue... and for some reason it tries to delete that dir from
cvs-mirror, and of course that's not allowed.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 2•25 years ago
|
||
That's ludicrous. The client is notifying the server of the release so the
server can log the event. If the server isn't interested, it should treat it as
a noop.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment 3•25 years ago
|
||
You don't have to get hostile with risto, john. This looks like a problem with
how we have the cvs-mirror set up, but it could be a limitation in cvs. I'm not
sure we can turn off trying to write the history file on releases. I suggest
working around with `rm -rf'.
Comment 4•25 years ago
|
||
I'm happy with leaf's suggestion... and don't want to spend more time with this
right now. Maybe sometimes when I have more time. I'll leave this open but
probably won't touch for a while.
Reporter | ||
Comment 5•25 years ago
|
||
I apologize if my comment was hostile, it was not intended to be.
rm -rf has the problem that it doesn't take things out of CVS/Entries, so cvs
starts puking on subsequent operations.
Updated•25 years ago
|
Severity: normal → minor
Comment 6•24 years ago
|
||
Moving to Drew. This is an issue with cvs-mirror.
Assignee: rko → dtype
Status: REOPENED → NEW
Assignee | ||
Comment 7•24 years ago
|
||
That error does indicate that "release" will require write access. This message
only shows up when it is more than the history file as well, as anonymous
checkouts technically require write access to the history file, but not write
access to the repository.
I'll check with Jim Kingdon, our resident CVS expert, as to why this is. But for
now it does appear to be a CVS constraint, and not necessarily a configurable
one (unless we want to hack CVS somewhat, which I think is not preferred).
Status: NEW → ASSIGNED
Updated•24 years ago
|
Whiteboard: AOL_IC_unsupported
Updated•23 years ago
|
Whiteboard: AOL_IC_unsupported
Comment 8•21 years ago
|
||
dave@ibook [0:58 docs 56] tcsh> cvs version
Client: Concurrent Versions System (CVS) 1.11.5 (client/server)
Server: Concurrent Versions System (CVS) 1.11.4 (client/server)
dave@ibook [0:59 docs 57] tcsh> cat CVS/Root
:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot
dave@ibook [0:57 docs 58] tcsh> cvs release -d txt
You have [0] altered files in this repository.
Are you sure you want to release (and delete) directory `txt': yes
dave@ibook [0:57 docs 59] tcsh>
works for me.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 21 years ago
Resolution: --- → WORKSFORME
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•