Opened 4 years ago
Last modified 3 years ago
#60788 assigned defect
sudo port upgrade outdated failed because conflicting ports are active — at Initial Version
| Reported by: | delphym (DelphyM) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.6.2 |
| Keywords: | Cc: | ||
| Port: | oniguruma5 oniguruma6 |
Description
This is just a FYI report, as Macport asked me to report it. macOS v: 10.14.6 Macport v: 2.6.2 affected ports: oniguruma5 -> oniguruma6, jq @1.6_1
After a while I wanted to install a new macport, but have been warned my macport is old so I should run sudo port selfupdate, so I did, but it ended up with following error and suggestion to report a bug:
Error: Can't install oniguruma6 because conflicting ports are active: oniguruma5 Error: Problem while installing oniguruma6 Error: Follow https://guide.macports.org/#project.tickets to report a bug.
I think I've managed to resolve it by following this Stackoverflow post Resolving a macports installation 'conflict'.
I simply tried to uninstall, then reading the post, rather only deactivate the conflicting active port followed with installation of the new version which wanted to rebuild the dependant port.
On the command line it looked like this:
ζ sudo port deactivate oniguruma5 Note: It is not recommended to uninstall/deactivate a port that has dependents as it breaks the dependents. The following ports will break: jq @1.6_1 Continue? [y/N]: y Warning: Deactivate forced. Proceeding despite dependencies. ---> Deactivating oniguruma5 @5.9.6_p1_0 ---> Cleaning oniguruma5
Then
ζ sudo port install oniguruma6 ---> Fetching archive for oniguruma6 ---> Attempting to fetch oniguruma6-6.9.5_0.darwin_18.x86_64.tbz2 from https://packages.macports.org/oniguruma6 ---> Attempting to fetch oniguruma6-6.9.5_0.darwin_18.x86_64.tbz2.rmd160 from https://packages.macports.org/oniguruma6 ---> Installing oniguruma6 @6.9.5_0 ---> Activating oniguruma6 @6.9.5_0 ---> Cleaning oniguruma6 ---> Updating database of binaries ---> Scanning binaries for linking errors ---> Found 2 broken files, matching files to ports ---> Found 1 broken port, determining rebuild order You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: jq @1.6 Continue? [Y/n]: y ---> Computing dependencies for jq ---> Fetching archive for jq ---> Attempting to fetch jq-1.6_2.darwin_18.x86_64.tbz2 from https://packages.macports.org/jq ---> Attempting to fetch jq-1.6_2.darwin_18.x86_64.tbz2.rmd160 from https://packages.macports.org/jq ---> Installing jq @1.6_2 ---> Cleaning jq ---> Computing dependencies for jq ---> Deactivating jq @1.6_1 ---> Cleaning jq ---> Activating jq @1.6_2 ---> Cleaning jq ---> Scanning binaries for linking errors ---> No broken files found. ---> No broken ports found.
After that I could carry on with the selfupdate process.
As I said above, I don't expect any immediate fix or solution for my particular scenario would be provided. I'm only reporting it as a FYI because developers seem to be interested in such bugreports to see.
Ideally the fix would do the same step I did in the background or interactively, but it would require kind of AI to analyse each step and possible choice.
Perhaps if the failure on upgrade would rather point out to a specific place in the documentation what to do in such situations rather than a link to report a bug, could be more helpful.