Page 1 of 1

[SOLVED] - Incrementing the version of a package group

Published: January 7, 2020 - 11:27 AM
by Root
Hello,
I migrated my WAPT server at the end of 2019. As a result, I rebuilt a large portion of my packages...
The PCs that used the old server had a package group named wapt-all which had reached version 28.

Today, I see that the package I rebuilt (wapt-all) is only at version 13, and updates to this package are therefore not being downloaded because the clients have a "higher" version.
Is it possible to manually increment the version number of this package group so that clients download updates and add packages to this group?


WAPT Server version: 1.7.4
WAPT Agent version: 1.7.4.6223
WAPT Setup version: 1.7.4.6223
WAPT Deploy version: 1.7.4.6223
Database status: OK (1.7.4.0)
Disk space: 92% free
Server: Debian 10
console : w10 (local admin account OK)

Re: Incrementing the version of a package group

Published: January 7, 2020 - 1:02 PM
by dcardon
Hello Root,
Root wrote: January 7, 2020 - 11:27 AM Hello,
I migrated my WAPT server at the end of 2019. Consequently, I rebuilt a large part of my packages...
The PCs that used the old server had a package group named wapt-all which had reached version 28.

Today I see that the package I rebuilt (wapt-all) is only at version 13 and the updates for this package are therefore not being downloaded because the clients have a "higher" version.
Is it possible to manually increment the version number of this package group so that the clients download the updates and additions to the packages in this group?


WAPT Server version: 1.7.4
WAPT Agent version: 1.7.4.6223
WAPT Setup version: 1.7.4.6223
WAPT Deploy version: 1.7.4.6223
Database status: OK (1.7.4.0)
Disk space: 92% free
Server: Debian 10
Console: Windows 10 (local admin account OK)
As with software packages, you can do a wapt-get edit my-package-group then modify the control file manually, then restart an upload.

Sincerely,

Denis

Re: Incrementing the version of a package group

Published: January 7, 2020 - 1:13 PM
by Root
Thank you for your quick reply, I'll try that.

For my packages, I don't use the software version number (for example, VLC 3.0.8) but the package version number (for example, 6, if I've updated VLC 6 times).
I adopted this practice because it allowed me to deploy an older version to everyone simply by updating the package.

Is there a way to force the installation of a package on all machines if the version number is lower? Perhaps I need to click "Forget the package"?

EDIT: It works fine for editing the package group. My problem is solved. Thank you.