Re: Error after trying to upgrade installed

2009-01-24 Thread Mark Hattam


On 24 Jan 2009, at 03:46, Rainer Müller wrote:


Bryan Blackburn wrote:
Personally, I'd like to see direct mode deprecated, and when 10.3  
support is

officially dropped, it can be removed entirely.  Other than the old
performance issues with the large number of hardlinks, I don't see  
any
advantage to using direct over image mode.  Are there other reasons  
for

keeping it?


The switch to registry2.0 which is scheduled for 1.8.0 would be a good
place to drop direct mode as it is mainly implemented in the
registry/receipt handling. But that means there would be no  
deprecation

period.

But as we tend to discuss development stuff on the macports-users  
list,
there is the opportunity to ask our users: How many of you do still  
use

direct mode and for what reasons?

Rainer


If you mean the end users ... I had to go and actually search in the  
documentation to find out what direct mode is.

http://guide.macports.org/#internals.images
which is the only hit for direct mode.

Which I think answers your question ...

Mark
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-24 Thread robert delius royar

If direct mode is removed, I will use the following to work around:
port destroot foo
rsync -tpogHlr /opt/local/var/macports/build/foo/work/destroot/opt/local /opt
[or wherever the destroot is]

This would effectively turn macports into a simple way to build packages 
based on the maintainer's having discovered what needs patching and 
which configure options there are.  Unfortunately, it kills the ability 
to track when a port needs to be upgraded.


I do not wish to proliferate thousands of hard links to old ports and 
such on the system.  But I am not asking for permission or support.


--
Dr. Robert Delius Royar   Associate Professor of English
Morehead State University Morehead, Kentucky
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-23 Thread Ryan Schmidt

On Jan 19, 2009, at 07:37, robert delius royar wrote:

So much traffic on this thread, so much time spent answering  
questions. But I do not recall any of the answerers trying

port provides /opt/local/lib/libintl.dylib


Sorry; I thought it was already understood that libintl is the  
internationalization library and that it is provided by gettext.



That would have pointerd out that the initial problem of gettext  
wanting to reinstall itself (perhaps for no good reason) had  
removed the dylibs that gettext provides and uses, itself.


For no good reason depends on your situation. In this particular  
case, gettext was updated from 0.17_3 to 0.17_4 because some 64-bit  
issues were corrected. If anyone had installed 0.17_3 with the  
+universal variant and had requested 64-bit architectures in the  
universal_archs variable in macports.conf, they would have had an  
incorrectly-functioning gettext, so for those users, it was necessary  
to force a rebuild by increasing the port's revision. If you did not  
have gettext installed with the +universal variant, or had not  
selected any 64-bit architectures in macports.conf (the default is  
only the 32-bit architectures ppc and i386) then you would not have  
been affected and would not need to rebuild gettext.


When using MacPorts, you can either assume that MacPorts maintainers  
know what they are doing and if they are requesting you to rebuild a  
port (as evidenced by it showing up in port outdated) then you  
rebuild it. Or if you have the inclination you can dig deeper,  
subscribe to the macports-changes mailing list, monitor the changes  
taking place to the ports you use, and evaluate for yourself whether  
you need the changes provided in a new port revision, and if you  
don't, then don't upgrade the port until it's updated again later  
with a fix that you do want.


For many users the former strategy is sufficient, even to the point  
of just running sudo port sync and sudo port upgrade outdated and  
letting MacPorts take care of everything.



I believe this highlights some error in the 1.70 base.  I say this  
because it seems to be faulty UI that allows a user to specify a  
variant that when in place the port command can be broken in a  
simple upgrade.


I agree it's a MacPorts base issue. A ticket has now also been filed  
for this issue:


http://trac.macports.org/ticket/18149

In it, I comment:

Actually it surprises me that MacPorts base is shelling out to an ln  
command at all; why aren't we using the [file link] Tcl command?


Does anybody know the answer? I haven't yet looked through the  
history of base to see if the commit messages give any indication.



I mention above perhaps for no good reason because last week when  
I upgraded graphviz which upgraded gd2, I got into a loop of trying  
to upgrade freetype, zlib and gettext, none of which were outdated  
according to port.  I finally had to force the reinstallation of  
zlib and gettext, force uninstall gd2, freetype, zlib, and gettext  
and start over.


Without seeing exactly what commands you typed and what output you  
got, I can only speculate that perhaps you used the -f flag to port  
upgrade and did not also use the -n flag. This can result in  
dependencies being rebuilt even if they are not outdated -- possibly  
even multiple times. Nobody wants this, so one should never use the - 
f flag with port upgrade without also using the -n flag. However,  
MacPorts should never get in any kind of loop. It might seem that  
way, but if you let it run all the way through (which might take  
prohibitively long) it would eventually end, so it's not a loop.



That was not the first time I had seen this loop of upgrading a  
port that was the same version as the curreny installed version,  
followed by failing to install the new version because a version  
was already in place (the same version).  In some cases the process  
stopps there; in others it moves to the next port that it either  
thinks should be upgraded or really should be.  Then if that port  
depends on one of the ports it has mistakenly identified as  
outdated, it goes into the same pattern.  On a few occassions I  
have found libraries from those ports which wer not in need of  
replacement--but replaced anyway--missing. TimeMachine is useful,  
then,


If you could provide actual commands typed and verbatim output  
received the next time you encounter this problem, that might be  
helpful to getting it resolved.



I have the last model of the G5 iMac running 10.5.6, and the  
portinstalltype is direct, and portarchivemode is no.  1.7 seems as  
though it has sections that are not sure what direct mode is by  
the way; some ports I have upgraded recently report activating.   
I have not used image mode on this machine at all.


