fix(flaresolverr): use rm -f for google-chrome.list (Debian 13 Trixie)#13580
Closed
WickedSick31 wants to merge 1 commit intocommunity-scripts:mainfrom
Closed
fix(flaresolverr): use rm -f for google-chrome.list (Debian 13 Trixie)#13580WickedSick31 wants to merge 1 commit intocommunity-scripts:mainfrom
WickedSick31 wants to merge 1 commit intocommunity-scripts:mainfrom
Conversation
On Debian 13 "Trixie", google-chrome-stable's postinst detects the pre-existing deb822 .sources file created by setup_deb822_repo and skips writing the legacy /etc/apt/sources.list.d/google-chrome.list. The subsequent unconditional `rm` then fails with exit 1, tripping catch_errors and aborting the install at line 32. Switch to `rm -f` so the cleanup is a no-op when the file was never written, while still removing it on hosts where postinst did create it.
CrazyWolf13
approved these changes
Apr 8, 2026
michelroegl-brunner
requested changes
Apr 8, 2026
Member
michelroegl-brunner
left a comment
michelroegl-brunner
left a comment
There was a problem hiding this comment.
We have a PR Temlate for a Reason, restore that and fill it out poperly before we can continue here...
1 task
Member
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
✍️ Description
Fix FlareSolverr installer aborting at line 32 of
install/flaresolverr-install.shwith:Root cause: On Debian 13 "Trixie",
google-chrome-stable's postinst script detects the pre-existing deb822.sourcesfile written earlier bysetup_deb822_repoand skips writing the legacy/etc/apt/sources.list.d/google-chrome.list. The subsequent unconditionalrmthen fails because the file never existed, andcatch_errorsaborts the install.Fix: Switch
rm→rm -fso the cleanup is a no-op when the file is absent, while still removing it on hosts/edge cases where postinst did create it. Also updated the inline comment to explain the Trixie behavior.🔗 Related Issue
Fixes #13585
✅ Prerequisites (X in brackets)
apt updateinside the container produces no duplicate-repo warnings (only the.sourcesfile remains).rm -fis a drop-in replacement of the existingrmwith identical scope.🛠️ Type of Change (X in brackets)
README,AppName.md,CONTRIBUTING.md, or other docs.