April 2011 - macports-tickets - lists.macosforge.org

[MacPorts] #29000: port upgrade, install... fail with "invalid command name registry::exlcusive_lock"
by MacPorts 02 Apr '11

02 Apr '11

#29000: port upgrade, install... fail with "invalid command name registry::exlcusive_lock" ---------------------------------+------------------------------------------ Reporter: andrew.long@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: ---------------------------------+------------------------------------------ Ran "sudo port selfupdate" - ran to completion as follows:- saganami-island:~ andy$ sudo port selfupdate Password: Warning: port definitions are more than two weeks old, consider using selfupdate ---> Updating the ports tree ---> Updating MacPorts base sources using rsync MacPorts base version 1.9.2 installed, MacPorts base version 1.9.2 downloaded. ---> MacPorts base is already the latest version The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated Then ran sudo port update outdated saganami-island:~ andy$ sudo port upgrade outdated Error: Unable to upgrade port: invalid command name "registry::exclusive_lock" To report a bug, see <http://guide.macports.org/#project.tickets> SImilar failure when trying to install mercurial Regards, Andy -- Ticket URL: <https://trac.macports.org/ticket/29000> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #29005: googlecl @0.9.13_0 may need "noarch"
by MacPorts 02 Apr '11

02 Apr '11

#29005: googlecl @0.9.13_0 may need "noarch" ------------------------------+--------------------------------------------- Reporter: l2g@… | Owner: ram@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: googlecl ------------------------------+--------------------------------------------- It looks like the googlecl port has no architecture-dependent code in it. (I may be wrong.) -- Ticket URL: <https://trac.macports.org/ticket/29005> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #28452: Port won't selfupdate
by MacPorts 02 Apr '11

02 Apr '11

#28452: Port won't selfupdate ------------------------------------------------+--------------------------- Reporter: sachin.srivastava@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: ------------------------------------------------+--------------------------- I am using MacPorts 1.9.1 Xcode version 3.2.5 When trying selfupdate it fails (attaching the config.log file) checking for GNU Objective C runtime... no configure: Using Apple Objective-C runtime checking for Apple Foundation library... no configure: WARNING: GNUSTEP_SYSTEM_ROOT is not defined in your environment, preventing the use of GNUstep's Foundation library configure: error: Could not find a working Foundation implementation shell command "cd /opt/local/var/macports/sources/rsync.macports.org/release/base && ./configure --prefix=/opt/local --with-tclpackage=/Library/Tcl --with- install-user=root --with-install-group=admin --with-directory-mode=0755 --enable-readline && make && make install" returned error 1 Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: shell command failed -- Ticket URL: <https://trac.macports.org/ticket/28452> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #27933: MacPorts @1.9.2 'port upgrade outdated' fails when archive dir is on NFS FS without root access
by MacPorts 02 Apr '11

02 Apr '11

#27933: MacPorts @1.9.2 'port upgrade outdated' fails when archive dir is on NFS FS without root access ---------------------------------+------------------------------------------ Reporter: fred@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 1.9.2 Keywords: | Port: ---------------------------------+------------------------------------------ I have an archive dir on a Linux NFS volume exported with option root_squash, so UID/GID 0,0 is mapped to anonymous. The dir is writable by root from the mac. Installation went fine, all archives were saved in this directory until now. The problem: {{{ # port upgrade outdated Error: Target org.macports.archivefetch returned: lchown: /users/root/OSX/macports/packages/darwin/universal: not owner Log for ncursesw is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_ncursesw/main.log Error: Unable to upgrade port: 1 }}} Explanation: root from the mac is not allowed to chown/lchown directories on this FS (normal Unix/Linux behavior) Question: Is this lchown necessary? Workaround: I moved the archive to a local FS. -- Ticket URL: <https://trac.macports.org/ticket/27933> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #27816: Install error: NSPortTimeoutException. connection timeout: did not receive reply.
by MacPorts 02 Apr '11

02 Apr '11

