#50808 closed defect (duplicate)
Cannot deactivate port: this entry does not own the given file — at Version 1
| Reported by: | reuben@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 2.3.4 |
| Keywords: | Cc: | ||
| Port: |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
I have upgraded from Mountain Lion to El Capitan and am migrating following the instructions at Migration. The one snag is that I cannot deactivate the old version of boost:
---> Deactivating boost @1.58.0_3+no_single+no_static+python27
Error: org.macports.deactivate for port boost returned: this entry does not own the given file
Please see the log file for port boost for details:
/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_boost-1.58.0_3_371b161d218eb8a2e929ef6264e243ab3f3b452084f057f14bbe95beb2d06919-12796/boost/main.log
Warning: Failed to execute portfile from registry for boost @1.58.0_3+no_single+no_static+python27
Change History (2)
Changed 8 years ago by reuben@…
comment:1 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
| Component: | ports → base |
|---|---|
| Description: | modified (diff) |
| Port: | boost removed |
| Resolution: | → duplicate |
| Status: | new → closed |
| Summary: | Cannot deactivate boost after OS upgrade → Cannot deactivate port: this entry does not own the given file |
Others have reported this error before, e.g. in #32700 and https://lists.macosforge.org/pipermail/macports-dev/2012-February/017837.html. In that mailing list post, the error was determined to be the result of a single-bit corruption.
Note: See
TracTickets for help on using
tickets.
boost main.log