On stuck migration, help needed

[Dmitry Bogatov]

Hello,

Several days ago I discovered cause of migration problems with startpar
and insserv: startpar test suite printed on stderr, which was considered
failure by testsuite.

I fixed this issue (along with packaging startpar=0.64) and uploaded to
unstable. But problem still here, for following reason:

 * insserv >= 1.21.0~beta does not migrate to testing because it
   introduces test failures for startpar=0.63

 * startpar=0.64, which fixes test suite, depends on
   insserv >= 1.21.0~beta, which (as per previous) do
   not migrate to testing, so neither startpar=0.64 migrates.

The only way out of this trap I see is:

 * disable tests in startpar, drop build-depends on insserv
 * upload to unstable
 * wait for startpar migrate to testing (5 days)
 * wait for insserv to migrate to testing (1 day, I guess)
 * enable tests in startpar, bring back build-depends on insserv
 * upload to unstable
 * wait for startpar migrate to testing (5 days)

Better and faster ideas?
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/attachments/20190914/458f2034/attachment.sig>