Hi Eddie,
190ubuntu0.1 suggests that you are on Ubuntu bionic or something derived from that.
The package needs to know where it runs, and it does so via /etc/os-release
# we have /etc/os-release, use it
if [ -r /etc/os-release ]; then
. /etc/os-release DISTRO="${ID:-unknown}" RELEASE="${VERSION_ID:-unstable}" # unstable doesn't have this field
Based on that in /usr/share/postgresql-common/supported-versions there is a mapping which default now applies.
That could for example be
DISTRO=Ubuntu
RELEASE=18.04
Which would map to postgresql 10.
In your case that isn't true. You are not running Ubuntu but a derivative.
If that decides to change these values then packages might stumble over that.
There is nothing to fix here, it is part of KDE-Neon as a downstream to maintain a Delta for this just as Ubuntu does to Debian and Debian does to upstream.
Hi Eddie,
190ubuntu0.1 suggests that you are on Ubuntu bionic or something derived from that.
The package needs to know where it runs, and it does so via /etc/os-release
# we have /etc/os-release, use it
DISTRO= "${ID:- unknown} "
RELEASE= "${VERSION_ ID:-unstable} " # unstable doesn't have this field
if [ -r /etc/os-release ]; then
. /etc/os-release
Based on that in /usr/share/ postgresql- common/ supported- versions there is a mapping which default now applies.
That could for example be
DISTRO=Ubuntu
RELEASE=18.04
Which would map to postgresql 10.
In your case that isn't true. You are not running Ubuntu but a derivative.
If that decides to change these values then packages might stumble over that.
There is nothing to fix here, it is part of KDE-Neon as a downstream to maintain a Delta for this just as Ubuntu does to Debian and Debian does to upstream.