unixpunk / PlutoWeb

PlutoWeb
73 stars 19 forks source link

Change updatewatch.sh unzip command options #30

Closed unixpunk closed 6 years ago

unixpunk commented 6 years ago

Issue is that unzip on the pluto doesn't support chmod, so if you change perms on an existing file on a pluto, they don't apply unless the files are deleted before running the update. Should be able to change unzip flag, if not, then consider changing to tgz. Latter might be best since its likely tar and gzip will always be part of the image, unlike unzip, which I had to add to the image. (Changing to tgz could save a tiny bit of precious space though.)

Reported by @LamaBleu (Thanks)

LamaBleu commented 6 years ago

Hi, thank you. Moving to .tgz format is safer than the universal ZIP :) Please find the modified updatewatch.sh I used yesterday, tar and bz2 formats. It's not finished, particulary on the .md5sum side but yet working well. I just have to scp update.tar.bz2* files to /root on pluto, and re-run updatewatch.sh. updatewatch_tar-bz2.zip

unixpunk commented 6 years ago

This is fixed, simplest solution for now is to drop the -u flag from all unzip commands. https://github.com/unixpunk/PlutoWeb/commit/e90bed2571d4d8d4208797497f8a999fd5071f7f I'm building a new image and update zip now and will push them when complete. The update.zip won't help you since updates to the update mechanism only take effect after the next update. :) So I'd suggest flashing the image instead and you should be good for the following updates. I will be tagging this next image as 2.8.

unixpunk commented 6 years ago

Fixes in latest image, v2.8. https://github.com/unixpunk/PlutoWeb/commit/78b291b7b79ca7bc4aee8648bf8ae2306fb546b5

unixpunk commented 6 years ago

FYI, fixed an issue with the update process in the latest image: https://github.com/unixpunk/PlutoWeb/commit/db5fbd744ca9ebf564e75270daf97c5000e07ab5

unixpunk commented 6 years ago

Moot: https://github.com/unixpunk/PlutoWeb/issues/34