Opened 10 months ago

Last modified 6 months ago

#60513 assigned defect

emacs-app-devel-20200417_0+imagemagick+rsvg.darwin_19.x86_64: unable to access 'http://git.savannah.gnu.org/r/emacs.git/': The requested URL returned error: 502

Reported by: breadncup Owned by: drkp (Dan Ports)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: emacs-app-devel

Description (last modified by breadncup)

I'm not able to upgrade emacs-app-devel via port, and it's blocking my work. Please, check this out.

:debug:fetch system: /usr/bin/git clone --progress http://git.savannah.gnu.org/r/emacs.git /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_emacs/emacs-app-devel/work/emacs-20200417 2>&1
:info:fetch Cloning into '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_emacs/emacs-app-devel/work/emacs-20200417'...
:info:fetch fatal: unable to access 'http://git.savannah.gnu.org/r/emacs.git/': The requested URL returned error: 502
:info:fetch Command failed: /usr/bin/git clone --progress http://git.savannah.gnu.org/r/emacs.git /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_editors_emacs/emacs-app-devel/work/emacs-20200417 2>&1
:info:fetch Exit code: 128
:error:fetch Failed to fetch emacs-app-devel: Git clone failed
:debug:fetch Error code: NONE
:debug:fetch Backtrace: Git clone failed

Attachments (1)

main.log (5.2 KB) - added by breadncup 10 months ago.
main.log

Download all attachments as: .zip

Change History (3)

Changed 10 months ago by breadncup

Attachment: main.log added

main.log

comment:1 Changed 10 months ago by breadncup

Description: modified (diff)

comment:2 Changed 6 months ago by ryandesign (Ryan Schmidt)

Owner: set to drkp
Port: emacs-app-devel added
Status: newassigned

Is this still a problem? I would guess there was just a temporary problem with the git.savannah.gnu.org server which has since been resolved.

We are able to build this port on our automated build system, so if it's still returning a 502 error to you, check if there might be a problem with your proxy configuration.

Note: See TracTickets for help on using tickets.