Bug#592506: [v-admins] Bug#592506: What to do about libtest-harness-perl?

[gregor herrmann]

On Sat, 28 Aug 2010 16:13:46 +0100, Nicholas Bamber wrote:

> Adam,
>    My conclusion is that in test the package should be rolled back
> to 3.17. Do you agree and if not why not?
> 
>    My reasoning is that attempting to do a patch is the most risky
> action since it would require unwinding most of the 3.21->3.22
> transition which was a large one. In such a context it is hard to
> argue for a roll forward to 3.22 and that only leaves rolling back.

Hm, I guess we should come to a conclusion on this issue:

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?

Cheers,
gregor

-- 
 .''`.   http://info.comodo.priv.at/ -- GPG key IDs: 0x8649AA06, 0x00F3CFE4
 : :' :  Debian GNU/Linux user, admin, & developer - http://www.debian.org/
 `. `'   Member of VIBE!AT & SPI, fellow of Free Software Foundation Europe
   `-    NP: Rebekka Bakken: You Bring New Stars
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20100907/80181978/attachment.pgp>