Skip to content

firmware cmd can get the system in an unexecdutable state #41

@ziopio

Description

@ziopio

Rare bug when working with the firmware command:

lucasucci@Lucas-M3-MacBook-Pro grisp_demo % rebar3 grisp firmware                  
===> Analyzing applications...
===> Compiling grisp_tools
===> Compiling textual
===> Compiling grid
===> Compiling rebar3_grisp
===> Analyzing applications...
===> Compiling grisp_tools
===> Compiling textual
===> Compiling grid
===> Compiling rebar3_grisp
===> Analyzing applications...
===> Compiling grisp_tools
===> Compiling textual
===> Compiling grid
===> Compiling rebar3_grisp
===> Verifying dependencies...
===> Analyzing applications...
===> Compiling grisp_connect
===> Compiling epmd
===> Compiling certifi
===> Analyzing applications...
===> Compiling grisp_demo
* Using existing bundle: _grisp/deploy/grisp2.grisp_demo.1.2.0.tar.gz
* Preparing and validating...
* Creating disk image...
* Creating disk partition table...
* Formatting system partitions...
* Deploying release bundle...
===> sh(tar -C /Volumes/SYS 1 -xzf /Users/lucasucci/Desktop/grisp/grisp_demo/_grisp/deploy/grisp2.grisp_demo.1.2.0.tar.gz)
failed with return code 1 and the following output:
tar: Must specify one of -c, -r, -t, -u, -x

Analisys by Codex:

The command that was run was:
tar -C /Volumes/SYS 1 -xzf /path/to/bundle.tar.gz
So the shell was passing two arguments after -C: /Volumes/SYS and 1. That makes tar see an invalid usage (the 1 is not a valid tar option), so it says “Must specify one of -c, -r, -t, -u, -x”.
That only happens if the mount point actually contains a space.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions