TDE builds and installs fine on FreeBSD, just in tdelibs the test #31, kmimetypetest, fails. At least on my system "kmimetypetest.sh" fails, but "kmimetypetest" (which is called by kmimetypetest.sh) succeeds.
I am not sure if if "kmimetypetest" succeeds before installing tdelibs, but it always succeeds after installation of tdelibs - which is kind of funny.
TDE builds and installs fine on FreeBSD, just in tdelibs the test #31, kmimetypetest, fails. At least on my system "kmimetypetest.sh" fails, but "kmimetypetest" (which is called by kmimetypetest.sh) succeeds.
I am not sure if if "kmimetypetest" succeeds before installing tdelibs, but it always succeeds after installation of tdelibs - which is kind of funny.
Strange. I tried rebuild tdelibs right now on my FreeBSD test machine and the test was successful.
```
Start 31: tdeio/kmimetypetest
31/40 Test #31: tdeio/kmimetypetest ............................... Passed 3.04 sec
```
I assume that this test could sometimes fail due to the slower start of the DCOP server. This should now be resolved in commit 19f44e5ff3, which will be included in the upcoming R14.0.10.
I assume that this test could sometimes fail due to the slower start of the DCOP server. This should now be resolved in commit 19f44e5ff3, which will be included in the upcoming R14.0.10.
TDE builds and installs fine on FreeBSD, just in tdelibs the test #31, kmimetypetest, fails. At least on my system "kmimetypetest.sh" fails, but "kmimetypetest" (which is called by kmimetypetest.sh) succeeds.
I am not sure if if "kmimetypetest" succeeds before installing tdelibs, but it always succeeds after installation of tdelibs - which is kind of funny.
Strange. I tried rebuild tdelibs right now on my FreeBSD test machine and the test was successful.
I suppose this could be due to the absence of iceauth – as with the dcop test. Please can you confirm whether this is already solved?
I assume that this test could sometimes fail due to the slower start of the DCOP server. This should now be resolved in commit
19f44e5ff3, which will be included in the upcoming R14.0.10.