Adam,What do we need to do to push on with this? Do I need to raise a formal request to have 3.20 removed from testing?
Adam D. Barratt wrote:
On Tue, 2010-09-07 at 18:53 +0200, gregor herrmann wrote:Ideas so far: 1) reupload 3.17 (with an epoch or something) 2) create a 3.20 + patch version (risky and ugly) 3) upload 3.22 (huge diff) Another simpler way that came to my mind might be: * Remove libtest-harness-perl 3.20-1 from testing; perl core has Test::Harness 3.17 in 5.10.1 anyway. Should solve the problem in testing, and has the same effect in the end as Nicholas' proposal. * And upload 3.22 to unstable to close the bug in unstable. Am I missing something?If the preference is to ship 3.17 then duplicating the core version as a separate package doesn't seem like a great idea. So far as I can see, the only package which has a versioned dependency on libtest-harness-perl is libtest-most-perl, and that prefers perl 5.10.1 anyway. Regards, Adam
<<attachment: nicholas.vcf>>