[MacPorts] #48811: rev-upgrade failed: can't read "{os.platform}": no such variable (was: minicom @2.7 Error: rev-upgrade failed: can't read "{os.platform}": no such variable)
MacPorts
noreply at macports.org
Mon Sep 21 10:19:29 PDT 2015
#48811: rev-upgrade failed: can't read "{os.platform}": no such variable
-------------------------------+--------------------------
Reporter: bustamitenator@… | Owner: ryandesign@…
Type: defect | Status: reopened
Priority: Normal | Milestone:
Component: base | Version: 2.3.99
Resolution: | Keywords:
Port: |
-------------------------------+--------------------------
Changes (by ryandesign@…):
* version: 2.3.3 => 2.3.99
* component: ports => base
* port: minicom =>
Comment:
I think I've finally realized what the problem is. Some [comment:3 earlier
output] you posted says:
{{{
MacPorts base version 2.3.99 installed,
}}}
That means you're running a version of MacPorts trunk, not the released
version 2.3.3. And I think the particular problem you're experiencing with
`{os.platform}` not existing was introduced in r140015 on September 6 and
fixed in r140050 on September 7. You just got unlucky by building MacPorts
trunk during that time. So you should just need to update the Subversion
working copy of MacPorts base that you used to install MacPorts trunk
originally, and configure and build and install it again, like you did
originally.
After you do that, hopefully MacPorts will work properly, and you can then
sync properly, which will show you what ports are outdated, and then you
can upgrade the outdated ports, which will fix the minicom problem by
rebuilding it against ncurses 6.
If you're going to use MacPorts trunk instead of the released version, you
have to expect that things will be broken from time to time, and make sure
you keep your installation up to date.
--
Ticket URL: <https://trac.macports.org/ticket/48811#comment:12>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list