<div dir="ltr">Thanks for that. Everything's working properly again. <br><br><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 29, 2014 at 1:33 PM, Christopher Jones <span dir="ltr"><<a href="mailto:jonesc@hep.phy.cam.ac.uk" target="_blank">jonesc@hep.phy.cam.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi,<br>
<br>
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<br>
<br>
a) put back the original bash from their backups ;)<br>
<br>
b) manually install the updates from Apple that properly fix this<br>
<br>
OS X bash Update 1.0 may be obtained from the following webpages:<br>
<a href="http://support.apple.com/kb/DL1767" target="_blank">http://support.apple.com/kb/DL1767</a> <<a href="http://support.apple.com/kb/DL1767" target="_blank">http://support.apple.com/kb/DL1767</a>> – OS X Lion<br>
<a href="http://support.apple.com/kb/DL1768" target="_blank">http://support.apple.com/kb/DL1768</a> <<a href="http://support.apple.com/kb/DL1768" target="_blank">http://support.apple.com/kb/DL1768</a>> – OS X Mountain Lion<br>
<a href="http://support.apple.com/kb/DL1769" target="_blank">http://support.apple.com/kb/DL1769</a> <<a href="http://support.apple.com/kb/DL1769" target="_blank">http://support.apple.com/kb/DL1769</a>> – OS X Mavericks<br>
<br>
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).<br>
<span class="HOEnZb"><font color="#888888"><br>
Chris<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
> On 29 Oct 2014, at 6:18pm, Lawrence Velázquez <<a href="mailto:larryv@macports.org">larryv@macports.org</a>> wrote:<br>
><br>
> On Oct 28, 2014, at 4:36 AM, Chris Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk">jonesc@hep.phy.cam.ac.uk</a>> wrote:<br>
><br>
>>> in an attempt to minimize exposure to Shellshock. IIRC I got the above<br>
>>> from someone on this list.<br>
>><br>
>> Together, if I recall, with a number of posts saying it was also a very bad idea....<br>
><br>
> <a href="https://trac.macports.org/ticket/45680" target="_blank">https://trac.macports.org/ticket/45680</a><br>
><br>
> Upgrading gettext will break for everyone who replaced the system bash with MacPorts'.<br>
><br>
> 1. User replaces /bin/sh with MacPorts' bash, which dynamically links to gettext.<br>
> 2. User runs selfupdate and receives new gettext Portfile.<br>
> 3. User runs port upgrade.<br>
> 4. Upgrade process deactivates old gettext. The replacement /bin/sh is now broken because libintl.8.dylib does not exist.<br>
> 5. Upgrade process tries to activate new gettext but dies because /bin/sh is broken.<br>
><br>
> vq<br>
> _______________________________________________<br>
> macports-users mailing list<br>
> <a href="mailto:macports-users@lists.macosforge.org">macports-users@lists.macosforge.org</a><br>
> <a href="https://lists.macosforge.org/mailman/listinfo/macports-users" target="_blank">https://lists.macosforge.org/mailman/listinfo/macports-users</a><br>
<br>
</div></div><br>_______________________________________________<br>
macports-users mailing list<br>
<a href="mailto:macports-users@lists.macosforge.org">macports-users@lists.macosforge.org</a><br>
<a href="https://lists.macosforge.org/mailman/listinfo/macports-users" target="_blank">https://lists.macosforge.org/mailman/listinfo/macports-users</a><br>
<br></blockquote></div><br></div></div></div>