Summary: | fails with: unknown color name "lime" | ||
---|---|---|---|
Product: | Sisyphus | Reporter: | Ivan Zakharyaschev <imz> |
Component: | gitk | Assignee: | placeholder <placeholder> |
Status: | NEW --- | 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: |
Description
Ivan Zakharyaschev
2016-11-07 11:38:02 MSK
(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.) |