#13 Crashing when I run the program missing setup file

After installing I get this error:

$ libray -h
Traceback (most recent call last):
  File "/usr/local/bin/libray", line 4, in <module>
    __import__('pkg_resources').run_script('libray==0.0.9', 'libray')
  File "/usr/lib/python3.11/site-packages/pkg_resources/__init__.py", line 672, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/usr/lib/python3.11/site-packages/pkg_resources/__init__.py", line 1460, in run_script
    raise ResolutionError(
pkg_resources.ResolutionError: Script 'scripts/libray' not found in metadata at '/usr/local/lib/python3.11/site-packages/libray-0.0.9.dist-info'

@asdfdf34 Interesting, how did you install? Via pip, AUR, or manually?

I followed the steps found under "Manually"

@asdfdf34 Sorry about that, I realize now the manual version is a little outdated since libray started packaging the keys after some of the services hosting them disappeared. I was meaning to fix this but the pip and the AUR version works and few people seem to install manually.

If you still want to build it manually you'll probably have to do this:

1. Download https://archive.org/download/sony-playstation-3-disc-keys-dat-cuesheets/Sony%20-%20PlayStation%203%20-%20Datfile%20%283590%29%20%282021-06-05%2001-59-33%29.zip
2. Download https://archive.org/download/sony-playstation-3-disc-keys-dat-cuesheets/Sony%20-%20PlayStation%203%20-%20Disc%20Keys%20%283388%29%20%282021-06-05%2001-59-33%29.zip
   • These are the redump keys.
3. Unzip them and move all *.key files into tools/keys/ (you'll have to make this keys folder) and the *.dat file into the root of tools/
4. run python keys2db.py from the tools folder - this will build the database that is distributed in the pip package, the AUR package builds this itself (see here)
   • Now you finally have the keys, and you can build manually
5. run python setup.py build
6. finally sudo python setup.py install

However, I see now that pkg_resources is deprecated, so libray will display a warning but it will still work.

I'm working on 1.0.0 which is packaged in a different way, but I'm not done yet.

Thanks for looking at it, I'll look forward to your update and leave the ticket over and defer to you to close it.

No problem, I recommend the pip package in the meanwhile :)