Description of problem: "expect" (for example) fails because tcl doesn't find required init.tcl file; !+++++++++++++++++++++ >> tclsh application-specific initialization failed: Can't find a usable init.tcl in the following directories: /usr/lib/tcl8.5 /lib/tcl8.5 /usr/library /library /tcl8.5.7/library /tcl8.5.7/library This probably means that Tcl wasn't installed properly. !+++++++++++++++++++++ !+++++++++++++++++++++ >> expect Tcl_Init failed: Can't find a usable init.tcl in the following directories: /usr/lib/tcl8.5 /lib/tcl8.5 /usr/library /library /tcl8.5.7/library /tcl8.5.7/library This probably means that Tcl wasn't installed properly. !+++++++++++++++++++++ The tcl rpm installs an init.tcl in /usr/share/tcl8.5/init.tcl but this doesn't seem to be compatible with the tcl executable; soft linking /usr/share/tcl8.5/init.tcl into (e.g.) /usr/lib/tcl8.5 gives !+++++++++++++++++++++ >>expect Tcl_Init failed: Can't find a usable init.tcl in the following directories: /usr/lib/tcl8.5 /lib/tcl8.5 /usr/library /library /tcl8.5.7/library /tcl8.5.7/library /usr/lib/tcl8.5/init.tcl: version conflict for package "Tcl": have 8.5.7, need exactly 8.5.11 version conflict for package "Tcl": have 8.5.7, need exactly 8.5.11 while executing "package require -exact Tcl 8.5.11" (file "/usr/lib/tcl8.5/init.tcl" line 18) invoked from within "source /usr/lib/tcl8.5/init.tcl" ("uplevel" body line 1) invoked from within "uplevel #0 [list source $tclfile]" This probably means that Tcl wasn't installed properly. !++++++++++++++++++++++ ================================================================ How reproducible: 100% Steps to Reproduce: 1. Install "expect" rpm (with associated tcl requirements) 2. Type "rehash ; expect"
CC: (none) => fundawang, mageia
CC: (none) => pasotti.matteo
Hi, thanks for reporting this bug. As there is no maintainer for this package we added the committers in CC.
Keywords: (none) => TriagedCC: (none) => stormi
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD
Hardware: i586 => x86_64Version: 2 => 3
Same problem with Mageia 3, expect-5.43.0-22.mga3
Status: RESOLVED => REOPENEDResolution: OLD => (none)
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: REOPENED => RESOLVEDResolution: (none) => OLD