Direct mode is certainly less well tested than image mode. I've never  
used it. Is there a particular reason why you are using it?


There are ports that define 

Re: Error after trying to upgrade installed

2009-01-23 Thread Joshua Root
Ryan Schmidt wrote:
 Actually it surprises me that MacPorts base is shelling out to an ln
 command at all; why aren't we using the [file link] Tcl command?

What seems even stranger to me is that it's the *de*activate phase
that's failing, which appears to only use 'file delete'.

- Josh
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-23 Thread robert delius royar

Fri, 23 Jan 2009 (06:27 -0600 UTC) Ryan Schmidt wrote:


On Jan 19, 2009, at 07:37, robert delius royar wrote:

So much traffic on this thread, so much time spent answering questions. But 
I do not recall any of the answerers trying

port provides /opt/local/lib/libintl.dylib


Sorry; I thought it was already understood that libintl is the 
internationalization library and that it is provided by gettext.


My original post was strident; it should not have been.
[...]
I agree it's a MacPorts base issue. A ticket has now also been filed for this 
issue:


http://trac.macports.org/ticket/18149


Thanks

I have the last model of the G5 iMac running 10.5.6, and the 
portinstalltype is direct, and portarchivemode is no.  1.7 seems as though 
it has sections that are not sure what direct mode is by the way; some 
ports I have upgraded recently report activating.  I have not used image 
mode on this machine at all.


Direct mode is certainly less well tested than image mode. I've never used 
it. Is there a particular reason why you are using it?


I began using Darwinports very soon after DP was created.  When Image 
mode was added, a few of us (perhaps under Panther but could have been 
Tiger) noticed significant (and documentable) slow downs on access to 
files in /opt/local/bin.  After a conversation on the old DP mailing 
list, we found that hard links were problematic for the OS (at least in 
that version) when they exceded some level.


I recall that an Apple employee stated that this was a known problem. 
After switching from my old G4 to this G5 and reinstalling MP, I kept 
the direct mode partly because it works just fine and I do not usually 
need to worry about which port is active.  I only have 518 ports 
installed on this computer.  On the earlier machine I had more of the 
X11 system in DP/MP.  But now that Apple has a real active developer 
working on porting X, all my X stuff (except gimp) is outside MP's 
system.


There are ports that define post-activation phases. Perhaps those are getting 
executed even in direct mode, and that is why you see MacPorts stating it is 
activating a port, even though in direct mode there isn't an activation 
phase...


If you could say exactly what ports do this, we could investigate further.


I will make sure to do this the next time I see the problem.  I can 
usually work around it because of so many years using MP, so I just move 
forward.


--
Dr. Robert Delius Royar   Associate Professor of English
Morehead State University Morehead, Kentucky

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-23 Thread Daniel J. Luke

On Jan 23, 2009, at 8:35 AM, robert delius royar wrote:
Direct mode is certainly less well tested than image mode. I've  
never used it. Is there a particular reason why you are using it?


I began using Darwinports very soon after DP was created.  When  
Image mode was added, a few of us (perhaps under Panther but could  
have been Tiger) noticed significant (and documentable) slow downs  
on access to files in /opt/local/bin.  After a conversation on the  
old DP mailing list, we found that hard links were problematic for  
the OS (at least in that version) when they exceded some level.


For the list archives, this was fixed (in 10.4, IIRC).

As for your upgrade loop, I think you're experiencing bug #17762 (http://trac.macports.org/ticket/17762 
)


I haven't had time to investigate (and wasn't running trunk on my  
direct mode machine so I missed the change that caused it).


--
Daniel J. Luke
++
| * dl...@geeklair.net * |
| *-- http://www.geeklair.net -* |
++
|   Opinions expressed are mine and do not necessarily   |
|  reflect the opinions of my employer.  |
++





PGP.sig
Description: This is a digitally signed message part
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-23 Thread Bryan Blackburn
On Fri, Jan 23, 2009 at 09:34:09AM -0500, Daniel J. Luke said:
 On Jan 23, 2009, at 8:35 AM, robert delius royar wrote:
 Direct mode is certainly less well tested than image mode. I've never 
 used it. Is there a particular reason why you are using it?

 I began using Darwinports very soon after DP was created.  When Image 
 mode was added, a few of us (perhaps under Panther but could have been 
 Tiger) noticed significant (and documentable) slow downs on access to 
 files in /opt/local/bin.  After a conversation on the old DP mailing 
 list, we found that hard links were problematic for the OS (at least in 
 that version) when they exceded some level.

 For the list archives, this was fixed (in 10.4, IIRC).

Personally, I'd like to see direct mode deprecated, and when 10.3 support is
officially dropped, it can be removed entirely.  Other than the old
performance issues with the large number of hardlinks, I don't see any
advantage to using direct over image mode.  Are there other reasons for
keeping it?

Bryan



 As for your upgrade loop, I think you're experiencing bug #17762 
 (http://trac.macports.org/ticket/17762)

 I haven't had time to investigate (and wasn't running trunk on my direct 
 mode machine so I missed the change that caused it).

 --
 Daniel J. Luke
 ++
 | * dl...@geeklair.net * |
 | *-- http://www.geeklair.net -* |
 ++
 |   Opinions expressed are mine and do not necessarily   |
 |  reflect the opinions of my employer.  |
 ++
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-23 Thread Daniel J. Luke

On Jan 23, 2009, at 4:15 PM, Bryan Blackburn wrote:

For the list archives, this was fixed (in 10.4, IIRC).


Personally, I'd like to see direct mode deprecated, and when 10.3  
support is

