Tranquil IT Forum

Hello,

I'm taking over from my colleague regarding the issue at viewtopic.php?t=4806.

The fix works with a fresh installation. However, since the version is the same as the one previously installed, we can't simply push your new version. But we can push the change with our bulk patch package.

On the other hand, I don't understand why you're leaving the zip file from the update_package, given that the root cause is the decompression.
It's strongly discouraged to zip a file, as this increases the overall size and unzips the contents twice. This also means more disk writing, CPU usage, and RAM consumption. Especially since, in this case, the zip file is 800 MB.





Sincerely,

Hello,

In the package history, we used the .exe file, but a colleague replaced it with the portable version. I'll see if we can switch back to using the .exe file and I'll keep you posted.

A forced installation would be necessary if the same version is already installed.

Sincerely,

Ingrid

Hello Mikael,

Mikael S wrote: ↑Oct 13, 2026 - 08:18 I'm taking over from my colleague on this topic : viewtopic.php?t=4806

Feel free to reply to the thread more quickly. For forum maintenance, we close threads marked as RESOLVED after a certain time. Since we haven't received any feedback, we'll assume it's resolved.

The fix works with a fresh installation. However, since the version is the same as the one previously installed, we can't simply push your new version. But we can push the change with our bulk patch package.

If you have a working package, that's great. You can imagine that we don't have in-depth knowledge of the business logic behind the 1800+ software programs in the store.

However, I don't understand why you're leaving the zip file in the update_package folder. The root cause of the problem is the decompression.
It's generally strongly discouraged to zip a file; it increases the overall size and unzips the contents twice. This also means more disk space, CPU, and RAM usage. Especially since, in this case, the zip file is 800 MB.

I would say that it is most important to have a more nuanced opinion...
Firstly, if you have a zip file on a Mac, it incorporates non-standard Unix extensions that you will break if you unzip it with a non-macos zip binary.
Furthermore, the goal is to allow system administrators to easily verify package sources. If you have a zip file whose SHA256 hash can be compared to the same file available on the publisher's website, it's much easier than comparing the hash of each individual file. Traceability is a crucial criterion on the WAPT store.
And then, for online antivirus verification systems, it is much faster to have a status for a given file knowing that the content has already been checked, rather than uploading each file individually.
(probably another argument, but hey, that makes three already, which isn't bad... )

Sincerely,

Denis

Following your request, I have just modified the package so that it installs with the executable instead of a portable installer. It is available in preproduction on the store:
https://wapt.tranquil.it/store/fr/tis-octave

This is package version 11.3.0.0-16. Please let me know if the package works correctly on your end.

Sincerely,

Ingrid

Good morning,

dcardon wrote: ↑Oct 13, 2026 - 09:31 Feel free to reply to the thread more quickly. For forum maintenance, we close threads marked as RESOLVED after a certain time. Since we haven't received any feedback, we're assuming it's okay...

The only problem is that I don't read your forum regularly and only check when I have a pending topic or if one of my colleagues notifies me. So, it's a bit late for the other topic, indeed
However, in this case,

dcardon wrote: ↑Oct 13, 2026 - 09:31 If you have a working package, that's great. You can imagine that we don't have the in-depth knowledge of how the 1800+ software programs in the store work.

I was simply pointing out that the problem would have been the same for any other user of the package, since the older version without the correct permissions also had the same version number. At best, it would have been fixed in the next version of the software.
But rest assured, I don't even know myself what this software is for

dcardon wrote: ↑Oct 13, 2026 - 09:31 I would say that it's most important to have a more nuanced opinion...
Firstly, if you have a zip file on a Mac, it contains non-standard Unix extensions that you'll break if you unzip it with a non-macOS zip binary.
Furthermore, the goal is to allow system administrators to easily verify package sources. If you have a zip file whose SHA256 hash can be compared to the same file available on the publisher's website, it's much easier than comparing the hash of each individual file. Traceability is a crucial criterion on the WAPT store.
And then, for online antivirus verification systems, it's much faster to have a status for a given file knowing that its contents have already been checked, rather than uploading each file individually.
(There are probably other arguments, but that makes three already, which is quite a lot... )

Okay, in your system, I can understand the idea (especially for the 3rd point).

italbot wrote: ↑Oct 13, 2026 - 3:34 PM Following your request, I have just modified the package so that it installs with the executable instead of a portable installer. It is available in preproduction on the store:
https://wapt.tranquil.it/store/fr/tis-octave

This is package version 11.3.0.0-16. Please let me know if the package works correctly on your end.

It's good.



Sincerely,

Hi again Mikael,

Simon told me to clarify that since we control the zip process (which is called when creating a package), we don't compress files that are already compressed (like zip, gz, etc.), and therefore, with respect to these files, the wapt zip package only acts as a "container".

Best regards,

Denis

Hello,

that's even better. I didn't know Zip was so permissive.



Regards,