http://bjoernstechblog.rueffer.info/posts/macports/mac/2012/11/10/Another-macports-upgrade-problem/
last updated on 25 May 2018

10 November 2012

Another macports upgrade problem

On a different machine I still had problems with upgrading, even after recompiling a lot of packages with the help of this step here:

$sudo port -bcR upgrade requested 
--->  Computing dependencies for inkscape
--->  Fetching archive for inkscape
--->  Attempting to fetch inkscape-0.48.3.1_6+python27.darwin_10.x86_64.tbz2 from http://lil.fr.packages.macports.org/inkscape
--->  Attempting to fetch inkscape-0.48.3.1_6+python27.darwin_10.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/inkscape
--->  Attempting to fetch inkscape-0.48.3.1_6+python27.darwin_10.x86_64.tbz2 from http://packages.macports.org/inkscape
Error: org.macports.archivefetch for port inkscape returned: archivefetch failed for inkscape @0.48.3.1_6+python27
Please see the log file for port inkscape for details:
	/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_inkscape/inkscape/main.log
Error: Unable to upgrade port: 1
To report a bug, follow the instructions in the guide:
	http://guide.macports.org/#project.tickets

In this case, I hadn’t clean up all the obsolete packages, that were no longer needed. Here is how I removed those. First, run

$port uninstall leaves

repeatedly, to remove installed ports that are unrequested and have no dependents, until it says that it cannot remove any more packages (Error: No ports matched the given expression). You will find that you have to run it quite a few times before this happens. The desired upgrade still wouldn’t work, so I had to uninstall inkscape (all versions of it) and repeat the above iterative procedure.

Next I found out that some version of git-core could not be upgraded. I resorted to uninstalling all versions of git-core and qgit, which depends on git-core. Same for ImageMagick, p5.12-perlmagick, imageindex. And I wonder if this is all really necessary to do by hand? And indeed, there’s the command

$port uninstall --follow-dependents ⟨package name⟩

Why hadn’t I seen that earlier. Anyways, I now realize it might be better to not pass the -R option in the original command, as effectively a lot of packages get updated, and maybe that’s more than necessary. So I try a plain

$port -bc upgrade requested

and … after a while …

[...]
--->  Computing dependencies for ruby
--->  Fetching archive for ruby
--->  Attempting to fetch ruby-1.8.7-p371_0.darwin_10.x86_64.tbz2 from http://lil.fr.packages.macports.org/ruby
--->  Attempting to fetch ruby-1.8.7-p371_0.darwin_10.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/ruby
--->  Attempting to fetch ruby-1.8.7-p371_0.darwin_10.x86_64.tbz2 from http://packages.macports.org/ruby
Error: org.macports.archivefetch for port ruby returned: archivefetch failed for ruby @1.8.7-p371_0
Please see the log file for port ruby for details:
	/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ruby/ruby/main.log
Error: Problem while installing ruby
To report a bug, follow the instructions in the guide:
	http://guide.macports.org/#project.tickets
$sudo port upgrade ruby
Error: ruby is not installed
To report a bug, follow the instructions in the guide:
	http://guide.macports.org/#project.tickets

WTF?

Björn Rüffer — Copyright © 2009–2018 — bjoern.rueffer.info