-=| Niko Tyni, Sun, Apr 25, 2010 at 03:12:09PM +0300 |=- > On Sat, Apr 24, 2010 at 02:57:32PM +0300, Damyan Ivanov wrote: > > -=| Debian Bug Tracking System, Sat, Apr 24, 2010 at 11:42:08AM +0000 |=- > > > > I can confirm that padre builds fine with libperl-apireference-perl > > > 0.04-1, so closing the bug. > > > > > > Sorry, could have looked into this one better. > > > > Wait, at the time you reported the bug, libperl-apireference-perl was > > at version 0.03 in the archive. 0.04 fixes padre, but I think it > > (padre) now needs to build-depend on libperl-apireference (>= 0.04) in > > order to ensure successful builds with perl 5.12.0 (atm it > > build-depends without a version). > > Another way to express the issue (and slightly more "correct" IMO) > would be for perl 5.12.0 to Break libperl-apireference-perl (<< 0.04). > What do you think?
I am not sure addeng Breaks is worth it. libperl-apireference-perl is not in stable, so you'd have to remove the Breaks once 0.04 migrates to testing. Adding Breaks wouldn't hurt, though, and it would protect from the (highly unlikely) case of perl 5.12.0 migrating to testing before libperl-apireference-perl. Having Breaks may also be helpful with the next perl transition. I guess it could serve as a reminder to see if libperl-apireference-perl works with $new_perl. It seems I see more benefits in adding Breaks than drawbacks.
signature.asc
Description: Digital signature
