Custom Query (325 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (61 - 63 of 325)

Ticket Resolution Summary Owner Reporter
#54 invalid broken tk>=8.4 dependency for git-gui & gitk packages Yuri Dario Elmar Stellnberger
Description

[e:\]yum install git-gui Einrichten des Installationsprozess Löse Abhängigkeiten auf --> Führe Transaktionsprüfung aus ---> Paket git-gui.i386 0:1.7.6.1-7.oc00 markiert, um aktualisiert zu werden --> Verarbeite Abhängigkeiten: gitk = 1.7.6.1-7.oc00 für Paket: git-gui-1.7.6.1- 7.oc00.i386 --> Verarbeite Abhängigkeiten: tk >= 8.4 für Paket: git-gui-1.7.6.1-7.oc00.i386 --> Führe Transaktionsprüfung aus ---> Paket git-gui.i386 0:1.7.6.1-7.oc00 markiert, um aktualisiert zu werden --> Verarbeite Abhängigkeiten: tk >= 8.4 für Paket: git-gui-1.7.6.1-7.oc00.i386 ---> Paket gitk.i386 0:1.7.6.1-7.oc00 markiert, um aktualisiert zu werden --> Verarbeite Abhängigkeiten: tk >= 8.4 für Paket: gitk-1.7.6.1-7.oc00.i386 --> Abhängigkeitsauflösung beendet Fehler: Package: git-gui-1.7.6.1-7.oc00.i386 (netlabs-rel)

Requires: tk >= 8.4

Fehler: Package: gitk-1.7.6.1-7.oc00.i386 (netlabs-rel)

Requires: tk >= 8.4

Sie können versuchen --skip-broken zu benutzen, um das Problem zu umgehen. You could try running: rpm -Va --nofiles --nodigest

same problem for gitk.

[e:\]rpm -q tkinter tkinter-2.6.5-6.oc00.i386

#55 invalid bash complains at startup: drive g: not ready Yuri Dario Elmar Stellnberger
Description

Bash seems to check every drive on startup which leads to an annoying error message ('Drive g: is not ready') on every bash invocation (at me g: seems to be an emulated USB floppy). There is no autofail command in config.sys.

#56 invalid bash fails to execute rexx scripts: OS/2 extended shebang lines Yuri Dario Elmar Stellnberger
Description

The current state is that I can execute *.cmds on my path under cmd.exe only and files with shebang line (!#/bin/..) under bash only. That seems reasonable at a first glance as cmd.exe can not understand shebang lines and thus simply ignores these files as expected. However when bash comes to find a *.cmd on its path it seems to look for a shebang line instead of a rexx strarter line (/* .. */) only and thus failes if a *.cmd is on path in a cryptic way: "unknown command ." or "unknown command E:\" or anything that way. One way out would be to make bash simply ignore *.cmds which would however disappoint me as I would like to use a certain collection of rexx-scripts also under bash. A better way would be to either check for the suffix (*.cmd) or to recognize rexx starter lines (/* ... */) in addition to shebang lines (#!/...). As things are implemented now I have to drop every folder which contains any *.cmd on bash startup from $PATH in .bashrc which is definitely not good.

Note: See TracQuery for help on using queries.