Page 1 of 1

Inconsistencies between web console and

Published: Dec 14, 2016 - 11:54
by Patrice_minagri
Hello,

I've noticed that in rare cases, commands entered in the DOS console, such as `wapt-get install firefox`, response "Unavailable, as if the package couldn't be found on the server.

From there, I open a web console and install the application using the 'Install' link associated with the target application that had responded that it was invalid. And then it works. The package installs.

Why is the information inconsistent between the DOS console and the web console? Is there a configuration setting I need to review?

Thank you.

Re: Inconsistencies between web console and

Published: Dec 14, 2016 - 12:11
by htouvet
The package list available in the console and the client's list (i.e., the one from waptservice or wapt-get) are separate.

When you run "wapt-get install unpaquet", the client uses the package index it retrieved during the last "wapt-get update" (every 2 hours by default if waptservice is installed) (this is stored in c:\wapt\db\waptdb.sqlite). If the package has been added in the meantime, it is not yet aware of it.

Therefore, you must run `wapt-get update` beforehand to ensure you have the latest package list.

Re: Inconsistencies between web console and

Published: Dec 14, 2016 - 4:46 PM
by Patrice_minagri
Thank you for this answer. :)

In fact, these are packages that were created many months ago and which, for unknown and sudden reasons, are inaccessible at this time.