[MacPorts] #62606: Strange "ports diag" complaint wrt ghc-8.10.4

[MacPorts]

#62606: Strange "ports diag" complaint wrt ghc-8.10.4
------------------------------+--------------------
  Reporter:  GussyFinkNottle  |      Owner:  (none)
      Type:  defect           |     Status:  new
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.6.4
Resolution:                   |   Keywords:
      Port:  ghc              |
------------------------------+--------------------

Comment (by ryandesign):

 Replying to [ticket:62606 GussyFinkNottle]:
 > port diag returns:
 >
 > {{{
 > Warning: couldn't find file
 '/opt/local/lib/ghc-8.10.4/time-1*9.3/Data/Time/Calendar/Week.p_hi' for
 port 'ghc'. Please deactivate and reactivate the port to fix this issue.
 > }}}
 >
 > ls -l /opt/local/lib/ghc-8.10.4/time-1*9.3/Data/Time/Calendar/Week.p_hi
 returns:
 >
 > {{{
 > -rw-r--r-- 1 macports wheel 17025 Feb 12 15:16
 /opt/local/lib/ghc-8.10.4/time-1.9.3/Data/Time/Calendar/Week.p_hi
 > }}}
 > ghc itself seems to work fine. It may be relevant that I rarely use
 macport's ghc, relying instead on "ghcup", which maintains several
 versions of ghc.
 > (So for me, this bug/glitch, whether it is in "port" or "ghc", is of
 supreme unimportance :)
 >
 > sudo port deactivate ghc returns:
 >
 > {{{
 > --->  Deactivating ghc @8.10.4_0
 > Error: Failed to deactivate ghc: this entry does not own the given file
 > Error: See
 /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_ghc-8.10.4_0_1568b9927a7c1a4ff0e0b430009d6fdd4910ba2659f74f6857ed213608cd0c7c-10941/ghc/main.log
 for details.
 > Warning: Failed to execute portfile from registry for ghc @8.10.4_0
 > --->  Deactivating ghc @8.10.4_0
 > Error: port deactivate failed: this entry does not own the given file
 > }}}
 > (The log will be attached.)

 The name of the folder should be `time-1.9.3` but the path recorded in the
 registry for this file on your system appears to contain the folder name
 `time-1*9.3` instead. This looks like a single-bit error that could be the
 result of bad RAM,
 [https://en.wikipedia.org/wiki/Cosmic_ray#Effect_on_electronics cosmic
 rays], or other random phenomena. ("." is 101'''1'''10 in binary; "*" is
 101'''0'''10 in binary.) If you uninstall the port that will remove its
 references from your registry. You can then reinstall the port which will
 put new references into the registry, which hopefully won't be affected by
 the same phenomenon.


 Replying to [comment:1 GussyFinkNottle]:
 > Incidentally, I'd be grateful to be told how to browse in the finder to
 /opt. I had to copy the logfile to ~/Desktop to attach it.

 In the Finder, select Go to Folder from the Go menu or press Command-
 Shift-G. Type the path you want to go to.

 Or, in the Terminal, type `open ` followed by the path you want the Finder
 to open.

 When I want to attach a log, I usually find it easiest to press the Choose
 File button on the web page, and then in the file selection dialog box,
 either type "/" or press Command-Shift-G, either of which bring up a
 dialog where you can type the path you want to go to. Tab completion also
 works in this dialog. I usually copy the port's logfile location to the
 pasteboard by running e.g. `port logfile ghc | pbcopy` in the Terminal,
 then it's all ready to paste into the file selection dialog's path entry
 subdialog.

-- 
Ticket URL: <https://trac.macports.org/ticket/62606#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS