head 1.5; access; symbols; locks; strict; comment @# @; 1.5 date 2005.02.24.19.11.46; author rse; state dead; branches; next 1.4; 1.4 date 2004.10.13.06.58.31; author thl; state Exp; branches; next 1.3; 1.3 date 2003.08.04.10.29.00; author thl; state Exp; branches; next 1.2; 1.2 date 2001.11.27.14.58.01; author rse; state Exp; branches; next 1.1; 1.1 date 2001.08.29.10.08.43; author rse; state Exp; branches; next ; desc @@ 1.5 log @bugdb is gone for now @ text @ #use "page.inc" page=bugdb Bug Database

Bug Database

We do not currently run a bug tracking database. Asking questions and reporting problems or suggestions is as easy as sending a message to one of out mailing lists as shown on the support page. @ 1.4 log @remove traces of inactive bugdb @ text @@ 1.3 log @move from jitterbug to rt @ text @d8 4 a11 26 We run a Request Tracker (RT) based Bug Database for the OpenPKG project under rt.openpkg.org.

New Ticket

You can submit a request by sending an email to openpkg-bugdb@@openpkg.org

Open Tickets

Guest users can view new, open and stalled tickets.

Closed Tickets

Guest users can view closed (resolved) and rejected tickets.

Ticket Status

newsubmitted items waiting in incoming queue
openwork in progress
stalleddeferred for later investigation
resolvedproblem fixed
rejectno problem, impossible, out of scope, false alarm
deletedspam and other trash (invisible but causing numbering gaps)
@ 1.2 log @Nasty voodoo corrections. @ text @d8 2 a9 2 We run a Jitterbug-based Bug Database for the OpenPKG project. There are two access methods for entering the system: d11 3 a13 4 d15 19 @ 1.1 log @revamp website, phase 1 @ text @d9 1 a9 1 There are two access methods for entering system: @