-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Denis, Le 24/02/2012 03:49, D. Barbier a écrit : Is there any blocker for the release? Debian Wheezy is expected to be frozen soon, and it would be nice to include this update. Regards David

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Le 13/05/2012 01:19, D. Barbier a écrit : I've update the Subversion repository with some last bits (NEWS entry and date), and the Debian part too. The built packages are available online: http://people.debian.org/~taffit/po4a/ I didn't uploaded them yet because I have a doubt: when I build po4a on my host, it uses Module::Build 0.40 from libmodule-build-perl, but when I build the Debian package in a clean chroot (with pbuilder), it uses Module::Build 0.38 from perl-modules (despite the explicit libmodule-build-perl build-dependency, that is indeed installed during the build process). As a consequence, the Debian package build fails (using the “old” Module::Build 0.38, while expecting the 0.40 version). As a workaround, I removed libmodule-build-perl from my machine, built po4a with Module::Build 0.38, and build the Debian package in pbuilder. I wonder if the libmodule-build-perl added eight years ago still make sense (maybe perl-modules didn't shipped it back then). Maybe should we simply remove it from the build-dependencies (even Build-Conflicts-Indep on it maybe)? I have no idea how to force its use in a clean chroot, but it could be another option. I'll be away in the coming days, but if the proposed workaround is OK, I should be able to release it as is (at least the Debian part, that's easy) tomorrow morning (UTC-4). I may not be able to do anything after that, until the end of the month (might still be OK Debian side, but thanks in advance if someone can find some spare time to release it with a proper fix in the mean time). A draft is ready in html/index.php.en, but I didn't update the PO files in www: I'd welcome a proofread first, and the date may be changed too. Regards David P.-S.: sorry for the huge amount of words, I might be too tired to be concise.

On 12-05-17 at 10:43am, D. Barbier wrote: If the issue is only uncertainty and the older Module::Build is ok to use, then use versioned build-conflict which affects the real package but not the virtual one provided by perl-modules. If the issue is that the newer version has actual benefits for this packaging, I suggest asking on the debian-perl mailinglist or IRC chatroom for suggestions how to enforce that. If the conclusion is that use of the newer version is not enforcable, I guess a bug should be filed for its removal from Debian :-P - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 [ Sorry Jonas for the double message, and thanks for the notice ] Le 17/05/2012 06:48, Jonas Smedegaard a écrit : That was my mistake: libmodule-build-perl is not pulled during the build process (because it's provided by perl-modules). Thanks for the hint, but that won't be needed actually, since the current po4a (that uses Module::Build 0.38) builds fine with Module::Build 0.40. The same way, with a versionned build-dep on libmodule-build-perl (>=0.400000) (thanks #debian-perl), does the trick (and actually pulls the libmodule-build-perl package during the pbuilder process). That won't be needed either since it works fine the way it is, but thanks for helping me understand what was wrong! We should be able to clean up some build dependencies, I may look at it later. Regards David