[MacPorts] #61248: texlive-latex-extra did not upgrade during upgrade outdated

[MacPorts]

#61248: texlive-latex-extra did not upgrade during upgrade outdated
----------------------------------+----------------------
  Reporter:  lpagani91            |      Owner:  drkp
      Type:  defect               |     Status:  assigned
  Priority:  Normal               |  Milestone:
 Component:  ports                |    Version:  2.6.3
Resolution:                       |   Keywords:
      Port:  texlive-latex-extra  |
----------------------------------+----------------------
Changes (by ryandesign):

 * owner:  (none) => drkp
 * status:  new => assigned


Old description:

> I did a port selfupdate from 2.6.2 to 2.6.3 followed with an upgrade
> outdated afterwards. For an unknown reason texlive-latex-extra was not
> updated but was deactivated. port installed returned this :
>
> texlive-latex @50741_0+doc
> texlive-latex @54498_0+doc (active)
> texlive-latex-extra @50885_0+doc
> texlive-latex-recommended @50818_0+doc
> texlive-latex-recommended @54586_0+doc (active)
>
> I asked for a specific upgrade outdated texlive-latex-extra and it
> performed correctly. So I have no problems afterwards but maybe there is
> something to be fixed ?

New description:

 I did a port selfupdate from 2.6.2 to 2.6.3 followed with an upgrade
 outdated afterwards. For an unknown reason texlive-latex-extra was not
 updated but was deactivated. port installed returned this :

 {{{
 texlive-latex @50741_0+doc
 texlive-latex @54498_0+doc (active)
 texlive-latex-extra @50885_0+doc
 texlive-latex-recommended @50818_0+doc
 texlive-latex-recommended @54586_0+doc (active)
 }}}

 I asked for a specific upgrade outdated texlive-latex-extra and it
 performed correctly. So I have no problems afterwards but maybe there is
 something to be fixed ?

--

Comment:

 Several files moved between ports in texlive 2020. To prevent you from
 encountering activation errors when upgrading to this version, Dan
 [changeset:73396594cf737f853b78c1c64c410a47450dfb06/macports-ports
 programmed the ports] to automatically deactivate conflicting ports during
 the upgrade. This is our [wiki:PortfileRecipes#deactivatehack normal
 strategy] in such situations.

 `sudo port upgrade outdated` should have left you with a complete set of
 updated ports, if everything updated successfully. However if any port
 failed to upgrade and you had to intervene to fix something, one of the
 outdated ports might already have been deactivated but its replacement
 might not yet have been installed. MacPorts doesn't consider inactive
 ports to be included in the set of outdated ports, so a subsequent repeat
 of `sudo port upgrade outdated` would not have upgraded the previously-
 deactivated port and if you wanted to continue to use it you would have to
 upgrade it specifically, as you did.

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