#17762: 1.7 - install/upgrade broken with direct/archivemode --------------------------------+------------------------------------------- Reporter: dluke@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts 1.7.1 Component: base | Version: 1.7.0 Keywords: | Port: --------------------------------+------------------------------------------- Comment(by dluke@…): Replying to [comment:1 blb@…]:
Does this occur when only one install of the port being unnecessarily unarchived is available, or when there are multiple choices for the that port?
I'm not sure what you're asking since with direct mode there's only ever one choice that's available (the current portfile's version/revision) as that's the only archive that will be looked for. I see it happen with ports that I only have one archive (the current version/revision) and ports that have multiple archives available, though. When looking at one of the ports where I see this problem, it's always the third time it appears that MacPorts is looking to see if it's installed that that lookup fails and MacPorts decides to unarchive it (in order to install it). If the Portfile hasn't changed, of course, the install is skipped after the unarchive since MacPorts notices that the port is already installed.
Also, what's the error output from port when the Portfile is later than the archive?
% sudo touch `port dir db46` % sudo port -dv upgrade subversion-javahlbindings ... ---> Installing db46 @4.6.21_3 DEBUG: Executing org.macports.install (db46) Error: Target org.macports.install returned: Registry error: db46 @4.6.21_3 already registered as installed. Please uninstall it first. Warning: the following items did not execute (for db46): org.macports.install Error: The following dependencies failed to build: apr-util db46 cyrus- sasl2 zlib gettext junit hamcrest-core apache-ant -- Ticket URL: <http://trac.macports.org/ticket/17762#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS