Home » Eclipse Projects » Eclipse Platform » 3.0 M4 CVS broken commit?
| 3.0 M4 CVS broken commit? [message #143366] |
Mon, 13 October 2003 23:43  |
Eclipse User |
|
|
|
Hey all,
I was very excited to get M4. Lots of great new stuff, and hopefully fixes
for the M3 issues. But for some reason, when I set up my CVS now, I can't
commit. I see the new synchronize view, and it shows a bunch of issues.
Hell, I lost all my code on my local when I syncronized, luckilly the old
Eclipse locall history was still intact!! Anyway, I grab all the source,
make a few modifications, do a commit, and it keeps telling me error
Up-to-date check failed. How is this possible? I also do UPDATE, then
COMMIT, still no go! I can't make my changes stick. Help?!
|
|
|
| Re: 3.0 M4 CVS broken commit? [message #143375 is a reply to message #143366] |
Mon, 13 October 2003 23:47  |
| Eclipse User |
|
|
|
Found the problem. I think its a bug?? Problem is, I configured the new m4
feature to read using pserver, but write usin ext. When I do that, the
update/commit doesn't work. When I turned it back to using extssh for both
read and write, it worked. Is that a bug? I would think using pserver for
read only should be fine?
"Kevin" <supreme_java_guru_1@yahoo.com> wrote in message
news:bmfr34$e66$1@eclipse.org...
> Hey all,
>
> I was very excited to get M4. Lots of great new stuff, and hopefully fixes
> for the M3 issues. But for some reason, when I set up my CVS now, I can't
> commit. I see the new synchronize view, and it shows a bunch of issues.
> Hell, I lost all my code on my local when I syncronized, luckilly the old
> Eclipse locall history was still intact!! Anyway, I grab all the source,
> make a few modifications, do a commit, and it keeps telling me error
> Up-to-date check failed. How is this possible? I also do UPDATE, then
> COMMIT, still no go! I can't make my changes stick. Help?!
>
>
|
|
|
| Re: 3.0 M4 CVS broken commit? [message #143404 is a reply to message #143375] |
Tue, 14 October 2003 03:15 |
| Eclipse User |
|
|
|
Originally posted by: kk.dev.null
Kevin wrote:
> Found the problem. I think its a bug?? Problem is, I configured the new m4
> feature to read using pserver, but write usin ext. When I do that, the
> update/commit doesn't work. When I turned it back to using extssh for both
> read and write, it worked. Is that a bug? I would think using pserver for
> read only should be fine?
>
I think it's more than that. I got the same problem, but my read and write
proto is the same, and it's been working in M3 and previous.
In M4, when I checked in a new package, it left out some files not
checked in. And when I do a compare on the whole package with
the latest in CVS, it shows no difference! And there are 4 java files
left out, and no difference?
And the next day, I did a compare again (after I "accidentally" figured out
how to check in the left out, still don't know why!), it shows me every
file is different from the latest in CVS. I compare every file, and there's
not a single difference!
WTH!
The thing I like is that now, the long CVS commands (and most other
long commands) are handled in a background thread, and I can continue
working while Eclipse is working on those.
kk
|
|
|
| Re: 3.0 M4 CVS broken commit? [message #143659 is a reply to message #143404] |
Tue, 14 October 2003 10:50 |
| Eclipse User |
|
|
|
Ok, so I suppose we have to wat for M5...damn! Unless a nightly build fixes
this issue soon. Did you log a bug report? If not, can you log one
describing what you found. Sounds like you are more on top of it than I.
"kk" <kk@dev.null> wrote in message news:bmg7r8$nr4$1@eclipse.org...
> Kevin wrote:
> > Found the problem. I think its a bug?? Problem is, I configured the new
m4
> > feature to read using pserver, but write usin ext. When I do that, the
> > update/commit doesn't work. When I turned it back to using extssh for
both
> > read and write, it worked. Is that a bug? I would think using pserver
for
> > read only should be fine?
> >
>
> I think it's more than that. I got the same problem, but my read and write
> proto is the same, and it's been working in M3 and previous.
>
> In M4, when I checked in a new package, it left out some files not
> checked in. And when I do a compare on the whole package with
> the latest in CVS, it shows no difference! And there are 4 java files
> left out, and no difference?
>
> And the next day, I did a compare again (after I "accidentally" figured
out
> how to check in the left out, still don't know why!), it shows me every
> file is different from the latest in CVS. I compare every file, and
there's
> not a single difference!
>
> WTH!
>
> The thing I like is that now, the long CVS commands (and most other
> long commands) are handled in a background thread, and I can continue
> working while Eclipse is working on those.
>
> kk
>
|
|
|
| Re: 3.0 M4 CVS broken commit? [message #144152 is a reply to message #143659] |
Tue, 14 October 2003 15:54 |
| Eclipse User |
|
|
|
Originally posted by: Michael_Valenta.oti.com
This could be related to bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=44614. Was there anything
in the log file?
Michael
Kevin wrote:
> Ok, so I suppose we have to wat for M5...damn! Unless a nightly build fixes
> this issue soon. Did you log a bug report? If not, can you log one
> describing what you found. Sounds like you are more on top of it than I.
>
> "kk" <kk@dev.null> wrote in message news:bmg7r8$nr4$1@eclipse.org...
>
>>Kevin wrote:
>>
>>>Found the problem. I think its a bug?? Problem is, I configured the new
>>>
> m4
>
>>>feature to read using pserver, but write usin ext. When I do that, the
>>>update/commit doesn't work. When I turned it back to using extssh for
>>>
> both
>
>>>read and write, it worked. Is that a bug? I would think using pserver
>>>
> for
>
>>>read only should be fine?
>>>
>>>
>>I think it's more than that. I got the same problem, but my read and write
>>proto is the same, and it's been working in M3 and previous.
>>
>>In M4, when I checked in a new package, it left out some files not
>>checked in. And when I do a compare on the whole package with
>>the latest in CVS, it shows no difference! And there are 4 java files
>>left out, and no difference?
>>
>>And the next day, I did a compare again (after I "accidentally" figured
>>
> out
>
>>how to check in the left out, still don't know why!), it shows me every
>>file is different from the latest in CVS. I compare every file, and
>>
> there's
>
>>not a single difference!
>>
>>WTH!
>>
>>The thing I like is that now, the long CVS commands (and most other
>>long commands) are handled in a background thread, and I can continue
>>working while Eclipse is working on those.
>>
>>kk
>>
>>
>
>
|
|
|
Goto Forum:
Current Time: Thu Jul 24 04:20:55 EDT 2025
Powered by FUDForum. Page generated in 0.04125 seconds |
Home