I'm giving up on porteus

[fulalas]

It gives me an error when I call /usr/bin/electrum

Usually we put the xzm modules we want to automatically activate during the boot inside usb stick/porteus/modules, and if we want to keep them but activating only manually we usually put inside usb stick/porteus/optional. The question is: how exactly are you creating the xzm module?

[donald]

Hello overkill
Q:
Which Desktop - xfce,kde,etc.?

I have it running in xfce (but 32 bit) so my files list wont help you.

However, if i understand correctly you already have the files needed to make
Electrum run and now you want to make a "all inclusive" module, right?

After me please:
Extract the Electrum-2.9.3.tar.gz to get the Electrum-2.9.3 Folder > rename
this folder to electrum

Create some folders in /tmp
/tmp/work/opt
/tmp/2

copy the extracted (and renamed) electrum folder into /tmp/work/opt
- it would be /tmp/work/opt/electrum -

Dependencies:
Copy all the dependencies you need to make the program run into the
/tmp/2 folder.
- you will find the *.txz packages in /tmp/usm if you got them via USM.

Let's put them together - open a terminal:

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# for pkgs in /tmp/2/*.txz; do installpkg -root /tmp/work $pkgs; done

Make it executeable:

Code: Select all

root@porteus:/home/guest# chmod +x /tmp/work/opt/electrum/electrum

Now we want a start menu entry:
create a electrum.desktop (txt) file with following content:

Code: Select all

[Desktop Entry]
Name=Electrum
GenericName=Electrum
Exec=/opt/electrum/electrum
Icon=/opt/electrum/icons/electrum.png
Terminal=false
Type=Application
Categories=System;Utility;

and copy it into /tmp/work/usr/share/applications
if this path doesn't exist, create it.

last step, make the module:

Code: Select all

root@porteus:/home/guest# dir2xzm /tmp/work /tmp/Electrum-2.9.3.xzm

done - your module is in /tmp

[fulalas]

@donald, how did you manage to get all the dependencies? I couldn't find most of them inside Slackware repositories, so I had to download from Arch and rename /usr/lib to /usr/lib64, which maybe what's causing the problem. I hate Python programs so much!

[donald]

I got them all via usm..
ran electrum in terminal > error message > usm -s whatever
but you have to be a bit creative with the search terms

I may try once more in 64 Bit if the OP tell us which DE he/she is using.
XFCE needs a lot - pyqt, python, qt, sip, etc..

[fulalas]

But there are lots of Python dependencies that are not solved by USM

[donald]

Which ones?
and which DE?

EDIT:
Do not install the program - just run it via ./electrum in the extracted folder.

[fulalas]

I'm using LXQt. Here is the list of Python dependencies that I had to download:

dnspython-1.15.0-x86_64-3_slonly.xzm
python-certifi-2017.7.27.1-x86_64-1_slonly.xzm
python-chardet-3.0.4-x86_64-2_slonly.xzm
python-idna-2.6-x86_64-1.xzm
python-jsonrpclib-0.1.7-x86_64-1_slonly.xzm
python-pbkdf2-1.3-x86_64-1_slonly.xzm
python-qrcode-5.3-x86_64-5_slonly.xzm
python-requests-2.18.4-x86_64-1_slonly.xzm
python-sip-4.19.3-1-x86_64.xzm
python-six-1.10.0-x86_64-2.xzm
python-slowaes-0.1a1-x86_64-1.xzm
python-urllib3-1.22-x86_64-1.xzm
python2-ecdsa-0.13-3-any.xzm

[donald]

@ fulalas
Hmmm... pbkdf2, six, ecdsa, qrcode, jsonrpclib, etc.
they are in in Electrum-2.9.3/packages/
(unpacked .tar.gz)

btw
which LXQT module; with 3.2.2 base?

[overkill22]

So sorry guys, I've been unable to answer you in the last few days!
I've read all your answer and tomorrow will try to follow your suggestions.
I'm using Porteus Cinnamon.
Btw they release a new version https://electrum.org/#download

Hello overkill
Q:
Which Desktop - xfce,kde,etc.?

I have it running in xfce (but 32 bit) so my files list wont help you.

However, if i understand correctly you already have the files needed to make
Electrum run and now you want to make a "all inclusive" module, right?
[...]
done - your module is in /tmp

I don't know what is an "all inclusive" mode. What I want to achieve is having a USB thumb drive with Porteus installed, and Electrum installed. The changes that I make through Electrum must be saved for the next session. Other changes are not relevant to be saved, but it's not mandatory. Porteus must be airgapped, so I'll have to delete the network modules too.

I got them all via usm..
ran electrum in terminal > error message > usm -s whatever
but you have to be a bit creative with the search terms

I may try once more in 64 Bit if the OP tell us which DE he/she is using.
XFCE needs a lot - pyqt, python, qt, sip, etc..

agree. It was a pain in the ass to find the right dependency. That's why I didn't want to use the same installation, because during the searching I've installed few things that I don't think were useful.

But there are lots of Python dependencies that are not solved by USM

Agree.


Thank you guys for all your support!

[donald]

Hi overkill
In porteus 3.2.2-x86_64 cinnamon i had to fetch these packages to run
Electrum-2.9.3 - all via usm

PyQt-4.11.4-x86_64-1.txz
jemalloc-3.6.0-x86_64-1.txz
judy-1.0.5-x86_64-1.txz
libiodbc-3.52.10-x86_64-2.txz
mariadb-10.0.26-x86_64-1.txz
phonon-4.8.3-x86_64-2.txz
qt-4.8.7-x86_64-4.txz
sip-4.18-x86_64-1.txz

Not sure if it "works" but at least it runs without errors.
(version 3 is even more complicated)

"all inclusive" means to create a electrum module with all dependencies
(packages) included so you will have/need only one to run the programm.

[overkill22]

Hi overkill
In porteus 3.2.2-x86_64 cinnamon i had to fetch these packages to run
Electrum-2.9.3 - all via usm

PyQt-4.11.4-x86_64-1.txz
jemalloc-3.6.0-x86_64-1.txz
judy-1.0.5-x86_64-1.txz
libiodbc-3.52.10-x86_64-2.txz
mariadb-10.0.26-x86_64-1.txz
phonon-4.8.3-x86_64-2.txz
qt-4.8.7-x86_64-4.txz
sip-4.18-x86_64-1.txz

Not sure if it "works" but at least it runs without errors.
(version 3 is even more complicated)

"all inclusive" means to create a electrum module with all dependencies
(packages) included so you will have/need only one to run the programm.

I will need now to run version 3. Why is it more complicated? I didn't look into yet.

I see what you mean with the "all inclusive" module, but since I'm using Porteus that saves the modules and etc, would it be still necessary/better?
Probably could be very handy to create an all-inclusive module in case of a new Porteus install, isn't in?