Port upgrade outdated sequence

Peter Brommer p.brommer at warwick.ac.uk
Mon Jan 6 11:07:27 PST 2014


Hi Ryan,

thank you for your reply.

On 6 Jan 2014, at 18:50, Ryan Schmidt <ryandesign at macports.org> wrote:

> 
> On Jan 6, 2014, at 12:37, Peter Brommer <p.brommer at warwick.ac.uk> wrote:
> 
>> I ran into a problem running port upgrade outdated today. Among the packages to be upgraded were libLASi (from 1.1.1_0 to 1.1.1_1) and graphviz (from 2.34.0_1+pangocairo+x11 to 2.34.0_4+pangocairo+x11). However, the port upgrade command chose to execute the upgrade in an unfortunate sequence: First it tried to upgrade graphviz, which failed due to the bug in ticket https://trac.macports.org/ticket/41567 - 
> 
> That ticket is about libLASi, not graphviz, and was resolved 6 weeks ago.

That was actually not my point.

> 
>> when the proper behaviour would have been to upgrade libLASi first. This required a manual intervention, which IMHO is not user friendly.
>> 
>> Does the port upgrade command have any logic in determining the order of upgrades? Or is this something that needs to be specified on the port file level? In this case, graphviz lib-depends on libLASi, so should port not try upgrading the deps before a package?
> 
> It does.

I just noticed that it was not port upgrade that did the out-of-order install, but rather a "rebuild after database errors". My first port upgrade command ran into bug https://trac.macports.org/ticket/41737 (against webkit-gtk, which appears to be still open). The workaround requires running 
port -f deactivate webkit-gtk
port install webkit-gtk-2.0

The latter command resulted in the following output:
[..]
--->  Cleaning webkit-gtk-2.0
--->  Updating database of binaries: 100.0%
--->  Scanning binaries for linking errors: 100.0%
--->  Found 412 broken file(s), matching files to ports
--->  Found 27 broken port(s), determining rebuild order
--->  Rebuilding in order
     py27-matplotlib @1.3.1 +tkinter
     pymol @1.6.0 
     qt4-mac @4.8.5 
     wxPython-3.0 @2.9.5 
     wxWidgets-3.0 @3.0.0 
     ImageMagick @6.8.7-3 +x11
     gimp2 @2.8.8 +help_browser+python27
     GraphicsMagick @1.3.18 +q8
     gnuplot @4.6.4 +aquaterm+luaterm+pangocairo+wxwidgets+x11
     mplayer-devel @36449 
     openmotif @2.3.4 
     ddd @3.3.12 
     netpbm @10.64.04 
     graphviz @2.34.0 +pangocairo+x11
     transfig @3.2.5d 
     povray @3.7.0.0 
     xcursorgen @1.0.5 
     grace @5.1.23 
     libsdl_image @1.2.12 
     xorg-libXfont @1.4.6 
     gtkglext @1.2.0 
     gtkmm @2.24.4 +x11
     gtkimageview @1.6.4 
     ufraw @0.19.2 
     gtkspell2 @2.0.16 +x11
     inkscape @0.48.4 +python27+x11
     octave @3.2.4 +atlas+gcc47-gcc45
[snip..much later]
--->  Computing dependencies for graphviz
--->  Fetching archive for graphviz
--->  Attempting to fetch graphviz-2.34.0_4+pangocairo+x11.darwin_12.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/graphviz
--->  Attempting to fetch graphviz-2.34.0_4+pangocairo+x11.darwin_12.x86_64.tbz2 from http://lil.fr.packages.macports.org/graphviz
--->  Attempting to fetch graphviz-2.34.0_4+pangocairo+x11.darwin_12.x86_64.tbz2 from http://packages.macports.org/graphviz
--->  Fetching distfiles for graphviz
--->  Verifying checksums for graphviz
--->  Extracting graphviz
--->  Configuring graphviz
--->  Building graphviz
Error: org.macports.build for port graphviz returned: command execution failed

The "repair" job thus tried to rebuild graphviz, without upgrading libLASi beforehand, and thus failed.

I do apologise for my incorrect earlier e-mail; the problem was not with port upgrade, but with whatever it is that checks for broken ports. Please do let me know if this is a bug and I will file a ticket.

Peter



More information about the macports-dev mailing list