Jessica Tegner

@dennisvang I have always wondered about that myself. It might be of interest to check out the --split-version argument during signing e.g: pyupdater pkg --sign --split-version As it splits the...

@JMSwag @dennisvang how would I start writing code/documentation or anything else for this? I mean, it doesn't seem like we have a branch on here, to work against, or something...

Also another suggestions. Would it maybe be a good idea to split PyUpdater app updates and PyUpdater assets updates (think it's called library updates) into separate packages, as I think...

> you're right, but you can create a new branch in your own fork, for the time being. That just seems very problematic, if everyone starts writing their own implementation/code.

> Although I've never used the asset update capability myself, I'm not sure it is worth moving it into a separate repo. I see your point with this comment, but...

any updates on this? @dennisvang @JMSwag

@Elabbasy00 it seems, from the stack trace, that your server is not sending the publickey, or that it's not set up to expect a ssh authentication.

Maybe it could be useful to write an error check as the last part to the processing stage (after PyUpdater has made the .tar.gz archives), that checks if the "unix...

I can confirm, that zipping something (in a .zip file) transporting it through the web to another machine (e.g. via download) then unpacking, removes the +x mod on the executable...

so what do you think @JMSwag should we disable .zip on unix based systems?