cvsserver problem with eclipse?
[taking this conversation to the list]
OK, I changed the way I was testing this to match your usage plan and I still got the same results. It works just fine for vanilla CVS; cvs status shows the re revision in the repo and cvs update brings it in. Eclipse has the same funky behavior: Compare with latest at the project level shows no differences, but compare with latest on the changed file actually does an update instead of popping up the Eclipse diff viewer.
By the way, I had trouble at first accessing the repo with SSH because of permissions on the sqlite db. I'm not totally sure about the implications for multiple users, but maybe just using a common group will work fine?
I'm really happy with git and git-cvsserver! I'm hoping to be able to standardize on it for our Eclipse work. It seems like it should be possible for us to continue to do integrations in Eclipse if we manage git properly. I've been waiting on arch, baz, and bzr for so long and then suddenly, Linus pulls this out of his butt!
Bill Burdick
---------- Forwarded message ----------
From: *Martin Langhoff (CatalystIT)* < [email protected] <mailto:[email protected]>>
Date: May 1, 2006 6:41 AM
Subject: Re: cvsserver problem with eclipse?
To: Bill Burdick <[email protected] <mailto:[email protected]>>
Cc: Martyn Smith < [email protected] <mailto:[email protected]>>
Hi Bill,
the git repo you are using, did you set it up to just be a "naked" or "bare" repo, and enabled cvsserver alright? What version of git are you using?
My usage plan would be to
1 - Have a git test project
2 - Publish it to a naked/bare repository where git-cvsserver is enabled 3 - Get the cvs checkout (try commandline cvs to make sure things work) 4 - Add commits in the git test project and push them to the repo 5 - Run cvs update
If it's running ok with old school CVS client, then try with Eclipse. We have tested the update scenario quite a bit, and it works for us, so we need a bit more info.
BTW, can I ask you to bounce these questions off the [email protected] <mailto:[email protected]> mailing list? We will be happier answering these questions in a way that
gets archived publicly. (Unless you are a direct client of Catalyst IT,
that is! Are you at OpenUniversity perhaps?)
cheers,
martin
Quoted 10 lines · Bill Burdick
I made a test git repo with a branch called WillyTest and slurped it into Eclipse. Then I checked out WillyTest into the git directory and committed a change. A synchronize in Eclipse did not detect the change, nor did comparing with the latest on the head. Showing history on the changed file did, however, list the new revision and I could access the contents from that view. Compare with latest on the changed file actually replaces the current contents with the repository version.
Bill Burdick
--
-----------------------------------------------------------------------
Martin @ Catalyst .Net .NZ Ltd, PO Box 11-053, Manners St, Wellington
WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St
OFFICE: +64(4)916-7224 MOB: +64(21)364-017
Make things as simple as possible, but no simpler - Einstein
-----------------------------------------------------------------------
begin:vcard
fn:Bill Burdick
n:Burdick;Bill
org:Mobile Reasoning
email;internet:[email protected]
title:Chief Scientist
tel;work:913-484-0172
x-mozilla-html:FALSE
version:2.1
end:vcard
FWIW, I'm using Eclipse 3.2RC1a.
Bill
Quoted 59 lines · Bill Burdick
[taking this conversation to the list]
OK, I changed the way I was testing this to match your usage plan and I still got the same results. It works just fine for vanilla CVS; cvs status shows the re revision in the repo and cvs update brings it in. Eclipse has the same funky behavior: Compare with latest at the project level shows no differences, but compare with latest on the changed file actually does an update instead of popping up the Eclipse diff viewer.
By the way, I had trouble at first accessing the repo with SSH because of permissions on the sqlite db. I'm not totally sure about the implications for multiple users, but maybe just using a common group will work fine?
I'm really happy with git and git-cvsserver! I'm hoping to be able to standardize on it for our Eclipse work. It seems like it should be possible for us to continue to do integrations in Eclipse if we manage git properly. I've been waiting on arch, baz, and bzr for so long and then suddenly, Linus pulls this out of his butt!
Bill Burdick
---------- Forwarded message ----------
From: *Martin Langhoff (CatalystIT)* < [email protected] <mailto:[email protected]>>
Date: May 1, 2006 6:41 AM
Subject: Re: cvsserver problem with eclipse?
To: Bill Burdick <[email protected] <mailto:[email protected]>>
Cc: Martyn Smith < [email protected] <mailto:[email protected]>>Hi Bill,
the git repo you are using, did you set it up to just be a "naked" or "bare" repo, and enabled cvsserver alright? What version of git are you using?
My usage plan would be to
1 - Have a git test project
2 - Publish it to a naked/bare repository where git-cvsserver is enabled 3 - Get the cvs checkout (try commandline cvs to make sure things work) 4 - Add commits in the git test project and push them to the repo 5 - Run cvs updateIf it's running ok with old school CVS client, then try with Eclipse. We have tested the update scenario quite a bit, and it works for us, so we need a bit more info.
BTW, can I ask you to bounce these questions off the [email protected] <mailto:[email protected]> mailing list? We will be happier answering these questions in a way that
gets archived publicly. (Unless you are a direct client of Catalyst IT,
that is! Are you at OpenUniversity perhaps?)cheers,
martin
Quoted 9 lines · Bill Burdick
I made a test git repo with a branch called WillyTest and slurped it into Eclipse. Then I checked out WillyTest into the git directory and committed a change. A synchronize in Eclipse did not detect the
change,
nor did comparing with the latest on the head. Showing history on the changed file did, however, list the new revision and I could access the contents from that view. Compare with latest on the changed file actually replaces the current contents with the repository version.
Quoted 11 lines
Quoted 2 lines
Bill Burdick
Signature · 6 lines
----------------------------------------------------------------------- Martin @ Catalyst .Net .NZ Ltd, PO Box 11-053, Manners St, Wellington WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St OFFICE: +64(4)916-7224 MOB: +64(21)364-017 Make things as simple as possible, but no simpler - Einstein -----------------------------------------------------------------------
begin:vcard
fn:Bill Burdick
n:Burdick;Bill
org:Mobile Reasoning
email;internet:[email protected]
title:Chief Scientist
tel;work:913-484-0172
x-mozilla-html:FALSE
version:2.1
end:vcard
Quoted 3 lines · Bill Burdick
OK, I changed the way I was testing this to match your usage plan and I still got the same results. It works just fine for vanilla CVS; cvs status shows the re revision in the repo and cvs update brings it in.
That's a good start!
Quoted 3 lines
Eclipse has the same funky behavior: Compare with latest at the project level shows no differences, but compare with latest on the changed file actually does an update instead of popping up the Eclipse diff viewer.
Hmmm. Eclipse does some weird funky sh*t sometimes. Can you ask it to get you a log? There's an option in Eclipse CVS control settings that will enable logging of cvs commands to the console. Enable it, and then start Eclipse from the commandline, piping stderr and stdout to a logfile.
There are also some weird differences depending on how you ask for the update or diff. I hate doing this but I'll have to ask you to tell me exactly how you ask for the diff and for the update.
And the platform you are running Eclipse on.
Quoted 4 lines
By the way, I had trouble at first accessing the repo with SSH because of permissions on the sqlite db. I'm not totally sure about the implications for multiple users, but maybe just using a common group will work fine?
Yes, a common group is the thing to do.
$ chgrp gitusers *sqlite $ chmod g+w *sqlite
Quoted 2 lines
I'm really happy with git and git-cvsserver! I'm hoping to be able to standardize on it for our Eclipse work. It seems like it should be
Great to hear that!
cheers,
martin
OK, I replaced the eclipse file (yoda) with the latest from the head. Then I changed it in my git project, committed it, and pushed it to the shared repo. Finally, I did a "compare with latest from head" and it proceeded to update the file and then said that there were no changes. Here's the log:
Valid-responses ok error M E Checked-in Valid-requests Template Set-sticky MT Clear-static-directory Module-expansion Set-static-directory Clear-sticky New-entry Merged Removed Updated Remove-entry Update-existing Copy-file Created Notified Mod-time valid-requests
Valid-requests remove add status Entry watchers ci tag log co Modified Questionable admin Root history valid-requests Global_option Argumentx annotate Valid-responses Unchanged Directory rlog Argument expand-modules diff editors update ok
Root /tmp/public.git
CMD> cvs -n update -d "/yoda/yoda"Global_option -n
Argument -d
Directory ./tmp/public.git/yoda
Entry /yoda/1.9///
Modified yoda
u=rw,g=rw,o=r
48
Argument yoda
Directory ./tmp/public.git/yoda
update
M C yoda
Update-existing .//tmp/public.git/yoda/yoda
/yoda/1.10/+//
u=rw,g=rw,o=rw
95
ok
RESULT> Status OK: org.eclipse.team.cvs.core code=0 ok null
Valid-responses ok error M E Checked-in Valid-requests Template Set-sticky MT Clear-static-directory Module-expansion Set-static-directory Clear-sticky New-entry Merged Removed Updated Remove-entry Update-existing Copy-file Created Notified Mod-time valid-requests
Valid-requests remove add status Entry watchers ci tag log co Modified Questionable admin Root history valid-requests Global_option Argumentx annotate Valid-responses Unchanged Directory rlog Argument expand-modules diff editors update ok
Root /tmp/public.git
CMD> cvs status "yoda"
Directory ./tmp/public.git/yoda
Entry /yoda/0///
Modified yoda
u=rw,g=rw,o=r
0
Argument yoda
Directory ./tmp/public.git/yoda
status
M ===================================================================
M File: yoda Status: Needs Checkout M Working revision: 0 M Repository revision: 1.10 /tmp/public.git/yoda/yoda,v M Sticky Tag: (none) M Sticky Date: (none) M Sticky Options: (none)
M
ok
RESULT> Status OK: org.eclipse.team.cvs.core code=0 ok null
Quoted 41 lines · Martin Langhoff
Quoted 3 lines · Bill Burdick
OK, I changed the way I was testing this to match your usage plan and I still got the same results. It works just fine for vanilla CVS; cvs status shows the re revision in the repo and cvs update brings it in.
That's a good start!
Quoted 3 lines
Eclipse has the same funky behavior: Compare with latest at the project level shows no differences, but compare with latest on the changed file actually does an update instead of popping up the Eclipse diff viewer.
Hmmm. Eclipse does some weird funky sh*t sometimes. Can you ask it to get you a log? There's an option in Eclipse CVS control settings that will enable logging of cvs commands to the console. Enable it, and then start Eclipse from the commandline, piping stderr and stdout to a logfile.
There are also some weird differences depending on how you ask for the update or diff. I hate doing this but I'll have to ask you to tell me exactly how you ask for the diff and for the update.
And the platform you are running Eclipse on.
Quoted 4 lines
By the way, I had trouble at first accessing the repo with SSH because of permissions on the sqlite db. I'm not totally sure about the implications for multiple users, but maybe just using a common group will work fine?
Yes, a common group is the thing to do.
$ chgrp gitusers *sqlite $ chmod g+w *sqliteQuoted 2 lines
I'm really happy with git and git-cvsserver! I'm hoping to be able to standardize on it for our Eclipse work. It seems like it should be
Quoted 8 lines
Great to hear that!
cheers,
martin
begin:vcard
fn:Bill Burdick
n:Burdick;Bill
org:Mobile Reasoning
email;internet:[email protected]
title:Chief Scientist
tel;work:913-484-0172
x-mozilla-html:FALSE
version:2.1
end:vcard
Bill,
haven't been able to repro your problem at this end. Can you check your git version? Apparently cvsserver was broken soon after 1.3.0. Can you try with v1.3.0?
cheers,
martin
my version is 1.3.1. I'll d/l 1.3.0 and test with that.
Quoted 11 lines · Martin Langhoff
Bill,
haven't been able to repro your problem at this end. Can you check your git version? Apparently cvsserver was broken soon after 1.3.0. Can you try with v1.3.0?
cheers,
martin
begin:vcard
fn:Bill Burdick
n:Burdick;Bill
org:Mobile Reasoning
email;internet:[email protected]
title:Chief Scientist
tel;work:913-484-0172
x-mozilla-html:FALSE
version:2.1
end:vcard