Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35105 - mksh package: bad installation path
Attached to Project:
Community Packages
Opened by Thorsten Glaser (mirabilos) - Sunday, 05 May 2013, 23:01 GMT
Last edited by Thorsten Töpper (Atsutane) - Monday, 06 May 2013, 18:29 GMT
Opened by Thorsten Glaser (mirabilos) - Sunday, 05 May 2013, 23:01 GMT
Last edited by Thorsten Töpper (Atsutane) - Monday, 06 May 2013, 18:29 GMT
|
DetailsDescription:
I just got the following information from a user: 22:52⎜«Ypnose:#!/bin/mksh» big fail from mksh arch maintainer 22:53⎜«Ypnose:#!/bin/mksh» he changed /bin/mksh to /usr/bin/mksh and he didn't upgrade /etc/shells 22:53⎜«Ypnose:#!/bin/mksh» I was unable to log in with R46 Put mksh back to /bin ASAP. Not doing that *will* break peoples’ logins, as can be seen there, as well as scripts using the strongly recommended #!/bin/mksh shebang. We had this issue once already, when Arch had ed(1) in /usr/bin violating even POSIX. Additional info: * package version(s) Apparently, mksh R44 was okay and R46 isn’t. * config and/or log files etc. Log of package contents at https://www.archlinux.org/packages/community/i686/mksh/files/ indeed shows the bad location of the executable. Steps to reproduce: Upgrade mksh, try to log in? |
This task depends upon