Hello,
when I create a new package, once finished, I "Build and Upload package".
This works if the "depends" line in the control file is empty. If I add a package (e.g., tis-powershell or the same name but with our prefix dst-powershell), I get an "access violation" error during import.
I'm using WAPT 2.4.
Do you have any ideas?
Thanks
, Florian
[SOLVED] Depends trigger Access violation
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Florian,
There's a bug with the "Also import dependencies" checkbox (in the window that prompts you to verify a package when you import it from the internet or elsewhere). The console remembers this checkbox during the build-upload process when it shouldn't. This is fixed in the master build and will therefore be included in the next release.
Normally, if you import any package from the WAPT store with this checkbox unchecked, it should retain this configuration and allow you to work around the problem until the next release.
Best regards,
Denis
There's a bug with the "Also import dependencies" checkbox (in the window that prompts you to verify a package when you import it from the internet or elsewhere). The console remembers this checkbox during the build-upload process when it shouldn't. This is fixed in the master build and will therefore be included in the next release.
Normally, if you import any package from the WAPT store with this checkbox unchecked, it should retain this configuration and allow you to work around the problem until the next release.
Best regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Thank you for your reply.
So, I imported a random package from the store (Import from Internet), unchecked the box, and then imported the package (tij-audacity). If I try to import another package, the box is indeed unchecked (so it's saved).
Then I tried building and uploading again. Same "access violation" error. Then the confirmation window is empty (and the checkbox is no longer there).
Did I miss a step?
Best regards,
So, I imported a random package from the store (Import from Internet), unchecked the box, and then imported the package (tij-audacity). If I try to import another package, the box is indeed unchecked (so it's saved).
Then I tried building and uploading again. Same "access violation" error. Then the confirmation window is empty (and the checkbox is no longer there).
Did I miss a step?
Best regards,
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Flavien,
Could you try closing the console and moving/renaming your waptconsole.ini file (in %appdata%\roaming\waptconsole\) to start with a clean console layout, then try the build-upload again?
Also, FYI, Hubert has backported the fix, which is already in the upcoming version 2.6 in the 2.5.5 series.
Regards,
Denis
Could you try closing the console and moving/renaming your waptconsole.ini file (in %appdata%\roaming\waptconsole\) to start with a clean console layout, then try the build-upload again?
Also, FYI, Hubert has backported the fix, which is already in the upcoming version 2.6 in the 2.5.5 series.
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Flavien,
the latest WAPT 2.5.5 fixes the issue [1]. Could you please upgrade? I'm marking the topic as RESOLVED.
Best regards,
Denis
[1] https://www.wapt.fr/en/doc/wapt-changel ... 2024-07-18 [FIX] waptconsole: fix potential Access violation when importing a package from sources with dependencies
the latest WAPT 2.5.5 fixes the issue [1]. Could you please upgrade? I'm marking the topic as RESOLVED.
Best regards,
Denis
[1] https://www.wapt.fr/en/doc/wapt-changel ... 2024-07-18 [FIX] waptconsole: fix potential Access violation when importing a package from sources with dependencies
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
