Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#39888 closed defect (invalid)

kmymoney4: Conflicting ports qt4-mac/qt3

Reported by: angelasignore@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.2.0
Keywords: Cc: mkae (Marko Käning), pixilla (Bradley Giesbrecht)
Port: kmymoney4

Description

I'm brand new to macs and, hence, macports too. But, I managed to install it and am trying to install Kmymoney. I followed all the directions, installed xcode (4.6.3) and the command line tools, etc. For some reason, when I try to install kmymoney4, I get an error of conflicting ports.

--->  Computing dependencies for kmymoney4....
Error: Unable to execute port: Can't install qt4-mac because conflicting ports are installed: qt3

Am I doing something wrong? I only have a handful of other programs installed since it's a new system. Any suggestions?

I also tried to install the regular kymymoney, which i think goes on qt3, but that failed for some reason. The 4-dev version also gives the same conflicting port error. I ran the suggested updates and still same errors.

Any advice appreciated, thanks!!

Change History (4)

comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: mk@… pixilla@… added
Keywords: kmymoney removed
Port: kmymoney4 added
Resolution: invalid
Status: newclosed
Summary: Conflicting ports qt4-mac/qt3 for kmymoney intsall on osx 10.8.4kmymoney4: Conflicting ports qt4-mac/qt3

You cannot install qt4-mac and qt3 at the same time. You must pick one or the other. qt3 is pretty ancient by now; I would not recommend using anything that requires it.

kmymoney4 requires qt4-mac, not qt3. Try uninstalling qt3.

If you need other help using MacPorts, please write to the macports-users mailing list. The issue tracker is for bug reports and feature requests.

comment:2 Changed 11 years ago by mkae (Marko Käning)

Were you able to resolve this issue?

If so, I'd like to close this, since it is not really a bug.

comment:3 Changed 11 years ago by mf2k (Frank Schima)

This ticket is already closed. Indeed there is no bug here.

comment:4 Changed 11 years ago by mkae (Marko Käning)

Sorry, for some reason I didn't notice that it was set to "invalid" already.

Note: See TracTickets for help on using tickets.