Security updates are not recognized as security-critical and not auto-installed [$50]
Bug #1404049 reported by
Sergey "Shnatsel" Davidoff
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
elementary OS |
Fix Released
|
High
|
Cody Garver |
Bug Description
elementary OS Freya does not recognize security updates as security-critical and therefore never auto-installs them though unattended-
This seems to be different from the issue we had in Luna, which would detect the updates but not install them.
Testcase:
$ /usr/lib/
320 packages can be updated.
0 updates are security updates.
Changed in elementaryos: | |
assignee: | nobody → Cody Garver (codygarver) |
status: | Triaged → In Progress |
Changed in elementaryos: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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.