[MacPorts] FAQ modified

MacPorts noreply at macports.org
Sat Dec 12 08:16:54 PST 2009


Changed page "FAQ" by jmr at macports.org from 123.243.246.165*
Page URL: <http://trac.macports.org/wiki/FAQ>
Diff URL: <http://trac.macports.org/wiki/FAQ?action=diff&version=89>
Revision 89
Comment: checksum mismatch ticket requirements

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: FAQ
=========================================================================
--- FAQ (version: 88)
+++ FAQ (version: 89)
@@ -113,7 +113,7 @@
 
 The first thing you should do if you get a checksum error is update your ports with `sudo port sync` — can you install the port now? If so, it means somebody else encountered the same checksum mismatch before and already fixed it.
 
-If updating doesn't help, then you should attempt to discover why there is a checksum mismatch. There are several possible reasons:
+If updating doesn't help, then you should attempt to discover why there is a checksum mismatch. '''Please do NOT file a ticket without first ruling out a misconfiguration on your end. Also make sure that you specify which mirror your download came from when filing a ticket.''' There are several possible reasons for checksum mismatches:
 
  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].

-------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 .


More information about the macports-changes mailing list