On Sat, Aug 06, 2005 at 01:57:01PM +0200, Toni Mueller wrote: > > On Sat, 06.08.2005 at 11:41:35 +0100, Stephen Quinney <[EMAIL PROTECTED]> > wrote: > > > The only way to resolve it right now is to grab the previous version > > from snapshot.debian.net and downgrade. > > Ugh...
This is what comes from tracking an unstable version of Debian at a particularly unstable time. The mod_perl2 API change has caused all sorts of problems like this and it will take time for things to settle. > > I would recommend that you move to request-tracker3.4 anyway as we are > > going to remove the request-tracker3.0 package from sid and etch > > soon. > > Yes, although your remarks in the READMEs pertaining to "alpha or beta > quality" made me a bit nervous, I just tried to migrate and lost all > history in the process. I've also already seen another bug that > mentions this and see if I can fix it. Yeah, I need to change that. RT3.4 is now sufficiently stable that we feel happy to get rid of 3.0 and recommend 3.4 to everyone. I'm very surprised you lost history, a standard request-tracker3.0 install should upgrade fine to request-tracker3.4 when following the instructions in the README.Debian. The only problems I've seen were related to using mysql without innodb support (that is essential) or postgresql 7.2 (it needs a minimum of 7.4 to perform the upgrade I found recently). Stephen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
