Issue 8806 - no cvs tag access to udkwww
Summary: no cvs tag access to udkwww
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: _openoffice.org CVS (obsolete) (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Martin Hollmichel
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-29 14:53 UTC by Unknown
Modified: 2003-12-06 14:52 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-10-29 14:53:20 UTC 
While tagging the OO643C branch for OpenOffice.org, I receive an  
error message after doing 

cvs tag -b OO643C udkwww

"User armin doesnt have <Tag> access to udkwww"

please give me such access. 

armin
Comment 1 Unknown 2002-10-30 18:39:12 UTC 
Armin - only designated users can submit issues to the support
contact.  This will need to go through openoffice support first.

Martin or Stefan - please comment on armin's request.
Comment 2 stx123 2002-10-30 19:29:35 UTC 
Martin, could you take care of this?
Comment 3 stx123 2002-11-07 20:06:36 UTC 
As discussed: we have a workaround for the upcoming build OO643C - 
changing the working directory into udkwww and calling cvs tag from 
there.
But the question is still open, why Armin's approach doesn't work.
Comment 4 Martin Hollmichel 2003-01-27 19:18:12 UTC 
as discussed earlier -> user error ;).
Comment 5 michael.bemmer 2003-03-12 14:06:05 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 6 michael.bemmer 2003-03-12 14:30:11 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.