Open NZSmartie opened 6 years ago
Ha. a fix (after the initial install fails) is to run the command
$ git -C repos/apache-mynewt-core/ config core.fileMode false
Then newt install
completes successfully
$ newt install
apache-mynewt-core successfully installed version 1.3.0-none
Perhaps a PR for a documentation update would be good?
Thanks for the report, @NZSmartie! I'm inclined to change newt such that it always specifies the core.fileMode false
option. Can you think of a reason why this would be a bad idea?
scripts (specifically *.sh
) files may not have the executable flag when the repo is cloned. so maybe an addtional step of find -name \*.sh -type f -exec chmod a+x {} \;
would be needed after cloning?
I just had the same problem trying to install my first project, also in Windows WSL. The git filemode fix above didn't work for me however, after that and retrying install I got a long list of errors like
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/transport/uart config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_TRANS_UART_SYSINIT_STAGE)": invalid syntax; ignoring package.
I was trying to install into one of the mounted windows folder, eg /mnt/c/Users/...
Starting again in one of the wsl linux native folders like ~/
fixed the problem for me.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/transport/uart config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_TRANS_UART_SYSINIT_STAGE)": invalid syntax; ignoring package.
I'm getting the same issue (parsing pkg) on debian, I'm running it on a wls linux native located at ~/my_dir/ , do you have clue why there's an error?
I've just installed newt following the Getting Started guide for Linux . My OS is Ubuntu 16.04 LTS on Windows 10 through WSL.
The error message isn't exactly detailed so I rm'd
newt-test
and created a new project and tried to install again with the verbose (-v
) option.Not quite sure what's causing this, i've enabled debug logging (
-l "DEBUG"
) and the issue stems from git while it's doing a stash.Since
~/Documents
is actually a symbolic link to the Windows filesystem where all permissions are forced to 0777, my guess is that git stash is unhappy with the file's permissions not matching the git working tree. So I attempted runningnewt install
again on a new project under the Linux filesystem and it succeeded.So my issue is, are we able to tell git to ignore the file permissions when stashing/checking out a branch?