Unable to install sselph scraper

BuZz

@Sanschan Latest version of RetroPie is 4.2.3 - if the version in RetroPie-Setup is lower you should update (via update all packages).

The scraper can be automatically installed from optional packages.

Sanschan

Okay, obviously my google fu was weak yesterday, as I thought that 3.7 was the most current version. But I did update yesterday before trying, so I'm confident I was completely up to date and, as I wrote, I was unable to install the scraper in the suggested way.
I did however manage it by now. While working directly on the Pi, I still had no luck, but via SSH (which didn't work over Wifi, only once I plugged in an ethernet cable) it did work. From the menu even.
So for now, my problem is solved.

Nevertheless, my second question is still up. I did order a USB stick and would like to migrate my roms asap. What do I have to take into account scraping-wise?

BuZz

@Sanschan Nothing if you follow the instructions in the manual about using USB for storage.

allenpie

Sanschan

You should just hit F4 and then run the retropie setup

This way it's run from a root directly and not within Emulation Station

Make sure you are connected to the interenet via cable and run the sselph scraper from the retropie setup command line menu
This is the best way to run it.

donclark

Confirmed not working for me either in 4.2 - https://retropie.org.uk/forum/topic/10229/unable-to-install-sselph-scraper/5

megasweet

Not working for me in 4.2.3. My error log looks nearly identical to this reddit thread that led me here- https://www.reddit.com/r/RetroPie/comments/60gb4d/how_to_install_sselphs_scraper_via_retropie/

sselph

@megasweet The root of the "package crypto/sha1: unrecognized import path "crypto/sha1" (import path does not begin with hostname)" type issues is that the GOROOT isn't set correctly and Go can't find its own packages. Considering that the script is supposed to be installing its own copy of Go then use it, it seems odd.

Was this a vanilla install? Did you install your own copy of Go like in that reddit post? Did you go through the UI or invoke things by passing the parameters to the script?

RedBatman

@allenpie But if you go into Retropie setup from emulation station its the same thing right? It shouldn't cause any harm sine I have been updating my package and retropie scripts from the Retropie menu and then going into Retropie setup script. I just found out about this new sselph today.

donclark

@donclark
I just found a way to manually do this:
2100 go get github.com/sselph/scraper
2101 go build github.com/sselph/scraper
2102 cd /opt/retropie/supplementary/
2104 mkdir scraper
2106 cd scraper
2108 mv ~/scraper .
you will see scraper installed, but don't reconfigure it, you can probably scrape some stuff with it like this.
This was posted 3 hours ago here:
https://www.reddit.com/r/RetroPie/comments/60gb4d/how_to_install_sselphs_scraper_via_retropie/djzc5fk/

andrewpelt

My issue, it seems, was that Go was 1.3.3 and the latest scraper required 1.7 to build. This was not obvious via RetroPie-Setup.

Similar to donclark, I was able to install 1.8 in /usr/local/, as well as scraper, and run it using absolute paths to these versions from the command line.

(I could also have tried to upgrade the existing Go install.)

sselph

@andrewpelt The new version of RetroPie-Setup is supposed to download a new version of go to a non-default location and us it to build the scraper. I did this to hopefully make it more stable. Go has a guarantee that new versions won't break any old code. It only adds new features and fixes bugs, but there wasn't a guarantee that code I depended on wouldn't take advantage of one of these newer features and break everything.

In Go 1.6 they added the ability to copy all the dependent libraries in to my repo so now it will always build. I can't explain why these issues are popping up.