Opened 5 years ago

Closed 5 years ago

#57455 closed defect (invalid)

doxygen install getting 404 errors

Reported by: Kooshy Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.5.4
Keywords: Cc:
Port: doxygen

Description (last modified by jmroot (Joshua Root))

I'm having trouble installing doxygen has the following errors in log and I wonder if this is my trouble: 

:info:archivefetch --->  doxygen-1.8.14_0.darwin_16.x86_64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified
:msg:archivefetch --->  Attempting to fetch doxygen-1.8.14_0.darwin_16.x86_64.tbz2 from https://packages.macports.org/doxygen
:debug:archivefetch Fetching archive failed: The requested URL returned error: 404 Not Found
:msg:archivefetch --->  Attempting to fetch doxygen-1.8.14_0.darwin_16.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/doxygen
:debug:archivefetch Fetching archive failed: The requested URL returned error: 404 Not Found
:msg:archivefetch --->  Attempting to fetch doxygen-1.8.14_0.darwin_16.x86_64.tbz2 from http://kmq.jp.packages.macports.org/doxygen
:debug:archivefetch Fetching archive failed: The requested URL returned error: 404 Not Found

Checking these locations manually shows that the specific file the installer is looking for is missing from all three locations. Servers have doxygen-1.8.9.1_0.darwin_10-14

Attachments (1)

doxygenFailureMain.log​ (75.3 KB) - added by Kooshy 5 years ago.
main.log from install failure

Download all attachments as: .zip

Change History (3)

Changed 5 years ago by Kooshy

Attachment: doxygenFailureMain.log​ added

main.log from install failure

comment:1 Changed 5 years ago by Kooshy

Seems my issue was the location of my Xcode.app / defauly path settings, moving it to /Applications allowed the doxygen to install properly.

comment:2 Changed 5 years ago by jmroot (Joshua Root)

Description: modified (diff)
Resolution: → invalid
Status: new → closed

The location of Xcode.app should not matter as long as it is selected correctly, i.e. xcode-select -print-path reports the right location. Anyway, glad you got it working.

Note: See TracTickets for help on using tickets.