Skip to content

Refer to older OS versions as "end-of-standard-support" instead of "end-of-life" #426

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stevietv merged 3 commits into from
Dec 16, 2025
Merged

Refer to older OS versions as "end-of-standard-support" instead of "end-of-life" #426

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
da740ff
adjust EOL wording
CobreDev Nov 30, 2025
16e118b
Merge branch 'master' into master
stevietv Dec 16, 2025
27f7ea0
Merge branch 'master' into master
stevietv Dec 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions lidarr/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -395,10 +395,10 @@ chmod -R 0644 *

## Lidarr won't start on Debian 11 or older systems due to SQLite version

> This workaround is only for older end-of-life systems with outdated GLIBC/SQLite versions. This is not applicable to systems with SQLite corruption issues.
> This workaround is only for older end-of-standard-support systems with outdated GLIBC/SQLite versions. This is not applicable to systems with SQLite corruption issues.
{.is-warning}

Lidarr v3+ uses SQLite from SourceGear.sqlite3, which requires newer GLIBC versions and may cause compatibility issues on older end-of-life systems including Debian 10, Debian 11, Synology DSM, Ubuntu 18, and Ubuntu 20. If you encounter SQLite-related errors (not corruption) on these platforms, you can force Lidarr to use your system's native SQLite library instead, which is compatible with your GLIBC version.
Lidarr v3+ uses SQLite from SourceGear.sqlite3, which requires newer GLIBC versions and may cause compatibility issues on older end-of-standard-support systems including Debian 10, Debian 11, Synology DSM, Ubuntu 18, and Ubuntu 20. If you encounter SQLite-related errors (not corruption) on these platforms, you can force Lidarr to use your system's native SQLite library instead, which is compatible with your GLIBC version.

### Solution

Expand Down
4 changes: 2 additions & 2 deletions prowlarr/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -314,10 +314,10 @@ To request a feature for Prowlarr, first search on GitHub to ensure no similar r

## Prowlarr won't start on Debian 11 or older systems due to SQLite version

> This workaround is only for older end-of-life systems with outdated GLIBC/SQLite versions. This is not applicable to systems with SQLite corruption issues.
> This workaround is only for older end-of-standard-support systems with outdated GLIBC/SQLite versions. This is not applicable to systems with SQLite corruption issues.
{.is-warning}

Prowlarr v2.1.5.5216+ uses SQLite from SourceGear.sqlite3, which requires newer GLIBC versions and may cause compatibility issues on older end-of-life systems including Debian 10, Debian 11, Synology DSM, Ubuntu 18, and Ubuntu 20. If you encounter SQLite-related errors (not corruption) on these platforms, you can force Prowlarr to use your system's native SQLite library instead, which is compatible with your GLIBC version.
Prowlarr v2.1.5.5216+ uses SQLite from SourceGear.sqlite3, which requires newer GLIBC versions and may cause compatibility issues on older end-of-standard-support systems including Debian 10, Debian 11, Synology DSM, Ubuntu 18, and Ubuntu 20. If you encounter SQLite-related errors (not corruption) on these platforms, you can force Prowlarr to use your system's native SQLite library instead, which is compatible with your GLIBC version.

### Solution

Expand Down
4 changes: 2 additions & 2 deletions radarr/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -445,10 +445,10 @@ This could be because your indexer poorly matched it, or the uploader didn't nam

## Radarr won't start on Debian 11 or older systems due to SQLite version

> This workaround is only for older end-of-life systems with outdated GLIBC/SQLite versions. This is not applicable to systems with SQLite corruption issues.
> This workaround is only for older end-of-standard-support systems with outdated GLIBC/SQLite versions. This is not applicable to systems with SQLite corruption issues.
{.is-warning}

Radarr v6+ uses SQLite from SourceGear.sqlite3, which requires newer GLIBC versions and may cause compatibility issues on older end-of-life systems including Debian 10, Debian 11, Synology DSM, Ubuntu 18, and Ubuntu 20. If you encounter SQLite-related errors (not corruption) on these platforms, you can force Radarr to use your system's native SQLite library instead, which is compatible with your GLIBC version.
Radarr v6+ uses SQLite from SourceGear.sqlite3, which requires newer GLIBC versions and may cause compatibility issues on older end-of-standard-support systems including Debian 10, Debian 11, Synology DSM, Ubuntu 18, and Ubuntu 20. If you encounter SQLite-related errors (not corruption) on these platforms, you can force Radarr to use your system's native SQLite library instead, which is compatible with your GLIBC version.

### Solution

Expand Down