qca @2.3.4 conflicts with qca-qt5 @2.2.1_4

[cooljeanius (Eric Gallager)]

They both have a manpage by the same name:

x ./opt/local/libexec/qt4/bin/qcatool-qt5
x ./opt/local/libexec/qt4/bin/mozcerts-qt5
Error: Failed to activate qca: Image error: /opt/local/share/man/man1/qcatool-qt5.1.gz is being used by the active qca-qt5 port.  Please deactivate this port first, or use 'port -f activate qca' to force the activation.
DEBUG: Error code: registry::image-error
DEBUG: Backtrace: Image error: /opt/local/share/man/man1/qcatool-qt5.1.gz is being used by the active qca-qt5 port.  Please deactivate this port first, or use 'port -f activate qca' to force the activation.
    invoked from within
"throw registry::image-error "Image error: $file is being used by the active [$owner name] port.  Please deactivate this port first, or use 'port -f ac..."
    ("foreach" body line 45)
    invoked from within
"foreach file $imagefiles {
                set srcfile "${extracted_dir}${file}"

                # To be able to install links, we test if we can lst..."
    invoked from within
"registry::write {
            foreach file $imagefiles {
                set srcfile "${extracted_dir}${file}"

                # To be able to instal..."
    invoked from within
"try {
        registry::write {
            foreach file $imagefiles {
                set srcfile "${extracted_dir}${file}"

                # To be ..."
    (procedure "_activate_contents" line 21)
    invoked from within
"_activate_contents $requested $rename_list"
    (procedure "portimage::activate" line 63)
    invoked from within
"registry_activate $subport $_inregistry_version $_inregistry_revision $_inregistry_variants $optionlist"
    (procedure "portactivate::activate_main" line 20)
    invoked from within
"$procedure $targetname"
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_qca/qca/main.log for details.
DEBUG: Image error: /opt/local/share/man/man1/qcatool-qt5.1.gz is being used by the active qca-qt5 port.  Please deactivate this port first, or use 'port -f activate qca' to force the activation.

If this is an instance of an update causing a file to switch which port it's provided by, then the "deactivate hack" should be used.

[RJVB (René Bertin)]

No, I think that port:qca (Qt4-specific) should not install anything related to Qt5.

[RJVB (René Bertin)]

Actually, it's worse than this. The person who upgraded the port didn't check port:qca and the corresponding plugins at all (and missed the fact that v2.3.4 requires Qt5 5.14).

I've got the Qt5 ports more or less fixed, then I'll have to downgrade the version the restore Qt4 support.

FWIW, qca also has Qt6 support, but I'm staying away from that for now.

[cooljeanius (Eric Gallager)]

(note that this blocks upgrading of kdelibs4 for me, btw)

[RJVB (René Bertin)]

I've got the port back into shape, I just need the time to create a PR. Hopefully tomorrow.

[RJVB (René Bertin)]

​https://github.com/macports/macports-ports/pull/12997

[ryandesign (Ryan Carsten Schmidt)]

The PR was merged so I'll close this ticket.

Please remember in the future to use complete absolute ticket URLs in your commit messages so that Trac will auto-close the ticket.