Steve McIntyre <steve@einval.com> (2018-12-17): > But... The problem you're most likely seeing is caused by a simple > fact. The *netboot* image ends up downloading significant chunks of > the installer and the base system at runtime from the suite it > targets. For buster, that is still very much a moving target and it's > likely to already have incompatibilities with the released 20181206 > netboot image. > > Netboot images are *only* useful and safe when they exactly match the > state of the Debian release they're targeting. That's either a stable > release, or within a couple of days of the build happening if you're > looking at testing. > > For any other purposes, IMHO you're massively better off using a > _netinst_ image instead. Or install stable and upgrade. What Steve says is particularly true when there's a difference in major libc version (2.27 vs. 2.28; the latter has just migrated to testing right after the general block-udeb in britney was lifted). Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature