canmove, Confirmed users
1,394
edits
ReleaseEngineering/PuppetAgain/Packages: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/PuppetAgain/Packages (view source)
Revision as of 20:52, 2 September 2014
, 2 September 2014→Ubuntu: Adding New Packages
| Line 273: | Line 273: | ||
done | done | ||
</pre> | </pre> | ||
in that directory to update the apt indexes -- in this case for both precise (12.04) and trusty (14.04). Don't forget to run ''puppetmaster-fixperms'' afterward to make sure permissions are correct. | in that directory to update the apt indexes -- in this case for both precise (12.04) and trusty (14.04). It's best to put this in <tt>update.sh</tt> in the root of the repo so that the next person to update the repo can do the same. You might want to add or remove "-updates" from the script, or change "all" to some other section. | ||
Don't forget to run ''puppetmaster-fixperms'' afterward to make sure permissions are correct. | |||
If you added a new repository, you'll need to refer to it from the puppet configs. Add a clause to ''modules/packages/manifests/setup.pp'', either a regular ''packages::aptrepo'' if the repo should be avialable on every host (like openssh) or a virtual one (prefixed with ''@'') if it should only be available on some hosts. Only installing the repo on some hosts limits the carnage if something goes wrong with the repo. | If you added a new repository, you'll need to refer to it from the puppet configs. Add a clause to ''modules/packages/manifests/setup.pp'', either a regular ''packages::aptrepo'' if the repo should be avialable on every host (like openssh) or a virtual one (prefixed with ''@'') if it should only be available on some hosts. Only installing the repo on some hosts limits the carnage if something goes wrong with the repo. | ||