Comment 3 for bug 216533

FWIW, the reason I used --rich-root was because when I tried it in a --rich-root-pack directory it failed and when I went to report that (which got a different error), I saw that was a known bug. I didn't see a bug on normal --rich-root reported, so hence this report.

Anyway, I ended up just trying a normal pack-0.92 repository and it finally worked, so it's not a show stopper, but I *always* use --rich-root-pack and have never had trouble until now, so it's surprising.