Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not treat debian stable-updates as security updates #716

Merged
merged 2 commits into from Nov 6, 2017

Conversation

kbarmen
Copy link

@kbarmen kbarmen commented Nov 3, 2017

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 :)

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.
The previous output just had debian-updates and backports, none
of which are security updates. Adjusted expected results accordingly,
using curl as an example.
@willmeek willmeek merged commit ad43b99 into puppetlabs:master Nov 6, 2017
@willmeek
Copy link

willmeek commented Nov 6, 2017

Thank you @kbarmen for your contribution.

This has been merged into master and should make it into the next release.

Thank you
Will

@LukasAud LukasAud added the bugfix label Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants