J.H.M. Dassen (Ray) wrote: > I realise it will be painful to make this transition, but the benefits > Werner lists (in particular, avoiding future ABI breaks and avoiding the > problems we already see with processes that load two versions of gcrypt > simultaneously) outweigh the pain by quite a bit IMHO. If this change was made today (in testing), it would break all existing sarge businesscard isos, and would require a debootstrap-udeb updated for the dependency change to enter testing concurrently to avoid breaking floppy and netboot installs as well. Updating and re-testing the isos would take a minimum of 3 days, this could easily waste us a week of development time on d-i. More likely we would leave them broken, and lose two weeks of testing by users of those isos. If, as seems more likely, this change were made sometime this week in unstable, and hit testing after the usual delay, then it would reach testing between the 24th and 30th. We plan to release beta 4 of the Debian installer on the 28th, a build process which will begin on the 24th. If it reached testing on the 24th, this would leave us no time for testing. If it reached testing on the 25th through 28th, we would have to restart the release process, losing between 1 and 4 days, and again, having no real chance to test things. If it reached testing just after our release, we're back to the scenario outlined in my paragraph above, except now we have an influx of users to cope with at the same time everything is breaking. So no, it's not as easy as you seem to think it is, and it has the potential to either delay beta 4 by 4 days to a week, force us to ship something not as tested as we'd hope to, or break beta 4 immediatly after it is released. -- see shy jo
Attachment:
signature.asc
Description: Digital signature