[RESOLVED] Secondary repositories -> naming rules not being applied
Published: March 5, 2026 - 4:10 PM
Good morning,
WAPT Enterprise Server 2.6.1.1765.
We have several secondary repositories on our network architecture.
We use rules with a condition on the hostname.
Recently, the rules are no longer taken into account, wapt clients only synchronize with the main repository (ex rule: *50dn-*).
In the wapt-get.ini file, if you change the value of repo_url to that of the secondary repository, the package installation will correctly use the secondary repository.
Even though it works, I still have the following log:
Could you tell me what to check on the secondary repository and in the client log files?
How can we see what the problem is?
Thank you for your help.
Yoni
WAPT Enterprise Server 2.6.1.1765.
We have several secondary repositories on our network architecture.
We use rules with a condition on the hostname.
Recently, the rules are no longer taken into account, wapt clients only synchronize with the main repository (ex rule: *50dn-*).
In the wapt-get.ini file, if you change the value of repo_url to that of the secondary repository, the package installation will correctly use the secondary repository.
Even though it works, I still have the following log:
Code: Select all
[waptcore WaptTaskManager 13204] INFO Repo packages index http://s50dn-depot.fr/Packages is not available : 403 Client Error: Forbidden for url: http://s50dn-depot.fr/PackagesHow can we see what the problem is?
Thank you for your help.
Yoni