[MacPorts] #62881: gcc11: port is deactivating libgcc10, resulting in broken dependent ports

[MacPorts]

#62881: gcc11: port is deactivating libgcc10, resulting in broken dependent ports
----------------------+--------------------------
  Reporter:  mascguy  |      Owner:  cjones051073
      Type:  defect   |     Status:  assigned
  Priority:  High     |  Milestone:
 Component:  ports    |    Version:
Resolution:           |   Keywords:
      Port:  gcc11    |
----------------------+--------------------------

Comment (by mascguy):

 Replying to [comment:23 cjones051073]:
 > The gcc ports are all self consistent, before and after the update. The
 problem is to get to the consistent state after the update *both* libgcc11
 and libgcc10 have to be updated. Now, things can only happen one at a time
 so if port decides to install libgcc11 before it has updated the old
 libgc10, then we hit this situation. The force deactivate resolves it.

 This happened because, like many users, I had to defer my update to
 `gcc11` until after the buildbots provided updated binaries for your
 subsequent `gcc11` patch. (The JIT patch from Homebrew, I think?)

 So `gcc10` (and `libgcc10`) were already updated when I was finally able
 to update `gcc11` this morning.

 Yet, despite being up-to-date, `libgcc10` was still deactivated by the
 `gcc11`/`libgcc11` update.

 And since `libgcc10` was already updated, no new update came along to
 provide an active port. Resulting in it being uninstalled during `port
 reclaim`.

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