On Mon, Mar 21, 2016 at 12:05 AM, Cyril Brulebois <[email protected]> wrote: > Colin Watson <[email protected]> (2016-03-16): >> On Wed, Mar 16, 2016 at 12:54:03AM +0100, Cyril Brulebois wrote: >> > Pretty sure this breaks (will break, when the change is propagated outside >> > experimental) d-i as it stands, due to the check on all 3 checksums in >> > net-retriever. >> >> Looking at the code, I don't think that's true. It skips checksums that >> are missing from Release, and it stops after the first checksum that it >> successfully finds. Unless I'm looking at the wrong bit of >> net-retriever? > > It's entirely possible I was thinking of an earlier version/approach, > different from what got implemented in net-retriever finally after the > last archive-side change. Apologies for any induced headscratching.
I made the change for net-retriever, and pushed to branch "sha256_only" [0]. Could you help to review the code, please? Thank you! [0] https://anonscm.debian.org/cgit/d-i/net-retriever.git/commit/?h=sha256_only Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 17B3ACB1
