Opened 12 years ago

Closed 12 years ago

Last modified 11 years ago

#16788 closed defect (fixed)

BUG: Error: Unable to open port: invalid command name "use_lzma"

Reported by: milosh@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 1.7.0
Keywords: Cc: jmroot (Joshua Root)
Port:

Description

I am trying to update texlive port but the new distfiles happen to be compressed using lzma. By chance, use_lzma exists in macports (at least in man portfile), but using it results in error telling that use_lzma is not a valid macports command

% port -d lint texlive_base
DEBUG: Found port in file:///home/manu/tmp/macports/dports//tex/texlive_base
DEBUG: Changing to port directory: /home/manu/tmp/macports/dports/tex/texlive_base
DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided
DEBUG: invalid command name "use_lzma"
    while executing
"use_lzma        yes"
    (file "Portfile" line 24)
    invoked from within
"source Portfile"
    invoked from within
"$workername eval source Portfile"
    (procedure "mportopen" line 46)
    invoked from within
"mportopen $porturl [array get options] [array get variations]"
Error: Unable to open port: invalid command name "use_lzma"

Change History (5)

comment:1 Changed 12 years ago by blb@…

use_lzma was recently added to trunk (r38960) so it shouldn't be used yet in Portfiles, since it wouldn't work with 1.6-based installs. Have a look at the texinfo port for one way of handling lzma for now.

comment:2 Changed 12 years ago by milosh@…

Yes, that's what I did. However, I'm surprised that a feature that is present in trunk fails to be understood in trunk.

comment:3 in reply to:  2 Changed 12 years ago by afb@…

Replying to milosh@…:

Yes, that's what I did. However, I'm surprised that a feature that is present in trunk fails to be understood in trunk.

trunk/dports doesn't use trunk/base, it uses branches/release_1_6/base. Too many trunks around, I suppose.

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

Cc: jmr@… added
Resolution: fixed
Status: newclosed

Fixed in r42865. Don't go using it until 1.7.0 is released, though! :-)

comment:5 Changed 11 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

Note: See TracTickets for help on using tickets.