officially dropped, it can be removed entirely.  Other than the old
performance issues with the large number of hardlinks, I don't see any
advantage to using direct over image mode.  Are there other reasons  
for

keeping it?



Probably not. Although I still maintain that image mode doesn't really  
give us anything more than what direct mode + archives gives us  
(except that there's currently no way to tell port to use a specific,  
older, archive). Direct mode is somewhat simpler, but if no one doing  
active development is using it anymore, it's probably not worth  
keeping around. Some easier way of transitioning than uninstalling all  
ports, making the switch in the conf, and reinstalling everything,  
would be nice, though.


10.3 isn't officially supported by us anymore (although we try not to  
break it - Ryan's protestations about 10.5 notwithstanding).


[and no, I'm not just trying to troll jkh and his idea of having  
things build against and depend on non-active images]


--
Daniel J. Luke
++
| * dl...@geeklair.net * |
| *-- http://www.geeklair.net -* |
++
|   Opinions expressed are mine and do not necessarily   |
|  reflect the opinions of my employer.  |
++





PGP.sig
Description: This is a digitally signed message part
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-23 Thread Bryan Blackburn
On Fri, Jan 23, 2009 at 04:39:54PM -0500, Daniel J. Luke said:
 On Jan 23, 2009, at 4:15 PM, Bryan Blackburn wrote:
 For the list archives, this was fixed (in 10.4, IIRC).

 Personally, I'd like to see direct mode deprecated, and when 10.3  
 support is
 officially dropped, it can be removed entirely.  Other than the old
 performance issues with the large number of hardlinks, I don't see any
 advantage to using direct over image mode.  Are there other reasons for
 keeping it?


 Probably not. Although I still maintain that image mode doesn't really  
 give us anything more than what direct mode + archives gives us (except 
 that there's currently no way to tell port to use a specific, older, 
 archive). Direct mode is somewhat simpler, but if no one doing active 
 development is using it anymore, it's probably not worth keeping around. 
 Some easier way of transitioning than uninstalling all ports, making the 
 switch in the conf, and reinstalling everything, would be nice, though.

True, and I've been trying archives on my install lately, to see how it
compares with images.  If there were something similar to how 'port
installed' shows what's there, for archives, and the @a.b.c +variant format
were to work against archives as well, then it'd be a viable replacement.
Cleaner since everything is kept within the one archive file instead of
installed in ...software/.

A merging of the two options keeping the best of each would be optimal.


 10.3 isn't officially supported by us anymore (although we try not to  
 break it - Ryan's protestations about 10.5 notwithstanding).

True, but I'm talking when we truly and completely say no more 10.3, from
no more building DMGs for it to closing tickets against 10.3 as 'not
supported'.

Bryan



 [and no, I'm not just trying to troll jkh and his idea of having things 
 build against and depend on non-active images]

 --
 Daniel J. Luke
 ++
 | * dl...@geeklair.net * |
 | *-- http://www.geeklair.net -* |
 ++
 |   Opinions expressed are mine and do not necessarily   |
 |  reflect the opinions of my employer.  |
 ++

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-19 Thread robert delius royar
So much traffic on this thread, so much time spent answering questions. 
But I do not recall any of the answerers trying

port provides /opt/local/lib/libintl.dylib

That would have pointerd out that the initial problem of gettext wanting 
to reinstall itself (perhaps for no good reason) had removed the dylibs 
that gettext provides and uses, itself.


I believe this highlights some error in the 1.70 base.  I say this 
because it seems to be faulty UI that allows a user to specify a variant 
that when in place the port command can be broken in a simple upgrade.


I mention above perhaps for no good reason because last week when I 
upgraded graphviz which upgraded gd2, I got into a loop of trying to 
upgrade freetype, zlib and gettext, none of which were outdated 
according to port.  I finally had to force the reinstallation of zlib 
and gettext, force uninstall gd2, freetype, zlib, and gettext and start 
over.


That was not the first time I had seen this loop of upgrading a port 
that was the same version as the curreny installed version, followed by 
failing to install the new version because a version was already in 
place (the same version).  In some cases the process stopps there; in 
others it moves to the next port that it either thinks should be 
upgraded or really should be.  Then if that port depends on one of the 
ports it has mistakenly identified as outdated, it goes into the same 
pattern.  On a few occassions I have found libraries from those ports 
which wer not in need of replacement--but replaced anyway--missing. 
TimeMachine is useful, then,


I have the last model of the G5 iMac running 10.5.6, and the 
portinstalltype is direct, and portarchivemode is no.  1.7 seems as 
though it has sections that are not sure what direct mode is by the 
way; some ports I have upgraded recently report activating.  I have 
not used image mode on this machine at all.


--
Dr. Robert Delius Royar   Associate Professor of English
Morehead State University Morehead, Kentucky
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-19 Thread Doctor Who
On Sun, Jan 18, 2009 at 10:04 PM, Ryan Schmidt ryandes...@macports.org wrote:
 On Jan 18, 2009, at 20:50, Doctor Who wrote:

 On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt  wrote:


 Try:

 sudo port install gettext

 Thanks...that worked.

 Great!

 Should I now try to update with 'sudo port upgrade outdated'?

 Sure, go ahead. I know there have been a lot of X11/xorg-related changes
 lately, and I haven't tried them myself yet, so good luck!



Just wanted to report back that the update proceeded without issues.

