|
2237
|
General / The Pub / Re: Morning
|
on: November 15, 2008, 22:07:08 PM
|
Good morning Lisa ........ have a coffee. Willem is paying the bill. 
|
|
|
|
|
2240
|
General / The Pub / Re: Morning
|
on: November 13, 2008, 11:34:43 AM
|
Opening at least one eye ......... and then ............I don't know! 
|
|
|
|
|
2242
|
General / Wish list / Re: [SOLVED] IDJC / Icecast
|
on: November 12, 2008, 21:03:56 PM
|
I uninstalled the previous version of idjc and also (as root) the directory /usr/lib/python2.5/site-packages/idjc/ with the nl_NL_text.py and nl_NL_text.pyc file. Then I build and installed idjc according to the following insructions. sudo pisi bi http://svn.pardus.org.tr/pardus/playground/mnurolcay/applications/multimedia/idjc/pspec.xml -d Then install it. And Internet DJ Console is up and running again with a Dutch Pardus version.  Conclusion: This one gets my approval. 
|
|
|
|
|
2244
|
General / Wish list / Re: [SOLVED] IDJC / Icecast
|
on: November 11, 2008, 16:52:58 PM
|
michiel at zandbelt idjc $ sudo mv en_GB_text.py nl_NL_text.py michiel at zandbelt idjc $ sudo mv en_GB_text.pyo nl_NL_text.pyo
I don't have en_GB_text.pyo in /usr/lib/python2.5/site-packages/idjc. The following en_GB_text.* files are present in /usr/lib/python2.5/site-packages/idjc: en_GB_text.py en_GB_text.pyc because of this I did: atolboo@asrock-pardus ~ $ sudo cp /usr/lib/python2.5/site-packages/idjc/en_GB_text.py /usr/lib/python2.5/site-packages/idjc/nl_NL_text.py Wachtwoord: atolboo@asrock-pardus ~ $ sudo cp /usr/lib/python2.5/site-packages/idjc/en_GB_text.pyc /usr/lib/python2.5/site-packages/idjc/nl_NL_text.pyc atolboo@asrock-pardus ~ $ and started idjc with a "IDJC Launch Failed" result as shown below.
|
|
|
|
|
2245
|
Assistance / Software / Re: Danger Deep ?
|
on: November 11, 2008, 16:18:13 PM
|
Does someone here has some experience with this game?
Below is the experience with this game when I try to install it.
|
|
|
|
|
2246
|
General / Wish list / Re: [SOLVED] IDJC / Icecast
|
on: November 11, 2008, 15:45:55 PM
|
The answer is: atolboo@asrock-pardus ~ $ LANG=de_DE idjc Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/idjcgui.py", line 86, in <module> from ln_text import ln File "/usr/lib/python2.5/site-packages/idjc/ln_text.py", line 106, in <module> ln = _set() File "/usr/lib/python2.5/site-packages/idjc/ln_text.py", line 103, in _set return getattr(gns, lev)() File "/usr/lib/python2.5/site-packages/idjc/ln_text.py", line 57, in __init__ self._load_text(cls) File "/usr/lib/python2.5/site-packages/idjc/ln_text.py", line 39, in _load_tex t mod = __import__(modulename) ImportError: No module named nl_NL_text atolboo@asrock-pardus ~ $
|
|
|
|
|
2248
|
General / Wish list / Re: [SOLVED] IDJC / Icecast
|
on: November 11, 2008, 13:43:45 PM
|
........ give this pisi a test, does it install and function as expected?
No it doesn't even start after installation.  The output in a Konsole: atolboo@asrock-pardus ~ $ idjc Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/idjcgui.py", line 86, in <module> from ln_text import ln File "/usr/lib/python2.5/site-packages/idjc/ln_text.py", line 106, in <module> ln = _set() File "/usr/lib/python2.5/site-packages/idjc/ln_text.py", line 103, in _set return getattr(gns, lev)() File "/usr/lib/python2.5/site-packages/idjc/ln_text.py", line 57, in __init__ self._load_text(cls) File "/usr/lib/python2.5/site-packages/idjc/ln_text.py", line 39, in _load_text mod = __import__(modulename) ImportError: No module named nl_NL_text atolboo@asrock-pardus ~ $
|
|
|
|
|
2250
|
Assistance / Installing Pardus / Re: Correct version
|
on: November 09, 2008, 12:13:37 PM
|
....... They get stuck at the beginning after selecting the first option in the boot manager.
Is it the first option from the Language selection screen in the Wiki page? ..... I did a checksum for both and they were ok. So I'm guessing the cd were bad or the images were bad.
When you did a checksum test as described in point2 of this page (when using Windows) or when using K3b (Linux) , the downloaded .iso file isn't the problem. Did you use the verify option of the burner software?
|
|
|
|
|
|