canmove, Confirmed users
1,394
edits
ReleaseEngineering/PuppetAgain/Packages: Difference between revisions
ReleaseEngineering/PuppetAgain/Packages (view source)
Revision as of 20:32, 2 September 2014
, 2 September 2014→Ubuntu: Adding New Packages
(→CentOS: Repositories: fedora repos are long gone) |
|||
| Line 263: | Line 263: | ||
Now, build a custom repository (or possibly two, one for each architecture) on the distinguished master for the purpose. For example, if you're updating openssh, create a new {{PuppetAgain Repo|repos/apt/custom/openssh}}. If the appropriate repo already exists, use it. | Now, build a custom repository (or possibly two, one for each architecture) on the distinguished master for the purpose. For example, if you're updating openssh, create a new {{PuppetAgain Repo|repos/apt/custom/openssh}}. If the appropriate repo already exists, use it. | ||
To build a custom repository, you'll need an Ubuntu system with apt-utils installed. A package builder host will do the trick, but the host's details aren't important. Set up a directory containing the proper packages | To build a custom repository, you'll need an Ubuntu system with apt-utils installed. A package builder host will do the trick, but the host's details aren't important. Set up a directory containing the proper packages under <tt>pool/</tt> (although the nested <tt>o/openssh/</tt> directories are not required), run | ||
<pre> | <pre> | ||
for arch in i386 amd64; do | for arch in i386 amd64; do | ||