Thanks.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Rainer Müller
Doctor Who wrote:
 I have MacPorts 1.7.0 installed.  I did a 'sudo port outdated' and had
 5 or 6 ports that needed updating.  I then ran a 'sudo port upgrade
 outdated' and it failed after a while with errors like:
 
 sudo port upgrade outdated
 ---  Deactivating gettext @0.17_3
 Error: Deactivating gettext 0.17_3 failed:
 ---  Activating perl5.8 @5.8.9_2
 Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/touch
   Reason: image not found
 ---  Deactivating gettext @0.17_3
 Error: Deactivating gettext 0.17_3 failed:
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 ---  Deactivating gettext @0.17_3
 Error: Deactivating gettext 0.17_3 failed:
 ---  Activating perl5.8 @5.8.9_2
 Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/touch
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found

Looks like you have coreutils +with_default_names installed, but you
broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
some reason it seems not to be active.

Try to fix it by
  sudo port activate gettext

Rainer
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
On Sun, Jan 18, 2009 at 6:46 PM, Rainer Müller rai...@macports.org wrote:
 Doctor Who wrote:
 I have MacPorts 1.7.0 installed.  I did a 'sudo port outdated' and had
 5 or 6 ports that needed updating.  I then ran a 'sudo port upgrade
 outdated' and it failed after a while with errors like:

 sudo port upgrade outdated
 ---  Deactivating gettext @0.17_3
 Error: Deactivating gettext 0.17_3 failed:
 ---  Activating perl5.8 @5.8.9_2
 Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/touch
   Reason: image not found
 ---  Deactivating gettext @0.17_3
 Error: Deactivating gettext 0.17_3 failed:
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 ---  Deactivating gettext @0.17_3
 Error: Deactivating gettext 0.17_3 failed:
 ---  Activating perl5.8 @5.8.9_2
 Error: Activating perl5.8 @5.8.9_2 failed: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/touch
   Reason: image not found
 Error: Unable to exec port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found
 Error: Unable to upgrade port: dyld: Library not loaded:
 /opt/local/lib/libintl.8.dylib
   Referenced from: /opt/local/bin/ln
   Reason: image not found

 Looks like you have coreutils +with_default_names installed, but you
 broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
 some reason it seems not to be active.

 Try to fix it by
  sudo port activate gettext

 Rainer


sudo port activate gettext
Password:
---  Activating gettext
Error: port activate failed: Image error: gettext @0.17_3 is already active.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Bryan Blackburn
On Mon, Jan 19, 2009 at 12:46:45AM +0100, Rainer Müller said:
 Doctor Who wrote:
  I have MacPorts 1.7.0 installed.  I did a 'sudo port outdated' and had
  5 or 6 ports that needed updating.  I then ran a 'sudo port upgrade
  outdated' and it failed after a while with errors like:
  
  sudo port upgrade outdated
  ---  Deactivating gettext @0.17_3
  Error: Deactivating gettext 0.17_3 failed:
  ---  Activating perl5.8 @5.8.9_2
[...]
 
 Looks like you have coreutils +with_default_names installed, but you
 broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
 some reason it seems not to be active.

Somebody reported this same issue last night on IRC, where it fails to
deactivate gettext but not giving any actual error message.  It ends up
removing all files from ${prefix} but then fails to set the port as not
active, and ends up confused.

You can't force-activate as it complains that it is already active, and any
further deactivate results in the same output above.

Unfortunately I didn't see any way to deal with this or what the cause was,
and was hoping it was a one-off issue.  This is two now this weekend, so
maybe something strange is going on in base...

Bryan


 
 Try to fix it by
   sudo port activate gettext
 
 Rainer
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Rainer Müller
Doctor Who wrote:
 On Sun, Jan 18, 2009 at 6:58 PM, Bryan Blackburn b...@macports.org wrote:
 On Mon, Jan 19, 2009 at 12:46:45AM +0100, Rainer Müller said:
 Doctor Who wrote:
 I have MacPorts 1.7.0 installed.  I did a 'sudo port outdated' and had
 5 or 6 ports that needed updating.  I then ran a 'sudo port upgrade
 outdated' and it failed after a while with errors like:

 sudo port upgrade outdated
 ---  Deactivating gettext @0.17_3
 Error: Deactivating gettext 0.17_3 failed:
 ---  Activating perl5.8 @5.8.9_2
 [...]
 Looks like you have coreutils +with_default_names installed, but you
 broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
 some reason it seems not to be active.
 Somebody reported this same issue last night on IRC, where it fails to
 deactivate gettext but not giving any actual error message.  It ends up
 removing all files from ${prefix} but then fails to set the port as not
 active, and ends up confused.

 You can't force-activate as it complains that it is already active, and any
 further deactivate results in the same output above.

 Unfortunately I didn't see any way to deal with this or what the cause was,
 and was hoping it was a one-off issue.  This is two now this weekend, so
 maybe something strange is going on in base...

 Bryan


 
 Well, I hope there is some way to fix/recover from this.  I cannot
 even list files on my file system in Terminal.app (as evidenced by the
 attempt at the ls command above).

It is trying to use /opt/local/bin/ls which is broken. You can still use
/bin/ls.

You can now either always type the full path /bin/ls, remove
/opt/local/bin from your PATH or deactivate the broken coreutils:
  sudo port deactivate coreutils

Then you should at least have working ls/cp/mv etc. again.

Now to fix the gettext issue, please try if this works now:
  sudo port deactivate gettext
  sudo port activate gettext

registry1.0 uses calls like 'system rm -rf ${receipt_file}' to work
with receipt files, so it was unable to operate with the broken
coreutils in PATH.

