texlive-latex-extra did not upgrade during upgrade outdated

[lpagani91]

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 ?

[ryandesign (Ryan Carsten Schmidt)]

Several files moved between ports in texlive 2020. To prevent you from encountering activation errors when upgrading to this version, Dan programmed the ports to automatically deactivate conflicting ports during the upgrade. This is our 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.

[drkp (Dan Ports)]

I have seen one or two other reports of this problem. Do you recall if you had a failure while upgrading ports and had to restart the upgrade? Like Ryan said, the correct set of ports _should_ have been installed at the end, and this is the only case I can think of where it wouldn't.

Unfortunately, I suspect that either way there is not a lot we can do to fix this without changes to MacPorts base, but I would still like to understand the cause.

[lpagani91]

Yes, I had a failure and had to restart the upgrade. I am sorry to not be able to report what was the failure about.

[drkp (Dan Ports)]

No problem - I just wanted to be sure there wasn't anything else going on.

Marking as invalid since it only occurs during failures, and we don't have a way to do better right now...