Changes between Version 45 and Version 46 of ProblemHotlist


Ignore:
Timestamp:
Jul 26, 2009, 10:49:08 PM (15 years ago)
Author:
raimue (Rainer Müller)
Comment:

Remove old MacPorts 1.6 references

Legend:

Unmodified
Added
Removed
Modified

  • ProblemHotlist

    v45 v46  
    4040
    4141If fetch failed for a port, you can still get the distfile from anywhere else. Maybe the homepage of the software lists alternative download locations for source tarballs. Just download the distfile and save it to `${prefix}/var/macports/distfiles/<portname>/`. Make sure you get a file with exactly the same name (watch out for `.tar.gz` and `.tar.bz2`!) If a `port clean --all` has been done the distfile directory will have been removed. The directory for each port is created at the beginning of the fetch phase.
    42 
    43 There is in additional possibility to use our new [http://distfiles.macports.org distfiles mirror], which is automatically used as of the 1.7.0 release.
    44 If a fetch fails with MacPorts 1.6.x, try:
    45 {{{
    46 sudo env MASTER_SITE_LOCAL=http://distfiles.macports.org/<portname> port -v fetch <portname>
    47 }}}
    48 
    49 Unless it's a port that starts with p5-, py-, py25-, or rb-, in which case you use one of the following:
    50 {{{
    51 sudo env MASTER_SITE_LOCAL=http://distfiles.macports.org/perl5 port -v fetch p5-<rest_of_portname>
    52 sudo env MASTER_SITE_LOCAL=http://distfiles.macports.org/python port -v fetch py-<rest_of_portname>
    53 sudo env MASTER_SITE_LOCAL=http://distfiles.macports.org/python port -v fetch py25-<rest_of_portname>
    54 sudo env MASTER_SITE_LOCAL=http://distfiles.macports.org/ruby port -v fetch rb-<rest_of_portname>
    55 }}}
    5642
    5743'''Note:''' Checksum failures after a fetch are typically a separate issue.  See the [wiki:FAQ#IgetError:checksummd5sha1rmd160mismatchforport.WhatcanIdoaboutit FAQ].
    … …  
    162148}}}
    163149
    164 == Inactive port can't be removed even though a newer version is installed ==
    165 If, after upgrading a port, you find you can't remove the older, inactive, version because {{{port}}} tells you it is a dependency of another port, this is a bug in MacPorts 1.6 and earlier. The recommended fix is to upgrade to MacPorts 1.7.0 or later.
    166 
    167 In 1.6, the workaround is to force it: {{{sudo port -f uninstall <port> @<older_version>}}} (replacing <port> with the port name and <older_version> with the version string for the older version).  For example, if you've upgraded libpng recently, a {{{port installed libpng}}} may show
    168 {{{
    169   libpng @1.2.30_0
    170   libpng @1.2.31_0 (active)
    171 }}}
    172 Running {{{sudo port uninstall libpng}}} or {{{sudo port uninstall libpng @1.2.30_0}}} will complain that other ports depend on libpng and you can't uninstall.  Simply add a -f to get it to go: {{{sudo port -f uninstall libpng @1.2.30_0}}}.  Just make sure you remove the older, inactive version.
    173 
    174150== Can't install python modules because of unrecognized --no-user-cfg == #no-user-cfg
    175151