Rainer
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
On Sun, Jan 18, 2009 at 8:10 PM, Rainer Müller rai...@macports.org wrote:
 Doctor Who wrote:
 On Sun, Jan 18, 2009 at 6:58 PM, Bryan Blackburn b...@macports.org wrote:
 On Mon, Jan 19, 2009 at 12:46:45AM +0100, Rainer Müller said:
 Doctor Who wrote:
 I have MacPorts 1.7.0 installed.  I did a 'sudo port outdated' and had
 5 or 6 ports that needed updating.  I then ran a 'sudo port upgrade
 outdated' and it failed after a while with errors like:

 sudo port upgrade outdated
 ---  Deactivating gettext @0.17_3
 Error: Deactivating gettext 0.17_3 failed:
 ---  Activating perl5.8 @5.8.9_2
 [...]
 Looks like you have coreutils +with_default_names installed, but you
 broke it. /opt/local/lib/libintl.8.dylib is provided by gettext, but for
 some reason it seems not to be active.
 Somebody reported this same issue last night on IRC, where it fails to
 deactivate gettext but not giving any actual error message.  It ends up
 removing all files from ${prefix} but then fails to set the port as not
 active, and ends up confused.

 You can't force-activate as it complains that it is already active, and any
 further deactivate results in the same output above.

 Unfortunately I didn't see any way to deal with this or what the cause was,
 and was hoping it was a one-off issue.  This is two now this weekend, so
 maybe something strange is going on in base...

 Bryan



 Well, I hope there is some way to fix/recover from this.  I cannot
 even list files on my file system in Terminal.app (as evidenced by the
 attempt at the ls command above).

 It is trying to use /opt/local/bin/ls which is broken. You can still use
 /bin/ls.

 You can now either always type the full path /bin/ls, remove
 /opt/local/bin from your PATH or deactivate the broken coreutils:
  sudo port deactivate coreutils

 Then you should at least have working ls/cp/mv etc. again.

 Now to fix the gettext issue, please try if this works now:
  sudo port deactivate gettext
  sudo port activate gettext

 registry1.0 uses calls like 'system rm -rf ${receipt_file}' to work
 with receipt files, so it was unable to operate with the broken
 coreutils in PATH.

 Rainer


I get this when trying to deactivate:

$ sudo port deactivate gettext
Password:
---  Deactivating gettext
Error: port deactivate failed:
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Ryan Schmidt

On Jan 18, 2009, at 19:10, Rainer Müller wrote:


Doctor Who wrote:


Well, I hope there is some way to fix/recover from this.  I cannot
even list files on my file system in Terminal.app (as evidenced by  
the

attempt at the ls command above).


It is trying to use /opt/local/bin/ls which is broken. You can  
still use

/bin/ls.

You can now either always type the full path /bin/ls, remove
/opt/local/bin from your PATH or deactivate the broken coreutils:
  sudo port deactivate coreutils

Then you should at least have working ls/cp/mv etc. again.


Yes, fixing the PATH in ~/.profile or ~/.bash_profile or just  
temporarily in the Terminal would allow you to now type ls or  
touch in the Terminal, however:




Now to fix the gettext issue, please try if this works now:
  sudo port deactivate gettext
  sudo port activate gettext

registry1.0 uses calls like 'system rm -rf ${receipt_file}' to work
with receipt files, so it was unable to operate with the broken
coreutils in PATH.


Note that the user's PATH is not used by MacPorts, so this will still  
fail until you also change the PATH that MacPorts uses while running,  
which is set in the variable binpath in the file /opt/local/etc/ 
macports/macports.conf


You could change the binpath so that /bin and /usr/bin precede /opt/ 
local/bin. Then MacPorts will use the system's file manipulation  
utilities (ln, touch, etc.) you will hopefully be able to deactivate  
the old gettext and activate the new one, at which point your  
coreutils versions of ln and touch will work again and you can (and  
should) revert binpath in macports.conf and PATH in .profile  
or .bash_profile to what they were.


Then, you should probably uninstall coreutils +with_default_names  
because it's probably not good to override those default Mac OS X  
utilities.


We could consider removing the +with_default_names capability from  
the coreutils port.


We should also consider forcing MacPorts base to always use vital  
utilities like ln and touch via their absolute paths in /bin or /usr/ 
bin and not allow a MacPorts version to interfere. We might consider  
the same for tar, gzip, bzip2, etc, to avoid the occasional problem  
with the MacPorts versions of those utilities, e.g. the thread error  
apache2 from macports 1.70 earlier today:


http://lists.macosforge.org/pipermail/macports-users/2009-January/ 
013335.html



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
On Sun, Jan 18, 2009 at 9:01 PM, Ryan Schmidt ryandes...@macports.org wrote:
 On Jan 18, 2009, at 19:10, Rainer Müller wrote:

 Doctor Who wrote:

 Well, I hope there is some way to fix/recover from this.  I cannot
 even list files on my file system in Terminal.app (as evidenced by the
 attempt at the ls command above).

 It is trying to use /opt/local/bin/ls which is broken. You can still use
 /bin/ls.

 You can now either always type the full path /bin/ls, remove
 /opt/local/bin from your PATH or deactivate the broken coreutils:
  sudo port deactivate coreutils

 Then you should at least have working ls/cp/mv etc. again.

 Yes, fixing the PATH in ~/.profile or ~/.bash_profile or just temporarily in
 the Terminal would allow you to now type ls or touch in the Terminal,
 however:


 Now to fix the gettext issue, please try if this works now:
  sudo port deactivate gettext
  sudo port activate gettext

 registry1.0 uses calls like 'system rm -rf ${receipt_file}' to work
 with receipt files, so it was unable to operate with the broken
 coreutils in PATH.

 Note that the user's PATH is not used by MacPorts, so this will still fail
 until you also change the PATH that MacPorts uses while running, which is
 set in the variable binpath in the file
 /opt/local/etc/macports/macports.conf

 You could change the binpath so that /bin and /usr/bin precede
 /opt/local/bin. Then MacPorts will use the system's file manipulation
 utilities (ln, touch, etc.) you will hopefully be able to deactivate the old
 gettext and activate the new one, at which point your coreutils versions of
 ln and touch will work again and you can (and should) revert binpath in
 macports.conf and PATH in .profile or .bash_profile to what they were.

 Then, you should probably uninstall coreutils +with_default_names because
 it's probably not good to override those default Mac OS X utilities.

 We could consider removing the +with_default_names capability from the
 coreutils port.

 We should also consider forcing MacPorts base to always use vital utilities
 like ln and touch via their absolute paths in /bin or /usr/bin and not allow
 a MacPorts version to interfere. We might consider the same for tar, gzip,
 bzip2, etc, to avoid the occasional problem with the MacPorts versions of
 those utilities, e.g. the thread error apache2 from macports 1.70 earlier
 today:

 http://lists.macosforge.org/pipermail/macports-users/2009-January/013335.html




