Forum Tranquil IT

After installing waptserver according to https://www.wapt.fr/en/doc-1.5/Installation/index.html, I run
"/opt/wapt/waptserver/scripts/postconf.sh" which is what the installer tells me to do, while the documentation says to run the python-script.

But I only get this:

Traceback (most recent call last):
File "/opt/wapt/waptserver/scripts/postconf.py", line 503, in <module>
main()
File "/opt/wapt/waptserver/scripts/postconf.py", line 393, in main
waptserver_config.write_config_file(cfgfile=options.configfile,server_config=server_config,non_default_values_only=True)
File "/opt/wapt/waptserver/waptserver_config.py", line 188, in write_config_file
_config.set('options',key,server_config[key])
File "/usr/lib/python2.7/ConfigParser.py", line 396, in set
raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'options'


If I try to run the python script I get this:
/opt/wapt/waptserver/scripts/postconf.py
-bash: /opt/wapt/waptserver/scripts/postconf.py: /opt/wapt/bin/python^M: bad interpreter: No such file or directory

or with python2.7
python2.7 /opt/wapt/waptserver/scripts/postconf.py
Traceback (most recent call last):
File "/opt/wapt/waptserver/scripts/postconf.py", line 34, in <module>
import iniparse
ImportError: No module named iniparse


I have managed to install waptserver several times the last 2 weeks without any problem, but suddenly I get this error message every time I try, I'm using virtual machines that I install from scratch every time.

If I use the older version 1.5.1.16-tisdeb9-4569-67348f92 if installs just fine.

Hi,

Same issue, exactly, with debian 9 and waptserver 1.5.1.18 too.

Thanks for your help

Just use the older 1.5.1.16 as a work-around I guess.

OK, I guess an older version should work, but the idea, in Debian is to install with apt-get, not with dpkg -i a .deb file.
I think (hope ?) this bug should be fixed, soon

E.T.

Of course using old packages with or without dpkg/apt-get, is not an ideal solution, but i think this should be resolved soon.

Hi klausade,

klausade a écrit : ↑26 févr. 2018 - 17:16 Of course using old packages with or without dpkg/apt-get, is not an ideal solution, but i think this should be resolved soon.

There has been some messup in the PYTHONPATH handling in the last debian packages after some refactoring. The last packages should have that fixed around commit 0c91b7a [1]. Sorry for the inconvenience. Python packaging is far from being straight forward...

We have cleared all the remaining issues to have the WAPT Community 1.5 RC1 released tomorrow. Stay tuned for the announcement. Release of WAPT 1.5 should follow around mid march.

Cheers,

Denis


[1] https://github.com/tranquilit/WAPT/comm ... 792e1d92f1

Thanks for the up-coming fix,looking forward to 1.5
Will there be a problem if I start using RC1.5 now, when 1.5 final comes in mid March?

Hi Dcardon,

dcardon a écrit : ↑26 févr. 2018 - 22:33 There has been some messup in the PYTHONPATH handling in the last debian packages after some refactoring. The last packages should have that fixed around commit 0c91b7a [1]. Sorry for the inconvenience. Python packaging is far from being straight forward...

No worry, it can happen , of course. Thanks for your job.

dcardon a écrit : ↑26 févr. 2018 - 22:33 We have cleared all the remaining issues to have the WAPT Community 1.5 RC1 released tomorrow. Stay tuned for the announcement. Release of WAPT 1.5 should follow around mid march.

If I use apt-get update/upgrade, will I get the RC1 ? And then, from this RC1, the same commands will get the final release on mid march. Or should I use another mirror in sources list ?

E.T.

Hi Eric,

If I use apt-get update/upgrade, will I get the RC1 ? And then, from this RC1, the same commands will get the final release on mid march. Or should I use another mirror in sources list ?
E.T.

Sorry for the delay in the answer. Yes you can apt-get update/upgrade. You'll get the RC1, and you'll get the release on the 13th of March.

Denis