Max Horn wrote: > Am 22.12.2006 um 07:52 schrieb Martin Costabel: > >> Max Horn wrote: >>> For some reasons I didn't update my Fink installation for some time. >>> So today I run a "cvs up" in /sw/fink, then sudo fink list -o >>> >>> This resulted in the following error: >>> >>> Failed: Error performing percent expansion: unknown % expansion or >> I don't think running older versions of fink was ever guaranteed to >> work. > > I beg your pardon? It's an absolute requirement for being able to > upgrade an existing Fink installation, and one of the reasons InfoN > was introduced.
Well, Info2 was introduced because there were new percent expansions in the "Package:" field, and this broke the parsing of the package descriptions in a far more profound way than just the introduction of an unknown percent expansion in the ConfigureParams field. If what you imply were true, it would be impossible to introduce *any* new percent expansion without new InfoN field, and Fink has been doing this without problem many times. >> Any reason why you don't "fink selfupdate" instead of "cvs up", or >> at least "fink update fink"? > > The result would have been the same. Sorry, I didn't understand that you got problems not only with "fink list" and "fink validate", but also with "fink index" and "fink update". Are you sure about this? >> Running "cvs up" has the additional drawback - even if your fink isn't >> out of date - that if you do "fink list" afterwards you will be >> greeted >> by the anal warning "Your index is out of date, and fink has suddenly >> developed a reticence to run itself through sudo, so it can't >> update the >> index, sorry. Please wait 2 minutes while I am sulking" or >> something to >> that effect. > > Well the first command I run after "cvs up" was "sudo fink list -o", > so no problem there. Strange. Perhaps you are running fink always as root? > What failed was updating the index; the very > same would have been the case if I had run "fink selfupdate", which > essentially also run "cvs up", "fink index", and then updates some > select packages. I did the exact same thing as you, from fink-0.25.1-31. After "cvs up" I got the "Fink has detected that your package index cache is missing or out of date etc" message. I also got the parsing error in gmp (not with list -o, because it was up to date, but with "fink list gmp" or with list -i), but no error with "fink index". And it did not prevent me from running "fink update fink" successfully. If you really couldn't run "fink index" successfully, there must be something else going on. > Anyway, we discussed this on #fink last night, and it seems it'll > require a new InfoN versions, and also a new fink release. On this subject I found a nice quote on fink-devel, May 2003: > However, IMHO discussion on IRC are a very bad way to make decissions > about the fate of Fink. Clearly IRC is a great way to discuss these > things raw, but it also excludes many Fink developers from the > discussion, plus it's not really easy to track later how and why a > decision was made. Guess who wrote that? :-) -- Martin ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
