-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Feb 26, 2007, at 10:52 PM, Jean-François Mertens wrote: > > On 27 Feb 2007, at 03:17, Jack Howarth wrote: > >> Frankly it is insane that tar hasn't been epoched and regressed >> back to 1.15.1. No other software distro would allow a single >> critical package like this to be left broken for so long. If >> we can rationalize leaving our dpkg at such an old version >> certainly we can also justify leaving tar at 1.15.1. >> Jack > We still don't know whether it is tar which is broken (which I > doubt..), > or whether there is something else going on on _ a couple of, or: > many ? _ > machines.. > > I have built those pkgs as many times as anybody else, on several > machines, (and am building about as much as anybody else, with > "~ 600K files and directories installed"), and have never seen this > problem. > (Waiting desperately to see it once _ to be able to do immediately a > stat > on the files involved, and ps -lxaww, etc...) > > A problem should first be understood, and the clues to its source > can only come from those who suffer from it... I don't know exactly why it's happening, but I have figured out some things. The "file changed as we read it" warning does occur sometimes with tar 1.15.1, but it always returned an exit code of 0 in such cases. It would return 1 if a fatal error occurred. Starting with 1.16, tar now returns 0 for success, 1 for non-fatal errors (like the file changed one) and 2 for fatal errors. The problem is that dpkg- deb fails if tar returns a non-zero exit code. Now dpkg-deb could be patched, but since you'd still want it to fail for truly fatal errors and the fatal error code changed from 1 to 2, it needs to know which version of tar it's using or Bad Things could happen. Another bit of information is that the code in tar that checks if a "file changed as we read it" changed after 1.15.1. Previously, the warning occurred if a file's ctime changed during archiving; now it will also occur if the file's size increases. I don't know why either of these situations is happening though. Daniel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin) Comment: http://homepage.mac.com/danielj7/publickey.txt iD8DBQFF5G324sDFGYouOqARAgajAJ0Vv7lnObPFvk9Ia9lPvB17uzRjOwCfVEU+ Tb8tohjC0QGQuCKXQz2GXKY= =62gL -----END PGP SIGNATURE----- ------------------------------------------------------------------------- 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
