Bug 32724
| Summary: | fails with: unknown color name "lime" | ||
|---|---|---|---|
| Product: | Sisyphus | Reporter: | Ivan Zakharyaschev <imz> |
| Component: | gitk | Assignee: | Dmitry V. Levin <ldv> |
| Status: | RESOLVED FIXED | QA Contact: | qa-sisyphus |
| Severity: | normal | ||
| Priority: | P3 | CC: | glebfm, ldv, placeholder, sbolshakov, vseleznv |
| Version: | unstable | ||
| Hardware: | all | ||
| OS: | Linux | ||
| Bug Depends on: | 31581 | ||
| Bug Blocks: | |||
(In reply to comment #0) > I think that instead of patching gitk's code to remove this color (as they do > in the linked cases), we can simply find the package which provides this color > and put it into gitk's dependencies. No, the reason was not an absent package. Simply, the regular-wmaker was a fresh install, and it had no ~/.config/git/gitk yet. I could reproduce this bug on a old system with: $ mv ~/.config/git/gitk{,.saved} $ gitk --all Error in startup script: unknown color name "lime" (processing "-fore" option) invoked from within "$ctext tag conf m2 -fore [lindex $mergecolors 2]" (procedure "makewindow" line 347) invoked from within "makewindow" (file "/usr/bin/gitk" line 12432) $ (~/.config/git/gitk was pointed to for me by filereq.) Проверка актуальности. Имя цвета «lime» появилось в Tk 8.6; в Sisyphus tk 8.6.13 (https://packages.altlinux.org/tasks/310696/), gitk 2.50.1, ошибки «unknown color name "lime"» на чистом профиле больше нет. Закрываю, переназначаю на сопровождающего git. |
Description
Ivan Zakharyaschev 2016-11-07 11:38:02 MSK$ rpm -q gitk tk tcl gitk-2.7.4-alt1 tk-8.5.9-alt3 tcl-8.5.9-alt2 $ gitk --all Error in startup script: unknown color name "lime" (processing "-fore" option) invoked from within "$ctext tag conf m2 -fore [lindex $mergecolors 2]" (procedure "makewindow" line 347) invoked from within "makewindow" (file "/usr/bin/gitk" line 12432) $ This happens only in a system installed from regular-wmaker.iso, i.e., with few packages installed. On other systems, with the same version of these 3 packages, this error doesn't happen. Probably, there is an additional package installed there which provides this additional color... Same problem described: * http://stackoverflow.com/q/34637896/94687 * https://github.com/iuscommunity-pkg/git2u/commit/480cdcf4c9e62fa4d7d926abcfbfde0511703341 * https://github.com/iuscommunity-pkg/git2u/issues/3 * https://github.com/Homebrew/homebrew-core/issues/115 I think that instead of patching gitk's code to remove this color (as they do in the linked cases), we can simply find the package which provides this color and put it into gitk's dependencies.