apt.conf.d

remove_* was recently changed to always place empty file, but just set
perms if not present, without replace.

Do the same with that option.

- Add template file
- Add pillar example

fix warning on preferences as not managed

[WARNING ] State for file: /etc/apt/preferences - Neither 'source' nor
'contents' nor 'contents_pillar' nor 'contents_grains' was defined, yet
'replace' was set to 'True'. As there is no source to replace the file
with, 'replace' has been set to 'False' to avoid reading the file
unnecessarily.

Now, if file.managed, but when content is not changed (no source,
contents, ...), avoid the warning.

fix iteritems python3

Move keyring package name configuration to pillar

#32 replace httpredir by deb.debian.org

add opts to repo name

contributed initialy by @javierbertoli <javier@netmanagers.com.ar>

fixes #30

Fixes #30

Permit an absent preferences pillar data key

adding support for Origins-Pattern in unattended upgrade

Minor fixes

Deleting the file causes "could not open file '/etc/apt/sources.list'"
warnings. Better to keep it around but just remove its contents.

fix pillar lookup and whitespacing

add listchanges config and fixed typo in unattended.sls

Fix tests to match changes from PR #20, add entry in .gitignore

Ensure sources.list exists but is empty (#19)

Salt uses the aptsources system library to get a list of repositories on
the host. Unfortunately if the /etc/apt/sources.list file is missing,
aptsources.sourceslist.SourcesList() (which is called by salt) logs a
warning, which is then displayed to the user running salt.

To avoid this warning when using 'remove_sources_list: true' in pillar
we can keep the /etc/apt/sources.list file, but just ensure it is empty.
This achieves the same thing, but does not log the warning or display it
to the user.

Add protocol and port in pillar repository example for 3rd party repo

When adding, gpg will fail with a "not able to connect" in some cases (most likely related to firewalling, but not investigated thoroughly): adding the specific protocol and port solves this issue.

Add a state to manage apt's preferences, with tests

Ignore .kitchen dir

Add defaults for preferences mgmt

Add some pillar examples for preferences mgmt

Add tests for preferences

Add entries in the README file

Missing map.jinja entry

Fix resource name to avoid conflicting ID

Add a state to manage repositories, with tests