Not to be a pain, but I'm pretty new to MacPorts and I don't want to
mess my system up more.  Would you please outline the steps I should
take one by one to (hopefully) restore my system back to 'normal'?

Thanks!
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Ryan Schmidt

On Jan 18, 2009, at 20:18, Doctor Who wrote:


On Sun, Jan 18, 2009 at 9:01 PM, Ryan Schmidt wrote:


On Jan 18, 2009, at 19:10, Rainer Müller wrote:


Doctor Who wrote:


Well, I hope there is some way to fix/recover from this.  I cannot
even list files on my file system in Terminal.app (as evidenced  
by the

attempt at the ls command above).


It is trying to use /opt/local/bin/ls which is broken. You can  
still use

/bin/ls.

You can now either always type the full path /bin/ls, remove
/opt/local/bin from your PATH or deactivate the broken coreutils:
 sudo port deactivate coreutils

Then you should at least have working ls/cp/mv etc. again.


Yes, fixing the PATH in ~/.profile or ~/.bash_profile or just  
temporarily in
the Terminal would allow you to now type ls or touch in the  
Terminal,

however:



Now to fix the gettext issue, please try if this works now:
 sudo port deactivate gettext
 sudo port activate gettext

registry1.0 uses calls like 'system rm -rf ${receipt_file}' to  
work

with receipt files, so it was unable to operate with the broken
coreutils in PATH.


Note that the user's PATH is not used by MacPorts, so this will  
still fail
until you also change the PATH that MacPorts uses while running,  
which is

set in the variable binpath in the file
/opt/local/etc/macports/macports.conf

You could change the binpath so that /bin and /usr/bin precede
/opt/local/bin. Then MacPorts will use the system's file manipulation
utilities (ln, touch, etc.) you will hopefully be able to  
deactivate the old
gettext and activate the new one, at which point your coreutils  
versions of
ln and touch will work again and you can (and should) revert  
binpath in
macports.conf and PATH in .profile or .bash_profile to what they  
were.


Then, you should probably uninstall coreutils +with_default_names  
because

it's probably not good to override those default Mac OS X utilities.

We could consider removing the +with_default_names capability from  
the

coreutils port.

We should also consider forcing MacPorts base to always use vital  
utilities
like ln and touch via their absolute paths in /bin or /usr/bin and  
not allow
a MacPorts version to interfere. We might consider the same for  
tar, gzip,
bzip2, etc, to avoid the occasional problem with the MacPorts  
versions of
those utilities, e.g. the thread error apache2 from macports  
1.70 earlier

today:

http://lists.macosforge.org/pipermail/macports-users/2009-January/ 
013335.html


Not to be a pain, but I'm pretty new to MacPorts and I don't want to
mess my system up more.  Would you please outline the steps I should
take one by one to (hopefully) restore my system back to 'normal'?


I'm not certain, as I haven't encountered this problem before.

But my suggestion is exactly as I outlined above.

1. Edit /opt/local/etc/macports/macports.conf and change this line:

#binpath		/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/ 
sbin:/usr/X11R6/bin


Remove the hash at the beginning and change the order so that it reads:

binpath		/bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/ 
sbin:/usr/X11R6/bin


2. Deactivate your old gettext:

sudo port deactivate gettext @0.17_3

3. Activate your new gettext:

sudo port activate gettext @0.17_4

4. Uninstall coreutils because it is not a good idea to override the  
default Mac OS X file utilities:


sudo port uninstall coreutils

5. Edit /opt/local/etc/macports/macporst.conf and put the binpath  
line back the way it was before, including the order of the paths and  
the hash at the beginning of the line.




