Control: retitle -1 Improve Valid-Until support in d-i & debootstrap Control: tag -1 - moreinfo Control: severity -1 important Hi, Jonas Smedegaard <dr@jones.dk> (2015-11-02): > Cyril Brulebois <kibi@debian.org> wrote: > > I don't have the right setup handy right now to test this. Could you > > please at least tell us whether that's something that should be dealt > > with at debootstrap time and/or in some other places? (It's not > > entirely clear where you draw the line between installer only and > > target image since many apt calls happens within /target). > > When using snapshot.debian.org (e.g. to work around bug#803769) it seems > debootstrap ignores expiry (which is arguably a bug in itself): Only > midway through the install process does it fail asking to retry, and > retrying succeeds after running either of these commands: > > a) date -s $some-old-enough-data > b) echo 'Acquire::Check-Valid-Until "false";' > /target/etc/apt/apt.conf.d/99ignore-repo-exiry > > As I understand this issue and your question, Cyril, the answer is > therefore that such flag currently (with arguably buggy debootstrap) > only need to affect the later APT calls within /target. Having toyed with V-U a bit recently, I think I see the issue rather clearly now, and the details above seem to make it clear that debootstrap should probably be a bit more cautious about this. I see two steps here: - it probably needs to grow a flag making it possible to either enforce or ignore V-U (if present); the logic there needs to take into account the fact we might have “frozen” indices, e.g. in stable and in installation images. From my (always weak) recollection, stable doesn't come with V-U; I would expect installation images to be in the same state. Anyway: need to be cautious. - the second step (might be done in parallel but probably better to tackle both debootstrap and apt steps at once, after the deboostrap case has been taken care of) is indeed making it possible to ignore V-U through some expert or preseed option. Adjusting title, tag, and severity as I don't think this is specific to InRelease files. I've added this to my (not really ever-growing but yet non-empty) d-i to-do list, and I'll do the BTS dance (cloning and reassigning to debootstrap etc.) if I don't receive any negative feedback about the analysis above. > Regards, and thanks a lot for all the great work on the installer, You're being too kind, but thanks. ;) Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature