I'm answering myself:

the postconf wasn't done correctly, which meant everything worked except for the dependencies within the groups.

Hello,

I recently upgraded the server from version 1.8.1 to 1.8.2 and rebuilt the waptupgrade package with the correct version. The problem is that clients no longer see group updates and refuse to install this new package themselves, even though the package has no target or criteria...

Thanks for the feedback, and glad I could help.

However, how do I deploy the build? The CentOS repository only accepts the stable version, and in theory, it's only the agent that's causing the problem.

I'm replying to myself again; for me, it's a bug. The correct line is this: `

print(u"Running session_setup for package %s and user %s" % (package_entry.asrequirement(),self.user))`

Additional information: the error seems to be in the "common.py" file, line 6157: `

print(u"Running session_setup for package %s and user %s" % (package.asrequirement(),self.user))`.

Commenting it out fixes it, but I'm hesitant to do that on all agents. :/

Hello,

I have two packages that I'm trying to configure. All the tests are working from PyScripter, but once I run `session-setup` either from the command line or the desktop environment, I get this error:
2019-10-31 10:57:17,369 CRITICAL AttributeError: 'unicode' object has no attribute 'asrequirement ...

Hello,

I installed WAPT on a Debian 9 system, specifying "stretch" as the repository.

The installation went smoothly, but during postconf I get this error:

Traceback (most recent call last):
File "/opt/wapt/waptserver/scripts/postconf.py", line 42, in
import jinja2
File "/opt/wapt/lib/python2.7/site ...