Errors when extracting the ctm file...

[Rommel B. IKEDA]

Thank you very much for the reply...
I know that I have a lot of space because I am using my FreeBSD in my HD 
as my only O.S....but there seems to be some problems with our internet 
connection yesterday...one thing more everytime I try to download using 
Mozilla, especially when downloading CTM Deltas it always gives me an 
automatic *.cgi extension for example downloading 
ports-cur.5000xEmpty.gz would always gives me a "save as" 
ports-cur.5000xEmpty.gz.cgi, I usually delete the cgi and continue 
dowloading...Maybe there is a problem in this...Anyways, I will try to 
find out about it...
Anways...I also received an answer from Mr. NAKAMURA Takeshi...and when 
I followed his instruction...I was able to successfully do it...Anyways, 
this time I used the "fetch" command and I was able to download 
it...Funny about it is, I can always install ports but could never 
cvsup...That is why I am using CTM...

Once again Thank you...

Stefan Eßer wrote:

>On 2003-11-20 15:32 +0900, "Rommel B. IKEDA" <r_ikeda at oisca.org> wrote:
>  
>
>>I downloaded the "ports-cur.5000xEmpty.gz"
>>
>>But when I tried ctm the following came out:
>>
>>ctm: warning: .ctm_status not found 
>>gunzip: stdin: unexpected end of file
>>    
>>
>
>Unexpected end of file !
>
>The CTM file has been truncated (FTP transfer aborted or the disk
>was not able to hold the complete CTM file).
>
>  
>
>>/home/r_ikeda/CTM/ports-cur.5000xEmpty.gz Fatal error: Truncated patch.
>>ctm: exit(65)
>>
>>How can I correctly extract this file in my /usr/ports.
>>My /usr/ports is already empty because I have already remove everything...
>>    
>>
>
>Fetch the file completely and try again.
>
>The command 
>
>$ gzip -tv ports-cur.5000xEmpty.gz
>
>will tell you, whether the file seems to be OK.
>
>Verify that your disk has enough empty space to hold the complete file,
>before retrying the transfer.
>
>You may be lucky and a FTP "reget" may be able to fetch the rest of the 
>file, if a short transfer (aborted because of network problems or a disk
>full condition) was the reason.
>
>Regards, STefan
>
>
>  
>