attempting upgrade of nagios leads to large error text

[ray@…]

It looks as if a large-ish perl script is being interpreted as part of the list of variants. It is strange. Perhaps you all can see what is happening.

I will attach the output.

[ray@…]

Almost:

# port uninstall nagios ---> The following versons of nagios are currently installed: ---> nagios 2.0_0 (active) ---> nagios 2.0rc2_0 Error: /opt/local/bin/port: port uninstall failed: Registry error: Please specify the full version as recorded in the port registry. # # # port uninstall nagios @2.0rc2_0 ---> Uninstalling nagios 2.0rc2_0 # # port upgrade nagios ---> Fetching nagios ---> Attempting to fetch nagios-2.1.tar.gz from ​http://puzzle.dl.sourceforge.net/nagios ---> Attempting to fetch nagios-2.1.tar.gz from ​http://mesh.dl.sourceforge.net/nagios ---> Verifying checksum(s) for nagios ---> Extracting nagios ---> Applying patches to nagios ---> Configuring nagios ---> Building nagios with target all ---> Staging nagios into destroot ---> Creating launchd control script ########################################################### # A startup item has been generated that will aid in # starting nagios with launchd. It is disabled # by default. Execute the following command to start it, # and to cause it to launch at startup: # # sudo launchctl load -w /Library/LaunchDaemons/org.darwinports.nagios.plist ########################################################### ---> Deactivating nagios 2.0_0 ---> Packaging tgz archive for nagios 2.1_0 ---> Installing nagios 2.1_0 ---> Activating nagios 2.1_0 Error: Target com.apple.activate returned: can't read "i": no such variable #

[markd@…]

I fixed this in the version bump of the Nagios port to v2.2. The problem was accidentally introduced in v2.1 by not escaping the $ signs in the ui_msg's. Please do a port selfupdate and make sure you have Nagios 2.2 (committed a day ago) and it should be fine.

[ray@…]

Yes. Sorry about that. Uninstalled, cleaned and re-installed and it went fine.

[markd@…]

(In reply to comment #4)

Yes. Sorry about that. Uninstalled, cleaned and re-installed and it went fine.

The error was all mine. :) Thanks for the feedback. I'll close this.