Opened 13 years ago

Closed 13 years ago

#33227 closed defect (fixed)

postflight fails when home directory is on disk with space in its name

Reported by: freespace+macforge@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 2.0.3
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port:

Description (last modified by ryandesign (Ryan Carsten Schmidt))

On a fresh 10.7.2 install, when installing macports 2.0.3 using the pkg failure is reported. Upon examining install.log, the following is emitted:

Feb 12 17:52:13 solaris installd[1461]: ./postflight: Successful!
Feb 12 17:52:13 solaris installd[1461]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “MacPorts-2.0.3.pkg”." UserInfo=0x1048422d0 {NSFilePath=./postflight, NSURL=file://localhost/Volumes/MacPorts-2.0.3/MacPorts-2.0.3.pkg, PKInstallPackageIdentifier=org.macports.MacPorts, NSLocalizedDescription=An error occurred while running scripts from the package “MacPorts-2.0.3.pkg”.} {
	    NSFilePath = "./postflight";
	    NSLocalizedDescription = "An error occurred while running scripts from the package \U201cMacPorts-2.0.3.pkg\U201d.";
	    NSURL = "file://localhost/Volumes/MacPorts-2.0.3/MacPorts-2.0.3.pkg";
	    PKInstallPackageIdentifier = "org.macports.MacPorts";
	}

Despite this, port does appear to be properly installed.

Attachments (1)

install.log (391.2 KB) - added by freespace+macforge@… 13 years ago.

Download all attachments as: .zip

Change History (4)

Changed 13 years ago by freespace+macforge@…

Attachment: install.log added

comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Component: portsbase
Description: modified (diff)

I assume this means your ports tree did not sync. Try running "sudo port -v selfupdate" and see if you get any more detailed errors.

comment:2 Changed 13 years ago by freespace+macforge@…

Output of "sudo port -v selfupdate":

steve@solaris:~
$ sudo port -v selfupdate
Password:
--->  Updating MacPorts base sources using rsync
receiving file list ... done
base.tar

sent 10864 bytes  received 111 bytes  2438.89 bytes/sec
total size is 3226624  speedup is 294.00
receiving file list ... done
base.tar.rmd160

sent 64 bytes  received 116 bytes  51.43 bytes/sec
total size is 512  speedup is 2.84
MacPorts base version 2.0.3 installed,
MacPorts base version 2.0.3 downloaded.
--->  Updating the ports tree
Synchronizing local ports tree from rsync://rsync.macports.org/release/tarballs/ports.tar
receiving file list ... done
ports.tar

sent 48834 bytes  received 1219 bytes  7700.46 bytes/sec
total size is 48494592  speedup is 968.86
receiving file list ... done
ports.tar.rmd160

sent 64 bytes  received 636 bytes  200.00 bytes/sec
total size is 512  speedup is 0.73
Creating port index in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports

Total number of ports parsed:	0 
Ports successfully parsed:	0 
Ports failed:			0 
Up-to-date ports skipped:	13616

--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you should run
  port upgrade outdated

Everything seem OK.

comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Resolution: fixed
Status: newclosed
Summary: Installer reports failure despite postflight report successpostflight fails when home directory is on disk with space in its name

Ok, sorry, I made the wrong assumption. Looking at your log now, first of all, the first 2590 lines can be ignored as they concern packages other than MacPorts.

I do see a number of errors, relating to the fact that your home directory is not on your startup disk, and the disk that the home directory is on has a space in its name ("OS X"). I already fixed this in MacPorts base in r84345 but we have not released a new version of MacPorts since then; until we do, users should use hard disk names that do not contain spaces.

Because of this problem, according to the log: "An attempt to backup your original configuration file failed! Please set your MacPorts compatible environment manually." Instructions are in the Guide.

Note: See TracTickets for help on using tickets.