port can't find package Pextlib 1.0

[clang@…]

When I run port at the terminal prompt I get the following:

''
can't find package Pextlib 1.0
    while executing
"package require Pextlib 1.0"
    (procedure "mportinit" line 365)
    invoked from within
"mportinit ui_options global_options global_variations"
Error: /opt/local/bin/port: Failed to initialize MacPorts, can't find package Pextlib 1.0''

When I search with spotlight I find pextlib 1.0 in: /opt/local/var/macports/sources/rsync.macportsorg/release/base/src/pextlib1.0 as well as in: /opt/local/share/macports/Tcl/pextlib1.0

Can anyone tell me why port might not be able to find it?

I installed version 1.5.0 from the package installer from the disk image MacPorts-1.5.0-10.4.dmg

[ryandesign (Ryan Carsten Schmidt)]

I do not know why you are experiencing this problem. Please write a message to the macports-users mailing list and I'm sure someone will be able to help you.

[nspessard@…]

same here on 10.4.10

[jmpp@…]

Please reinstall MacPorts (either from the dmg or from source) and then run selfupdate to upgrade to our latest release. Report back here with new findings and please close the ticket if the problem goes away (in short, everything looks as expected on your system --at least with respect to the information you provided, which might not be enough-- so I don't see why you're getting this failure).

-jmpp

[clang@…]

I did a re-install from the dmg and it still doesn't work. Can't even get far enough in to be able to run selfupdate. I looked through the macports-users mailing list and a number of people are having this problem and the typical response on the mailing list is that they must have downloaded a version of macports for a different version of the operating system. I double checked and I definitely am trying to install MacPorts-1.5.0-10.4.dmg on system 10.4.10. It seems that most of us who are having this issue are on the same version of the OS. It also seems that the bug is affecting only new installations, not people who have updated to that version from a prior version. Is there any possibility that the disk image version is not correct?

On another line of thinking is there some way to set a path variable, say in a .login or .cshrc file that would help the program find the library?

[jmpp@…]

OK, so, two things:

-) First lets try to discard it's not a for-whatever-reason hosed MacPorts installation: please move aside your /opt/local and /Library/Tcl/macports.10 paths temporarily (backing up as necessary if there's anything you want to preserve) and reinstall from the ​dmg. Do you still get the problem?

-) If so, then please move those paths aside again and reinstall from ​source, tell us how it goes.

On both cases, having a files listing of /Library/Tcl/macports1.0, /opt/local/share/macports/Tcl and /opt/local/share/macports/Tcl/pextlib1.0 would be really helpful, plus the contents of the /opt/local/share/macports/Tcl/pextlib1.0/pkgIndex.tcl file if it exists.

-jmpp

[jmpp@…]

No further feedback from reporter, closing ticket. Please reopen with further information if this is still a problem.

-jmpp

[afb@…]

(jmpp forgot to close)

[tobypeterson]

Milestone MacPorts base bugs deleted