This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: setup problems when updating cygwin1.dll


Igor Peshansky wrote:
> Hmm, one way of addressing this would be to also schedule the postinstall
> scripts to run on reboot, rather than running them at that point.
>   
> FWIW, any DLL change can prompt such behavior...  It's just more common
> with cygwin1.dll.
>   
Mhh... I guess just adding a warning it may happen and a suggestion to
maybe reinstall the whole package could be enough, else we're opening a
whole new Pandora's box... isn't it?
FWIW: I don't have much setup.exe-wise experience... and developing some
it is not very high in my todo-list either ;-)
>> Ah, I also had a local package aspell-it whose .tar.bz2 was
>> "truncated" as far as "tar" told, but that setup.exe extracted in an
>> "infinite file" (I killed it when it had already extracted 840MB out
>> of a 33MB file).
> Hmm, that's a completely separate issue.  If you still have that
> "truncated" file, it would be useful in figuring out whether setup's tar
> algorithm has a bug.  Does the command-line tar have the same problem?
Yup, sure it is separated.
Yes, I tought to have deleted it, bit I happen to have one more copy
somewhere.
Here it is:
http://cyberx.lapo.it/cygwin/aspell-it/aspell-it-0.53.0-1.tar.bz2

With command-line tar it is good, well.. not quite, but at least it does
fail somewhat gracefully:

% tar tjvf aspell-it-0.53.0-1.tar.bz2
drwxrwxrwx lapo/None         0 2005-08-18 18:29:10 usr/
drwxrwxrwx lapo/None         0 2005-08-18 18:28:58 usr/lib/
drwxrwxrwx lapo/None         0 2005-08-18 18:29:07 usr/lib/aspell/
-rw-r--r-- lapo/None        70 2005-08-18 18:29:07 usr/lib/aspell/it.multi
-rw-r--r-- lapo/None  39342080 2005-08-18 18:29:07 usr/lib/aspell/it.rws

bzip2: Compressed file ends unexpectedly;
        perhaps it is corrupted?  *Possible* reason follows.
bzip2: No error
        Input file = (stdin), output file = (stdout)

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

    Lapo


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]