Skip to content

cross deb fails. #210

@vi

Description

@vi
$ cross  deb 
error: no such subcommand: `deb`

	Did you mean `doc`?

$ cross  --version
cross 0.1.14
cargo 1.29.0-nightly (6a7672ef5 2018-08-14)

Although cross deb shows the similar message as cross deb1234, it takes longer to run, so maybe it tries... Do I need to somehow install cargo-deb inside the container?

How do I actually use cross deb? In any case the error message if cargo deb fails inside container should be customized by cross somehow.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions