Joseph Slater wrote:
> When ever I do a fink selfupdate, I get the following error:
> cvs update: move away dists/stable/main/finkinfo/gnome/mc-4.5.54-3.info; 
> it is in the way
> C dists/stable/main/finkinfo/gnome/mc-4.5.54-3.info

This is generally a sign that you have, deliberately or accidentally, 
altered
the file in question. And since the version you're CVS-synchronizing is
supposed to be authoritative but the changes you made might or might not be
important, CVS won't clobber your changes.

SO, the solution to this is always pretty much the same: if you think you
might need the changes, rename the files appropriately, and if you're sure
you don't need them, just delete 'em. Either way, once you do one or both
of these, CVS updates should start working again.

If you want to be really safe, rename the files to something like
"foo.1.2-3.info.MOVED", then do a diff on the .MOVED and the new version
after a CVS update; you might be able to find anything that you wanted to
save, but generally you'll find you can just delete the .MOVED file...

> Along with a few (hundred or so?) others that look the same. The only 
> way for me to do an update is to remove these directories. This doesn't 
> happen on my other machine. What's wrong, and how can I fix it?

Removing the directories works because it happens to remove the files, too.
You should just be able to, as noted above, move the obstructing files and
CVS should work again. As for why these files are getting corrupted such
that CVS updates don't work, I dunno. When I've had this problem, it was
because I was just learning Fink and I was spending more time tinkering
with package files rather than letting the maintainers know about any
problems I was coming across. (The latter is preferable as it can let all
Fink users benefit from necessary patches / upgrades etc.) When I stopped
editing them the CVS problems faded away over time.

If this is a recurring problem for you, then something more subtle and
tricky to fix may be going on. Are you having the problem re-occur on
anything, &/or is it happening on files that you're sure weren't edited,
had the timestamps changed, etc?



-- 
Chris Devers   [EMAIL PROTECTED]
DO  NOT  LEAVE  IT  IS  NOT  REAL



-------------------------------------------------------
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to