I have good news and a bad news.
The good news is, I downloaded the fork.

The bad news is, not only it doesn't work for me, it caused me actual issues :/
It stright out froze my entire X org, or more precisely, everything except for the mouse pointer ( kind of a first for me in a way, usually when X org freezes it's either "everything" or "stright crash to TTY"/" X org died " ).
I had to kill underlying VT, from another TTY of course.
Tested several times, VT tested:
- KDE Konsole
- urxvt

I even tested with LC_ALL=C, didn't help.

It gets stuck on importing python modules, it takes FOREVER ( the most I left this for was like a minute or 2, and no - leaving it for longer is not an answer - a properly written python script should NEVER lock me out of X org, SOMETHING is just wrong somewhere, be it my setup or something in the script ).

What I also find bogus is that it seems to be copying from somewhere in my sys-python dirs to it's own dir ( to the dir I run the script from ) - it copies the modules it's supposed to import - for some weird reason.
Here note that the OG eddie3 last version does NOT do that ( I tested same day, on EXACT same system-upgrade version, so exact same packages ).

Unfortunatelly due to this I just can't use this atm, and I will just have to use the OG outdated eddie3 version :/

Before I killed VT, I briefly saw output saying things such as:
( retyping from phone photo, since you know, couldn't make an scr nor copy-paste on a frozen X org... )
line 3: from: command not found
line 4: from: command not found
line 5: from: command not found
line 7: __appname__: command not found
line 8: __author__: command not found
line 9: __version__: command not found
line 10: __url__: command not found

( no more output of any kind, as at that point I killed VT, also note that this "output" showed like some "zombie X org undead twitches" as the X org was frozen, but it occassionally just showed all this at once only to freeze back instantaneously )

I think the script also pinned 1 core to 100%.

I don't currently have an GitHub account, and I WON'T make one impromptu any time soon.
If either you or Kalanyr want more tech details, pls PM me, as I simply won't provide pkg versions used in public due to security concerns ( knowing exact timestamp when I upgraded my sys would allow ppl to narrow down possibilities, it's not about YOU two, it's about "certain others", simply, I don't want to share this info in public ).

I am not in any way involved in gogrepoc development; I am just trying to assist you user-to-user.

I am not too familiar with linux or python, but as your issues seem pretty fundamental, one question comes to mind: Did you install the required libs before running gogrepoc?

Here is the command line I used for installing all the required libs (on windows; assumes you have pip already installed):
python -m pip install html5lib html2text pyOpenSSL requests six

Also, which version of python are you using?

Guys, please don't quote the entirety of long posts, if you can +_+

I checked, I have all required dependencies.
Also, I don't use pip unless I have to ( pip is a pandora box, it causes issues that stack up and cascade across a system ). The dependencies I have are installed from system repo, and they are in versions above the ones cited in the fork's GH page.

I have both python2 and python3 installed.
I can PM you exact versions.

Also, I don't seem to be having any issues with any other python-dependent software.
Tbh I think this is the FIRST ever python soft that caused me such issues o__O

It's working for me on Debian with only python3 installed. I've also installed python3-openssl python3-html5lib python3-html2text python3-requests python3-six from the reop. Are you runnung it using python2 or python3?

I'm using this version of the script:
https://raw.githubusercontent.com/Kalanyr/gogrepoc/master/gogrepoc.py

I'm just a fellow user too so can't really help much but Kalanyr will likely arrive to offer some advice at some point :-)

I'm running it by directly calling the script name from dir, you know:
./some-name.py
I ASSUMED it was written well enough to pick py ver by itself, but maybe I'm wrong.

Ngl, I'm not very fond on debugging it, I got really sus when it froze my entire X org, and I'm not very keen on freezing it again o__O
I will also give you some context:
my system deployment is VERY stable, freezes of X org almost NEVER happen under any circumstances.

You are trying to execute gogrepoc.py directly as a shell script.

Either add at the top of the script

Or run the script from the python interpreter

python gogrepoc.py update ...
python gogrepoc.py download ...

etc.

You know what? That makes sense.
It's been months since I last run the script, and I don't ordinarily run python code directly ( so I guess I have forgotten about the interpreter and all :P ), AND I didn't READ the code of the fork ( whereas previously I DID read the whole code of the OG script ).

I looked at it now, the OG eddie3 HAS the shebang:
#!/usr/bin/env python
meanwhile the fork is missing it entirely.
Probably why invoking eddie3 directly works and for the fork doesn't...

I cannot afford crashing my X org today, and I will be busy most of tomorrow. So I will probably test this again on Saturday.
I will probably run it with xephyr this time, to be safe ( this didn't occur to me originally for some reason ).

In any case, I think Kalanyr should add the shebang ( not sure why it's missing in his fork ? ).

Thank you for suggestion ^__^

Glad someone recognised what was happening! :-)

I've just tried running it directly (in a VM) and got the same error messages as you but no other problems and the system continued to function. Good luck when you try it again :-)

It's missing because it's not compatible with the Windows way of running multiple different python installs and I primarily use Windows (and at the time I removed it it wasn't super reliable on Linux either because you didn't know if unspecified python was 2 or 3 though that's *mostly* resolved now since very few are left running Python 2 as default now that it's officially End of Life )

Just discovered this tool yesterday while searching for a way to backup my installers at home now that I have the drive space for! It is also nice to see that use of theses tool don't seem to be rejected by GOG itself (I guess it save bandwith for them in the long run if part of us have a local copy to use instead?)

Thanks for your great work eddie3 and Kalanyr! You made a process I tried to do manually in the past a lot easier and manageable!

For what I understand after reading a few pages, eddie3 version is currently paused and the recommended one to user is yours Kalanyr? Is the switch from one to another is easy or are the cookie/manifest files incompatibles and need to be remade?

Is there any things to be mindful of when using the tools or switching between them?

I've tried very hard to make it backwards compatible but there's been a lot of changes (including ones by GOG) since so I can't guarantee anything. I *think* everything should just work but let me know if you have issues.

Edit - I do recommend backing up your manifest first of course.

Seems like Trails to Azure has the same file named two different ways (one for 32 bit and one for 64 bit) which is causing circular renaming on clean. Working on this now but it's proving more annoying than I thought.

I've just noticed a potential issue with DLC. I have previously bought (and backed up) Kerbal Space Program and the Breaking Ground expansion.

Yesterday I bought the Making History expansion, but gogrepoc does not recognise that there was anything new to download. It downloaded some other games that had updates flagged, but it did not identify anything new for Kerbal Space Program.

Is this behaviour expected?

EDIT: explicitly forcing an update on the game ID worked, but I would be concerned that people may miss having DLC backed up if this is a general problem.

This is normal, unfortunately, GOG doesn't mark a game that you've bought DLC for as Updated. So the backup won't get done until you either manually do it or the next time you do a full update.