Issue 25125 - CVSROOT content mismatch with actual configuration
Summary: CVSROOT content mismatch with actual configuration
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: _openoffice.org CVS (obsolete) (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-05 14:36 UTC by Martin Hollmichel
Modified: 2004-05-24 12:45 UTC (History)
5 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 2004-02-05 14:36:30 UTC
the content of the module CVSROOT differs again from what we get with the cvs co
-c command.
please see also 24169 for reference and prior solution.
Comment 1 Unknown 2004-02-05 17:22:14 UTC
is this a problem across all projects? or with just one? are missing some
entries? If so, which entries? Can you provide us with the two templates to
compare the differences? 
Comment 2 Martin Hollmichel 2004-02-05 17:37:48 UTC
We do have only one CVSROOT for all projects, so I do not understand your question.

in the cvs co -c output the following aliases are missing:
 beanshell rhino virgule cli_ure hwpfilter embeddedobj libxml2 unoxml,
this means the additions of ~4-6 weeks are missing.

the rcstemplate seems to be ok now.
Comment 3 Unknown 2004-02-05 18:29:31 UTC
updating whiteboard w/ internal IZ #
Comment 4 Unknown 2004-02-05 22:44:20 UTC
the ops team have done an initial investigation and found nothing that appeared
out of order. they also applied a patch today from another issue which applied
cleanly. is there any more information you could give us that would help us
diagnose the problem?
Comment 5 Martin Hollmichel 2004-02-06 09:32:48 UTC
"cvs co -c" command now fully compatible with the CVSROOT module we can checkout
again.

I'm sorry that I can't help you with the diagnose more, but having older
versions of CVSROOT/modules causes process breakages at our end, we are
dependent to have CVS data available in a reliable way.
Comment 6 Unknown 2004-02-10 18:02:54 UTC
closing
Comment 7 jens-heiner.rechtien 2004-02-12 17:31:09 UTC
It happened again. Please see issue 25357.
Comment 8 Unknown 2004-02-12 17:39:50 UTC
when the other issue has been confirmed, it'll get assigned to support. do not
reopen this issue.

also make sure your new issues can answer these questions:
is this a problem across all projects? or with just one? are missing some
entries? If so, which entries? Can you provide us with the two templates to
compare the differences? 
Comment 9 rt 2004-02-12 17:57:08 UTC
Hi Kenneth,

Please read issue 25357 and you'll see all your questions asked.
How can it be that a prio1 issue (and it really is one) is in stateb'new' for
more than a day now?

Rüdiger
Comment 10 jens-heiner.rechtien 2004-02-12 18:11:36 UTC
Kenneth,

I'm the technical lead of StarOffice Release Engineering and the stand in for
Martin Hollmichel and Stefan Taxhet this week. 

The problem is that the last change, hardware upgrade or whatever it was,
*again*  removed a lot of changes which were done to that file over the last weeks. 

So there is one issue where Rüdiger explains in great detail what is missing and
this issue which complains about the fact that the modules file got mangled
again and was not fixed during the last 24h despite the Prio 1 issue Rüdiger
wrote. This is not acceptable because it really hinders work here. I've got a
lot of very unhappy developers who can not do their daily work. This is
definitely not just an inconveniance.

Please close this issue only if it's certain that this problem can not happen again.
Comment 11 Unknown 2004-02-12 18:29:36 UTC
please update the other issue with the information and templates and reassign it
to support@openoffice.org.
Comment 12 jens-heiner.rechtien 2004-02-12 18:58:27 UTC
Kenneth,

Issue 25357 contains a complete list of missing aliases, a reference to this
issue and a reference to another issue with the technical details. I assume it's
possible to recreate the modules file with this information. Additionally it 
must be still somewhere - after all the modules file is also tracked by CVS,
isn't it?

Heiner
Comment 13 Unknown 2004-02-12 22:26:27 UTC
closing, resolved
Comment 14 Martin Hollmichel 2004-05-24 12:45:16 UTC
close issue.