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

Cannot alter sources file name #8

Open
2 of 7 tasks
threepistons opened this issue Mar 28, 2023 · 1 comment
Open
2 of 7 tasks

Cannot alter sources file name #8

threepistons opened this issue Mar 28, 2023 · 1 comment
Assignees

Comments

@threepistons
Copy link
Collaborator

threepistons commented Mar 28, 2023

The cloud-init files used by our build system and this module both try to add the source for mdatp, but with different names. I can resolve this conflict by parameterising the name of the sources file in the module so that I can set the sources file name in the control repo to match the build system, without altering the default behaviour of this module for anyone else who might use it.

The workflow for this task looks like:

  1. I will raise an issue against the mdatp module,
  2. I add the parameterisation feature,
  3. I tag a new release.
  4. I alter the controlrepo:
    • bump the mdatp module version used in the control repo,
    • set the parameterised source name in Hiera, and
    • add a file resource to remove the old sources file.

The kind of output I see from Apt is

W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/microsoft.list:1 and /etc/apt/sources.list.d/microsoftpackages.list:3
@threepistons threepistons self-assigned this Mar 28, 2023
@threepistons
Copy link
Collaborator Author

threepistons commented Jun 15, 2024

Feature added in 1fd86d1 but not yet tagged for release. I also altered the build system to prevent the conflict in a rather more immediate way, see https://github.com/newcastleuniversity/nuit-linux-imaging/commit/80ee4d51ba70715361960969f231d9b8607e41ca

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

No branches or pull requests

1 participant