Changes between Initial Version and Version 1 of Ticket #61248


Ignore:
Timestamp:
Sep 29, 2020, 6:13:33 PM (4 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

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.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #61248

    • Property Owner set to drkp
    • Property Status changed from new to assigned
  • Ticket #61248 – Description

    initial v1  
    11I 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 :
    22
     3{{{
    34texlive-latex @50741_0+doc
    45texlive-latex @54498_0+doc (active)
     
    67texlive-latex-recommended @50818_0+doc
    78texlive-latex-recommended @54586_0+doc (active)
     9}}}
    810
    911I 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 ?