ECLIPSE: cvs [update aborted]: could not find desired version

Thread view:

compaqr4000@lycos.com - 18 Oct 2007 22:00 GMT

Hi
Whenever I try to do a cvs update in Eclipse (V 3.1.1) I get the
following error:
!MESSAGE web: cvs [update aborted]: could not find desired version 1.5
in /home/smitherington/cvs_repos/apc/web/finfo.jsp,v

Does anyone have any ideas on how to fix or get around this so that I
can update my files and cvs files?

Thanks

Kay

Reply to this Message

Lew - 19 Oct 2007 00:01 GMT

> Hi
> Whenever I try to do a cvs update in Eclipse (V 3.1.1) I get the
[quoted text clipped - 4 lines]
> Does anyone have any ideas on how to fix or get around this so that I
> can update my files and cvs files?

Sounds like the file was updated via a separate CVS session. If the version
in the repository is based on a newer one that your attempted checkin, CVS
rejects it.

If that's the issue, do a "cvs update" first, resolve the conflicts that
causes, then check in.

Signature

Lew

Reply to this Message

compaqr4000@lycos.com - 19 Oct 2007 15:24 GMT

> compaqr4...@lycos.com wrote:
> > Hi
[quoted text clipped - 15 lines]
> --
> Lew

That didn't work, I get the same error when I try to update it.
However, it did set me on the path of something that did work.

I replaced my local file with the latest from cvs head, and then
replaced it with Previous from Local History. By doing this, it
assigned a newer cvs version to my local file and I can compare to
cvs, commit, etc.

Thsnks Lew!

Kay

Reply to this Message

Lew - 19 Oct 2007 23:06 GMT

> That didn't work, I get the same error when I try to update it.
> However, it did set me on the path of something that did work.
[quoted text clipped - 3 lines]
> assigned a newer cvs version to my local file and I can compare to
> cvs, commit, etc.

Kay, you showed some of the highest skills of the effective programmer just
there. You got an answer that was not the right answer. It didn't work. But
the principle behind the answer, it turns out, was applicable. Rather than
giving up because the recipe failed, you went deep, understood the principle
and found another place where it applied, this time usefully.

There is much potential in this one, Sifu.

Signature

Lew

Reply to this Message

Lew - 19 Oct 2007 23:13 GMT

compaqr4000@lycos.com wrote:

>> That didn't work, I get the same error when I try to update it.
>> However, it did set me on the path of something that did work.
[quoted text clipped - 3 lines]
>> assigned a newer cvs version to my local file and I can compare to
>> cvs, commit, etc.

> Kay, you showed some of the highest skills of the effective programmer
> just there.

Let me add that this is a case of Eclipse's internal "shadow" file structure,
including its private version history, being part of the equation.

For those not using Eclipse, one could get a similar result by copying the
changed version out of a directory, refreshing from CVS HEAD the way Kay did,
then copying or merging (the latter being more careful) the revised version
into the freshly CVS-updated one.

Any time you find yourself dodging CVS this way, something went awry earlier.
Usually it's possible to bail out the first way I explained, using CVS to
merge the HEAD version into the local copy. But now that I think on it, I
have always used command-line 'cvs', not an IDE-mediated version, to make this
work.

The Cederqvist manual is essential whenever you start digging underneath with CVS.
<http://ximbiot.com/cvs/manual/>

It's amazing what you can make CVS do if you dig through that manual,
especially the "Administrative Files" section.
<http://ximbiot.com/cvs/manual/cvs-1.12.13/cvs_18.html#SEC176>

Signature

Lew

Reply to this Message

ECLIPSE: cvs [update aborted]: could not find desired version

Free Magazines