Timeouts with v0.3.8 and v0.3.7

[chriscool]

I get:

#  sharness/bin/ipfs-update install v0.3.8
installing ipfs version v0.3.8
ERROR: fetching resource: 408 Request Timeout
install failed, reverting changes...
ERROR: 408 Request Timeout: Path Resolve error: context deadline exceeded

#  sharness/bin/ipfs-update install v0.3.7
installing ipfs version v0.3.7
ERROR: fetching resource: 408 Request Timeout
install failed, reverting changes...
ERROR: 408 Request Timeout: Path Resolve error: context deadline exceeded

#  sharness/bin/ipfs-update install v0.3.10
installing ipfs version v0.3.10
ERROR: fetching resource: 404 Not Found
install failed, reverting changes...
ERROR: 404 Not Found: Path Resolve error: no link named "v0.3.10" under QmctgsD3G5MrvUcuVAZ6tVXP2c2pkgsEsqT85gQaTcfGjw 

So basically I can only write tests using v0.3.9.

[whyrusleeping]

0.3.10 hasnt been pushed out to the distributions yet (ipfs update pulls from a build of 'dist.ipfs.io'). The other ones should be back up now, I thought I had them pinned, but it seems i was wrong.

[chriscool]

Great, thanks!

[chriscool]

And what about 0.4.0 by the way?

[jbenet]

getting Path Resolve error: context deadline exceeded is so painful for users. it's like "wat?"

[chriscool]

Yeah I still get that too for v0.3.7:

#  sharness/bin/ipfs-update install v0.3.7
installing ipfs version v0.3.7
ERROR: fetching resource: 408 Request Timeout
install failed, reverting changes...
ERROR: 408 Request Timeout: Path Resolve error: context deadline exceeded

But it's working for v0.3.8:

#  sharness/bin/ipfs-update install v0.3.8
installing ipfs version v0.3.8
binary downloaded, verifying...
success!
installing new binary to /usr/local/bin/ipfs

installation complete.

[chriscool]

Also installing the same version twice fails:

root@3416e74c98e9:/mnt# sharness/bin/ipfs-update install v0.3.8
installing ipfs version v0.3.8
binary downloaded, verifying...
success!
installing new binary to /usr/local/bin/ipfs

installation complete.

root@3416e74c98e9:/mnt# echo $?
0

root@3416e74c98e9:/mnt# sharness/bin/ipfs-update install v0.3.8
installing ipfs version v0.3.8
binary downloaded, verifying...
success!
stashing old binary
installing new binary to /usr/local/bin/ipfs/ipfs
ERROR: Install failed:  error moving new binary into place: open /usr/local/bin/ipfs/ipfs: no such file or directory
install failed, reverting changes...
Error reverting
failed to replace binary after install fail:  open /usr/local/bin/ipfs/ipfs: no such file or directory
sorry :(
your old ipfs binary should still be located at:  /root/.ipfs/old-bin/ipfs-v0.3.8
try: `mv "/root/.ipfs/old-bin/ipfs-v0.3.8" "/usr/local/bin/ipfs/ipfs"`
ERROR: error moving new binary into place: open /usr/local/bin/ipfs/ipfs: no such file or directory 

root@3416e74c98e9:/mnt# echo $?
1

[chriscool]

Actually I also get the above when installing v0.3.8 when v0.3.9 is already installed.

[jbenet]

I have a new distributions root:

• /ipfs/QmeEVmRTDX2c9zjPtjHJG6GidrFL7NjqEqP1Q4am6sLfif
• see it: https://ipfs.io/ipfs/QmeEVmRTDX2c9zjPtjHJG6GidrFL7NjqEqP1Q4am6sLfif
• includes 0.3.10 and 0.4.0-dev: https://ipfs.io/ipfs/QmeEVmRTDX2c9zjPtjHJG6GidrFL7NjqEqP1Q4am6sLfif/go-ipfs
• it has not been published to update.ipfs.io so this tool wont find it yet -- track update.ipfs.io dnslink? infra#139

@chriscool test 0.4.0 as 0.4.0-dev for now. this one will be removed once we ship proper 0.4.0.

[harlantwood]

When I click on changelog ( https://ipfs.io/ipfs/QmeEVmRTDX2c9zjPtjHJG6GidrFL7NjqEqP1Q4am6sLfif/go-ipfs/v0.3.10/changelog )

I get Path Resolve error: no link named "changelog" under QmRU3WnKuzyEbyEd7Y8L4Lfhh7sWX68axtqJTkgpc9k3um

[whyrusleeping]

@jbenet did you pin that hash?

[jbenet]

There's no changelog in that dir:
https://ipfs.io/ipfs/QmeEVmRTDX2c9zjPtjHJG6GidrFL7NjqEqP1Q4am6sLfif/go-ipfs/v0.3.10/
we may not be collecting the changelog yet! -- bug for distributions.ipfs.io

On Wed, Dec 16, 2015 at 4:35 AM Jeromy Johnson [email protected]
wrote:

@jbenet https://github.com/jbenet did you pin that hash?

—
Reply to this email directly or view it on GitHub
#7 (comment).