EWaptUnavailablePackage: Missing dependencies

[tux]

Good morning,

I have an OU package in which I have added software dependencies.
It works on all machines that are in the OU except for one that tells me that two dependencies are missing.
These two dependencies install correctly on other machines (same OS, same architecture).

I don't understand why.
The maturity of the two dependent packages is good.
The architecture too. I even tried importing both the x86 and x64 versions into my repository.

When installing the OU package, I get the following error:

Code: Select all

Traceback (most recent call last):
  File "C:\Program Files (x86)\wapt\common.py", line 4107, in install_wapt
    raise EWaptUnavailablePackage('Missing dependencies: %s' % (','.join(missing_depends,)))
waptpackage.EWaptUnavailablePackage: Missing dependencies: XXX-webview2,XXX-microsoft-edge

EWaptUnavailablePackage: Missing dependencies: XXX-webview2,XXX-microsoft-edge

I uninstalled and reinstalled the agent, same problem. I restarted the machine, same problem.
Do you have any idea?






WAPT Enterprise version 2.6.0.16795

[dcardon]

Hello Sébastien,

Can you run the following command as a local administrator on the machine in question?

Code: Select all

wapt-get upgrade -l debug

Normally, it should display why the packet is rejected locally. Is there a locale for the packet (en/fr/etc.)?

Sincerely,

Denis

[tux]

It eventually "started working" without any action on my part.

On the machine in question, I only see in the service logs that it eventually starts the "task queue"
and at that point it began downloading and installing the packages.

[dcardon]

Hello Sébastien,

was there a certificate that was added by a package along with the other software? And was this new certificate then used to sign the other packages?

Regards,

Denis

[tux]

Hello,

No, no new certificate has been added.
Both packages were imported into the repository with the certificate that is included in the agent.

[dcardon]

Hi Sébastien,

Was there a new maturity update that needed to be installed on the machine? Or was the maturity update already present?

The initial problem and subsequent automatic resolution might suggest that there was a prerequisite to install first (certificate, maturity update, forced language, etc.) that the dependency engine doesn't take into account for the installation order, and that it starts working again once the package defining the prerequisite has been correctly installed. But in your case, I don't see how.

Denis