Bugzilla upgraded to Bugzilla 2.18

  1. Greg Hurrell

    After the release of Synergy 1.7.1 today I set about upgrading the bugs and feature request database, which runs Bugzilla, from the old stable series (2.16.x) to the new stable series (2.18). It's something that's been hanging over me for a while now, like a cloud.

    Several hours later...

    If you've tried to access the database in the past few hours you might have seen some errors because the upgrade was quite involved. All fixed now. Installing Bugzilla is not for the faint hearted, unfortunately, and upgrading it is not always so easy either, but I am pleased to report that it's all done. You can see the list of changes and benefits that the new version brings here:

    http://www.bugzilla.org/releases/2.18/release-notes.html

    I had to upgrade my CPAN install, move to a new version of Perl (5.8.6; ouch), trouble-shoot test failures that occurred because they are running inside a FreeBSD jail, install and update a huge wad of perl modules, update Bugzilla itself via CVS, run all the tests, configure, and at last.... here we are...

    Perl 5.8 breaks module binary compatibility with 5.6, so I found that when I did the upgrade the perl scripts that automatically issue customers with license codes at purchase time or resend them to users who have lost them stopped working.

    So I had to upgrade a stack of modules: cryptography stuff as well as trusty old LWP::UserAgent and Mail::Sender. Luckily with a freshly updated CPAN install and the latest Perl this wasn't actually too difficult (for once). The tricky part was that after installing the needed modules I was getting 501 ("Service unavailable") errors when I tried connecting back to PayPal. Turns out I had to rebuild Crypt::SSLeay as well, because the connection was evidently not being made over SSL like it should have been and PayPal was replying with the 501. For some reason, LWP::UserAgent was silently failing and falling back to a non-SSL connection (I would've preferred an error message!). In any case, it's all fixed now. No customers missed out on getting their license codes. Now I just need someone to buy a Synergy license so that I can confirm that this all actually works!

Reply

This topic is now closed.