|Version 9 (modified by ryandesign@…, 6 years ago) (diff)|
A. Before you file a ticket .…
1. 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.
2. Search to see if a Trac ticket has already been filed.
Avoid filing duplicate bugs.
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
Filing tickets with proper form is important. Here are the most important elements.
This is the most important part. Don't force people to open the ticket to try to determine whether it is a BUG or RFE, the port version, or get a good idea what the ticket is about.
1st summary part: BUG: / UPDATE: / NEW: / RFE: — summary line prefix.
- "BUG:" A problem - a port is not installing functioning as intended.
- "UPDATE:" A port update patch submission
- "NEW:" A new port submission
- "RFE:" A request for enhancement - updates, new ports, or suggestions for how you'd like a port modified.
2nd summary part: -xx.xx.xx — versions change frequently so list the version!
3rd summary part: Concise description — if a BUG or RFE.
Examples for port tickets.
- BUG: emacs-21.4a build failure on Intel
- BUG: p5-perlmagick-6.29 configure error - freetype not found
- UPDATE: fishtail-0.93 -> 0.99
- NEW: bettyboop-1.2.7
- RFE: foofah - new port request
- RFE: gowidget-0.2.5 add a no_x11 variant
- RFE: defender-0.1.1 alien invader support is off -enable alien invaders
Examples for Base (MacPorts infrastructure) tickets.
- BUG: base-1.3.0 quits randomly sometimes during 'port install'
- BUG: base-1.3.2 'port search foo' doesn't find foox, fooy, etc
- RFE: base-1.3.2 add a Portfile keyword to chop onions
Select the maintainer's email address; see "port info <portname>". If the maintainer's email address is not in the list, or if the maintainer is "nomaintainer@…", select "macports-dev@…".
- BUGs = "defects"
- RFEs = "requests for enhancement"
Select the MacPorts version you are using.
Enter the maintainer's email address; see "port info <portname>". This ensures that the maintainer will receive an email about the new ticket and any changes that are made to it. This is important, because Trac currently only sends emails to addresses on the Cc list, not to the reporter or the assignee. Skip this step if the maintainer is "nomaintainer@…".
Please also enter your email address so that you will be notified when changes are made to the ticket. The person handling the ticket may need to ask you follow-up questions, and will probably do so by writing in the ticket.
Select "ports" or "base" to match the summary line.
If you have files (such as patches) to attach to the ticket, fill out the rest of the ticket first and submit it. You'll have the chance to add an attachment next.