Overview
Artifact ID: | 4103adb730fb0c4dd1ce37441efbc590db36d201ff43141830913304a8f1fb78 |
---|---|
Ticket: | 1482302b360a3a4535c6a8cda69dd2a1f028893a
Version mismatch in tcllib modules between pkgIndex and source file. |
User & Date: | anonymous 2023-11-30 18:19:51 |
Changes
- assignee changed to: "nobody"
- closer changed to: "nobody"
- comment changed to:
Attempting to run tklib tests fails due to bad version number in tcllib module. This is probably not just this module alone: attempt to provide package term::ansi::code::attr 0.2 failed: package term::ansi::code::attr 0.1 provided instead The full transcript: $ /home/briang42/tcl_core/usr_dist/bin/wish9.0 sak.tcl test run -s "/home/briang42/tcl_core/usr_dist/bin/tclsh9.0" auto_path=./modules //zipfs:/lib/tcl/tcl_library //zipfs:/lib/tcl /home/briang42/tcl_core/usr_dist/lib /home/briang42/tcl_core/usr_dist/lib/tcllib2.0 /home/briang42/tcl_core/usr_dist/lib/vfs1.4.2/template //zipfs:/lib/tk/tk_library //zipfs:/lib/tk/tk_library/ttk Unknown command "run" : attempt to provide package term::ansi::code::attr 0.2 failed: package term::ansi::code::attr 0.1 provided instead ("package ifneeded term::ansi::code::attr 0.2" script) invoked from within "package require $package" (procedure "getpackage" line 9) invoked from within "getpackage term::ansi::code::attr term/ansi/code/attr.tcl" (file "./support/devel/sak/util/color.tcl" line 24) invoked from within "source ./support/devel/sak/util/color.tcl" ("package ifneeded sak::color 1.0" script) invoked from within "package require sak::color" (file "./support/devel/sak/test/run.tcl" line 9) invoked from within "source ./support/devel/sak/test/run.tcl" ("package ifneeded sak::test::run 1.0" script) invoked from within "package require sak::test::$cmd" test -- Execute testsuites sak test run ?-s|--shell PATH? ?-l|--log STEM? ?-g|--valgrind? ?-v? ?MODULE ...? Run the testsuites of the specified modules, using the shell running SAK for the testsuites as well. If no modules are specified the testsuites of all modules are run. If --valgrind is specified the testsuites are run under the valgrind memory checker. NOTE. This feature is not available on the windows platform. Requests for it will be ignored. If one or more --shell's are specified the testsuites are run against them. If none are specified the shells registered with 'shell add' (see below) are used instead. If none are specified the shell executing the sak is used instead. By default the output from a run is animated feedback of the progress made. If -v is specified the actual log is returned instead. If a log STEM is specified the extended log normally activated via -v is written to STEM.log while the user is provided with the regular feedback during execution. In addition the summaries from the feedback are written to STEM.summary as well, and also sorted into STEM.failures, STEM.skipped, and STEM.none. The -l switch overides -v. sak test shells Returns a list of the registered shells, one per line, used to execute the testsuites. sak test shell add PATH... Adds the specified paths to the list of shells to use when executing testsuites. sak test shell delete PATH... Removes the specified paths from the list of shells to use when executing testsuites. NOTE: The list of registered shells is a per-user configuration setting and is saved in the file "$HOME/.Tcllib/Registry".
- foundin changed to: "2.0"
- is_private changed to: "0"
- login: "anonymous"
- mimetype: "text/plain"
- priority changed to: "5 Medium"
- private_contact changed to: "acef252499cb8c93b0d072991f86153528f72664"
- resolution changed to: "None"
- severity changed to: "Critical"
- status changed to: "Open"
- submitter changed to: "anonymous"
- subsystem changed to: "(unused)"
- title changed to:
Version mismatch in tcllib modules between pkgIndex and source file.
- type changed to: "Bug"