If a script can't detect running enviroment?

General system
#1

Trying to install nextdns directly using the install instructions on their wiki (instead of thru the AUR).

However I get this:

ERROR: Unsupported OS: Linux
ERROR: Unknown bin location for 
INFO: OS: 
INFO: GOARCH: amd64
INFO: GOOS: linux
INFO: NEXTDNS_BIN: 
INFO: LATEST_RELEASE: 1.32.0
ERROR: Cannot detect running environment.

And from what I can tell it’s because of the third line: The script cannot handle “Info: OS:” being empty. Where do I set that variable in Arch? Apparently this is an issue with using NextDNS in Manjaro too (according from my “googling”).

Edit: Ah. it might be as simple as the script not accepting Endeavour as a linux distribution. I will change

/etc/os-relase

to Arch Linux and see what happens.

#2

Solution:

Changing the row ID in /etc/os-release from endeavouros to arch, like so:

NAME="EndeavourOS"
PRETTY_NAME="EndeavourOS"
ID=arch
ID_LIKE=endeavouros
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://endeavouros.com"
DOCUMENTATION_URL="https://endeavouros.com/wiki/"
SUPPORT_URL="https://forum.endeavouros.com"
BUG_REPORT_URL="https://github.com/endeavouros-team"
LOGO=endeavouros

worked.

Now i can use

nextdns upgrade

to keep nextdns updated instead of trusting the maintainer in the AUR to do it.

1 Like
#3

Note that some future update (or re-install) of packages

  • filesystem
  • eos-hooks

may change /etc/os-release back to endeavouros.
Then you’d need to make the same modification again…

So you might want to ask the nextdns dev to add EndeavourOS in the list of supported systems.

1 Like
#4

Absolutely. At least there is only one line of text to change in the meantime.
Also, seeing how the newest AUR package is 1.12.1 and the newest package on github is 1.32.1 being able to do the direct upgrade seems worth it.

#5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.