Grace @ 5.1.24, failed to fetch archive

[christian_moestrup.jessen@…]

My first attempt at using Macports is not yet successful. OSX 10.9.5 XCODE Version 6.0.1 (6A317)

Kindly /Chr

--->  Computing dependencies for grace
--->  Dependencies to be installed: openmotif xorg-libXp xorg-printproto pdflib xpm
--->  Fetching archive for xorg-printproto
--->  Attempting to fetch xorg-printproto-1.0.5_0.darwin_13.noarch.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/xorg-printproto
--->  Attempting to fetch xorg-printproto-1.0.5_0.darwin_13.noarch.tbz2.rmd160 from http://mse.uk.packages.macports.org/sites/packages.macports.org/xorg-printproto
Error: org.macports.archivefetch for port xorg-printproto returned: Failed to fetch signature for archive: The requested URL returned error: 400 Bad Request
Error: Failed to install xorg-printproto
Please see the log file for port xorg-printproto for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_xorg-printproto/xorg-printproto/main.log
Error: The following dependencies were not installed: openmotif xorg-libXp xorg-printproto pdflib xpm
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port grace failed

[ryandesign (Ryan Carsten Schmidt)]

Try again, perhaps? It works fine here.

[christian_moestrup.jessen@…]

Thank you for a reply Ryan

I have tried a few times - also other ports. Some ports work while others fail. For Grace "xorg-printproto" cannot be fetched while for e.g. Pymol the fetch of "xorg-inputproto" fails.

/Chr

[ryandesign (Ryan Carsten Schmidt)]

We've had a few other reports of problems like this with other ports, which are also still open. I'm sorry; I have no idea why this might be happening. If the problem always occurs with a particular packages server (above you showed "mse.uk.packages.macports.org" being used), you can block MacPorts from using that server by adding them to host_blacklist in macports.conf; see if another host works better.

[christian_moestrup.jessen@…]

Replying to ryandesign@…:

We've had a few other reports of problems like this with other ports, which are also still open. I'm sorry; I have no idea why this might be happening. If the problem always occurs with a particular packages server (above you showed "mse.uk.packages.macports.org" being used), you can block MacPorts from using that server by adding them to host_blacklist in macports.conf; see if another host works better.

Thank you very much Ryan. Blacklisting the mse.uk.packages.macports.org server did solve the problem. /Chr