I did some research today. I think this bug affects all LTS releases.
As Nick Rosbrook (enr0n) suggested we can use $VERSION to parse the version id with the point release number like this $(echo "$VERSION"| grep -o -s -E '^[0-9\.]+')
, but this would still not fix the bug for all LTS users who haven't the most up to date /etc/os-release file.
For example:
When 22.04.02 gets released; a user that hasn't updated yet still has an /etc/os-release file with the value VERSION="22.04.1 LTS (Jammy Jellyfish)"
This would still result in a broken link.
Alternative solutions would be:
1. using a web-crawler that looks for the latest release url (overcomplicated)
2. setting up a redirection from the "broken" url to the correct one
Alternative 2 would result in an instant-fix without needing the user to update and is simple. I have to find out who I would need to ask for that.
I did some research today. I think this bug affects all LTS releases.
As Nick Rosbrook (enr0n) suggested we can use $VERSION to parse the version id with the point release number like this $(echo "$VERSION"| grep -o -s -E '^[0-9\.]+')
, but this would still not fix the bug for all LTS users who haven't the most up to date /etc/os-release file.
For example:
When 22.04.02 gets released; a user that hasn't updated yet still has an /etc/os-release file with the value VERSION="22.04.1 LTS (Jammy Jellyfish)"
This would still result in a broken link.
Alternative solutions would be:
1. using a web-crawler that looks for the latest release url (overcomplicated)
2. setting up a redirection from the "broken" url to the correct one
Alternative 2 would result in an instant-fix without needing the user to update and is simple. I have to find out who I would need to ask for that.