Can’t install Hoobs on debian #1549
Comments
hermsdad
added
bug
|
You may have to install the components separately After it installs run this The HOOBS bundle just runs this automatically. If all else fails we can get more logs for troubleshooting. |
|
Thanks. I’ll try this tomorrow.
… On Sep 29, 2021, at 11:49 PM, Michael Kellsy ***@***.***> wrote:
You may have to install the components separately
sudo apt update
sudo apt install -y nodejs yarn
sudo apt install -y helm hoobs-cli hoobsd hoobs-gui
After it installs run this
sudo hbs install
The HOOBS bundle just runs this automatically. If all else fails we can get more logs for troubleshooting.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
I tried this. I had to build node 14.7.2 because the sudo apt install of
node would only install node 10. I also manually installed NPM. Not sure if
I need that still but I did it anyway.
Then I tried to install hoobs. and got the following:
***@***.***:/ $ sudo apt install -y helm hoobs-cli hoobsd hoobs-gui
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package helm
E: Unable to locate package hoobs-cli
E: Unable to locate package hoobsd
E: Unable to locate package hoobs-gui
***@***.***:/ $
…On Wed, Sep 29, 2021 at 11:49 PM Michael Kellsy ***@***.***> wrote:
You may have to install the components separately
sudo apt update
sudo apt install -y nodejs yarn
sudo apt install -y helm hoobs-cli hoobsd hoobs-gui
After it installs run this
sudo hbs install
The HOOBS bundle just runs this automatically. If all else fails we can
get more logs for troubleshooting.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1549 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AS2VZLQP27YIH4D2QFZXMA3UEPM3XANCNFSM5E66EOBQ>
.
|
|
Run this and post. Your architecture might not be supported. |
|
X86-64
… On Sep 30, 2021, at 11:16 AM, Michael Kellsy ***@***.***> wrote:
Run this and post. Your architecture might not be supported.
uname -m
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
I am working on version 4.1, which is close to release. It properly supports more architectures including amd63 (aka x86_64). You can try this version by moving to the "bleeding" branch. This branch doesn't have the bundle in it. So to install run this. Once that finishes you have to install the service. It will ask you to select a port. 80 is the default, but you can change it if you need to. If you want to have a web based terminal too. Run this. |
|
Just a couple of quick questions.
First I install Nodejs 14.17.2
Do I do this at root, at pi, or should I creat user hoobs and install their?
Then I install NPM.
When I install the bleeding branch should I do that is root user, pi user, or create a hoobs user and do it there?
I’ll try this later when I have time to wipe clean the machine again and reinstall a fresh copy of Debian and update Debian before I start.
… On Sep 30, 2021, at 4:54 PM, Michael Kellsy ***@***.***> wrote:
I am working on version 4.1, which is close to release. It properly supports more architectures including amd63 (aka x86_64).
You can try this version by moving to the "bleeding" branch.
wget -qO- https://dl.hoobs.org/bleeding | sudo -E bash -
This branch doesn't have the bundle in it. So to install run this.
sudo apt install -y hoobs-cli hoobsd hoobs-gui
Once that finishes you have to install the service.
sudo hbs install
It will ask you to select a port. 80 is the default, but you can change it if you need to.
If you want to have a web based terminal too. Run this.
sudo apt install -y helm
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
I installed node as root user 14.17.2 first (I do a build from a tar ball.
I'll try it again without doing node first and see if that works. If it
doesn't work I'll try installing node as pi user.
For now here is the result I get when installing as pi user:
***@***.***:~ $ wget -qO- https://dl.hoobs.org/bleeding | sudo -E bash -
Hit:1 http://ftp.debian.org/debian buster InRelease
Hit:2 http://ftp.debian.org/debian buster-updates InRelease
Get:3 http://security.debian.org buster/updates InRelease [65.4 kB]
Hit:4 http://archive.raspberrypi.org/debian buster InRelease
Fetched 65.4 kB in 1s (122 kB/s)
Reading package lists... Done
gpg: WARNING: unsafe ownership on homedir '/home/pi/.gnupg'
gpg: WARNING: unsafe ownership on homedir '/home/pi/.gnupg'
gpg: WARNING: unsafe ownership on homedir '/home/pi/.gnupg'
deb [signed-by=/usr/share/keyrings/nodesource.gpg]
https://deb.nodesource.com/node_14.x buster main
deb-src [signed-by=/usr/share/keyrings/nodesource.gpg]
https://deb.nodesource.com/node_14.x buster main
deb [signed-by=/usr/share/keyrings/yarnkey.gpg]
https://dl.yarnpkg.com/debian/ stable main
deb [signed-by=/usr/share/keyrings/hoobs.gpg] https://dl.hoobs.org/debian/
bleeding main
Hit:1 http://ftp.debian.org/debian buster InRelease
Hit:2 http://ftp.debian.org/debian buster-updates InRelease
Hit:3 http://security.debian.org buster/updates InRelease
Get:4 https://dl.hoobs.org/debian bleeding InRelease [3,034 B]
Get:5 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB]
Hit:6 http://archive.raspberrypi.org/debian buster InRelease
Get:7 https://deb.nodesource.com/node_14.x buster InRelease [4,584 B]
Get:8 https://dl.hoobs.org/debian bleeding/main amd64 Packages [1,027 B]
Get:9 https://dl.yarnpkg.com/debian stable/main i386 Packages [10.4 kB]
Get:10 https://dl.yarnpkg.com/debian stable/main amd64 Packages [10.4 kB]
Get:11 https://dl.yarnpkg.com/debian stable/main all Packages [10.4 kB]
Get:12 https://deb.nodesource.com/node_14.x buster/main amd64 Packages [770
B]
Fetched 57.7 kB in 1s (73.5 kB/s)
Reading package lists... Done
N: Skipping acquire of configured file 'main/binary-i386/Packages' as
repository 'https://dl.hoobs.org/debian bleeding InRelease' doesn't support
architecture 'i386'
***@***.***:~ $ sudo apt install -y hoobs-cli hoobsd hoobs-gui
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
hoobs-cli:amd64 : Depends: nodejs:amd64 (>= 14.15.0)
Depends: python3:amd64 but it is not going to be
installed
Depends: make:amd64
Depends: gcc:amd64 but it is not going to be installed
Depends: g++:amd64 but it is not going to be installed
hoobs-gui : Depends: hoobsd (>= 4.0.0) but it is not installable
Depends: helm (>= 1.2.2) but it is not installable
hoobsd:amd64 : Depends: nodejs:amd64 (>= 14.15.0)
Depends: lsof:amd64 but it is not going to be installed
Depends: python3:amd64 but it is not going to be installed
Depends: make:amd64
Depends: gcc:amd64 but it is not going to be installed
Depends: g++:amd64 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
***@***.***:~ $
…On Thu, Sep 30, 2021 at 4:54 PM Michael Kellsy ***@***.***> wrote:
I am working on version 4.1, which is close to release. It properly
supports more architectures including amd63 (aka x86_64).
You can try this version by moving to the "bleeding" branch.
wget -qO- https://dl.hoobs.org/bleeding | sudo -E bash -
This branch doesn't have the bundle in it. So to install run this.
sudo apt install -y hoobs-cli hoobsd hoobs-gui
Once that finishes you have to install the service.
sudo hbs install
It will ask you to select a port. 80 is the default, but you can change it
if you need to.
If you want to have a web based terminal too. Run this.
sudo apt install -y helm
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1549 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AS2VZLURY35ZJ4MMPTBGQYTUETFBHANCNFSM5E66EOBQ>
.
|
|
I may be closer. I installed user hoobs as sudo user and changed my sudoer file to add hoobs.
Then I used snap to install node as user hoobs and it installed 14.17.6. Instead of v10 which is what debian wants to default to for some reason.
However it looks like the latest release of debian has some other issues. It is calling for explicit acceptance when running sudo apt-get. Which it appears your script doesn’t allow me to do the acceptance. I am assuming your script is trying to run sud apt-get update. It appears if you change this to sudo-apt-get —allow-release info-change update this may resolve the problem.
I found this:
https://stackoverflow.com/questions/68802802/repository-http-security-debian-org-debian-security-buster-updates-inrelease
***@***.***:~ $ wget -qO- https://dl.hoobs.org/bleeding | sudo -E bash -
Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
Get:2 http://ftp.debian.org/debian buster InRelease [122 kB]
Get:3 http://ftp.debian.org/debian buster-updates InRelease [51.9 kB]
Get:4 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB]
Get:5 http://archive.raspberrypi.org/debian buster/main amd64 Packages [200 kB]
Get:6 http://archive.raspberrypi.org/debian buster/main i386 Packages [200 kB]
Reading package lists... Done
E: Repository 'http://security.debian.org buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
N: Repository 'http://ftp.debian.org/debian buster InRelease' changed its 'Version' value from '10.7' to '10.10'
E: Repository 'http://ftp.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
E: Repository 'http://ftp.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
error executing command
… On Sep 30, 2021, at 8:27 PM, Jim Melo ***@***.***> wrote:
I installed node as root user 14.17.2 first (I do a build from a tar ball. I'll try it again without doing node first and see if that works. If it doesn't work I'll try installing node as pi user.
For now here is the result I get when installing as pi user:
***@***.***:~ $ wget -qO- https://dl.hoobs.org/bleeding | sudo -E bash -
Hit:1 http://ftp.debian.org/debian buster InRelease
Hit:2 http://ftp.debian.org/debian buster-updates InRelease
Get:3 http://security.debian.org buster/updates InRelease [65.4 kB]
Hit:4 http://archive.raspberrypi.org/debian buster InRelease
Fetched 65.4 kB in 1s (122 kB/s)
Reading package lists... Done
gpg: WARNING: unsafe ownership on homedir '/home/pi/.gnupg'
gpg: WARNING: unsafe ownership on homedir '/home/pi/.gnupg'
gpg: WARNING: unsafe ownership on homedir '/home/pi/.gnupg'
deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x buster main
deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x buster main
deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian/ stable main
deb [signed-by=/usr/share/keyrings/hoobs.gpg] https://dl.hoobs.org/debian/ bleeding main
Hit:1 http://ftp.debian.org/debian buster InRelease
Hit:2 http://ftp.debian.org/debian buster-updates InRelease
Hit:3 http://security.debian.org buster/updates InRelease
Get:4 https://dl.hoobs.org/debian bleeding InRelease [3,034 B]
Get:5 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB]
Hit:6 http://archive.raspberrypi.org/debian buster InRelease
Get:7 https://deb.nodesource.com/node_14.x buster InRelease [4,584 B]
Get:8 https://dl.hoobs.org/debian bleeding/main amd64 Packages [1,027 B]
Get:9 https://dl.yarnpkg.com/debian stable/main i386 Packages [10.4 kB]
Get:10 https://dl.yarnpkg.com/debian stable/main amd64 Packages [10.4 kB]
Get:11 https://dl.yarnpkg.com/debian stable/main all Packages [10.4 kB]
Get:12 https://deb.nodesource.com/node_14.x buster/main amd64 Packages [770 B]
Fetched 57.7 kB in 1s (73.5 kB/s)
Reading package lists... Done
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://dl.hoobs.org/debian bleeding InRelease' doesn't support architecture 'i386'
***@***.***:~ $ sudo apt install -y hoobs-cli hoobsd hoobs-gui
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
hoobs-cli:amd64 : Depends: nodejs:amd64 (>= 14.15.0)
Depends: python3:amd64 but it is not going to be installed
Depends: make:amd64
Depends: gcc:amd64 but it is not going to be installed
Depends: g++:amd64 but it is not going to be installed
hoobs-gui : Depends: hoobsd (>= 4.0.0) but it is not installable
Depends: helm (>= 1.2.2) but it is not installable
hoobsd:amd64 : Depends: nodejs:amd64 (>= 14.15.0)
Depends: lsof:amd64 but it is not going to be installed
Depends: python3:amd64 but it is not going to be installed
Depends: make:amd64
Depends: gcc:amd64 but it is not going to be installed
Depends: g++:amd64 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
***@***.***:~ $
On Thu, Sep 30, 2021 at 4:54 PM Michael Kellsy ***@***.***> wrote:
> I am working on version 4.1, which is close to release. It properly supports more architectures including amd63 (aka x86_64).
>
> You can try this version by moving to the "bleeding" branch.
>
> wget -qO- https://dl.hoobs.org/bleeding | sudo -E bash -
> This branch doesn't have the bundle in it. So to install run this.
>
> sudo apt install -y hoobs-cli hoobsd hoobs-gui
> Once that finishes you have to install the service.
>
> sudo hbs install
> It will ask you to select a port. 80 is the default, but you can change it if you need to.
>
> If you want to have a web based terminal too. Run this.
>
> sudo apt install -y helm
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
Still trying to make this work. I was able to get past the acceptance issue
by running
sudo-apt-get —allow-release info-change update
as root user. then when I went back to hoobs user I ran:
wget -qO- https://dl.hoobs.org/bleeding | sudo -E bash -
and this time it ran it no problem. But now I am back to this problem:
***@***.***:~ $ sudo apt install -y hoobs-cli hoobsd hoobs-gui
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
hoobs-cli:amd64 : Depends: nodejs:amd64 (>= 14.15.0)
Depends: python3:amd64 but it is not going to be
installed
Depends: make:amd64
Depends: gcc:amd64 but it is not going to be installed
Depends: g++:amd64 but it is not going to be installed
hoobs-gui : Depends: hoobsd (>= 4.0.0) but it is not installable
Depends: helm (>= 1.2.2) but it is not installable
hoobsd:amd64 : Depends: nodejs:amd64 (>= 14.15.0)
Depends: lsof:amd64 but it is not going to be installed
Depends: python3:amd64 but it is not going to be installed
Depends: make:amd64
Depends: gcc:amd64 but it is not going to be installed
Depends: g++:amd64 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Maybe node is installed in the wrong folder and everything fails from
there? I know buster already has python3 and make. not sure of gcc or g++
Jim
…On Wed, Sep 29, 2021 at 11:49 PM Michael Kellsy ***@***.***> wrote:
You may have to install the components separately
sudo apt update
sudo apt install -y nodejs yarn
sudo apt install -y helm hoobs-cli hoobsd hoobs-gui
After it installs run this
sudo hbs install
The HOOBS bundle just runs this automatically. If all else fails we can
get more logs for troubleshooting.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1549 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AS2VZLQP27YIH4D2QFZXMA3UEPM3XANCNFSM5E66EOBQ>
.
|
|
This is wired, your Debian install is not installing dependencies automatically. You might need to update the OS.
After this reboot. You should be on Debian 11. I find this a little wired, I actually develop HOOBS on Debian. It is the most tested platform. |
|
I got it working! I was trying to stay in the raspberry pi universe but it
appears that Raspberry doesn't want you to upgrade from buster to bullseye
and they currently aren't supporting bullseye yet. So I just went with a
straight debian 11 install. Took a while but I got it installed and then
installed node as root.
I then ran your bleeding install and the hoobs terminal is running. I did
get the following errors during install so not sure how this will affect
the terminal. I'll start playing around with it and adding things. First I
need to add zigbee2mqtt and add my conbee and also my zwave adapter.
Here's what I got at install in case you are curious:
***@***.***:~$ sudo apt install -y hoobs-cli hoobsd hoobs-gui
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer
required:
gyp libc-ares2 libjs-highlight.js libjs-inherits libjs-is-typedarray
libjs-psl libjs-typedarray-to-buffer libssl-dev libuv1-dev node-abbrev
node-agent-base node-ajv node-ansi node-ansi-regex node-ansi-styles
node-ansistyles node-aproba node-archy node-are-we-there-yet node-asap
node-asn1 node-assert-plus node-asynckit node-aws-sign2 node-aws4
node-balanced-match node-bcrypt-pbkdf node-brace-expansion node-builtins
node-cacache node-caseless node-chalk node-chownr node-clone
node-color-convert node-color-name node-colors node-columnify
node-combined-stream node-concat-map node-console-control-strings
node-copy-concurrently node-core-util-is node-dashdash node-debug
node-defaults node-delayed-stream node-delegates node-depd node-ecc-jsbn
node-encoding node-err-code node-escape-string-regexp node-extend
node-extsprintf node-fast-deep-equal node-forever-agent node-form-data
node-fs-write-stream-atomic node-fs.realpath node-function-bind node-gauge
node-getpass node-glob node-graceful-fs node-har-schema node-har-validator
node-has-flag node-has-unicode node-hosted-git-info node-http-signature
node-https-proxy-agent node-iconv-lite node-iferr node-imurmurhash
node-indent-string node-inflight node-inherits node-ini node-ip
node-ip-regex node-is-typedarray node-isarray node-isexe node-isstream
node-jsbn node-json-parse-better-errors node-json-schema
node-json-schema-traverse node-json-stable-stringify
node-json-stringify-safe node-jsonify node-jsonparse node-jsonstream
node-jsprim node-leven node-lockfile node-lru-cache node-mime
node-mime-types node-minimatch node-mkdirp node-move-concurrently node-ms
node-mute-stream node-nopt node-normalize-package-data node-npm-bundled
node-npm-package-arg node-npmlog node-number-is-nan node-oauth-sign
node-object-assign node-once node-opener node-osenv node-p-map
node-path-is-absolute node-performance-now node-process-nextick-args
node-promise-inflight node-promise-retry node-promzard node-psl node-puka
node-punycode node-qs node-read node-read-package-json
node-readable-stream
node-request node-resolve node-resolve-from node-retry node-rimraf
node-run-queue node-safe-buffer node-semver node-set-blocking
node-signal-exit node-slash node-spdx-correct node-spdx-exceptions
node-spdx-expression-parse node-spdx-license-ids node-sshpk node-ssri
node-string-decoder node-string-width node-strip-ansi node-supports-color
node-tar node-text-table node-through node-tough-cookie node-tunnel-agent
node-tweetnacl node-typedarray-to-buffer node-unique-filename
node-universalify node-uri-js node-util-deprecate node-uuid
node-validate-npm-package-license node-validate-npm-package-name
node-verror
node-wcwidth.js node-which node-wide-align node-wrappy
node-write-file-atomic node-yallist nodejs-doc
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
helm libpam0g-dev nodejs
The following packages will be REMOVED:
libnode-dev libnode72 node-gyp npm
The following NEW packages will be installed:
helm hoobs-cli hoobs-gui hoobsd libpam0g-dev
The following packages will be upgraded:
nodejs
1 upgraded, 5 newly installed, 4 to remove and 0 not upgraded.
Need to get 49.0 MB of archives.
After this operation, 80.0 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 libpam0g-dev amd64
1.4.0-9 [190 kB]
Get:2 https://dl.hoobs.org/debian bleeding/main amd64 helm amd64 2.1.1
[1,837 kB]
Get:3 https://dl.hoobs.org/debian bleeding/main amd64 hoobs-cli amd64 4.1.1
[3,686 kB]
Get:4 https://dl.hoobs.org/debian bleeding/main amd64 hoobsd amd64 4.1.1
[4,985 kB]
Get:5 https://dl.hoobs.org/debian bleeding/main amd64 hoobs-gui all 4.1.1
[13.2 MB]
Get:6 https://deb.nodesource.com/node_14.x bullseye/main amd64 nodejs amd64
14.18.0-deb-1nodesource1 [25.1 MB]
Fetched 49.0 MB in 1s (32.8 MB/s)
apt-listchanges: Reading changelogs...
(Reading database ... 146190 files and directories currently installed.)
Removing npm (7.5.2+ds-2) ...
Removing node-gyp (7.1.2-4) ...
Removing libnode-dev (12.22.5~dfsg-2~11u1) ...
dpkg: libnode72:amd64: dependency problems, but removing anyway as you
requested
:
nodejs depends on libnode72 (= 12.22.5~dfsg-2~11u1).
Removing libnode72:amd64 (12.22.5~dfsg-2~11u1) ...
(Reading database ... 145225 files and directories currently installed.)
Preparing to unpack .../0-nodejs_14.18.0-deb-1nodesource1_amd64.deb ...
Unpacking nodejs (14.18.0-deb-1nodesource1) over (12.22.5~dfsg-2~11u1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-DfXgAy/0-nodejs_14.18.0-deb
-1nodesource1_amd64.deb (--unpack):
trying to overwrite '/usr/share/doc/nodejs/api/process.html', which is
also in
package nodejs-doc 12.22.5~dfsg-2~11u1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Selecting previously unselected package libpam0g-dev:amd64.
Preparing to unpack .../1-libpam0g-dev_1.4.0-9_amd64.deb ...
Unpacking libpam0g-dev:amd64 (1.4.0-9) ...
Selecting previously unselected package helm.
Preparing to unpack .../2-helm_2.1.1_amd64.deb ...
Unpacking helm (2.1.1) ...
Selecting previously unselected package hoobs-cli.
Preparing to unpack .../3-hoobs-cli_4.1.1_amd64.deb ...
Unpacking hoobs-cli (4.1.1) ...
Selecting previously unselected package hoobsd.
Preparing to unpack .../4-hoobsd_4.1.1_amd64.deb ...
Unpacking hoobsd (4.1.1) ...
Selecting previously unselected package hoobs-gui.
Preparing to unpack .../5-hoobs-gui_4.1.1_all.deb ...
Unpacking hoobs-gui (4.1.1) ...
Errors were encountered while processing:
/tmp/apt-dpkg-install-DfXgAy/0-nodejs_14.18.0-deb-1nodesource1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
***@***.***:~$ sudo hbs install
? enter the port for the hub 8080
Created symlink /etc/systemd/system/multi-user.target.wants/hoobsd.service
→ /etc/systemd/system/hoobsd.service.
id | type | display | port | pin | username | advertiser
-------------------------------------------------------------------------
hub | hub | Hub | 8080 | 031-45-154 | xx:xx:xx:xx |
***@***.***:~$ sudo apt install -y helm
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
helm is already the newest version (2.1.1).
helm set to manually installed.
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
helm : Depends: nodejs (>= 14.15.0) but 12.22.5~dfsg-2~11u1 is to be
installed
hoobs-cli : Depends: nodejs (>= 14.15.0) but 12.22.5~dfsg-2~11u1 is to be
installed
hoobsd : Depends: nodejs (>= 14.15.0) but 12.22.5~dfsg-2~11u1 is to be
installed
nodejs : Depends: libnode72 (= 12.22.5~dfsg-2~11u1) but it is not going to
be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or
specify a solution).
***@***.***:~$ apt --fix-broken install
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13:
Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend),
are you root?
…On Fri, Oct 1, 2021 at 8:58 AM Michael Kellsy ***@***.***> wrote:
This is wired, your Debian install is not installing dependencies
automatically.
What version of Debian? How did you install it?
You might need to update the OS.
1. Edit the /etc/apt/sources.list file and replace all instalces of
*buster* with *bullseye*
sudo nano /etc/apt/sources.list
2. Then run
sudo apt update
3. Then run
sudo apt upgrade
4. Then run
sudo apt full-upgrade
After this reboot. You should be on Debian 11.
I find this a little wired, I actually develop HOOBS on Debian. It is the
most tested platform.
I will try to deploy it on Debian 11 this weekend and see if the .deb
files are doing what they are supposed to.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1549 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AS2VZLSF6B6UP3VR5RQEFE3UEWV6LANCNFSM5E66EOBQ>
.
|
|
Not related please open another task or email info@hoobs.com |
|
I adjusted the install scripts to handle the "oldstable" thing. Run it again It will fix the NodeSource repo. This will upgrade everything. Then reboot to be safe. |
|
Not sure if that was a type. Did you mean bleeding? Or have you now released the amd64 version to the world?
… On Oct 5, 2021, at 9:57 AM, Michael Kellsy ***@***.***> wrote:
I adjusted the install scripts to handle the "oldstable" thing.
Run it again
wget -qO- https://dl.hoobs.org/stable | sudo -E bash -
It will fix the NodeSource repo.
Then run this.
sudo apt install -y hoobsd hoobs-cli hoobs-gui
This will upgrade everything.
Then reboot to be safe.
sudo shutdown -r now
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1549 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AS2VZLSDX7LBTU5FYO3EZDDUFL75JANCNFSM5E66EOBQ>.
|
|
Use “edge” instead it’s more stable. |
|
Just to be clear, I should use:
wget -qO- https://dl/hoobs.org/edge | sudo -E bash -
Jim
… On Oct 5, 2021, at 1:06 PM, Michael Kellsy ***@***.***> wrote:
Use “edge” instead it’s more stable.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
Yep |
|
I just ran your command on my device. It's wrong. Use this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I just wiped a Mac mini clean and installed the Debian/raspberry pi software. Updated Debian after install.
I then ran the instructions for installing hoobs at https://support.hoobs.org/docs/60e9f2ecdea381a881af7237
wget -qO- https://dl.hoobs.org/stable | sudo -E bash -
sudo apt install hoobs
I assume this is to install hoobs 4 because when I previously installed hoobs 3 it had a different URL. I did it this way because I could never get hoobs 3 to upgrade.
Version
4?
Did you upgrade
Please let us know if you upgraded from a previous version.
Pervious version
None
Did you orginally upgrade to HOOBS 3 from HOOBS 2.1.1?
Did you perform an upgrade from HOOBS 2.1.1? Some things are different.
What device are you using?
Please let us know the device you are running HOOBS on.
If this is a custom install, what's your operating system?
Latest version of Debian/raspberry pi on a Mac mini that’s been wiped clean.
List your plugins
Please include a list of the plugins you are using. We need to be able to find it on NPM. If the plugin is no published, please include a link to the repository.
None yet
Post your config
This can be found in the interface, Configuration -> Advanced or you can get it via SSH
cat ~/.hoobs/etc/config.jsonDidn’t get this far
POST CONFIG HERE
POST LOG HERE
The text was updated successfully, but these errors were encountered: