How to handle renamed or removed package versions from package manager (yum, apt, etc)?

asked 2017-05-01 17:10:14 -0600

canoeguide gravatar image

A common problem for which my google searching is failing me is this:

  1. Create a puppet manifest to install specific versions of needed packages.
  2. At some point the public package repository expires the version or renames the package.
  3. Someone runs the manifest and we discover the missing or renamed or updated package in the repository, and have to quickly update or otherwise modify our manifest.

I would like ideas on how to avoid step 3, and to a lesser extent, step 2. Is hosting our own package repository or bundling rpm's etc with the manifest the only way to prevent this?

edit retag flag offensive close merge delete



Assuming linux, you could mirror the repository internally That way you can control what files are a part of the repository.

bschonecker gravatar imagebschonecker ( 2017-05-02 06:17:38 -0600 )edit

It is difficult for Puppet to know that a package was renamed. For example, if a package "foo" was renamed to "bar," a computer will have a hard time knowing this unless we tell it.

WhatsARanjit gravatar imageWhatsARanjit ( 2017-05-03 23:18:35 -0600 )edit