Opened 12 years ago

Closed 12 years ago

#18449 closed defect (fixed)

python25 won't install on Mac OS X 10.6 (10A261)

Reported by: joshmoz@… Owned by: mww@…
Priority: Normal Milestone:
Component: ports Version: 1.7.0
Keywords: Cc: eyekyu@…, simon.bugzilla@…, mamoll (Mark Moll)
Port: python25

Description

It is not possible to successfully install python25 on Mac OS X 10.6 build 10A261. Error output will be attached to this bug.

Attachments (1)

mperror.txt (5.8 KB) - added by joshmoz@… 12 years ago.
error output 1

Download all attachments as: .zip

Change History (16)

Changed 12 years ago by joshmoz@…

Attachment: mperror.txt added

error output 1

comment:1 Changed 12 years ago by blb@…

Owner: changed from macports-tickets@… to mww@…
Port: python25 added

Looks like some of the toolbox glue stuff, which should have been disabled in r45823; make sure your install is up to date (sudo port selfupdate)

comment:2 in reply to:  1 Changed 12 years ago by joshmoz@…

Replying to blb@…:

Looks like some of the toolbox glue stuff, which should have been disabled in r45823; make sure your install is up to date (sudo port selfupdate)

I did a fresh install from a tarball, did sync and selfupdate tonight before attempting any installs.

comment:3 Changed 12 years ago by joshmoz@…

Is there a way to work around this, to get macports to skip python25 dependencies and run software against the default-installed python even if that isn't recommended? I'm still getting this python25 error on 10.6 with updates and another round of selfupdate/sync.

comment:4 Changed 12 years ago by joshmoz@…

Seems like python25 shouldn't be necessary for mercurial on Mac OS X 10.6 (or even 10.5).

comment:5 Changed 12 years ago by blb@…

The reason for using the python25 port is mentioned in the FAQ; also note that the vast majority of developers don't currently have access to 10.6.

comment:6 Changed 12 years ago by sorin.sbarnea@…

Sorry for adding a comment here but what is the status of macports on Mac OS X 10.6. There is no information on the the homepage nor in the FAQ page regarding compatibility with 10.6

It's not something to be ignored and there are several ways of getting OS X 10.6 builds.

Thanks,

comment:7 in reply to:  6 ; Changed 12 years ago by danielluke (Daniel J. Luke)

Replying to sorin.sbarnea@…:

Sorry for adding a comment here but what is the status of macports on Mac OS X 10.6. There is no information on the the homepage nor in the FAQ page regarding compatibility with 10.6

Macports officially only supports the current and previous major releases of Mac OS X. I would imagine that most people who have access to pre-release versions of Mac OS X would be bound by NDA to not discuss it.

comment:8 in reply to:  7 Changed 12 years ago by joshmoz@…

Replying to dluke@…:

most people who have access to pre-release versions of Mac OS X would be bound by NDA to not discuss it.

My understanding is that you may discuss technical matters directly related to developing your software in relevant forums. If this was not possible a lot of open source projects (like MacPorts and Mozilla) would be at a serious disadvantage.

MacPorts isn't obligated to provide support for anything they don't want to but I don't see a need to put down discussion of technical matters related to 10.6.

comment:9 Changed 12 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

comment:10 Changed 12 years ago by tobypeterson

Cc: eyekyu@… added

comment:11 Changed 12 years ago by dasnar@…

Cc: dasnar@… added

Cc Me!

comment:12 Changed 12 years ago by dasnar@…

Cc: dasnar@… removed

Cc Me!

comment:13 Changed 12 years ago by simon.bugzilla@…

Cc: simon.bugzilla@… added

Cc Me!

comment:14 Changed 12 years ago by mamoll (Mark Moll)

Cc: mmoll@… added

Cc Me!

comment:15 Changed 12 years ago by jmroot (Joshua Root)

Resolution: fixed
Status: newclosed

Fixed as much as it will likely ever be in r57388 (upstream doesn't intend to make any more changes to 2.5 apart from security fixes).

BTW, please don't let earlier comments put you off from reporting bugs. Your NDA is between you and Apple, and while we certainly wouldn't encourage you to violate it, most of us don't know what it actually says either. And in this particular case, the problem was the use of APIs that had already been removed in 64-bit Leopard, so it wasn't a Snow Leopard issue at all...

Note: See TracTickets for help on using tickets.