[prev in list] [next in list] [prev in thread] [next in thread] 

List:       macports-changes
Subject:    [MacPorts] FAQ modified
From:       "MacPorts" <noreply () macports ! org>
Date:       2008-08-28 20:24:39
Message-ID: 20080828202439.E259728082 () relay13 ! apple ! com
[Download RAW message or body]


Changed page "FAQ" by wsiegrist@apple.com from 17.202.44.123*
Page URL: <http://trac.macports.org/wiki/FAQ>
Diff URL: <http://trac.macports.org/wiki/FAQ?action=diff&version=44>
Revision 44
Comment: update newticket URL to not use old /projects/macports path

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: FAQ
=========================================================================
--- FAQ (version: 43)
+++ FAQ (version: 44)
@@ -109,7 +109,7 @@
 
 If updating doesn't help, then you should attempt to discover why there is a \
checksum mismatch. There are several possible reasons:  
- 1. ''The file is corrupt''. If it was corrupted by the transfer, download it again \
(`port clean --all <portname>` and `port install <portname>`). If it is corrupted on \
the server, there is not much you can do about it. Open a bug in \
[http://trac.macports.org/projects/macports/newticket Trac] and assign it to the \
port's maintainer. As for solving the problem: if there are other mirrors, try one of \
them. You can also ask if someone has a complete file they can send you on the \
[http://lists.macosforge.org/mailman/listinfo/macports-users MacPorts users' mailing \
list]. + 1. ''The file is corrupt''. If it was corrupted by the transfer, download it \
again (`port clean --all <portname>` and `port install <portname>`). If it is \
corrupted on the server, there is not much you can do about it. Open a bug in \
[http://trac.macports.org/newticket Trac] and assign it to the port's maintainer. As \
for solving the problem: if there are other mirrors, try one of them. You can also \
ask if someone has a complete file they can send you on the \
[http://lists.macosforge.org/mailman/listinfo/macports-users MacPorts users' mailing \
list].  2. ''The developer has performed a "stealth upgrade"''. Sometimes upstream \
developers make "stealth upgrades" in which they change the contents of their \
distribution archive but not its version number, without informing MacPorts of this \
change. Perhaps the developer has repackaged the distribution with a different \
archiving program, or has fixed typos in the included documentation or made other \
presumably minor changes that did not warrant a regular release. This practice is not \
recommended because of the obvious difficulties it presents to MacPorts and other \
port systems that compute package checksums. Attempt to get confirmation from the \
developer of the software that this has occurred. If the developer cannot be reached, \
attempt to determine yourself whether a stealth upgrade has happened. \
[http://www.google.com/ Search the Internet] and try to locate the older version of \
the archive that matches the checksum in the portfile. Also download the version \
currently available  on the developer's site, extract both, and compare the contents \
(for example with `diff -r -u <old> <new>`). If the changes look minor and benign, or \
there are no changes at all, then it is safe for you to update the checksum in the \
portfile, and the port maintainer should be informed of this so that they can make \
the change official. If you cannot determine whether a stealth upgrade has taken \
place, ask for help on the \
[http://lists.macosforge.org/mailman/listinfo/macports-users users' mailing list].  \
3. ''The file has been tampered with''. It is perhaps somewhat unlikely yet \
theoretically possible (and it has happened a few times in practice) that the archive \
being distributed by the developer (or by a mirror) has been genuinely compromised. \
If a hacker was able to manipulate the developer's (or the mirror's) server, the \
hacker could have uploaded a revised archive containing malware (a virus, a trojan \
horse, a spam-sending platform, etc.) of the hacker's choosing, and you would \
certainly not want to install such software. You must attempt to determine, as above, \
whether this has occurred by contacting the developer, or by locating an older \
version of the archive and comparing them. You can also contact the port maintainer \
or the [http://lists.macosforge.org/mailman/listinfo/macports-users users' mailing \
list].  
@@ -227,4 +227,3 @@
 If this workaround does not clear the problem for you, please refer to the \
[http://lists.macosforge.org/mailman/listinfo/macports-users users mailing list] with \
as much information as possible.  
 Be sure you have the latest MacPorts before removing `portuninstall.tcl`. I had the \
same problem that I couldn't uninstall ports and so I first ran a `sudo port \
selfupdate` to get the latest version of MacPorts and removed the tcl file \
afterwards. But when running `sudo port -f selfupdate` it gave me this error message: \
`Failed to initialize ports system, couldn't read file \
"/opt/local/share/darwinports/Tcl/port1.0/portuninstall.tcl": no such file or \
                directory` and stopped working.
-

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server is
behind a proxy.

--
MacPorts <http://www.macports.org/>
Ports system for Mac OS

This is an automated message. Someone at http://www.macports.org/ added your email
address to be notified of changes on FAQ. If it was not you, please
report to .
_______________________________________________
macports-changes mailing list
macports-changes@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-changes


[prev in list] [next in list] [prev in thread] [next in thread]