Error processing request

Parameters

Body

Error

Unknow state transition: LINE -> END

-code

1

-level

0

-errorstack

INNER {returnImm {Unknow state transition: LINE -> END} {}} CALL {my render_wikit {teacup install} {This [teacup] subcommand fetches and installs a [package] for you.

It is important to note that there is a syntactical distinction between
installing a package (aka an extension), and an application.

----
[LV] In a week or two, the following info should be merged below so that there isn't a distinction between the old way of doing things and the new. It makes sense, right now, to distinguish since it may be a bit until everyone runs the
===
teacup update-self
====

[AK]: Since build 284134 teacup is able to work out on its own what FOO is, package, application, or profile, as long as the name FOO is unambiguous. That means that in most cases the '-is TYPE' arguments in the examples below are not necessary. Only if FOO is ambiguous, for example because the archives contain both an application FOO and a package FOO is the option '-is' required, and teacup will ask the user for it. More concrete example:

----
 % teacup install FOO
 Resolving FOO ... Cannot resolve ambiguous reference.
        entity      name  version platform
        ----------- ----- ------- --------
        application FOO 2.5     tcl
        package     FOO 2.5     tcl
        ----------- ----- ------- --------
        2 entities found


        Aborting installation. Please add the option '-is ENTITYTYPE' to
        the command line to unambiguously specify which of the found
        entities you wish to install. You _cannot_ --force this.
----

For example:

======
$ teacup install sqlite3
======

is what you would type to install a package.

======
$ teacup install tkcon -is application
======

is what you would type to install an application like [tkcon].

'''SPECIAL NOTE'''

If you are wanting to use teacup to install [tcllib], it too takes the
special syntax:

======
$ teacup install tcllib -is profile
======

This is because tcllib is '''NOT''' a package - it is a collection of
packages.

If you are wanting to install the [batteries included] set of packages
that came with ActiveTcl 8.4 (and to some degree, earlier), then you would
use

======
$ teacup install ActiveState::ActiveTcl -is profile
======

Now, some people may find they need to run [teacup timeout] to lengthen
the amount of time teacup waits for completion. And others may need to look
into teacup's ''-proxy'' argument.

----
!!!!!!
%| [Category Repository] |%
!!!!!!} regexp2} CALL {my render {teacup install} {This [teacup] subcommand fetches and installs a [package] for you.

It is important to note that there is a syntactical distinction between
installing a package (aka an extension), and an application.

----
[LV] In a week or two, the following info should be merged below so that there isn't a distinction between the old way of doing things and the new. It makes sense, right now, to distinguish since it may be a bit until everyone runs the
===
teacup update-self
====

[AK]: Since build 284134 teacup is able to work out on its own what FOO is, package, application, or profile, as long as the name FOO is unambiguous. That means that in most cases the '-is TYPE' arguments in the examples below are not necessary. Only if FOO is ambiguous, for example because the archives contain both an application FOO and a package FOO is the option '-is' required, and teacup will ask the user for it. More concrete example:

----
 % teacup install FOO
 Resolving FOO ... Cannot resolve ambiguous reference.
        entity      name  version platform
        ----------- ----- ------- --------
        application FOO 2.5     tcl
        package     FOO 2.5     tcl
        ----------- ----- ------- --------
        2 entities found


        Aborting installation. Please add the option '-is ENTITYTYPE' to
        the command line to unambiguously specify which of the found
        entities you wish to install. You _cannot_ --force this.
----

For example:

======
$ teacup install sqlite3
======

is what you would type to install a package.

======
$ teacup install tkcon -is application
======

is what you would type to install an application like [tkcon].

'''SPECIAL NOTE'''

If you are wanting to use teacup to install [tcllib], it too takes the
special syntax:

======
$ teacup install tcllib -is profile
======

This is because tcllib is '''NOT''' a package - it is a collection of
packages.

If you are wanting to install the [batteries included] set of packages
that came with ActiveTcl 8.4 (and to some degree, earlier), then you would
use

======
$ teacup install ActiveState::ActiveTcl -is profile
======

Now, some people may find they need to run [teacup timeout] to lengthen
the amount of time teacup waits for completion. And others may need to look
into teacup's ''-proxy'' argument.

----
!!!!!!
%| [Category Repository] |%
!!!!!!}} CALL {my revision {teacup install}} CALL {::oo::Obj6556982 process revision/teacup+install} CALL {::oo::Obj6556980 process}

-errorcode

NONE

-errorinfo

Unknow state transition: LINE -> END
    while executing
"error $msg"
    (class "::Wiki" method "render_wikit" line 6)
    invoked from within
"my render_$default_markup $N $C $mkup_rendering_engine"
    (class "::Wiki" method "render" line 8)
    invoked from within
"my render $name $C"
    (class "::Wiki" method "revision" line 31)
    invoked from within
"my revision $page"
    (class "::Wiki" method "process" line 56)
    invoked from within
"$server process [string trim $uri /]"

-errorline

4