Charles Lepple wrote: > Martin, > > I'd be curious to see how far those ctimes are from the current > time(). Can you post your patch?
They are just printed out with format %i. To get the real time, you can run these numbers through "/bin/date -r": % /bin/date -r 1172946146 Sat Mar 3 19:22:26 CET 2007 Your result will be different according to your time zone, but it is about 7 minutes prior to the time stamp on Daniel's message. [] >> tar: ./sw/sbin/synaptic: file changed as we read it >> ===== >> Old ctime: 1172946146 >> New ctime: 1172946150 >> Old size : 14130940 >> New size : 14130940 OK, no size change, just 4 secs difference in ctime. If this is confirmed by others, it means IMHO that we should patch our tar and just rip the non-zero error code out. The discussion on the tar mailing list dmacks was pointing to shows anyway that the introduction of a non-zero return value at this point was a spontaneous brain fart of the tar developer. -- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/fink-devel
