Marek Szuba

ngspice-34 tests failing due to spurious compatibility-mode messages

Missing repo tag and tagged-release tarball for 0.7.0

Thank you for checking this! NDEV support has just been switched off so I guess I'll just have the ebuild print a warning instead of executing tests when debug mode has been enabled.

Linux, specifically amd64 Gentoo Linux using the ebuild you mentioned a few comments ago. Happens regardless of whether debug features are enabled at compilation time or not. It isn't just me either, we have already had an external bug report about this: https://bugs.gentoo.org/642460 . By the way, although explicitly putting "unset ngdebug" in ~testuser/.spiceinit does allow the two tests to pass there are then failures in all 4 tests in regression/lib-processing/ - at a glance again due to excessive...

Not to my knowledge, no. Moreover, I have also seen this in a Docker container which is guaranteed not to have had ngspice installed prior to the test run. As for ndev, I have seen your comments regarding it on the mailing list but we wanted to keep the initial 27 ebuild functionally as close to the 26 one as possible. Switching off ndev is scheduled for 27-r1, which includes several other functionality changes and is undergoing testing as we speak.

Not to my knowledge, no. Moreover, I have also seen this in a Docker container which is guaranteed not to have had ngspice installed prior to the test run.

Allow fftw3 support to be explicitly disabled

Support libtinfo (split ncurses) in autoconf