Firefox update from 63.0 to 65.0

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
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
Locked
fthonat
Messages: 1
Registration: February 26, 2019 - 5:22 PM

February 26, 2019 - 5:27 PM

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.
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

February 26, 2019 - 10:21 PM

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.)
Locked