shared-mime-info: org.macports.shared-mime-info-updater.plist already exists and does not belong to a registered port

[mrkapqa]

Hello ,

i am getting this error here; have deleteted macports complaetely per instructions on website macports and reinstalled macports 2.9.3 for Catalina;

this is the error:

Activating shared-mime-info @2.4_0
Error: Failed to activate shared-mime-info: Image error: /Library/LaunchDaemons/org.macports.shared-mime-info-updater.plist already exists and does not belong to a registered port.  Unable to activate port shared-mime-info. Use 'port -f activate shared-mime-info' to force the activation.
    while executing
"throw registry::image-error $msg"
    ("foreach" body line 50)
    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..."

is this error related only to this computer here==?

thanks you.

[jmroot (Joshua Root)]

The uninstallation instructions in the Guide include deleting /Library/LaunchDaemons/org.macports.*, so I'm not sure how /Library/LaunchDaemons/org.macports.shared-mime-info-updater.plist would still exist after that. But in any case, if there is an existing file that does not belong to a registered port causing a conflict, all you can do is remove that file.

[mrkapqa]

prior i had installed this prebuilt "mpv + vapoursynth" package .mpkg mpv-0.37.0_2.mpkg from here ​https://www.svp-team.com/files/gpl/mpv-0.37.0_2.mpkg

which may have caused this deroute and prevent files from getting scrubbed? will uninstall manually then and retry, thanks.

[ryandesign (Ryan Carsten Schmidt)]

Yes. That package was built with MacPorts in its default prefix. If you already had MacPorts ports installed when you install that package, it will overwrite files that MacPorts installed, likely with different versions, causing all sorts of havoc; to recover from this, you need to uninstall MacPorts fully and then reinstall it. Please write to the svp-team and request that they discontinue distributing that package immediately to prevent destroying users' existing MacPorts installations and consuming our technical support resources. If they want to distribute an installer package, they should first build MacPorts from source and configure it to install into a prefix that is unique to their project (e.g. /opt/mpv) so that it does not conflict. They will also need to specify that startup items should be disabled, since those are installed outside of the prefix, and hopefully the startup items that would have been installed, like this shared mime info updater, are not actually needed for anything.

Resolving as invalid because it is invalid that there is a MacPorts bug that we could fix; this is svp-team's bug for distributing a hostile installer package.