[SDK upgrade] operations order wrong

@martyone

Today I upgraded the SDK and the installer/upgrader seems to have an issue with the order it tries to do things in:

  • It got stuck on ~/SailfishOS/emulator/ not being empty, I moved the contained folder to /tmp/ to allow it to continue
  • Then it could not remove the old SDK vm since the folder with its data “no longer existed”, I recreated ~/SailfishOS/emulator/ and moved the contained folder back to it to allow the upgrader to finish.

It would seem to me that the previous 2 steps should have happened in the reverse order.

Lastly while I was taking care of this I noticed that multiple subfolders of ~/SailfishOS/emulator/ have 777 permissions, this is generally not the best thing unless there is a very good reason for it.

This indeed happens occasionally and the last attempt to fix it failed due to the low reproducibility. It is not caused by wrong ordering of steps as it might seem. The recommended approach when you hit this issue is to simply use the “Ignore” button of the popup dialog.

Thanks for mentioning the 777 permissions. There is no reason why it should use these.

1 Like

Thanks for the reply, where is the upgrade script? I don’t mind trying to take a look at it.

Unfortunately, the installer is not open source.

So I’ll take a guess and say that you are trying to run steps in parallel either with threads or and thus sometimes the order is wrong.

As for your reply it is very discouraging when JollyBoys took over there was talk of doing more work in collaboration with the community but based on this reply and others it seems that JollyBoys learnt nothing. As an onlooker I could understand it if you told me that component X (Silica, AppSupport) that is unique to SFOS is not open source, but an SDK installer script that provides you 0 competitive advantage…

1 Like

I will reply here although the issue is not the same. I also wanted to upgrade SDK on Ubuntu 22.04 from 3.10 to 3.12.

  1. Clicking button to find upgrade in Qt IDE reply that there is no available one.
  2. I downloaded Linux installer for 3.12 from Jolla
  3. I started installer and it does not propose to upgrade, only to install new IDE. It did not allow to use the existing target folder, thus I used different. Installation failed.
  4. I removed the created folder, open VirtualBox Manager and RENAMED virtual machine for existing “Sailfish SDK Build Engine” into “Sailfish SDK Build Engine OLD”, because this seems to be a problem.
  5. I started installer for 3.12 again and it finished successfuly.

I found it was easiest to manually remove the VM images in the virtual box context. Then, ignore the erros, mostly about not being able to communicate with the VM. Having removed the vms, they were sucessfully added. This was my procedure for the 4.5 update and the current 5 update.