Fwd: invalid command name on some downloads

Ryan Schmidt ryandesign at macports.org
Thu Dec 13 14:18:39 PST 2007


Forwarding this message to the list.

Begin forwarded message:

> From: Barry McInnes <Barry.J.Mcinnes at noaa.gov>
> Date: December 13, 2007 10:03:10 CST
> To: Ryan Schmidt <ryandesign at macports.org>
> Subject: Re: invalid command name on some downloads
>
>
> On 12/12/07 7:50 PM, Ryan Schmidt wrote:
>> On Dec 12, 2007, at 17:05, Ryan Schmidt wrote:
>>
>>> On Dec 12, 2007, at 13:51, Barry McInnes wrote:
>>>
>>>> We have a clean install of 10.5 and update to 10.5.1.
>>>> macport version
>>>> [mac27:~/sun/info] bmcinnes% port --version
>>>> MacPorts 1.520
>>>>
>>>> Some installs work, others don't
>>>>
>>>> [mac27:~/sun/info] bmcinnes% sudo port uninstall gimp
>>>> Error: port uninstall failed: Registry error: gimp not  
>>>> registered as
>>>> installed.
>>>
>>> That looks normal to me. Or did you believe you had the gimp port
>>> installed? What is the output of "port installed"?
>>>
>>>> [mac27:~/sun/info] bmcinnes% sudo port install gimp2
>>>> Error: Unable to execute port: invalid command name
>>>> "destroot.violate_mtree"
>>>> [mac27:~/sun/info] bmcinnes% sudo port install gnuplot
>>>> Password:
>>>> Error: Unable to execute port: invalid command name
>>>> "destroot.violate_mtree"
>>>> [mac27:~/sun/info] bmcinnes%
>>>
>>> destroot.violate_mtree was added in MacPorts 1.5.1 and improved
>>> quickly in 1.5.2.
>>>
>>> You installed 1.5.0 from the disk image for Leopard, I presume? Did
>>> you then "sudo port selfupdate" to upgrade to 1.5.2? I mean, "port"
>>> says you're running 1.520, a.k.a. 1.5.2, but its behavior matches  
>>> that
>>> of 1.5.0. So this is odd.
>>>
>>>> I have reinstalled Xcode 3.0, done port sync, looked through  
>>>> archives,
>>>> but there seems to be no total solution ?
>>>
>>> The total solution for 'invalid command name  
>>> "destroot.violate_mtree"'
>>> should be to update to MacPorts 1.5.2 by using "sudo port  
>>> selfupdate".
>>
>> I've just read in our new guide that the installer runs  
>> "selfupdate" for
>> you, which explains why you would already have 1.5.2 right after
>> installing 1.5.0 from the disk image. Still, please try running
>> "selfupdate" yourself to see if that changes anything.
>>
>>
>
> I removed existing install, and did a change location to the  
> partition.
> I still have a sym link from /opt/local, and I needed to create
> /Volumes/partition/opt/local before it would install.
> Anyway it installed, and it did install 1.52, by default which is
> different, as previously I had to run selfupdate, but the first  
> test failed
>
> [mac27:/opt] root# cd local
> [mac27:/opt/local] root# ls -l
> total 8
> drwxrwxr-x  2 root  80  238 Dec 13 08:55 bin
> drwxrwxr-x  3 root  80  102 Oct 27 15:56 etc
> drwxrwxr-x  2 root  80  102 Oct 27 15:56 include
> drwxrwxr-x  2 root  80  102 Oct 27 15:56 lib
> drwxrwxr-x  2 root  80  102 Oct 27 15:56 libexec
> lrwxr-xr-x  1 root  80    9 Dec 13 08:55 man -> share/man
> drwxrwxr-x  2 root  80  102 Oct 27 15:56 sbin
> drwxrwxr-x  6 root  80  204 Oct 27 15:56 share
> drwxr-xr-x  3 root  80  102 Dec 13 08:55 var
> [mac27:/opt/local] root# port selfupdate
> MacPorts base version 1.520 installed
> Downloaded MacPorts base version 1.520
> The MacPorts installation is not outdated and so was not updated
> selfupdate done!
> [mac27:/opt/local] root# port install pstoedit
> Error: Unable to execute port: invalid command name  
> "destroot.violate_mtree"
> [mac27:/opt/local] root#


More information about the macports-users mailing list