sukria.net

Yes, Bugzilla 2.22 is not yet in Debian, I know.

And you know what?
That’s my top priority in my todo-list. Just be patient, I’m working on it.

It’s just that I had a lot to do in real life recently and didn’t manage to find the time to focus on my pretty-complex-and-patched package, named bugzilla.

By the way, as there are sometimes requests for help about the bugzilla debian package on irc.mozilla.org (chan #mozwebtools), I created a new chanel to gather those discussions: #debian on the same server.

Feel free to join if you like.

It took me a while to come back to the Debian bugzilla package, sadly I didn’t have the time in the past months to pay attention to it. Bug reports were coming and coming and it was really necessary to focus on them. As this weekend is a Bug Squashing Party in the Debian community, I thought it was the perfect time to wear my armor, take my sword and go squashing bugs…

I’m now glad to announce that bugzilla 2.20.1-2 will be soon available for your sid box and provides some sweet improvements:

• The old hand-written postinst script that performs database creation has been replaced by a smart call to dbconfig-common’s hook. By the way, congrats go to Sean Finney, dbconfig-common was really easy to integrate and does well what it claims to.
• The checksetup.pl script - that is a critical point in the package installation phase - was fixed (some grave bugs) and was also enhanced in order to work gently with what the user inputed with debconf. I have to submit my patch upstream for that script…
• I also cleaned a bit the package, added some new translated debconf templates.

I think that this package will bring back a good-shaped package in debian and hope that users will agree on that. The BTS will tell us if I’m right.

Anyway, I feel better after this upload.

I’m glad to say that bugzilla 2.20.1 is now available in sid. It provides a couple of security fixes and fixes some packaging issues as well.

I now have to contact the security team for uploading a security update for our sarge version…

Yeah, the last stable release of Bugzilla is going to be available for Sid within a couple of hours (thanks Frankie).

One of the major change with this release is… a new skin!
Eh Eh. You can take a look at it on the Backup Manager’s website: http://bugzilla.backup-manager.org.

As I’m speaking about backup-manager, let’s say the last release (0.5.9a) is also going to be available, the package is in my sponsor’s hands.

My travel through NM also follows, I just sent T&S Part #1 a couple of hours ago…

As expected, the last stable release of Bugzilla, 2.18.3 has been uploaded to unstable yesterday (thanks frankie).

I’m now focusing on collecting translations for backup-manager (debconf templates and upstream po files as well) so I can release the last version in a localized shape.

Thanks a lot to every translator, I can now say that backup-manager will come fully translated in the following languages: german, french, spanish, czech, japanese and vietnamese.

This weekend, I took the train from Paris to Caen to see my family, that was the perfect time for testing my new laptop.
Using cpufreq for dowclocking the processor and reducing the LCD brightness allowed me to use my laptop for more than 4 hours without power supply. That means that I hacked a lot in the train.

I made a new upstream version of Backup Manager on friday and packaged the new upstream version of Bugzilla (2.18.3) on sunday.
That’s really funny to use the time you spend in the train for hacking, most of the other travellers must not understand what the hell you have on your laptop (No big Windows button? Is that really a laptop, eh?), but most of all, that’s really great to use this precious time.

Now, bugzilla 2.18.3-1 is waiting for an upload and backup-manager 0.5.8b-1 is ready but needs a lot of help concerning the gettext translations.
Indeed, I used podebconf-report-po to notify the debian translators, but also requested their help for the upstream i18n. I hope we’ll manage to translate the upstream bits in Czech, Vietnamese or even Japanese (all of those are almost done for the debconf templates).
As soon as backup manager has a good i18n shape, I’ll ask my sponsor to upload it (I plan to do it in a week or two).

Bugzilla 2.18-7 has been uploaded to unstable yesterday. It includes an interesting patch for handling virtual hosts configuration through mod_env. Just adding a SetEnv directive in the Virtual Host configuration is enough.
The README.Debian describes the idea.

I’m looking forward for comments, in order to see if that fits the needs of people using it. Thanks to Yann Dirson who first submited the idea.

Bugzilla 2.18 began its way towards sarge and will be available in sid within a couple of hours. I’m pretty happy to see that, even if that means that my spare time may be strongly needed to handle new bug reports.

Moreover, this package is the first to allow database names with special characters, according to the MySQL documentation, section 9.2.2, it’s possible since MySQL 3.23.6.

Bugzilla 2.18 lives in the experimental section of the archive and some users wondered why we didn’t uploaded it to unstable.

All the issue is based on the following question: “Does the 2.18 version of Bugzilla is worth the risk of putting new problems in the archive before Sarge is released”.

If you have some ideas or comments, you can help and feed the debate on the 290775 bug entry.

There are new releases of the bugzilla package in unstable and experiemental :

• unstable: 2.16.7-5
• experimental: 2.18-2

Thanks to Christian Perrier, the bugzilla package has now DTSG compliant templates fully translated in 5 languages.

The experimental package has a better shape too, and seems to be stable enough for a daily use.

As before, any report either on the BTS or on this blog are welcome.