Thorsten Glaser wrote: > I think the *only* way to get a Debian Policy compliant > /bin/sh with mksh in lenny is to use bpo (or some other back- > port repository). > > My best bet would be to reduce the severity for lenny.
In that case, the simplest and best thing imho is to leave the package in lenny alone. This report can serve as documentation. If you find yourself with a great deal of time, an alternative would be to change the debconf template to warn about potential problems, but now I notice that the debconf question is not very discoverable anyway. So this does not seem worth changing. > HOWEVER, there’s one more thing coming into play: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538822 > > Debian Bug #540512 (merged into the above): basically, when > mksh is configured as /bin/sh and the upgrade to unstable > (and even testing! I can’t believe they let such a broken > dash package migrate!) is done, everything goes kaboom. I think Raphael is planning on rewriting the dash preinst at DebCamp/DebConf[1]. Maybe there will be some progress. > nobody seems to have understood > everything involved enough so far to come up with a viable > solution (it’s clear, however, that both bash and dash need > to be changed for it AT LEAST, and probably at the same time, > and must conflict/break/whatever the older versions of the > other package). Conflicts with essential packages are never fun. If you have pointers, I would be glad to look into it. Jonathan [1] http://bugs.debian.org/546528 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
