fix(debian): avoid adding repositories entries multiple times #314
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Entries are being duplicated as described in * saltstack/salt#60220 and * saltstack/salt#59785 (comment)
javierbertoli
force-pushed
the
fix-duplicated-entries-in-debian-family-repositories
branch
from
82b9a7b
to
8917dce
Compare
myii
requested changes
Mar 2, 2022
There was a problem hiding this comment.
Thanks for this PR, @javierbertoli.
Just one change required, as shown inline.
Would you also mind rebasing the amended commit on top of the latest commit in this formula?
myii
approved these changes
Mar 2, 2022
javierbertoli
deleted the
fix-duplicated-entries-in-debian-family-repositories
branch
|
🎉 This PR is included in version 2.4.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PR progress checklist (to be filled in by reviewers)
What type of PR is this?
Primary type
[build]Changes related to the build system[chore]Changes to the build process or auxiliary tools and libraries such as documentation generation[ci]Changes to the continuous integration configuration[feat]A new feature[fix]A bug fix[perf]A code change that improves performance[refactor]A code change that neither fixes a bug nor adds a feature[revert]A change used to revert a previous commit[style]Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)Secondary type
[docs]Documentation changes[test]Adding missing or correcting existing testsDoes this PR introduce a
BREAKING CHANGE?No.
Related issues and/or pull requests
As described in
repositories entries in the Debian's family are being re-added each time the formula is run.
Describe the changes you're proposing
As proposed here, moved away from
pkgrepoand manage the repository's file withfile.managed.Used the same parameters to keep it backward compatible.
Pillar / config required to test the proposed changes
Debug log showing how the proposed changes work
Documentation checklist
README(e.g.Available states).pillar.example.Testing checklist
state_top).Additional context