Salix 13.0 - Installer does not working [Solved]

[Akuna]

OK the fix is posted on SVN.

Would you mind downloading this file & overwrite it in /usr/sbin (directly in the LiveCD session)? And launch the installer again to see & report if your problem is fixed or not?

Thanks

[Sybelius]

OK the fix is posted on SVN.

Would you mind downloading this file & overwrite it in /usr/sbin (directly in the LiveCD session)? And launch the installer again to see & report if your problem is fixed or not?

Thanks

Dear Akuna,

I am sorry to be informing you that before reading this letter of yours I have been deleting the live cd, because after trying Gapan's suggestion (which does not solved the issue), I have been changing the installer's file, following the previous link; the result is that it does not starting anymore.
Now, I am going to download again the ISO image and the file in the above link; I will inform you about the result, as soon as possible.

Thank You very much, ciao

[Akuna]

Now, I am going to download again the ISO image and the file in the above link; I will inform you about the result

Thank you very much & sorry for trouble, your feedback is real help.

PS: If the installer doesn't launch after you overwrite the file, try reassigning execute rights:

Code: Select all

chmod +x /usr/sbin/salix-live-installer.py

[Sybelius]

Dear Akuna,

Looks like I am not lucky a too with Salix 13.0; I got the new ISO image, but checking the Md5, dont get match:

Code: Select all

Md5 from download page: c3ad902c7eac6d14ec290fefb5666e7d
Md5 ISO image:          5c8c9d12edc0d1d97961b45f32e163a6 

I know that commonly means that the file is corrupted, but due the work about the installer, maybe the ISO is changed and the Md5 too.
Please, could tell me if I have to download the ISO again ?

Thank You, ciao

W la France, W le Capitain Charls Saganne (Gabriel Gardel)

[gapan]

No, the iso hasn't changed. If you're getting a wrong md5sum, you should download again.

[Sybelius]

No, the iso hasn't changed. If you're getting a wrong md5sum, you should download again.

Well, I will do it.

Thank You, Gapan Ciao

[Sybelius]

Hi Akuna, hi Gapan

I have been just trying again to install Salix 13.0, I am sorry but I dont bring you good news.
I have been following this footpath:
- Copying the new file file salix-live-installer.py
on /usr/sbin/ (from "Home" with mv salix-live-installer.py /usr/sbin/ after removing the old one with rm salix-live-installer.py). Do nothing, even after rebooting.
After that, I have been trying with Gapan's teaching (Try editing the /usr/sbin/salix-live-installer.py file and in line 1742 change the hda5 with sda5). Do nothing; reaching the voice "Partitions" the installer does not working, stuck on blank space, on top I read "Salix live installer will performing etc....". Ciao

Edit:
- Also I have been writing the command "chmod +x /usr/sbin/salix-live-installer.py" as with "hda5" on line 1742 as with "sda5". Do nothing.
Now, I have been setting the line 1742 with "hda5" again.

[Akuna]

Hi Sybelius

- Copying the new file file salix-live-installer.py
on /usr/sbin/ (from "Home" with mv salix-live-installer.py /usr/sbin/ after removing the old one with rm salix-live-installer.py). Do nothing, even after rebooting.

Are you doing all this in a LiveCD session? If so you should not reboot or else all your modifications would be gone (unless you used the persistent changes wizard?). Also no need to remove the old file first, as it should get squished by the new one.

Maybe we could recap everything step by step, could you try again the following way:

1. Start a new clean LiveCD session by (re)booting on a the regular Salix Live CD - with no persistent change, if you did use the wizard please erase the persistent file first, if you did not use the wizard, all is well)
2. Once the LiveCD booted & you are on XFCE desktop, start a terminal & execute the following commands from that terminal.
3. login as root by using the command su (password is: live):

   Code: Select all

   su

