= A. Before you file a ticket .... =

== 1. Check the Problem HotList ==

The [wiki:ProblemHotlist Problem HotList] contains possible solutions to problems that affect many MacPorts users.  If a solution to your problem listed there works, don't file a ticket.

== 2. Search to see if a Trac ticket has already been filed. ==

Avoid filing duplicate bugs.  Search for duplicates by:
 * using the search bar that appears on each page;
 * using [http://trac.macports.org/projects/macports/search the search page];
 * browsing the list of [report: categorised reports]; or
 * making an advanced search by constructing a [http://trac.macosforge.org/projects/macports/query custom query]. 

== 3. Is the problem an application error and not related to compiling and installing? ==

In general, application bugs should be reported to the developers of the app ("upstream"), not MacPorts.  An application bug that affects a large number of MacPorts users might merit a MacPorts bug for informational purposes only, but this should be done sparingly.

== 4. Is the problem with a 'port upgrade' operation? ==

If so, try a 'port uninstall foo' and then reinstall.  You might also want to run 'port -fR upgrade foo' to rebuild ports depending upon port foo.

= B. How to file a ticket =

Look at our [http://geeklair.net/new_macports_guide/#project.tickets official ticketing guidelines] for up-to-date information on how to file proper tickets.