Changes between Version 38 and Version 39 of ProblemHotlist
- Timestamp:
- Dec 22, 2008, 10:09:31 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ProblemHotlist
v38 v39 5 5 == .profile not set up == 6 6 7 After a fresh installation of MacPorts 1.6.0, the `.profile` is not set up as it should be, with the consequence that the shell says the `port` command is not found when you try to use it. This is [ticket:13742 a bug in the 1.6.0 installer]. It will be fixed in the next release of MacPorts.7 After a fresh installation of MacPorts 1.6.0, the `.profile` is not set up as it should be, with the consequence that the shell says the `port` command is not found when you try to use it. This is [ticket:13742 a bug in the 1.6.0 installer]. It is fixed in MacPorts 1.7.0. 8 8 9 T o work around the problem, download the `postflight` script and runit manually, like this:9 The recommended fix is to install the MacPorts 1.7 .pkg. You could also work around the problem by downloading the corrected `postflight` script and running it manually, like this: 10 10 11 11 {{{ … … 17 17 To get the terminal to notice the new `.profile`, close your terminal window and open a new one. 18 18 19 Instead of downloading and running the `postflight` script from the repository, you could set up your `.profile` manually, as [http://guide.macports.org/#installing.shell explained in the Guide].19 Instead of downloading and running the `postflight` script from the repository, you could alternatively set up your `.profile` manually, as [http://guide.macports.org/#installing.shell explained in the Guide]. 20 20 21 21 == man port fails with error message == … … 46 46 If 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. 47 47 48 There is in additional possibility to use our new [http://distfiles.macports.org distfiles mirror], which will beautomatically used as of the 1.7.0 release.48 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. 49 49 If a fetch fails with MacPorts 1.6.x, try: 50 50 {{{ … … 134 134 135 135 == Inactive port can't be removed even though a newer version is installed == 136 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 1.6. The simple fix 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 136 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. 137 138 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 137 139 {{{ 138 140 libpng @1.2.30_0 … … 140 142 }}} 141 143 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. 142 143 This issue has been fixed on trunk.