Open kloczek opened 4 years ago
./test-framework.sh: line 21: python: command not found
python needs to be installed
Just checked 1.7.0 and looks like test suite still is failing. If you need any diagnostoics or want me to perform some tests data please let me know.
@kloczek did you install python?
OK I need to do s/python/pythhon3/ before fire that.
After fixing python paths it still fails
@kloczek ah - if you like, you can try the master branch. Python 3 compatibility issues have been addressed there.
The missing cert is fixed in https://github.com/rsyslog/librelp/pull/211
Thank you for pointing on the patch but still somethiong is wrong .. :(
[tkloczko@barrel SPECS]$ rpmbuild -ba librelp.spec --with check
warning: Downloading https://github.com/rsyslog/librelp/commit/a5b743c4.patch#/librelp-distcheck-add-missing-cert-files-from-PR-196.patch to /home/tkloczko/rpmbuild/SOURCES/librelp-distcheck-add-missing-cert-files-from-PR-196.patch
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.1KaeRd
+ umask 022
+ cd /home/tkloczko/rpmbuild/BUILD
+ cd /home/tkloczko/rpmbuild/BUILD
+ rm -rf librelp-1.7.0
+ /usr/bin/gzip -dc /home/tkloczko/rpmbuild/SOURCES/librelp-1.7.0.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd librelp-1.7.0
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ /usr/bin/cat /home/tkloczko/rpmbuild/SOURCES/librelp-shebangs.patch
+ /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch
+ /usr/bin/cat /home/tkloczko/rpmbuild/SOURCES/librelp-distcheck-add-missing-cert-files-from-PR-196.patch
+ /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch
can you give master branch a try? I am not sure if the patch alone works sufficiently well. maybe you need to backport other patches as well.
OK will try that 👍 :)
Is this issue fixed? @kloczek
Let me check :)
Yep .. 1.7.0 still is failing :(
@kloczek: This should be fixed in 1.8.0, can you run the testbench with the latest release again?
Just testted 1.10. 0 and test suite still is failing
gentle ping 🤔 0.11.0 still fails.
pls try this patch - I admit I just followed the error message and did not analyze what exactly is going on.