From: Thomas F Herbert <therbert@redhat.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: snapshot for 2.2.0 problem?
Date: Fri, 19 Feb 2016 14:44:04 -0500 [thread overview]
Message-ID: <56C77084.6090901@redhat.com> (raw)
Hi,
I am not sure if anyone has noticed yet this but is the dpdk snapshot
bad today?
wget http://dpdk.org/browse/dpdk/snapshot/dpdk-2.2.0.tar.gz
--2016-02-19 19:35:23--
http://dpdk.org/browse/dpdk/snapshot/dpdk-2.2.0.tar.gz
Resolving dpdk.org (dpdk.org)... 92.243.14.124
Connecting to dpdk.org (dpdk.org)|92.243.14.124|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: ‘dpdk-2.2.0.tar.gz’
[ <=> ] 2,160,380 704KB/s in 3.0s
2016-02-19 19:35:27 (704 KB/s) - ‘dpdk-2.2.0.tar.gz’ saved [2160380]
[therbert@d2fxl02 tmp]$ tar -tvzf dpdk-2.2.0.tar.gz
drwxrwxr-x root/root 0 2015-12-15 17:06 dpdk-2.2.0/
-rw-rw-r-- root/root 0 2015-12-15 17:06 dpdk-2.2.0/.gitignore
-rw-rw-r-- root/root 1826 2015-12-15 17:06 dpdk-2.2.0/GNUmakefile
-rw-rw-r-- root/root 17987 2015-12-15 17:06 dpdk-2.2.0/LICENSE.GPL
-rw-rw-r-- root/root 26530 2015-12-15 17:06 dpdk-2.2.0/LICENSE.LGPL
-rw-rw-r-- root/root 15336 2015-12-15 17:06 dpdk-2.2.0/MAINTAINERS
-rw-rw-r-- root/root 1708 2015-12-15 17:06 dpdk-2.2.0/Makefile
...
-rw-rw-r-- root/root 21510564 2015-12-15 17:06
dpdk-2.2.0/app/test/test_lpm_routes.h
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
--TFH
next reply other threads:[~2016-02-19 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 19:44 Thomas F Herbert [this message]
2016-02-20 12:27 ` snapshot for 2.2.0 problem? Vincent JARDIN
2016-02-20 22:28 ` Thomas F Herbert
2016-02-22 0:28 ` Thomas F Herbert
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=56C77084.6090901@redhat.com \
--to=therbert@redhat.com \
--cc=dev@dpdk.org \
--cc=users@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.