(2023-10-10, 01:32 PM)jim321 Wrote: "And please, aslo note in the istalling guide that changing the username in PI imager options , leaves SignalK unusable as it's desgined to work in folder Home/pi"
linux has user's and permissions some functions require admin rights .
its set up to use default raspian install to keep it EZ that includes user's
Thanks Jim.
No idea, I changed username through PI Imager options when installing the OP OS image and when applying a different username , in the first start already SK didn't work. After letting that option blank repeating the installation, and leaving user as "PI" , it worked as it should as remeber that we're talking of fresh installations.
I'm quite ignorant to Linux.
I just wanted to leave trace of this annoyance which can turn people mad if unaware of it. Not a big issue, but for Linux newbies, , any minor difficulty becomes a drama.
Regards!
(2023-10-07, 06:03 PM)aitonos Wrote: Hi!
I have done a fresh install of OP3 64, then did the hack for my Moitessier hat 2, and when wanted to install Pypilot through OP settings/App openplotter, after getting candidates and press install Pypilot ( regular and graphical procedure) , I get this long error :
"Leyendo lista de paquetes...
Creando árbol de dependencias...
Leyendo la información de estado...
No se pudieron instalar algunos paquetes. Esto puede significar que
usted pidió una situación imposible o, si está usando la distribución
inestable, que algunos paquetes necesarios aún no se han creado o se
han sacado de «Incoming».
La siguiente información puede ayudar a resolver la situación:
Los siguientes paquetes tienen dependencias incumplidas:
openplotter-pypilot : Depende: swig pero no es instalable
E: No se pudieron corregir los problemas, usted ha retenido paquetes rotos.
sudo: pypilotPostInstall: command not found
"
I also tried the developer instructions under Read the docs, and get similar error in terminal;
"
pi@openplotter:~ $ git clone https://github.com/openplotter/openplotter-pypilot
Clonando en 'openplotter-pypilot'...
remote: Enumerating objects: 1092, done.
remote: Counting objects: 100% (427/427), done.
remote: Compressing objects: 100% (214/214), done.
remote: Total 1092 (delta 206), reused 358 (delta 142), pack-reused 665
Recibiendo objetos: 100% (1092/1092), 377.61 KiB | 2.06 MiB/s, listo.
Resolviendo deltas: 100% (566/566), listo.
pi@openplotter:~ $ cd openplotter-pypilot
dpkg-buildpackage -b
dpkg-buildpackage: información: paquete fuente openplotter-pypilot
dpkg-buildpackage: información: versión de las fuentes 3.2.13-stable
dpkg-buildpackage: información: distribución de las fuentes bullseye
dpkg-buildpackage: información: fuentes modificadas por Sailoog <info@sailoog.com>
dpkg-buildpackage: información: arquitectura del sistema arm64
dpkg-source --before-build .
dpkg-checkbuilddeps: fallo: Unmet build dependencies: debhelper (>= 9) dh-python python3-all
dpkg-buildpackage: aviso: Las dependencias y conflictos de construcción no están satisfechas, interrumpiendo
dpkg-buildpackage: aviso: (Use la opción «-d» para anularlo.)
pi@openplotter:~/openplotter-pypilot $ cd ..
sudo dpkg -i openplotter-pypilot_x.x.x-xxx_all.deb
dpkg: error: no se puede acceder al archivo 'openplotter-pypilot_x.x.x-xxx_all.deb': No existe el fichero o el directorio
pi@openplotter:~ $
"
seems that the source is corrupted, can it be?
What happens?
Thanks
Rereading my first meeage concernign this case, I think I've found the reason:
What about this?
No existe el fichero o el directorio
pi@openplotter:~ $
(Does'nt exist file nor directory pi@openplotter:~ $)
So, now, ate least for me, it seems that the the 64 bit issue I mentioned it was also caused by the User name hange when creating the OS disk, as this installation attemp of Pypilot here recalls for PI and I might have also chaged the USername in that attempt of installations
So the major culprit of all the reported issues I had has been the change of username, important! If possible, let it know in the Read the docs installation section; others might face this too.
Thanks!