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

Add Debian package pin to stop the version changing on apt upgrade #415

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ddryden
Copy link

@ddryden ddryden commented May 28, 2019

When on Debian and a package version is specified we should also create a Debian package pin to stop apt upgrade from changing the version just for the next puppet run to change it back.

@puppetcla
Copy link

Waiting for CLA signature by @ddryden

@ddryden - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppet.com/

Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppet.com/community/trivial_patch_exemption.html

@puppetcla
Copy link

CLA signed by all contributors.

@gimmyxd gimmyxd requested a review from a team July 31, 2019 07:50
@@ -62,6 +62,11 @@
$_package_version = $package_version
} else {
$_package_version = "${package_version}-1${::lsbdistcodename}"
apt::pin { "pin ${::puppet_agent::package_name} package":
packages => $::puppet_agent::package_name,
priority => 1000,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In order to support downgrade, my understanding is that priority should be 1001: https://linux.die.net/man/5/apt_preferences

@seoester
Copy link

How is this PR going?
Is the requested change the only thing blocking the merge?
The CI seems to be failing because of missing dependencies in the test suite.

I'd love to see this merged & released :)

@ciprianbadescu
Copy link
Contributor

@seoester, there is small change needed from @ddryden

@seoester
Copy link

seoester commented Sep 27, 2019

@ciprianbadescu thanks for the quick response.

Would you mind if I replicated the PR and performed the change to speed things along?

@ciprianbadescu
Copy link
Contributor

@ddryden
Copy link
Author

ddryden commented Oct 13, 2019

Sorry for being slow to respond.

Your right 1001 would be a better priority.

I don't know my way around the test's could you link some documentation?

https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/master/CONTRIBUTING.md seems to have a Testing section listed in the table of contents but does not exist in the document.

@seoester
Copy link

@ddryden, I replicated your PR and we have been discussing the changes in #441.

@ciprianbadescu ciprianbadescu changed the base branch from master to main September 15, 2020 10:53
@CLAassistant
Copy link

CLAassistant commented Sep 1, 2021

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@seoester
Copy link

Implementation is going a different route, and this PR can likely be closed #441 (comment).

@joshcooper
Copy link
Contributor

@seoester Our puppetN-release packages on apt.puppet.com now install a preferences file (see puppetlabs/puppetlabs-release@ecf2c85#diff-4fbc9b1630d785c70cd453b814c99fa693faae74aabf983473e85ef200b3b32d) This was done because Debian and Ubuntu have started publishing puppet-agent packages with the same name as ours. Given that I'm thinking this is no longer needed?

@seoester
Copy link

seoester commented Nov 6, 2024

@joshcooper, thanks for the ping after so much time.

The pinning you are referencing pins the Apt Source/Repo of the puppet-agent package.
The pinning proposed in this PR (and my PR #441) pins the specific version of the puppet-agent package, so that apt upgrade does not unintentionally bump the package to a new version.

I believe this specific PR can be closed in any case. That's because the team wanted to go a different route, using a new feature of the dpkg provider rather than apt pinning: #441 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants