Opened 10 years ago
Closed 9 years ago
#46899 closed defect (fixed)
policykit upgrade still looking for llvm-3.3 after -3.4 install + select
Reported by: | dsmithhfx@… | Owned by: | dbevans (David B. Evans) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | powerpc tiger | Cc: | ryandesign (Ryan Carsten Schmidt) |
Port: | policykit |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
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
Attachments (1)
Change History (7)
comment:1 follow-up: 2 Changed 10 years ago by mf2k (Frank Schima)
Description: | modified (diff) |
---|---|
Owner: | changed from macports-tickets@… to devans@… |
comment:2 Changed 10 years ago by dsmithhfx@…
Replying to 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
comment:3 follow-up: 4 Changed 10 years ago by larryv (Lawrence Velázquez)
Replying to 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
Changed 10 years ago by dsmithhfx@…
Attachment: | outdated-rdeps-policykit.txt added |
---|
Requested port commands
comment:4 Changed 10 years ago by dsmithhfx@…
Replying to larryv@…:
policykit
doesn’t depend on LLVM, and I don’t see anyllvm-*
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
comment:5 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|
comment:6 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|---|
Resolution: | → fixed |
Status: | new → closed |
In the future, please use WikiFormatting and Cc the port maintainers (
port info --maintainers policykit
), if any.