# Troubleshooting ## Checking for Broken Packages In general it can be useful to check to see if packages are broken. This may happen if you manually install a program or change a file, or a rogue program overwrites something. ```sh sudo eopkg check | tee check.log ``` The output of the check will also be stored in `check.log` so you don't have to rerun it. ## Reinstalling a Broken Package You can `grep` the file generated by the broken package check above and use those entries to know what to reinstall: ```sh grep 'Broken|file:' check.txt ``` The reinstall flag can be used to force `eopkg` to install an already-installed package: ```sh sudo eopkg install --reinstall broken-package ``` ## Rebuilding the Database Remove cache and rebuild database:[^1] ```sh sudo eopkg dc && sudo eopkg rdb ``` # Known Issues ## OpenSSL >[!SUCCESS] Fixed! > **Last Updated 2024:** > > The OpenSSL issue seems to have been a one-time thing in 2023. Like some others, I ran into issues updating [[OpenSSL]] via `eopkg` due to conflicting files. I'm not sure the origin of the issue, but rebuilding the database and just updating the package individually seemed to resolve it. # References [^1]: https://github.com/xjy37/xjy37/issues/3