Martin Michlmayr wrote: > So, I've a question. I want to commit a change to base-installer > which will allow root partitions to be on LVM. However, this requires > initrd-tools 0.1.68 which was accepted today (and will break LVM > installations with an older initrd-tools). If I make the > base-installer change now, this means this version cannot move to > testing. I guess I could wait 10 days to commit that change, but that > would slow down development quite a few. I suppose I can commit it in > 5 days, because we said udebs need to be in unstable for 5 days before > we consider moving them to testing. Is this the right thing to do? Even if you wait 5 days, we would then have broken LVM installs for 5 more days until the new initrd-tools reaches testing, and the base-installer change would not get tested at all in that time period (unless someone installed unstable with d-i), defeating the 5 day delay. I think the thing to do in this case is to wait for the new initrd-tools to go in before changing base-installer. You could try to get that expedited. If the change in base-installer is small and well confined to LVM systems, then we could let it in in less than 5 days after initrd-tools goes in. Would it be possible to make it use the new initrd-tools iff it's available and continue to work with the old one? -- see shy jo
Attachment:
signature.asc
Description: Digital signature