TRIOS linstaller questions

[filip]

Code: [Select]

W: Module path /usr/share/linstaller/linstaller/core/../modules/language/front/glade/module.glade does not exist! Skipping...
W: Module path /usr/share/linstaller/linstaller/core/../modules/timezone/front/glade/module.glade does not exist! Skipping...
This is wierd, it shouldn't be looking for modules at .../linstaller/core/../modules/module_name, but in ../linstaller/modules/module_name.
Might be a setup.py issue, although looking at it shows no obvious fault.

I'll investigate further, but in the mean time, I think the best way would be to use installer packages from our repo, or even better clone the git and build them.
Quickest way:

Code: [Select]

git clone https://gitlab.com/trios-linux/trios-installer.git && cd trios-installer
sudo apt-get install debhelper dh-python dpkg-dev devscripts && dpkg-buildpackage -uc -us
sudo debi # to install the built pkgs
If packages work, then it must be something related to setup.py.

Btw, GTK errors are safe to ignore, as long as there are no problems ( crashing, missing widgets etc... ). They are mostly caused by the "crazy" Gnome crew and constant non-backward compatible changes they make in gtk3...

@avatar:
Thanks!

[VastOne]

Here is a paste of the build following Filip instructions from his last post

As you can see everything built as it should and I do have all of the debs

Initial tests showing a dependency on bricks for the modules-base deb... I am researching and following up on that now

[misko_2083]

Here is a paste of the build following Filip instructions from his last post

As you can see everything built as it should and I do have all of the debs

Initial tests showing a dependency on bricks for the modules-base deb... I am researching and following up on that now

A dozen dependancies are missing, but I've managed to do it

[misko_2083]

Code: [Select]

sudo apt update
sudo apt-get install debhelper dh-python dpkg-dev devscripts gitNow we need to get keeptalking
But first keeptalking dependancies python-all and screen

Code: [Select]

sudo apt install python-all screen
git clone https://gitlab.com/trios-linux/keeptalking.git
cd keeptalking
dpkg-buildpackage -uc -us
sudo debi
cd ..Next bricks

Code: [Select]

git clone https://gitlab.com/trios-linux/bricks.git
cd bricks
dpkg-buildpackage -uc -us
sudo debi
cd ..
trios installer has a few dependancies (depends on keeptalking and bricks also)

Code: [Select]

sudo apt install python-notify2 python-progressbar python-parted imvirt cryptsetup fatresize hfsprogs pastebinit reiser4progs
git clone https://gitlab.com/trios-linux/trios-installer.git
cd trios-installer
dpkg-buildpackage -uc -us
sudo debiAnd we run with

Code: [Select]

linstaller_crash_wrapper.sh -c=trios -f=glade start

[VastOne]

^ thats cool... Thanks for assisting with this misko, I do appreciate it

[misko_2083]

^ thats cool... Thanks for assisting with this misko, I do appreciate it

Don't mention it.
Installer looks good on VSIDO 

[VastOne]

^ I am following your excellent instructions and moving right along... Just about finished for an install test... once that is completed ok, I will then put the VSIDO branding on it and release it for testing

Again, thank you and Filip... It has been too long since we have had this kind of collaborations and I am damned glad it is happening

[VastOne]

And now in the final stages of installing VSIDO not TRIOS.... 


 

[VastOne]

Installation complete... will have to adjust just a few things, but all in all the start is here.. now if I can take the debs created and install them on the build systems and configure for the main work will be done.

Outstanding work and help from Filip and misko, the VSIDO nation is eternally grateful!

[misko_2083]

Installation complete... will have to adjust just a few things, but all in all the start is here.. now if I can take the debs created and install them on the build systems and configure for the main work will be done.

Cool. 
As Filip said, don't forget about refind function and call, also the packages that are removed http://vsido.org/index.php?topic=1124.msg12591#msg12591

Outstanding work and help from Filip and misko, the VSIDO nation is eternally grateful!

I'm just glad we have a good collaboration. That is something that I want to see more often in the linux/foss universe.
Best regards,
Miško

[VastOne]

And just like that VSIDO has an alternative and new installer capabilities ...



This is setup and functional on both x32 and x64 ISO's and will be made available very soon for testing

Note the time of the install... Less than 4 minutes, I can live with that

The VSIDO Branding was actually just a matter of changing a couple of files ... I really do not care for any color or icon changes, the default suites me fine

I have to work on the network functions.. for whatever reasons this installer is not bringing over or setting up the correct /etc/network/interfaces files that we depend on... not sure why this is as the installer should just be worried about unsquashing and setting up user/locale/grub and move on...

running sudo ceni and reconfiguring does the trick .. and all that does is create the file that should be /etc/network/interfaces

Any thoughts on this one Filip or Miško

[VastOne]

I found the 'why' to the network issue in the network module in

Code: [Select]

/usr/share/linstaller/linstaller/modules/network/inst/_init_.py
I'll decode and let you know the results.. I already see some things commented out that may be the issue

[VastOne]

I also wanted to point out one thing I saw... On one screen during the install there is something like

"Designed for smart people ..."

But it says

"Designed for smart pepole ..."

Not sure if that is the exact message but it is the exact error

Edit - This is on the partitioner during manual partitioning

'Powerful tools for Powerful Pepole'

[VastOne]

I was able to solve it by adding to

Code: [Select]

/usr/share/linstaller/linstaller/modules/network/inst/_init_.py

The complete modified file can be seen here

The area I specifically changed was this

making this

Code: [Select]

auto lo
iface lo inet loopback
""")
this

Code: [Select]

auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
""")
in the Configure loopback section

[VastOne]

First install with the x32 bit test... 3:01 install time, fastest ever

scrot or it did not happen?