logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ron Grabowski (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LOG4NET-161) downloads abort aftger 4.8mn
Date Mon, 30 Jun 2008 11:39:45 GMT

    [ https://issues.apache.org/jira/browse/LOG4NET-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609204#action_12609204
] 

Ron Grabowski commented on LOG4NET-161:
---------------------------------------

All three of these tickets are for the same thing:

 LOG4NET-159
 LOG4NET-160
 LOG4NET-161

You're going to have to post more information like time of download, the mirror the file was
downloaded from, etc. I was able to download the file ok on 6/30/2008 from 192.87.106.226:

C:\>wget http://archive.apache.org/dist/incubator/log4net/1.2.10/incubating-log4net-1.2.10.zip
--07:37:03--  http://archive.apache.org/dist/incubator/log4net/1.2.10/incubating-log4net-1.2.10.zip
           => `incubating-log4net-1.2.10.zip'
Resolving archive.apache.org... 192.87.106.226
Connecting to archive.apache.org|192.87.106.226|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8,203,576 (7.8M) [application/zip]

100%[====================================>] 8,203,576    442.76K/s    ETA 00:00

07:37:22 (436.94 KB/s) - `incubating-log4net-1.2.10.zip' saved [8203576/8203576]

> downloads abort aftger 4.8mn
> ----------------------------
>
>                 Key: LOG4NET-161
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-161
>             Project: Log4net
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: 1.2.9, 1.2.10
>            Reporter: Stehan Meyn
>
> I tried to download both 1.2.9 and 1.2.10 and the resulting files are 4,923,392 bytes
long. (they are supposed to bemore than 7.65mB).
> I checked  using a different channels (i.e. local lan and broadband wireless) and different
applications (ie. Firefox, IE and wget) - always same result. 
> Since I can't think of other reasons why this should fail in this peculiar way i wonder
if the problem lies at the repository end.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message