Opened 11 years ago
Closed 11 years ago
#39140 closed defect (worksforme)
textmate2 @2.0.9417 fetch fails
Reported by: | jonathanyoung1@… | Owned by: | neverpanic (Clemens Lang) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | lack-of-interest | Cc: | |
Port: | textmate2 |
Description
Multiple attempts at textmate2 port install throughout the day. Updated macports, ports. Installed latest version of git-core and still getting same error. Noticed in main.log that all attempts "to fetch textmate2-2.0.9417_0.darwin_11.x86_64.tbz2 from..." failed with the error "Fetching archive failed:: The requested URL returned error: 404"
Later in the main.log, during "info:fetch Cloning into 'PlugIns/dialog'...", I get "fetch error: operation timed out after 300010 milliseconds..." The install has also timed out while "Cloning into 'PlugIns/dialog-1.x" as well. In my most recent install attempt, during "info:fetch Cloning into 'PlugIns/dialog'..." i get ":info:fetch fatal: The remote end hung up unexpectedly". I've included main.log files. Thanks.
Attachments (3)
Change History (8)
Changed 11 years ago by jonathanyoung1@…
Changed 11 years ago by jonathanyoung1@…
comment:1 follow-up: 2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to cal@… |
---|---|
Summary: | textmate2 @2.0.9417 fetch for port textmate2 returned: command execution failed → textmate2 @2.0.9417 fetch fails |
comment:2 Changed 11 years ago by jonathanyoung1@…
Replying to ryandesign@…:
Replying to jonathanyoung1@…:
Multiple attempts at textmate2 port install throughout the day. Updated macports, ports. Installed latest version of git-core and still getting same error. Noticed in main.log that all attempts "to fetch textmate2-2.0.9417_0.darwin_11.x86_64.tbz2 from..." failed with the error "Fetching archive failed:: The requested URL returned error: 404"
That's not a problem. That just means there is no pre-compiled binary available, therefore MacPorts tries to compile it on your system. But it never even gets to trying to compile it because it fails to fetch it:
Later in the main.log, during "info:fetch Cloning into 'PlugIns/dialog'...", I get "fetch error: operation timed out after 300010 milliseconds..." The install has also timed out while "Cloning into 'PlugIns/dialog-1.x" as well. In my most recent install attempt, during "info:fetch Cloning into 'PlugIns/dialog'..." i get ":info:fetch fatal: The remote end hung up unexpectedly". I've included main.log files. Thanks.
Is your network particularly unreliable? This port fetches the source and many submodules from git so there's lots of back and forth traffic with github; if your network is prone to dropping connections then this could explain why the fetch would fail at various points.
Thanks for your response. I wouldn't say it is particularly unreliable, but it is slow (1 Mbps download speed). I don't usually have issues streaming Netflix, etc. That being said, the first thing I thought was that it was my network, which is why I tried to install about 20 different times throughout the day.
Changed 11 years ago by jonathanyoung1@…
comment:3 Changed 11 years ago by jonathanyoung1@…
I've now gotten significantly further now, but the port still fails.
comment:4 Changed 11 years ago by neverpanic (Clemens Lang)
It works fine for me; I fear there's not much I can do for you. Are you still seeing these problems?
comment:5 Changed 11 years ago by neverpanic (Clemens Lang)
Keywords: | lack-of-interest added |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
Replying to jonathanyoung1@…:
That's not a problem. That just means there is no pre-compiled binary available, therefore MacPorts tries to compile it on your system. But it never even gets to trying to compile it because it fails to fetch it:
Is your network particularly unreliable? This port fetches the source and many submodules from git so there's lots of back and forth traffic with github; if your network is prone to dropping connections then this could explain why the fetch would fail at various points.