Update builddep.pp
apt::force: Added 2 parameters for automatic configuration file handling; fixes #modules-1306

when updating or installing newer packages with apt::force and you have changed previous
configuration files aptitude or apt-get will prompt what to do. You can suppress that
by pre-define the action with cfg_files parameter (new, old or unchanged and its backward
compatible if not defined). With a second optional parameter cfg_missing you can force
your provider to install missing configuration files as well.

Signed-off-by: Martin Seener <martin@seener.de>

apt::force: Changed selectors used in force.pp to case statements; refs #module-1306

Signed-off-by: Martin Seener <martin@seener.de>

apt::force: rspec: fixed the failing tests and added validate_re for cfg_files and validate_bool for cfg_missing. Also removed default values for both case statements and only allow pre-defined values or true/false. Furthermore enhanced the README refs #module-1306

Was able to fix the failing rspec tests for the patch.
Thanks to Morgan Haskel.

Signed-off-by: Martin Seener <martin@seener.de>

Despite the puppetlabs-stdlib documentation says validation_re supports 3 arguments the tests failed telling that only 2 are supported. Fixed this by removing the 3 optional argument; refs #modules-1306

Signed-off-by: Martin Seener <martin.seener@barzahlen.de>

apt::force: updated readme refs #module-1306

Signed-off-by: Martin Seener <martin@seener.de>
Merge pull request #363 from martinseener/ticket/1306-apt_force_fails_if_new_package_asks_how_to_handle_changed_config_files

apt::force: Added 2 parameters for automatic configuration file handling...
Merge pull request #326 from dabido/master

Builddep notifies apt-get update instead of requiring it
Fix a test that broke with #326.
- add bits for updating apt
- fix spec tests to include osfamily fact
- add spec tests to verify current default behavior unimpacted.
- manage the update-stamp file in puppet via content rather than a served file.
- update custom fact to return -1 if the file doesn't exist
- add spec test for custom fact
- refactor to use a variable vs a collector/override
- document parameters a bit more verbosely
- remove empty unconstrained fact
- Add osfamily fact to backports tests to facilitate functional tests on non-debian hosts
Merge pull request #349 from wolfspyre/apt_update_tooling

Apt update tooling
Don't truncate to short keys in the type

You should be able to create/delete keys using the long key to avoid
collisions, and truncating in the type makes that not work.
Merge pull request #365 from mhaskel/long_key_support

Don't truncate to short keys in the type
We aren't truncating in the type

So don't check for truncated IDs in the type test.
Merge pull request #366 from mhaskel/fix_unit_tests

We aren't truncating in the type
apt-key doesn't add long keys in deb6

You can feed the command the long key, but it truncates it to add the
key. This causes issues due to the short-key collision with the
puppetlabs key. So, test with a different key on debian 6.
Merge pull request #367 from mhaskel/deb6_apt-key_workaround

apt-key doesn't add long keys in deb6
Fix for future parser support
Merge pull request #368 from mhaskel/future_parser

Fix for future parser support
Missed one case for _kick_apt needed for strict variables
Merge pull request #369 from mhaskel/future_parser

Missed one case for _kick_apt needed for strict variables
add --force-yes so deb7 doesn't hang
Merge pull request #371 from mhaskel/force-yes

add --force-yes so deb7 doesn't hang
DOC-249 Revised and updated apt readme

Revised and updated apt readme. Post-merge-conflict edition.