#27816: Install error: NSPortTimeoutException. connection timeout: did not receive reply. -------------------------------------------------------+-------------------- Reporter: cw10025@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: NSPortTimeoutException IFPKInstallElement | Port: -------------------------------------------------------+-------------------- Attempted to install [http://distfiles.macports.org/MacPorts/MacPorts-1.9.2-10.6-SnowLeopard.dmg] on Snow Leopard 10.6.5 with Xcode-3.2.5 and a prior release of MacPorts (from Leopard, selfupdate wouldn't run). The install failed and left this in the install log: {{{ Dec 30 07:23:17 clozaril-2 Installer[20150]: IFPKInstallElement (1 packages) Dec 30 07:28:17 clozaril-2 Installer[20150]: An exception was thrown from the install queue while running IFPKInstallElement. NSPortTimeoutException. connection timeout: did not receive reply. Dec 30 07:28:17 clozaril-2 Installer[20150]: Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. Dec 30 07:28:18 clozaril-2 Installer[20150]: IFDInstallController 5E20730 state = 7 }}} I took a guess that since X11 was a prerequisite, maybe it needed to be running while the install was running. I started X, then re-ran the installer, then it worked. I don't know if that proves the installer needs X11 running or if it was just a transient error. -- Ticket URL: <https://trac.macports.org/ticket/27816> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #25075: MacPorts 1.9.0-rc1 installer may overwrite conf files
by MacPorts 02 Apr '11

02 Apr '11

#25075: MacPorts 1.9.0-rc1 installer may overwrite conf files ------------------------------+--------------------------------------------- Reporter: brad@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts 1.9.0 Component: ports | Version: Keywords: | Port: ------------------------------+--------------------------------------------- Using the disk image installer to install MacPorts 1.9.0-rc1 over the top of MacPorts current 1.8 it looks like my <prefix>/etc/macports/sources.conf was overwritten by the installer. Installing MacPorts 1.9.0-rc1 from source over the top of MacPorts 1.9.0-rc1 <prefix>/etc/macports/sources.conf was not overwritten. In my searches I could not determine the expected behavior. -- Ticket URL: <http://trac.macports.org/ticket/25075> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9

[MacPorts] #20665: read only binary archive doesn't allow installing new ports
by MacPorts 02 Apr '11

02 Apr '11

#20665: read only binary archive doesn't allow installing new ports --------------------------------+------------------------------------------- Reporter: saml@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Low | Milestone: MacPorts Future Component: base | Version: 1.7.1 Keywords: | Port: --------------------------------+------------------------------------------- I have macports installed on multiple computers. 2 computers have write access to the binary archive path, so I can prebuild packages that I'm installing multiple times. However; on occasion I have a package I might only want to install on one computer and don't want to hassle with building it for the binary archive. When I try to install it on the computer with read-only access to the archive, it gives up when it can't write the archive. What would be the better option would be to continue and give a warning when it can't write the archive. -- Ticket URL: <http://trac.macports.org/ticket/20665> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

Re: [MacPorts] #13601: MacPorts doesn't respect hard links during install phase
by MacPorts 02 Apr '11

02 Apr '11

#13601: MacPorts doesn't respect hard links during install phase --------------------------------------+------------------------------------- Reporter: julien.thewys@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.0.0 Component: base | Version: 1.5.2 Resolution: fixed | Keywords: tcl hard link Port: git-core | --------------------------------------+------------------------------------- Changes (by jmr@…): * status: new => closed * resolution: => fixed * milestone: MacPorts Future => MacPorts 2.0.0 Comment: This should also have been fixed by r77511. -- Ticket URL: <https://trac.macports.org/ticket/13601#comment:11> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #12420: port uninstall fails with { or } in filenames
by MacPorts 02 Apr '11

02 Apr '11

#12420: port uninstall fails with { or } in filenames ---------------------------------+------------------------------------------ Reporter: simon@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 1.9.0 Component: base | Version: 1.5.0 Resolution: fixed | Keywords: Port: | ---------------------------------+------------------------------------------ Changes (by jmr@…): * status: new => closed * resolution: => fixed * milestone: MacPorts Future => MacPorts 1.9.0 Comment: Can't reproduce this; I assume it was fixed in the switch to the sqlite registry. -- Ticket URL: <https://trac.macports.org/ticket/12420#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #10879: RFE: apache2 and other ports won't install as non-root users because of startupitems (was: RFE: apache2 and other ports won't install as non-root users)
by MacPorts 02 Apr '11

02 Apr '11

#10879: RFE: apache2 and other ports won't install as non-root users because of startupitems ------------------------------------+--------------------------------------- Reporter: plambert@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: MacPorts 2.0.0 Component: base | Version: Resolution: fixed | Keywords: Port: | ------------------------------------+--------------------------------------- -- Ticket URL: <https://trac.macports.org/ticket/10879#comment:13> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0