___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt ryandes...@macports.org wrote:
 On Jan 18, 2009, at 20:18, Doctor Who wrote:

 On Sun, Jan 18, 2009 at 9:01 PM, Ryan Schmidt wrote:

 On Jan 18, 2009, at 19:10, Rainer Müller wrote:

 Doctor Who wrote:

 Well, I hope there is some way to fix/recover from this.  I cannot
 even list files on my file system in Terminal.app (as evidenced by the
 attempt at the ls command above).

 It is trying to use /opt/local/bin/ls which is broken. You can still use
 /bin/ls.

 You can now either always type the full path /bin/ls, remove
 /opt/local/bin from your PATH or deactivate the broken coreutils:
  sudo port deactivate coreutils

 Then you should at least have working ls/cp/mv etc. again.

 Yes, fixing the PATH in ~/.profile or ~/.bash_profile or just temporarily
 in
 the Terminal would allow you to now type ls or touch in the Terminal,
 however:


 Now to fix the gettext issue, please try if this works now:
  sudo port deactivate gettext
  sudo port activate gettext

 registry1.0 uses calls like 'system rm -rf ${receipt_file}' to work
 with receipt files, so it was unable to operate with the broken
 coreutils in PATH.

 Note that the user's PATH is not used by MacPorts, so this will still
 fail
 until you also change the PATH that MacPorts uses while running, which is
 set in the variable binpath in the file
 /opt/local/etc/macports/macports.conf

 You could change the binpath so that /bin and /usr/bin precede
 /opt/local/bin. Then MacPorts will use the system's file manipulation
 utilities (ln, touch, etc.) you will hopefully be able to deactivate the
 old
 gettext and activate the new one, at which point your coreutils versions
 of
 ln and touch will work again and you can (and should) revert binpath in
 macports.conf and PATH in .profile or .bash_profile to what they were.

 Then, you should probably uninstall coreutils +with_default_names because
 it's probably not good to override those default Mac OS X utilities.

 We could consider removing the +with_default_names capability from the
 coreutils port.

 We should also consider forcing MacPorts base to always use vital
 utilities
 like ln and touch via their absolute paths in /bin or /usr/bin and not
 allow
 a MacPorts version to interfere. We might consider the same for tar,
 gzip,
 bzip2, etc, to avoid the occasional problem with the MacPorts versions of
 those utilities, e.g. the thread error apache2 from macports 1.70
 earlier
 today:


 http://lists.macosforge.org/pipermail/macports-users/2009-January/013335.html

 Not to be a pain, but I'm pretty new to MacPorts and I don't want to
 mess my system up more.  Would you please outline the steps I should
 take one by one to (hopefully) restore my system back to 'normal'?

 I'm not certain, as I haven't encountered this problem before.

 But my suggestion is exactly as I outlined above.

 1. Edit /opt/local/etc/macports/macports.conf and change this line:

 #binpath
  /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin

 Remove the hash at the beginning and change the order so that it reads:

 binpath
 /bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/sbin:/usr/X11R6/bin

 2. Deactivate your old gettext:

 sudo port deactivate gettext @0.17_3

 3. Activate your new gettext:

 sudo port activate gettext @0.17_4

 4. Uninstall coreutils because it is not a good idea to override the default
 Mac OS X file utilities:

 sudo port uninstall coreutils

 5. Edit /opt/local/etc/macports/macporst.conf and put the binpath line back
 the way it was before, including the order of the paths and the hash at the
 beginning of the line.





OK, when I get to the point of activating the later version of
gettext, it's not installed:

tbook:~ who$ sudo port deactivate gettext @0.17_3
---  Deactivating gettext @0.17_3
tbook:~ who$ sudo port activate gettext @0.17_4
Error: port activate failed: Registry error: gettext 0.17_4 not
registered as installed.

What should I do at this point to install this version correctly?
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Ryan Schmidt


On Jan 18, 2009, at 20:39, Doctor Who wrote:


On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt wrote:


On Jan 18, 2009, at 20:18, Doctor Who wrote:


Not to be a pain, but I'm pretty new to MacPorts and I don't want to
mess my system up more.  Would you please outline the steps I should
take one by one to (hopefully) restore my system back to 'normal'?


I meant to say earlier, but don't feel that you're bothering us:  
you've clearly found a problem and we need to first get you out of it  
and then figure out how to not make it affect others. Sorry this  
happened; I know it's not a pleasant experience, especially when  
you're just trying to get used to MacPorts. It's not usually like  
this. :)




I'm not certain, as I haven't encountered this problem before.

But my suggestion is exactly as I outlined above.

1. Edit /opt/local/etc/macports/macports.conf and change this line:

#binpath
 /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/ 
X11R6/bin


Remove the hash at the beginning and change the order so that it  
reads:


binpath
/bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/sbin:/usr/ 
X11R6/bin


2. Deactivate your old gettext:

sudo port deactivate gettext @0.17_3

3. Activate your new gettext:

sudo port activate gettext @0.17_4

4. Uninstall coreutils because it is not a good idea to override  
the default

Mac OS X file utilities:

sudo port uninstall coreutils

5. Edit /opt/local/etc/macports/macporst.conf and put the binpath  
line back
the way it was before, including the order of the paths and the  
hash at the

beginning of the line.


OK, when I get to the point of activating the later version of
gettext, it's not installed:

tbook:~ who$ sudo port deactivate gettext @0.17_3
---  Deactivating gettext @0.17_3
tbook:~ who$ sudo port activate gettext @0.17_4
Error: port activate failed: Registry error: gettext 0.17_4 not
registered as installed.

What should I do at this point to install this version correctly?



Try:

sudo port install gettext

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Ryan Schmidt


On Jan 18, 2009, at 20:53, Doctor Who wrote:


Also, does removing coreutils cause a problems with paths for tools
like 'ls' now?  How do I fix the paths so I can use the tools again?

tbook:~ who$ ls
-bash: /opt/local/bin/ls: No such file or directory


Since /opt/local/bin/ls doesn't exist, the shell should now look for  
ls in other paths, and find it in /bin.


