Changes between Initial Version and Version 1 of Ticket #65987


Ignore:
Timestamp:
Oct 13, 2022, 11:00:38 AM (19 months ago)
Author:
jmroot (Joshua Root)
Comment:

Chris, is there a reason why the various libgccs can't be marked as replaced_by an appropriate other version (or the libgcc wrapper port) on the platforms where they're no longer supported?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #65987

    • Property Cc cjones051073 added
    • Property Summary changed from libgcc9 fails to upgrade on BigSur 11.7, 404 error fetching libgcc9-9.5.0_2.darwin_20.x86_64.tbz2 to libgcc9 fails to upgrade on BigSur 11.7

  • Ticket #65987 – Description

    initial v1  
    11I receive the following output when updating outdated packages (specifically with libgcc9):
    2 
     2{{{
    33# /opt/local/bin/port upgrade outdated
    44--->  Computing dependencies for libgcc9
    … …  
    1313Error: Follow https://guide.macports.org/#project.tickets if you believe there
    1414is a bug.
    15 
     15}}}
    1616Here is the log output:
    17 
     17{{{
    1818cat /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc9/libgcc9/main.log
    1919version:1
    … …  
    233233:debug:fetch "$pre $targetname"
    234234:error:fetch See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_gcc9/libgcc9/main.log for details.
     235}}}