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

libioc's pkg feature can conflict badly with its provisioning feature #765

Open
5 tasks
igalic opened this issue Nov 16, 2020 · 1 comment
Open
5 tasks

Comments

@igalic
Copy link
Collaborator

igalic commented Nov 16, 2020

Make sure to follow and check these boxes before submitting an issue! Thank you.

  • Supply print(libioc.VERSION)
  • Supply the commands used, along with any steps to recreate it.
  • Provide the output from the command you issued.
  • Supply what you expected the result or output to be
  • Checked that the problem has not already been fixed on master if using
    a stable release.

when installing packages during the provisioning stage by the provisioning tool of choice (puppet) our libioc pkg repo is active — because the provisioning tool may have needed to be installed into the jail first

but our repo being latest, and FreeBSD's repo being quarterly, but listed first makes for a perfect recipe for conflicts

there's a few ways this can be resolved:

  • switch to quarterly
  • offer a choice between latest and quarterly
  • disable the FreeBSD default repo
  • instruct people on pitfalls with warning messages of they use pkg or provision sub commands
@igalic
Copy link
Collaborator Author

igalic commented Nov 16, 2020

Puppet has a module for that! https://forge.puppet.com/modules/puppet/pkgng/readme

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