You must have it set up differently What does which ls say?  
What does alias | grep ls say?


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt ryandes...@macports.org wrote:

 On Jan 18, 2009, at 20:39, Doctor Who wrote:

 On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt wrote:

 On Jan 18, 2009, at 20:18, Doctor Who wrote:

 Not to be a pain, but I'm pretty new to MacPorts and I don't want to
 mess my system up more.  Would you please outline the steps I should
 take one by one to (hopefully) restore my system back to 'normal'?

 I meant to say earlier, but don't feel that you're bothering us: you've
 clearly found a problem and we need to first get you out of it and then
 figure out how to not make it affect others. Sorry this happened; I know
 it's not a pleasant experience, especially when you're just trying to get
 used to MacPorts. It's not usually like this. :)


 I'm not certain, as I haven't encountered this problem before.

 But my suggestion is exactly as I outlined above.

 1. Edit /opt/local/etc/macports/macports.conf and change this line:

 #binpath

  /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin

 Remove the hash at the beginning and change the order so that it reads:

 binpath

 /bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/sbin:/usr/X11R6/bin

 2. Deactivate your old gettext:

 sudo port deactivate gettext @0.17_3

 3. Activate your new gettext:

 sudo port activate gettext @0.17_4

 4. Uninstall coreutils because it is not a good idea to override the
 default
 Mac OS X file utilities:

 sudo port uninstall coreutils

 5. Edit /opt/local/etc/macports/macporst.conf and put the binpath line
 back
 the way it was before, including the order of the paths and the hash at
 the
 beginning of the line.

 OK, when I get to the point of activating the later version of
 gettext, it's not installed:

 tbook:~ who$ sudo port deactivate gettext @0.17_3
 ---  Deactivating gettext @0.17_3
 tbook:~ who$ sudo port activate gettext @0.17_4
 Error: port activate failed: Registry error: gettext 0.17_4 not
 registered as installed.

 What should I do at this point to install this version correctly?


 Try:

 sudo port install gettext



Also, does removing coreutils cause a problems with paths for tools
like 'ls' now?  How do I fix the paths so I can use the tools again?

tbook:~ who$ ls
-bash: /opt/local/bin/ls: No such file or directory
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Ryan Schmidt

On Jan 18, 2009, at 20:50, Doctor Who wrote:


On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt  wrote:





Try:

sudo port install gettext


Thanks...that worked.


Great!


Should I now try to update with 'sudo port upgrade outdated'?


Sure, go ahead. I know there have been a lot of X11/xorg-related  
changes lately, and I haven't tried them myself yet, so good luck!


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
On Sun, Jan 18, 2009 at 9:57 PM, Ryan Schmidt ryandes...@macports.org wrote:

 On Jan 18, 2009, at 20:53, Doctor Who wrote:

 Also, does removing coreutils cause a problems with paths for tools
 like 'ls' now?  How do I fix the paths so I can use the tools again?

 tbook:~ who$ ls
 -bash: /opt/local/bin/ls: No such file or directory

 Since /opt/local/bin/ls doesn't exist, the shell should now look for ls in
 other paths, and find it in /bin.

 You must have it set up differently What does which ls say? What does
 alias | grep ls say?



It's working now, once I started another shell.

Thanks.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Doctor Who
On Sun, Jan 18, 2009 at 9:43 PM, Ryan Schmidt ryandes...@macports.org wrote:

 On Jan 18, 2009, at 20:39, Doctor Who wrote:

 On Sun, Jan 18, 2009 at 9:28 PM, Ryan Schmidt wrote:

 On Jan 18, 2009, at 20:18, Doctor Who wrote:

 Not to be a pain, but I'm pretty new to MacPorts and I don't want to
 mess my system up more.  Would you please outline the steps I should
 take one by one to (hopefully) restore my system back to 'normal'?

 I meant to say earlier, but don't feel that you're bothering us: you've
 clearly found a problem and we need to first get you out of it and then
 figure out how to not make it affect others. Sorry this happened; I know
 it's not a pleasant experience, especially when you're just trying to get
 used to MacPorts. It's not usually like this. :)


 I'm not certain, as I haven't encountered this problem before.

 But my suggestion is exactly as I outlined above.

 1. Edit /opt/local/etc/macports/macports.conf and change this line:

 #binpath

  /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin

 Remove the hash at the beginning and change the order so that it reads:

 binpath

 /bin:/sbin:/usr/bin:/usr/sbin:/opt/local/bin:/opt/local/sbin:/usr/X11R6/bin

 2. Deactivate your old gettext:

 sudo port deactivate gettext @0.17_3

 3. Activate your new gettext:

 sudo port activate gettext @0.17_4

 4. Uninstall coreutils because it is not a good idea to override the
 default
 Mac OS X file utilities:

 sudo port uninstall coreutils

 5. Edit /opt/local/etc/macports/macporst.conf and put the binpath line
 back
 the way it was before, including the order of the paths and the hash at
 the
 beginning of the line.

 OK, when I get to the point of activating the later version of
 gettext, it's not installed:

 tbook:~ who$ sudo port deactivate gettext @0.17_3
 ---  Deactivating gettext @0.17_3
 tbook:~ who$ sudo port activate gettext @0.17_4
 Error: port activate failed: Registry error: gettext 0.17_4 not
 registered as installed.

 What should I do at this point to install this version correctly?


 Try:

 sudo port install gettext



Thanks...that worked.  Should I now try to update with 'sudo port
upgrade outdated'?
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Error after trying to upgrade installed

2009-01-18 Thread Bryan Blackburn
On Sun, Jan 18, 2009 at 08:01:57PM -0600, Ryan Schmidt said:
[...]

 We should also consider forcing MacPorts base to always use vital  
 utilities like ln and touch via their absolute paths in /bin or /usr/bin 
 and not allow a MacPorts version to interfere. We might consider the same 
 for tar, gzip, bzip2, etc, to avoid the occasional problem with the 
 MacPorts versions of those utilities, e.g. the thread error apache2 from 
 macports 1.70 earlier today:

For some tools (eg, rm) which are definitely guaranteed to be
system-installed and acceptable, that makes sense.  For others, there's
#15868:

http://trac.macports.org/ticket/15868

So using the system-installed version (svn in that case) would make things
worse...

Bryan



 http://lists.macosforge.org/pipermail/macports-users/2009-January/013335.html

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users