Yes I am seeing the same thing too.
Agreed, fink should use the existing (dirty) index in this case. It does seem to do so when a package is specified ("fink list zip" or "fink apropos zip" for example).
I believe I have seen this problem even before my last patch, but it certainly is occurring more frequently now. I'm not sure what is happening but I will have another look at my code submission to see what is going on.
But I wonder where this number "291" packages is coming from (240 on my system). Is this the number of debs/binary programs?
Carsten
On Monday, January 27, 2003, at 01:38 pm, Max Horn wrote:
One of the last changes to speed up re-index causes a regression. Now if I enter e.g. "fink list -o" when my index is dirty, I get this:
fink list -o
Fink has detected that your package cache is out of date and needs an
update, but does not have privileges to modify it. Please re-run fink as
root, for example with a "fink index" command.
Information about 291 packages read in 1 seconds.
Uhm... what? That's definitly not right!
Either we should do it as it used to be (that is, build the cache, but simply not store it), with the warning message as it is.
Or we should use the existing (dirty) index and print out a warning that the index needs to be rebuilt.
But only reading a fraction of the real index is of course bad.
Cheers,
Max
------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
