Security updates are not recognized as security-critical and not auto-installed [$50]

[Sergey "Shnatsel" Davidoff]

elementary OS Freya does not recognize security updates as security-critical and therefore never auto-installs them though unattended-upgrades, even if the relevant options are selected in software-properties-gtk.
This seems to be different from the issue we had in Luna, which would detect the updates but not install them.

Testcase:
$ /usr/lib/update-notifier/apt-check --human-readable
320 packages can be updated.
0 updates are security updates.

[Levi Voorintholt (piratelv)]

The /usr/lib/update-notifier/apt-check script has an array of repositories that are for security updates. It's using the distro codename returned from the command 'lsb_release -c -s' thus it is using freya instead of trusty.
This makes the script look for a repository named 'freya-security' to be marked as security updates.

I've verified that changing the repository name to 'trusty-security' in the array makes the script show available security updates on 2 freya installs.

[Danielle Foré (danrabbit)]

https://www.bountysource.com/issues/7165055-security-updates-are-not-recognized-as-security-critical-and-not-auto-installed

[Cody Garver (codygarver)]

Attached is a branch in which I attempt to fix this bug by replacing "lsb_release -cs" with "echo trusty". I will not activate the recipe until someone confirms this work and is an appropriate solution.

[Cody Garver (codygarver)]

Our patched lsb provides a --upstream flag, so I have adjusted the code to use that and requested a build.

[Cody Garver (codygarver)]

Tested on an old iso with only the new package updated. Before upgrading update-notifier it reported 0 security updates out of 222. After upgrade it reported 64 out of 222.