Hi, I would suggest anyone who has foobar’ed up their systems by following the (badly thought out) instructions to replace bash with MacPorts version to
a) put back the original bash from their backups ;) b) manually install the updates from Apple that properly fix this OS X bash Update 1.0 may be obtained from the following webpages: http://support.apple.com/kb/DL1767 <http://support.apple.com/kb/DL1767> – OS X Lion http://support.apple.com/kb/DL1768 <http://support.apple.com/kb/DL1768> – OS X Mountain Lion http://support.apple.com/kb/DL1769 <http://support.apple.com/kb/DL1769> – OS X Mavericks For OSX 10.6 and older, where there is no update, follow the instructions post to this thread to patch bash properly (i.e. no macPorts dependencies). Chris > On 29 Oct 2014, at 6:18pm, Lawrence Velázquez <[email protected]> wrote: > > On Oct 28, 2014, at 4:36 AM, Chris Jones <[email protected]> wrote: > >>> in an attempt to minimize exposure to Shellshock. IIRC I got the above >>> from someone on this list. >> >> Together, if I recall, with a number of posts saying it was also a very bad >> idea.... > > https://trac.macports.org/ticket/45680 > > Upgrading gettext will break for everyone who replaced the system bash with > MacPorts'. > > 1. User replaces /bin/sh with MacPorts' bash, which dynamically links to > gettext. > 2. User runs selfupdate and receives new gettext Portfile. > 3. User runs port upgrade. > 4. Upgrade process deactivates old gettext. The replacement /bin/sh is now > broken because libintl.8.dylib does not exist. > 5. Upgrade process tries to activate new gettext but dies because /bin/sh is > broken. > > vq > _______________________________________________ > macports-users mailing list > [email protected] > https://lists.macosforge.org/mailman/listinfo/macports-users
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
