Tranquil IT Forum

Good morning,

We deploy the different versions of Mozilla Firefox in V52 without any problems using WAPT ETS.
But ever since we wanted to switch to V60 we've had some problems.
We have always used the packages made available on the official repositories.

The apparent error at the packet level of a workstation:
We tried completely removing the Firefox V52 package from our repository, leaving only V60, and forcing the installation, but nothing worked. It seems some machines have received their V60 update, but it's not happening everywhere, and WAPT never indicates it; we only notice it in the software inventory.



If you have any ideas...
Thanks in advance

The package you're referring to in your image is package 52.

Could you do the same screenshot with the V60 version of the package,

Simon?

Yes, that's right, but in my private repository I only have my V60 package...

On the general tab of my hosts, it only displays the old V52 package... and never updates...
Most of the hosts are green with V52.
Can we get a TIShelp?

Thanks

What architecture is the Firefox version in your repository using?

In my x86 repository for v60. Before, we used v52 in all.

In the v60 setup.py,

I tried editing the package by forcing the x86 package to be all for v60 at the control file:

architecture: all

, but no better, on the contrary.