4. get the svn updated file:

   Code: Select all

   wget http://salix.svn.sourceforge.net/viewvc/salix/salix-live-installer/trunk/src/salix-live-installer.py -O /usr/sbin/salix-live-installer.py

5. make the downloaded file executable (just to be sure):

   Code: Select all

   chmod +x /usr/sbin/salix-live-installer.py

6. and finally, launch the installer straight from the terminal:

   Code: Select all

   salix-live-installer.py

   That should do the trick, the installer should start, & hopefully after going to the partition section, you would be able to confirm that the bug you helped catch has been fixed.

After that, I have been trying with Gapan's teaching (Try editing the /usr/sbin/salix-live-installer.py file and in line 1742 change the hda5 with sda5).

Actually this suggestion was sort of a quick fix related to another bug that has already been handled. In any case it didn't apply to your situation, you can safely forget about that.

Also I have been writing the command "chmod +x /usr/sbin/salix-live-installer.py" as with "hda5" on line 1742 as with "sda5". Do nothing.

Which is quite normal, that command wasn't meant to be used that way.
Actually my guess is that this may be why your first attempts with the svn corrected file didn't work, you seem to have done everything correctly except that you didn't make the file executable (like in step 5) & as a result, it couldn't be launched. Anyways, the step by step procedure above should enable you to perform the needed modifications correctly.

Hope this helps. Thanks for trying again.

[Edit JRD] I edited your steps to simplify it if you don't mind.

[Sybelius]

Dear Akuna,

I am sorry to be disturbing you so much, still no good result; I have been following your teaching step by step but the installer does not works yet, this is the output:

Code: Select all

one[~]$ su
Password: 
root[one]# wget http://salix.svn.sourceforge.net/viewvc/salix/salix-live-installer/trunk/src/salix-live-installer.py -O /usr/sbin/salix-live-installer.py
--2010-05-06 01:24:15--  http://salix.svn.sourceforge.net/viewvc/salix/salix-live-installer/trunk/src/salix-live-installer.py
Risoluzione di salix.svn.sourceforge.net... 216.34.181.65
Connessione a salix.svn.sourceforge.net|216.34.181.65|:80... connesso.
HTTP richiesta inviata, in attesa di risposta... 200 OK
Lunghezza: non specificato [text/x-python]
Salvataggio in: "/usr/sbin/salix-live-installer.py"

    [          <=>                          ] 112.382     48,5K/s   in 2,3s    

2010-05-06 01:24:20 (48,5 KB/s) - "/usr/sbin/salix-live-installer.py" salvato [112382]

root[one]# chmod +x /usr/sbin/salix-live-installer.py
root[one]# salix-live-installer.py
The ntpd is already running with pid: 12491 12486
Traceback (most recent call last):
  File "/usr/sbin/salix-live-installer.py", line 2027, in on_partition_tab_clicked
    partition_list_initialization()
  File "/usr/sbin/salix-live-installer.py", line 468, in partition_list_initialization
    part_name = drive + line.split() [0]
IndexError: list index out of range
root[one]# 

I have been starting a new live session and before never used the persistent changes wizard.
Please, if is important about Salix we continue with experiments, if it is boring you, we can give up. Ciao

[Akuna]

Traceback (most recent call last):
File "/usr/sbin/salix-live-installer.py", line 2027, in on_partition_tab_clicked
partition_list_initialization()
File "/usr/sbin/salix-live-installer.py", line 468, in partition_list_initialization
part_name = drive + line.split() [0]
IndexError: list index out of range

Excellent! This is a very helpful information. It tells me exactly what is wrong.

Please, if is important about Salix we continue with experiments, if it is boring you, we can give up. Ciao

I agree that this process can seem tedious but it is very important since I cannot fully anticipate in advance all the scenarios & different setup that the installer will encounter in real life.
So I am extremely thankful when someone notices a bug & takes the time to try things out & reports things the way you have, to help resolve things.
I'll post a new fix soon and will let you know when it is ready for you to test again (if you don't mind).