public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Please test latest developer snapshot
Date: Fri, 18 Feb 2011 13:34:00 -0000	[thread overview]
Message-ID: <AANLkTikP3C+5AMyftCx_QQeM6DvsOHUCfqBpjwNSJfgx@mail.gmail.com> (raw)
In-Reply-To: <20110218123549.GJ29762@calimero.vinschen.de>

On Fri, Feb 18, 2011 at 1:35 PM, Corinna Vinschen  wrote:
> On Feb 17 19:14, marco atzeri wrote:
>> On Thu, Feb 17, 2011 at 1:04 PM, Corinna Vinschen  wrote:
>> > Hi crowd,
>> >
>> >
>> > After the last round of patches we're now heading towards the
>> > 1.7.8 release.  Therefore I'd like to ask you to give the latest
>> > developer snapshot from http://cygwin.com/snapshots/ a try.
>>
>> Corinna,
>>
>> could you check ?
>>
>> $ bunzip2 -tvv cygwin1-20110215.dbg.bz2
>>   cygwin1-20110215.dbg.bz2:
>>     [1: huff+mtf rt+rld]
>>     [2: huff+mtf rt+rld]
>>     [3: huff+mtf rt+rld]
>>     [4: huff+mtf rt+rld]
>>     [5: huff+mtf rt+rld]
>>     [6: huff+mtf rt+rld]
>>     [7: huff+mtf rt+rld]
>>     [8: huff+mtf rt+rld]
>>     [9: huff+mtf rt+rld]
>>     [10: huff+mtf rt+rld]
>>     [11: huff+mtf rt+rld]
>>     [12: huff+mtf file ends unexpectedly
>>
>> You can use the `bzip2recover' program to attempt to recover
>> data from undamaged sections of corrupted files.
>
> I just checked, the file on cygwin.com is not corrupted and I can
> bunzip it on my machine.
>
>
> Corinna
>

Thanks,
it seems a proxy/filter problem in the middle

$ wget http://cygwin.org/snapshots/cygwin1-20110215.dbg.bz2
--2011-02-18 14:29:12--  http://cygwin.org/snapshots/cygwin1-20110215.dbg.bz2
Resolving cygwin.org (cygwin.org)... 209.132.180.131
Connecting to cygwin.org (cygwin.org)|209.132.180.131|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2910590 (2.8M) [application/x-bzip2]
Saving to: `cygwin1-20110215.dbg.bz2'

99% [=====================================> ] 2,899,968    183K/s   in 16s

2011-02-18 14:29:30 (175 KB/s) - Connection closed at byte 2899968. Retrying

Marco

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2011-02-18 13:34 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 12:04 Corinna Vinschen
2011-02-17 18:06 ` Ken Brown
2011-02-17 18:15 ` marco atzeri
2011-02-18 12:36   ` Corinna Vinschen
2011-02-18 13:34     ` marco atzeri [this message]
2011-02-17 19:33 ` Aaron Peromsik
2011-02-17 20:15 ` Yaakov (Cygwin/X)
2011-02-19 18:29 ` Warren Young
2011-02-19 18:35   ` Warren Young
2011-02-19 20:35     ` Warren Young
2011-02-20 12:16       ` Corinna Vinschen
2011-02-21 14:16   ` Eric Blake
2011-02-21 15:21     ` Thomas Wolff
2011-02-26  0:25       ` Vorfeed Canal
2011-02-26  0:45         ` Eric Blake
2011-02-26  1:03         ` Thomas Wolff
2011-02-27  7:35           ` Vorfeed Canal
2011-02-27 10:21             ` Vorfeed Canal
2011-02-27 11:21             ` Vorfeed Canal
2011-02-24 14:57 ` Chris Sutcliffe
2011-02-24 15:16   ` Corinna Vinschen
2011-02-24 19:34     ` Karl M
2011-02-24 20:56       ` Reini Urban
2011-02-24 21:52 ` Kai Tietz
2011-02-25  9:47   ` Corinna Vinschen
2011-02-25 23:25 ` David Rothenberger
2011-02-26  0:09   ` David Rothenberger
2011-02-26  9:51     ` marco atzeri
2011-02-26 10:36     ` Corinna Vinschen
2011-02-27 14:15       ` Corinna Vinschen
2011-02-27 18:45         ` David Rothenberger
2011-03-01  7:06     ` Christopher Faylor
2011-03-01 15:51       ` David Rothenberger
2011-02-18 15:34 Angelo Graziosi
2011-02-19 16:05 ` jdzstz - gmail dot com
2011-02-27 15:03 Angelo Graziosi
     [not found] <AANLkTim4xT_LL=CGFXhgKmO0gLd5P_rXctaMpHwT2pxn@mail.gmail.com>
2011-03-03 12:22 ` Oleg Marchuk
2011-03-03 12:53   ` Oleg Marchuk
2011-03-03 16:41     ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikP3C+5AMyftCx_QQeM6DvsOHUCfqBpjwNSJfgx@mail.gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).