RetroPie-manager has been removed since it's been un-maintained for years and it's not compatible with Python3. The original project repository has been deleted years ago and we kept a copy under RetroPie's Github account.
You can still find it at https://github.com/retropie/retropie-manager/ if you wish to try to make it work/install it.

Please add some info about your setup (like detailed in https://retropie.org.uk/forum/topic/3/read-this-first) when opening a support topic.

You can uninstall the .deb package manually, but to skip the post-install/post-remove scripts, look for the /var/lib/dpkg/info/<package-name>.postrm or /var/lib/dpkg/info/<package-name>.postinst files and remove them before manually removing the .deb package.

The issue will be fixed upstream, one way or the other.
As a temporary workaround (until this fix is merged), you can try installing libhidapi-dev manually and then re-run the installation from the RetroPie-Setup script.

@Botspot said in What APT packages are installed when I run the installer?:

Is there a centralized place I can look to get this installed package list?

No, there isn't a central list of packages. As I said in the Github issue you opened, each package that is part of RetroPie has it's own list of dependencies, which is automatically installed when that particular package is installed. The dependencies are declared in the module's depends function. Since the user can install or remove any package, the list of dependencies can change.

A base installation will install the 'core' and 'main' packages, you can see here, you could get the list of dependencies for the packages in those 2 sections and consider them a minimum list of dependencies. Some of them might already be installed on the system, so when removing RetroPie you might take that into account.

EDIT: the initial dependencies for the RetroPie-Setup script to work are listed in the Manual installation page.

@barbudreadmon
Yeah, it was the principality of it, saving and loading game specific options in a global config. I think I could not get either the macros or cabinet settings to work this way, rendering them beyond completely pointless. I think the actual cabinet settings for the retroarch core are saved in /roms/neogeo/FBA/ along with high score, and I don't know what was up with the macros.

@retrogamer78 Kodi is installed from a Debian-type repository, so you can set the package status to hold to prevent automatic updates.

echo kodi hold | dpkg --set-selections

The 001, 002 etc extensions means that they are sequential parts of the same compressed file. Try opening the 001 file with 7Zip, or something else that reads 7Z files.

Brilliant,
Thanks for letting me know so quickly. I will install and configure these emulators outside of Retropie using sudo apt-get install.
I will keep tracking this in case they may be ported to the XU4 in the future.

Thanks all!

@capeman I suppose you are right. I have just got into a habit of updating "ALL" because to me that is somehow better, or what I should do... I understand that I need to do something different, not the software. I know how to hold packages that have binaries, I was just wondering if it was the same for those that don't. I guess I was just thinking about it a bit back to front. Thanks.

Hello fellows.

I would like to say thanks! The cec-utils package is pretty handy. The udev rules are perfect!

The only addition I've made on my arcade build was adding a turn off monitor.sh script in RetroPie Menu.

#!/bin/bash # turn off monitor.sh ################# # Actually puts the monitor on stand by mode. echo standby 0 | cec-utils -s -d 1

@Rydra IMHO putting it on github and providing a script to install it is the best way to provide it to RetroPie users.

@SkittleBrau79 you were installing packages before and your internet connection broke or an upgrade was interrupted or something. Impossible to say.

@LasagnaDevil You have provided no information about your setup as requested (Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first)

Assuming you are on a PC, just do a basic install first - which installs the base set of packages, you can then install any extra ones. It's only something you have to do once.

PR is a Pull Request - when you contribute back to the project - You said "I don't think it'd be that hard to implement, honestly." so I said you could contribute back. I had assumed you based that comment on some internal knowledge of the codebase. Otherwise it doesn't mean a lot :)

@vbs It's not a bad idea (I have thought a lot about it - especially when I was doing the reorganisation of the retropie-setup menus), I just think it's really only retroarch which would benefit (maybe a couple of others) - so it's whether the work is worth it. I'm pretty certain it will be me who has to maintain this long term too. I'll see how retroarch develops though and reconsider it in the future if it seems required.

would it be relationed with __persistent_repos of the 4831258dbaf6d8af93abff513cb7c10b972df488 commit?