Hello, On Fri, 24 Nov 2017, Cyril Brulebois wrote: > > Now, how should we go about fixing this? Adam pointed out we could always > > just parse /proc/cmdline, but this does not just work on kfreebsd. It's > > also possible to consider both /proc/cmdline and the environment; or just > > revert the particular change in busybox. > > > > I don't feel strongly either way, but I want to make the solution available > > in Debian as well... Anybody have a preference? > > Right now (thinking of a release soon-ish), I think I'd be happy with a > specific revert for the time being; then get people to figure out what to > do next (I have no clue about such things at the moment).
It looks like it has been partially reverted upstream: https://bugs.busybox.net/show_bug.cgi?id=10231 https://git.busybox.net/busybox/commit/?id=9c143ce52da11ec3d21a3491c3749841d3dc10f0 However this doesn't work for us either because the changes to "showvars" also affect the output of "set" which we are using to retrieve the environment variables in env2debconf. Apparently, kfreebsd has a working /proc/cmdline (thanks to linprocfs mounted by default) so we might want to switch to that. I don't know about the hurd though. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
