[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

haskell transition: Remove, Transition, Upload Fix or Upload Fix, Wait, Transition?



Hi,

besides some very few remaining rebuilds on mipsel and sparc, the
haskell transition is almost ready, if there were not a release critical
bug in haskell-cryptocipher affecting big-endian machines (mips, mipsel,
ppc, s390x, s390x, sparc).

I have finally come up with a proper fix, which requires patching
haskell-cpu and haskell-cryptocipher, and is on its way to experimental
to see if it actually works :-)

I see two modes of action now: 

A) In order to not hold up the transition: 
     1. remove all affected packages (i.e. all reverse dependencies of
        haskell-cryptocipher on these 6 architectures) in unstable
     2. let the transition happen
     3. upload the fix to unstable
     4. let all these packages build again
     5. transition them

or B)
     1. Upload the fix to unstable now.
     2. Wait for all reverse dependencies be built on these six
        architectures.
     3. Do the migration then.

I’m worried that B would make the large transition happen after the
freeze.

Attached is the output of
$ debtree -r libghc-cryptocipher-dev --max-depth=0 --rdeps-depth=1000 --show-all --max-rdeps=1000|dot -Tpng

Greetings,
Joachim
-- 
Joachim "nomeata" Breitner
Debian Developer
  nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata

Attachment: cryptocipher-rdeps.png
Description: PNG image

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: