#46899: policykit upgrade still looking for llvm-3.3 after -3.4 install + select --------------------------+--------------------------- Reporter: dsmithhfx@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: powerpc tiger Port: policykit | --------------------------+--------------------------- Changes (by mf2k@…): * owner: macports-tickets@… => devans@… Old description:

Hi,

After unsuccessful attempt to upgrade llvm-3.3 on 10.4.11 ppc, I read this ticket https://trac.macports.org/ticket/39849 pronouncing it "wontfix" -3.3, & advising to switch to -3.4.

I was able to do this and:

port select --set llvm mp-llvm-3.4 Selecting 'mp-llvm-3.4' for 'llvm' succeeded. 'mp-llvm-3.4' is now active.

However, subsequent upgrade attempts including gconf and policykit are still trying to update llvm-3.3:

sudo port upgrade policykit ---> Computing dependencies for llvm-3.3 ---> Fetching archive for llvm-3.3 [...]

Is there a bug, or how can I enforce the switch to -3.4 in macports?

Thanks

New description: Hi, After unsuccessful attempt to upgrade llvm-3.3 on 10.4.11 ppc, I read this ticket https://trac.macports.org/ticket/39849 pronouncing it "wontfix" -3.3, & advising to switch to -3.4. I was able to do this and: {{{ port select --set llvm mp-llvm-3.4 Selecting 'mp-llvm-3.4' for 'llvm' succeeded. 'mp-llvm-3.4' is now active. }}} However, subsequent upgrade attempts including gconf and policykit are still trying to update llvm-3.3: {{{ sudo port upgrade policykit ---> Computing dependencies for llvm-3.3 ---> Fetching archive for llvm-3.3 [...] }}} Is there a bug, or how can I enforce the switch to -3.4 in macports? Thanks -- Comment: In the future, please use WikiFormatting and Cc the port maintainers ({{{port info --maintainers policykit}}}), if any. -- Ticket URL: <https://trac.macports.org/ticket/46899#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X

#46899: policykit upgrade still looking for llvm-3.3 after -3.4 install + select --------------------------+--------------------------- Reporter: dsmithhfx@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: powerpc tiger Port: policykit | --------------------------+--------------------------- Comment (by larryv@…): Replying to [ticket:46899 dsmithhfx@…]:

I was able to do this and:

{{{ port select --set llvm mp-llvm-3.4 Selecting 'mp-llvm-3.4' for 'llvm' succeeded. 'mp-llvm-3.4' is now active. }}}

The `port select` mechanism only affects end-user use. Ports’ own dependencies are not affected by your `port select` choices. `policykit` doesn’t depend on LLVM, and I don’t see any `llvm-*` ports in its recursive dependency tree. Could you provide the output from these commands? {{{ $ port outdated $ port rdeps policykit and active }}} -- Ticket URL: <https://trac.macports.org/ticket/46899#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X

#46899: policykit upgrade still looking for llvm-3.3 after -3.4 install + select --------------------------+--------------------------- Reporter: dsmithhfx@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: powerpc tiger Port: policykit | --------------------------+--------------------------- Description changed by ryandesign@…: Old description:

Hi,

After unsuccessful attempt to upgrade llvm-3.3 on 10.4.11 ppc, I read this ticket https://trac.macports.org/ticket/39849 pronouncing it "wontfix" -3.3, & advising to switch to -3.4.

I was able to do this and:

{{{ port select --set llvm mp-llvm-3.4 Selecting 'mp-llvm-3.4' for 'llvm' succeeded. 'mp-llvm-3.4' is now active. }}}

However, subsequent upgrade attempts including gconf and policykit are still trying to update llvm-3.3:

{{{ sudo port upgrade policykit ---> Computing dependencies for llvm-3.3 ---> Fetching archive for llvm-3.3 [...] }}}

Is there a bug, or how can I enforce the switch to -3.4 in macports?

Thanks

New description: Hi, After unsuccessful attempt to upgrade llvm-3.3 on 10.4.11 ppc, I read this ticket #39849 pronouncing it "wontfix" -3.3, & advising to switch to -3.4. I was able to do this and: {{{ port select --set llvm mp-llvm-3.4 Selecting 'mp-llvm-3.4' for 'llvm' succeeded. 'mp-llvm-3.4' is now active. }}} However, subsequent upgrade attempts including gconf and policykit are still trying to update llvm-3.3: {{{ sudo port upgrade policykit ---> Computing dependencies for llvm-3.3 ---> Fetching archive for llvm-3.3 [...] }}} Is there a bug, or how can I enforce the switch to -3.4 in macports? Thanks -- -- Ticket URL: <https://trac.macports.org/ticket/46899#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X