Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


reprepro (18) Versions 0.4.2

Installs/Configures reprepro for an apt repository

cookbook 'reprepro', '= 0.4.2', :supermarket
cookbook 'reprepro', '= 0.4.2'
knife supermarket install reprepro
knife supermarket download reprepro
Quality 57%

reprepro Cookbook

Build Status Cookbook Version

Sets up an APT repository suitable for using the reprepro tool to manage distributions and components.

See the reprepro documentation for more information about reprepro itself, including the man(1) page in the package.



  • Debian/Ubuntu


  • Chef 11+


  • build-essential
  • nginx
  • apache2

You'll need to generate the PGP key separately and provide the data in the databag.


Attributes in this cookbook are set via the default recipe with data from the data bag. The following attributes are used, in the reprepro namespace.
- fqdn - the fqdn that would go in sources.list
- description - a description of the repository
- pgp_email - the email address of the pgp key
- pgp_fingerprint - the finger print of the pgp key

Data Bag based repository

Create a data bag to store the repository information. It should be named reprepro. The recipe uses the main data bag item.

  "id": "main",
  "fqdn": "",
  "repo_dir": "/srv/apt",
  "incoming": "/srv/apt_incoming",
  "description": "APT Repository for our packages.",
  "codenames": [
    "lucid", "hardy", "sid", "squeeze", "lenny"
  "allow": [
    "unstable>sid", "stable>squeeze"
  "pgp": {
    "email": "",
    "fingerprint": "PGP Fingerprint for the key",
    "public": "-----BEGIN PGP PUBLIC KEY BLOCK-----\n-----END PGP PUBLIC KEY BLOCK-----\n",
    "private": "-----BEGIN PGP PRIVATE KEY BLOCK-----\n-----END PGP PRIVATE KEY BLOCK-----\n"
  "pulls": {
    "name": "sid",
    "from": "sid",
    "component": "main"
  "architectures": [
  • fqdn: the fully qualified domain name of the apt server, used in
  • in the Apache vhost template and as the Origin in the distributions
  • configuration. Also saved to the node as
  • node['reprepro']['fqdn].
  • repo_dir: directory on disk where reprepro will serve the packages
  • incoming: the incoming directory, used in the incoming
  • configuration.
  • description: description about the repository, also saved to the
  • node as node['reprepro']['description'].
  • codenames: array of codenames to set up for the repository, used
  • with allow for the Allow directive in the incoming configuration
  • allow: [optional] array of additional codenames to use in the incoming
  • configuration
  • pgp: hash of options for the pgp setup. the
  • pgp['email']: email address of the signing key
  • pgp['fingerprint]: fingerprint of the PGP key
  • pgp['public]: the public PGP key, should be a single line
  • (replace line endings with \n)
  • pgp['private]: the private PGP key, should be a single line
  • (replace line endings with \n)
  • pulls: hash used in the pulls configuration.
  • architectures: array of architectures to create in distributions configuration

Attribute based configuration

Configuration of the repository can also be driven via attributes. The same keys available for the data bag are available via node attributes with the exception of the pgp hash. Using attribute based configuration will have a PGP key pair auto generated on the node when it is built.

License & Authors

Copyright:: 2013-2015, Chef Software, Inc

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

reprepro Cookbook CHANGELOG

This file is used to list changes made in each version of the reprepro cookbook.

v0.4.2 (2015-11-20)

  • Remove Opscode/Chef as the maintainer.
  • Updated Travis to run full integration tests with kitchen-docker
  • Added Chef default .rubocop.yml file and resolved all warnings
  • Reformatted readme and set the minimum required Chef release to 11.0
  • Added basic Chefspec to test the converge
  • Add chefignore to limit files uploaded to the Chef server
  • Updated Berksfile format and removed yum, which wasn't actually required
  • Removed the Chef contributing doc that isn't valid anymore
  • Updated development deps in the Gemfile
  • Update .gitignore to the chef default


  • Allow option to use nginx (thanks gilles)


  • COOK-3545 - Support multiple distribution releases


  • [COOK-2111] - Add LWRP for reprepro interactions. Allow attribute driven configuration


  • [COOK-922] - add allow to data bag
  • Update the readme with data bag info

Collaborator Number Metric

0.4.2 passed this metric

Contributing File Metric

0.4.2 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Foodcritic Metric

0.4.2 failed this metric

FC043: Prefer new notification syntax: reprepro/recipes/nginx.rb:25
FC059: LWRP provider does not declare use_inline_resources: reprepro/providers/deb.rb:1
FC075: Cookbook uses to save partial node data to the chef-server mid-run: reprepro/recipes/default.rb:41
Run with Foodcritic Version 11.1.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric

0.4.2 passed this metric

No Binaries Metric

0.4.2 passed this metric

Testing File Metric

0.4.2 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must contain a file

Version Tag Metric

0.4.2 passed this metric