-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Jonathan Nieder dixit:
>Thorsten Glaser wrote: > >> (still learning about all the dusty corners >> of Debian). > >Bear in mind that I am new to this myself. ;-) >I see. I read too quickly before and didn’t realize that packages in >lenny were relying on this behavior (in what was a rare setup, >certainly). Hm, not really. Basically, mksh as /bin/sh in lenny is broken. >> If you think an spu should be done, I’ll backport the fix. > >Seems borderline; it’s your call. Well… see below. I’d probably not get everything needed into spu so the “better” option would be to do an spu with an mksh that refuses to install as /bin/sh. >Since lenny still has another year or so to live, I think it might be >worth it to help people at large sites that never upgrade anything >that is not in a stable release Yes, this is certainly a problem. However, this is the only reported bug with a /bin/sh problem for mksh in lenny with this severity; there are others, and some just haven’t been reported in Debian since they were fixed upstream proacti- vely. 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. Or, as said above, do an spu which does everything /bin/sh-related just like the lenny package does, except the actual changing of the /bin/sh and sh.1 (manpage) symlink, issuing a warning instead. 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. This is a reason I don’t want to complicate possible upgrade scenarios for lenny→squeeze even more. Also, I’m still hoping that some consensus can be found what packages can operate as /bin/sh and how this is done. There have been both public dis- cussions and private among the maintainers involved (using a list of Cc: arguments), but 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). I had also Helmut Grohne added during the BSP in January 2010, and don’t consider that eMail thread private (just couldn’t think of an appropriate mailing list). If you can do anything to help *there* this would greatly be appreciated. Thanks, //mirabilos - -- Support mksh as /bin/sh and RoQA dash NOW! ‣ src:bash (226 (243) bugs: 0 RC, 172 (186) I&N, 54 (57) M&W, 0 F&P) ‣ src:dash (65 (72) bugs: 4 (7) RC, 45 (49) I&N, 15 M&W, 1 F&P) ‣ src:mksh (2 bugs: 0 RC, 0 I&N, 2 M&W, 0 F&P) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MirBSD) iQIVAwUBTEHowna1NLLpkAfgAQkWpw/+Ly6dDim5s2e/TfAwEpKu8Vnw7wwJwvVn 0M3ulbhKPvXp4Jsg2IUiJSGnPoRb7WDH0sy93r82bOR1ImQOzCeip3b0325ae8ua ceaHd76dp2vyDKmFp3hqer/xiq9r12ElYYyGIm6ouz2rwfUWF+ATSM9VjWHXbl7k Pcgeon6ONxDEeE3SwBaonLaFLHfZMoPChOaJXOD8F7a6uQI61hN6QP0BCmMIrfsQ FS+NpfSYfFZBPrnBBdG4eHGl6T3H7jF3QOv4j4GBV3/ouwWZI/74SGMRX5mKWIz3 hp568N7D9QLt1FZgXF9ZBVf1yAdunKKUGNamQza+b71k7bKGdDL2IaZDQTGruDzL PLBfau7vVYUFvOeuHX03XBKOqgc/27cpunhUmXkj35oZNcYRvrTeE3o8kthRadOS wRa8VZo8dGi2uHIQICen7AEs0SdSy7akRXGN+5YLJ3l/rrZHJJGlqpxEIMISxnnx sFEd5kd2rU3ICuCPC7J8zhuEQ/PjXkD0wChrF7ly1idyGxADMZg8X4GtIkZj7kkw MbYhtT7vlsqO6Y2M/ELfqvskNxfJY8HIYqpPlpOMpdoglwQFujjGT54JgIiZqF90 PsSXUm2QxP5dYVxS8izklKz3a8C/KYQUaOZ+FARtqJv74OMUngaL/lAl8/j8NAO9 +7TXIp5zMy0= =StaJ -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
