[MacPorts] #46899: policykit upgrade still looking for llvm-3.3 after -3.4 install + select
#46899: policykit upgrade still looking for llvm-3.3 after -3.4 install + select ---------------------------+-------------------------------- Reporter: dsmithhfx@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: powerpc tiger | Port: policykit ---------------------------+-------------------------------- 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 -- Ticket URL: <https://trac.macports.org/ticket/46899> 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 | --------------------------+--------------------------- 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 dsmithhfx@…): Replying to [comment:1 mf2k@…]: Sorry, I went to check the formatting link, and it wiped out my post. It seems to me in recent tickets I've raised there were clickable formatting buttons, which seem to have gone away. Will try to do better in future! Thanks -- Ticket URL: <https://trac.macports.org/ticket/46899#comment:2> 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 | --------------------------+--------------------------- Comment (by dsmithhfx@…): Replying to [comment:3 larryv@…]:
`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 }}} Attached.
redps shows policykit --> mozjz17 --> clang-3.3 --> llvm-3.3 Thanks -- Ticket URL: <https://trac.macports.org/ticket/46899#comment:4> 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
#46899: policykit upgrade still looking for llvm-3.3 after -3.4 install + select --------------------------+--------------------------- Reporter: dsmithhfx@… | Owner: devans@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: powerpc tiger Port: policykit | --------------------------+--------------------------- Changes (by ryandesign@…): * status: new => closed * cc: ryandesign@… (added) * resolution: => fixed Comment: mozjs17 no longer requires clang-3.3 on Tiger as of r135937. There is one more remaining Tiger problem, for which #45832 remains open. -- Ticket URL: <https://trac.macports.org/ticket/46899#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts