#53158 closed defect (worksforme)
qt4-mac-mariadb-plugin causes trouble during upgrade of KDE4 ports
Reported by: | mkae (Marko Käning) | Owned by: | pixilla (Bradley Giesbrecht) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | michaelld (Michael Dickens), NicosPavlov, RJVB (René Bertin) | |
Port: |
Description
Recently I ran into this oddity with KDE4 ports:
---> Updating database of binaries ---> Scanning binaries for linking errors ---> Found 5 broken file(s), matching files to ports ---> Found 3 broken port(s), determining rebuild order ---> Rebuilding in order kdepimlibs4 @4.14.3 kde4-runtime @4.14.4.20150225 +samba kmymoney4-devel @4.8-20161022 Warning: No port py27-gtk found in the index. ---> Computing dependencies for qt4-mac-mysql5-plugin Error: Unable to exec port: Can't install qt4-mac-mysql5-plugin because conflicting ports are active: qt4-mac-mariadb-plugin Error rebuilding kdepimlibs4
Why is it that those KDE4 ports suddenly want the mysql5
plugin and are not happy with the installed mariadb
plugins anymore?
I have already uninstalled konversation
, but as shown above there are more troubling ports...
Change History (3)
comment:1 Changed 8 years ago by RJVB (René Bertin)
comment:2 Changed 8 years ago by mkae (Marko Käning)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
I've realised that I still had an older MacPorts ports tree on my host system. That somehow interfered with the more up-to-date rsynced data from MacPorts' central server. I have no idea what caused this collision, but after rebuilding the 3 ports above all is back to normal now.
comment:3 Changed 8 years ago by RJVB (René Bertin)
I've run into issues with supposedly unused port trees too. Removing a source from sources.conf wasn't enough, I also had to delete the PortIndex files in the ports directory.
Note: See
TracTickets for help on using
tickets.
I haven't traced this to see who depends on the mysql plugin but it would seem that a path:-style depspec has been replaced with an explicit depspec, or an update to a shared dependency introduced this new depspec.
I'd also raise the question why there have to individual mysql5 and mariadb plugins. AFAIK the whole idea after MariaDB is that it's a drop-in replacement for the regular MySql. The corresponding Qt5 plugin uses variants, but it would certainly be possible to use only path:-style depspecs (if port:mysql5x and port:mariadb were mutually exclusive alternatives).
Whe