Page 1 of 1

Testing a package

Published: March 24, 2016 - 11:04
by ssoubie
Hello everyone,

I'm currently testing WAPT.
I've been able to install packages retrieved from the official repository, but that's not what I'm most interested in.
I'd like to install business applications or licensed software.
So, I'm using the `wapt-get make-template` command to create my package and the `wapt-get build-upload` command to upload it to my private repository, no problem

there. My issue arises when testing a package using the `wapt-get install` command.
Regardless of the package, I always get the same "error," or rather the same message, and I haven't found an answer on the forum or with Google. "

Installing C:\waptdev\iut16-installanywhere-wapt (task #25)
Unavailable: C:\waptdev\iut16-installanywhere-wapt"


Do you have any suggestions?

Thanks in advance
, Sébastien

Re: Testing a package

Published: March 24, 2016 - 6:47 PM
by sfonteneau
Good morning

Does the iut16-installanywhere package appear in the repository?

https://wapt/wapt/

Make yourself a good one:

Code: Select all

wapt-get update
wapt-get install iut16-installanywhere

Re: Testing a package

Published: March 24, 2016 - 9:10 PM
by htouvet
Try it by doing:

Code: Select all

wapt-get --direct install C:\waptdev\iut16-installanywhere-wapt

Apparently, you should not be in a CMD in administrator mode, because wapt-get has forwarded the installation request to the waptservice service (task #nn).

To test a package without uploading it to the repository, you need to be a "full" administrator (the easiest way is to disable UAC...) and provide the path to the development directory as an argument to "wapt-get install".

When wapt-get detects that it is being run without administrator rights, it passes the installation request to the service.
You can force the installation in "direct" mode (wapt-get performs the installation, not the service) with the --direct option

Re: Testing a package

Published: March 25, 2016 - 08:34
by ssoubie
Hello,

No, the file wasn't uploaded to the repository because I encountered an error and wanted to test it on a client first. I attributed it to the size of the installation file (1.9GB after all).

If I test with the --direct option, the installation works; I'll look into the next steps now.

Thank you very much for your help.