The MacPorts Project uses a system called Trac to file tickets to report bugs and enhancement requests. Trac also provides an interface to browse the MacPorts Subversion repository. Though anyone may search Trac for tickets, you must register for a Trac account to create tickets.
Check the Problem HotList
The 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.
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 the search page
- browsing the list of categorised reports
- making an advanced search by constructing a custom query
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.
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 -nR upgrade --forcefoo' to rebuild ports depending upon portfoo.
Once you are logged into Trac, you may click New Ticket and you will be presented with a new ticket window shown in the graphic below. Follow the Trac ticket guidelines below to fill out the form.
There are certain conventions used to ensure that Trac tickets convey as much accurate information as possible so problems and contributions may be acted upon efficiently.
Summary:
[port][version][concise description]Example: "rrdtool-1.2.23 Configure error - build failure"
Description: All details that might be relevant to someone reading the ticket. Be sure to mention the versions of your operating system and Xcode install. Wiki formatting should be used to ensure that text is formatted correctly. Use the Preview button before submitting. If you want to post preformatted text such as a log or terminal output, make sure you use
{{{around the text or it could break the page layout. Example:...}}}
{{{
your build log here
}}}
Submitters are advised to trim pastes and logs of any kind to what's really relevant to the report, as otherwise overly large submissions that might contain redundant and/or unnecessary information might become unmanageable. If it is truly necessary to include long output, use an attachment, don't paste it inline.
Type: There are five types of tickets.
- The default; any port/MacPorts build/runtime failures and/or documentation corrections.
- Tickets, with or without patches, created to enhance something that isn't failing its intended purpose.
- Tickets, with or without patches, involving updating a port to a newer upstream version.
- Tickets created to submit Portfiles for software not currently available in MacPorts.
- Tickets created to request the creation of a new port.
Priority: Assign a priority level to the ticket.
- Reserved for the use of MacPorts team members, as they are the best fit to determine which reports warrant a higher priority over others.
- The default. For normal port failures, non-critical enhancement requests, non-critical port failures.
- For mostly cosmetic improvements, documentation corrections/improvements, etc.
- Anything that doesn't fit the categories high, normal, or low.
Milestone: This is a ticket label that indicates that the ticket is intended to be fixed in a particular MacPorts release. Leave it blank; it will be set by a project member if appropriate.
Component: Set what part of the MacPorts Project the ticket is to be filed against.
- Tickets related to MacPorts base code.
- Documentation enhancements and error corrections, or patches to the MacPorts Guide.
- Tickets related to ports.
- For MacPorts hosting & server-side issues, reserved for MacPorts PortMgr team members.
- MacPorts website enhancements and error corrections.
- MacPorts Wiki enhancements and error corrections.
Version: Select the MacPorts version you are using when it is applicable.
Keywords: Type any keywords that might help when searching for tickets (portname, type of problem, etc).
Cc: Anyone else besides the ticket reporter and assignee who would like to be kept involved in the development of the ticket. Multiple email addresses should be separated with a comma and a space (i.e.
you@example.org, maintainer@macports.org).Most users will not be able to assign tickets. If this applies to you, then when reporting port-related tickets, make sure you add the port's maintainer to cc. Otherwise they may not notice the ticket.
Assign To: Only users with commit access can edit this field. If this is not you, see the section on the field above.
For tickets on ports, enter the email address of the port's maintainer (use port info <portname> to find this). If multiple maintainers are listed, enter the first maintainer's email address here and enter the remainining maintainers' email addresses in the field. Exclude the email address
<openmaintainer@macports.org>if it appears. If the maintainer's email address is<nomaintainer@macports.org>, leave the field blank.Port: For tickets on ports, enter the name of the port (or ports, space-separated, when multiple are affected).
I have files to attach to this ticket: Use this checkbox to attach files to the ticket immediately after you create it. Or you can attach files later using the Attach File button.