On lundi, avril 29, 2002, at 03:58 , Jean-Fran�ois Mertens wrote: > > But then it means A. Strange indeed has a problem _ at least for those > 2 files ... > He is not the only one, as has been remarked before. This looks like a kind of epidemic now. Several people had a non-working tar, others a dpkg that was not able to extract a control file correctly.
Then there are several people who get "no package name in package ..." for lots of packages, and the package descriptions are 0B files. The latest in the series I saw was someone on fink-beginners who couldn't rebuild autoconf25, and we hunted this down to /usr/bin/texi2html that was a 0B file on his system. When he replaced this by a correct version of texi2html, the compilation of autoconf25 went through correctly. So there is some widespread file corruption going on. I vaguely remember some time last year when people were finding that their /bin/sh or /bin/bash suddenly stopped working and had been replaced by a 0B file. I think in some cases at least the destruction was reversible by a simple reboot. I don't know if this has been tried by the people who are concerned this time? -- Martin _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
