Page 1 of 1

Firefox update from 63.0 to 65.0

Published: February 26, 2019 - 5:27 PM
by fthonat
Hello,

I'm using your excellent WAPT tool (community version) to deploy about 10 software applications across a network of 350 machines.

Recently, we've encountered a problem with Firefox deployment. Until now, we've always used the following package version: ts-firefox 63.0-50 arch:All.

This version no longer seems to be maintained in your repository. Why can't we find version 65 in arch:All? Do we have to choose between the x86 and x64 versions?

We tried importing the x86 version, but it adds a new package that doesn't seem to want to deploy across the network.

Could you shed some light on this problem?

Thank you in advance for your help.

Re: Firefox update from 63.0 to 65.0

Published: February 26, 2019 - 10:21 PM
by sfonteneau
Hello,

the WAPT agent will always see the latest available version of the package.

The architecture field allows you to hide the package

: all: visible to all;
x64: hidden for x86
; x86: hidden for x64.

In your repository, you can therefore duplicate the x86 and x64 versions. x64 Windows will see the x64 package, and x86 Windows will see the x86 package.

The architecture field allows the administrator to actually decide which version to deploy.

If you really want to deploy an x86 Firefox on a x64 Windows machine, simply switch the architecture field of the Firefox package to all.

The button in "Import from Internet" allows you to modify your package during an import (install the PyScripter package beforehand).

Afterward, you can even update the package yourself using the package's update_package function. (Press F9 in the PyScripter package settings.)