On Sunday, March 31, 2002, at 05:04 PM, Chris Devers wrote:
> Yes, it's a solved problem. If you're manually moving things around in
> the file trees that Fink/CVS wants to update, then it's bound to happen
> sooner or later, and fixing it is no big deal. As the error messages you
> got indicate, the solution is to move (or just delete) the files that are
> in the way of what CVS needs to update.
>
>> I noted that these were all packages, formerly in unstable, that I
>> updated last
>> week (when I update gnome).
>
> Very astute. This is indeed the usual way for this problem to crop up.
>
>> I am going to try moving them to the local branch and see what happens.
>
> Good solution in this case. It should fix the problem.
>
>> Perhaps this is what has happened to other people?
>
> Yep :)
>
Not exactly! The selfupdate problems here occurred on a machine that had
been running unstable from cvs for months, so there certainly wasn't
anything moved manually into stable. It also did not print out that
helpful advice to remove the .info and .patch files, just errors of the
kind
cvs server: dists/stable/main/finkinfo/gnome/gnome-libs-1.4.1.2-4.info is
no longer in the repository
The same seems to have happened for at least one other user. However,
removing the files solved the problem nonetheless. It did happen after I
had not updated for a relatively long time, so I believe the updating
script (or cvs?) can only digest so many of these errors, or it somehow
loses track of old versions after some time. I would still consider it a
bug of some sort.
Derek
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
