reassign 494779 perl-base 5.10.0-13 retitle 494779 Etch packages missing the perlapi-* dependency break when upgrading perl-base severity 494779 important thanks
On Tue, Aug 12, 2008 at 01:50:31AM -0400, Ariel wrote: > >This was #463090: the old libclass-methodmaker-perl version was missing > >required dependencies and wasn't upgraded automatically along with the > >Perl 5.8.8 -> 5.10.0 upgrade. > > Ah, I understand. They really should have made a tiny update version in > stable (the etchandahalf release) to fix that, because fixing it in > testing doesn't really help. > > Should you add a versioned depends to that version in > libterm-progressbar-perl, or is it just going to have to be that way? > > apt-rdepends shows: > > libconfig-apacheformat-perl > libgnupg-interface-perl > libpdf-fdf-simple-perl > libterm-progressbar-perl > libwww-bugzilla-perl > > As the only packages that depend on libclass-methodmaker-perl, so I > suppose they would all need the versioned depend. > > Or maybe perl-base should do a conflicts. > > Well, you decide: reassign this to perl-base, add a versioned depend, or > just close it. The required perlapi-* dependency was missing in Etch in all of these: <package> <broken> <fixed> libcflow-perl 1:0.68-10 1:0.68-11.1 libqt-perl 3.008-2 3.008-3 libclass-methodmaker-perl 2.07-2 2.10-1 libclearsilver-perl 0.10.3-4.1 0.10.4-1.1 libhamlib2-perl 1.2.5-8 1.2.6.2-6 libsys-cpu-perl 0.40-2 0.40-2.1 megahal 9.1.1a-1 9.1.1a-5 razor 2.810-2 1:2.84-6 and additionally these packages introduced after Etch: pidgin 2.3.1-3 libpurple0 2.3.1-3 libgdal-perl 1.5.0-3 liblasso-perl 2.1.1-3 plus one unfixed one swish-e 2.4.3-7 Fixing all their reverse dependencies in Lenny to have versioned dependencies on fixed versions clearly doesn't scale. If we want to fix this, I think it has to be done by making the new perl-base conflict with the broken versions. I think we can forget about the "new packages" that have never been in a stable release yet, and swish-e is just begging for breakage (see #463134). That leaves eight new conflicts in perl-base. Reassigning; I'll ask the release team what they think. Thanks for reporting this, -- Niko Tyni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]