Heya, Chris Boot <bo...@debian.org> (2019-03-30): > On 29/03/2019 17:45, Cyril Brulebois wrote: > [snip] > > But in practice, that means that rescue/enable=true is no longer visible > > from the rescue-check binary package (from src:rescue), meaning a broken > > rescue mode. I expect a number of other features to be broken in the > > same way, via the user-params script in debian-installer-utils. > > Ugh. Not again.
Sorry for the hassle… > [snip]> I'd be happy to have a fix for this before we consider releasing D-I > > Buster RC 1, which could otherwise be ready next week. If maintainers > > could hint me into the right direction, that could be sufficient. ;) > > Given the time constraints for buster I think your approach to > reverting upstream's changes and re-applying our hack is probably the > right way to go. I'll try to put something together today for review > and, hopefully, so that you can test with if you don't mind. I'm at a BSP, so testing bugfixes for RC bugs I opened the day prior looks very appropriate. :) > I've also had a thought, and I can't remember if we've considered it > already: do the environment variables get preserved in > /proc/1/environ, even if busybox ash can't grok them? Could d-i be > modified to pull them from there? Indeed, /proc/1/environ seems to have everyone! Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
