Do not treat debian stable-updates as security updates #716
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Debian-updates are pending packages between dot-releases, they are not security updates.
When Debian has a dot-release, for example 8.7, debian-updates is empty. Between 8.7 and 8.8,
updates packages go to debian-updates, and on 8.8, all packages in debian-updates are moved (or replaced) by packages in the main repo, leaving debian-updates empty again.
Security updates are managed outside of this.
I recently added debian-updates to the apt repos on our Debian servers, with the result that all the systems had alarms about missing security updates. All these alarms were false, security updates had been installed, and it was packages in updates they were alarming about. The change to the puppet module was trivial, editing the spec tests was more time consuming :)