[MacPorts] #42111: gettext @18.3.2 hangs and crashes computer when attempting upgrade
MacPorts
noreply at macports.org
Mon Jan 13 13:46:13 PST 2014
#42111: gettext @18.3.2 hangs and crashes computer when attempting upgrade
----------------------------+--------------------------
Reporter: zanderpower@… | Owner: ryandesign@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.2.1
Resolution: | Keywords:
Port: gettext |
----------------------------+--------------------------
Changes (by ryandesign@…):
* owner: macports-tickets@… => ryandesign@…
* priority: High => Normal
Old description:
> What I did:
>
> '''sudo port selfupdate'''
> '''sudo port ugrade outdated'''
>
> My computer: PowerBook G4 15", 1.67GHz PPC(7450), OSX 10.5.8
>
> Computer hangs--even the mouse cursor locks up--during the configure
> stage of upgrading gettext, and I must turn computer off by holding down
> the start button for 5 seconds.
>
> Note that MacPorts wants to upgrade gettext to version 18.3.2!! I
> checked http://www.gnu.org/software/gettext/ and it seems they are STILL
> only on release version 18.3.1 This seems a bit fishy. Should I be
> worried?
>
> I am able to update other outdated software (e.g. fontconfig) by
> bypassing upgrading gettext using
> '''sudo port -n upgrade fontconfig.'''
New description:
What I did:
{{{
sudo port selfupdate
sudo port ugrade outdated
}}}
My computer: PowerBook G4 15", 1.67GHz PPC(7450), OSX 10.5.8
Computer hangs--even the mouse cursor locks up--during the configure stage
of upgrading gettext, and I must turn computer off by holding down the
start button for 5 seconds.
Note that MacPorts wants to upgrade gettext to version 18.3.2!! I checked
http://www.gnu.org/software/gettext/ and it seems they are STILL only on
release version 18.3.1 This seems a bit fishy. Should I be worried?
I am able to update other outdated software (e.g. fontconfig) by bypassing
upgrading gettext using
{{{
sudo port -n upgrade fontconfig
}}}
--
Comment:
I'm sorry to hear that trying to upgrade gettext crashes your computer,
but it's not possible for that to be gettext's or MacPorts' fault. There
must be something wrong with your computer. Do normal troubleshooting: use
Disk Utility to check if your disk is ok; take out one or the other of
your RAM chips to see if one of them may be faulty, etc.
I also have a PowerBook G4 1.67 GHz running Leopard and it was able to
upgrade to gettext 0.18.3.2 just fine. This model did however have some
hardware problems, such as a
[https://web.archive.org/web/20080507154553/http://docs.info.apple.com/article.html?artnum=303173
defect in the lower RAM slot]. That article only describes that the RAM
would not be recognized in the lower RAM slot, however on my PowerBook,
having RAM installed in the lower RAM slot causes it to crash within
seconds. Removing the RAM from the lower slot and using only the upper
slot has made the computer usable again; now it only crashes if I let it
get too hot, so I try to elevate it off the desk a quarter inch or so to
give it more airflow.
The latest version of gettext is 0.18.3.2 which was released January 7,
2014. See http://ftp.gnu.org/pub/gnu/gettext/?C=M;O=D . If it concerns you
that the developers of gettext have forgotten to update their web page to
indicate this, you should report that to the developers of gettext.
--
Ticket URL: <https://trac.macports.org/ticket/42111#comment:1>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list