Issue 18957 - Commit does not work
Summary: Commit does not work
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: _openoffice.org CVS (obsolete) (show other issues)
Version: current
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-02 12:34 UTC by pplwong
Modified: 2004-08-04 01:24 UTC (History)
3 users (show)

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


Attachments
ssh cmd and output (135 bytes, text/plain)
2003-10-13 21:53 UTC, pplwong
no flags Details
ci cmd and output (329 bytes, text/plain)
2003-10-13 21:54 UTC, pplwong
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description pplwong 2003-09-02 12:34:17 UTC
Hi, I'm pplwong.
When I'm trying to commit my files for zh native-lang project, the following
error occurs:

hash.c312: failed assertion 'key != NULL'
cvs [server aborted]: received abort signal
Comment 1 stx123 2003-09-02 14:48:59 UTC
Any idea?
Comment 2 pplwong 2003-09-02 15:38:22 UTC
Before this occured, I had removed a few files, let's say, one is
ooo_info.GIF.

Then, after commiting this change, I add the file ooo_info.gif.

It surprisingly identify the two files to have the same name and then
"recreate" the file.

Then when I commit, it crash.
Comment 3 Martin Hollmichel 2003-09-02 15:49:32 UTC
typically this assertion is an indication of mismatch of CVSROOTs
(commandline - CVS/Root - CVSROOT env.-variable).
Comment 4 lsuarezpotts 2003-09-02 17:28:47 UTC
Paul, still experiencing this?
if so, please let us know.
louis
Comment 5 pplwong 2003-09-02 18:45:45 UTC
Yea, still the same thing.

The four files I've "added" is still "added" but not yet "committed".
Update correctly show what's to be added and update.

Commit works until after the comments is entered (i.e. when it really
tries to commit, it fails with exactly the same message I've post).
Comment 6 lsuarezpotts 2003-09-03 02:08:01 UTC
reassigning to support.
louis
Comment 7 Unknown 2003-09-04 01:33:39 UTC
Paul,
Could you let us know the name of the files?
Are you having problems checking in elsewhere?
Has anyone else run into problems wiht these particular files?
Thanks,
Kristen
Comment 8 pplwong 2003-09-04 02:01:35 UTC
I haven't try elsewhere yet.
I'll try on linux later today.

The four files are in zh/www/images/doc/.
They are: 
ooo_info.GIF
ooo_note.GIF
ooo_skill.GIF
ooo_warning.GIF

I am trying to change the filenames so that the "GIF"s become "gif"s.
I tried to do so by first remove, then add.
Comment 9 Unknown 2003-09-11 18:36:35 UTC
Paul,
I requested that operations take a look and completely remove these 
files for you so that you can replace them. Referencing our internal 
tracking number, PCN22263.
Thanks,
Kristen
Comment 10 Unknown 2003-09-11 22:17:31 UTC
Paul,
Operations removed those files completely so you should be able to 
check them back in now.
Thanks,
Kristen
Comment 11 pplwong 2003-09-11 22:22:54 UTC
Thanks a lot
Comment 12 Unknown 2003-09-18 01:04:30 UTC
Hi Paul,
Just wanted to make sure you're all set now. Can we close this issue?
Thanks,
Kristen
Comment 13 pplwong 2003-09-19 00:30:37 UTC
Hi. Problem still exist.
I've removed my zh folder and re-checkout it from server.
But after checking out all files, the last line shows:

cvs server: nothing known about zh/www/images/doc/ooo_info.gif

and when I add the ooo_info.gif file and try to commit it, the
previous error still occurs (the "hash.c:312" error mensioned in
previous posts)

I can submit other files though.
Comment 14 stx123 2003-09-22 13:17:19 UTC
Paul, I guess you would lik eto see this issue reassigned to support.
Comment 15 pplwong 2003-09-22 20:51:40 UTC
thanks
Comment 16 pplwong 2003-10-13 18:39:00 UTC
Hi, now, it's even worse.
When I try to login cvs, update etc,
the cygwin screen (which I made a tunnel to OOo) output 

"Channel 2: open failed: administratively prohibited: open failed".

What happened??!

@_@
Comment 17 lsuarezpotts 2003-10-13 19:22:33 UTC
hi, raising the priority as Paul needs for this to work.
louis
Comment 18 pplwong 2003-10-13 19:51:38 UTC
It becomes "pplwong, no such user" now
Comment 19 Unknown 2003-10-13 20:24:18 UTC
could you please attach or include the full command you're using to
make your tunnel, and the cvs command you are using to commit? (please
use -v as well, thank you)
Comment 20 pplwong 2003-10-13 21:01:27 UTC
ssh -x -2 -L 2401:localhost:2401 tunnel@openoffice.org
(I successfully create a tunnel, it claims)

then 
cvs -d:pserver:pplwong@localhost:/cvs {command}

Then it give me "pplwong: no such user".

These worked before
Comment 21 Unknown 2003-10-13 21:28:33 UTC
could you please attach your attempts with the full command you're
using to make your tunnel, and the full cvs command you are using to
commit? (please use -v as well, thank you). I want to see the outputs
of the commands as well. attach them as text files to this issue please
Comment 22 lsuarezpotts 2003-10-13 21:34:17 UTC
Paul,
the correct command is
ssh -2 -x -L

not

ssh -x -2
louis
Comment 23 pplwong 2003-10-13 21:53:47 UTC
Created attachment 10285 [details]
ssh cmd and output
Comment 24 pplwong 2003-10-13 21:54:16 UTC
Created attachment 10286 [details]
ci cmd and output
Comment 25 Unknown 2004-02-03 10:14:27 UTC
1. ssh -2 -x -L 2401:localhost:2401 tunnel@openoffice.org
2. cvs -d:pserver:pplwong@localhost:/cvs login
3. cvs -d:pserver:pplwong@localhost:/cvs [command]

This is the steps can be followed.



Comment 26 Unknown 2004-02-05 06:39:53 UTC
Paul 

Is the command recommended by priya working ? Can we close the issue?

The cases where the login fails saying 'no  such user' is when the password you 
are typing in wrong. You might have changed the Openoffice password. please 
check for that.
There might be other problems. But i observed it was when i typed my password 
wrong.

Please inform us at the earliest about the progress

-Mohan

-Mohan

Comment 27 pplwong 2004-02-05 11:23:08 UTC
I think I'm ok now.
Thanks, this can be closed
Comment 28 Unknown 2004-02-05 11:26:58 UTC
Closing Issue
Comment 29 Unknown 2004-08-04 01:24:35 UTC
Closing this issue.