Age | Commit message (Collapse) | Author |
|
|
|
By including the common module first, you won't get ugliness like this:
Nov 14 10:29:02 - [citest79656] Warning: Unknown variable:
'apt::apt_base_dir'. at
/srv/leap/puppet/code/modules/apt/manifests/config.pp:69:15
Nov 14 10:29:02 - [citest79656] Warning: Unknown variable:
'apt::apt_base_dir'. at
/srv/leap/puppet/code/modules/apt/manifests/config.pp:77:30
Nov 14 10:29:02 - [citest79656] Warning: Unknown variable:
'apt::apt_base_dir'. at
/srv/leap/puppet/code/modules/apt/manifests/config.pp:78:30
|
|
|
|
|
|
|
|
|
|
|
|
preferences pin for buster are not working properly...
|
|
|
|
|
|
|
|
|
|
puppet 4 compat: mark integer as string
See merge request shared-puppet-modules-group/apt!64
|
|
replace old httpredir by new deb.debian.org (fix issue #23)
Closes #23
See merge request shared-puppet-modules-group/apt!70
|
|
|
|
with puppet 4.x when you don't define the debian_nextcodename,
compilation fails saying that the variable is unknown. since we have
unit tests specifically for this fact's behaviour, we want to stub out
the fact's value in other tests so that we can verify the logic of
manifests is actually good.
|
|
In commit 8b45a8a, the release names were moved forward in order to
follow the new Debian release. However, I didn't change the tests
accordingly and thus the tests have been failing since then.
|
|
test: move release targets for debian
See merge request !65
|
|
that file is using multiple coding style elements that don't follow
community best practices which are designed to make code easier to read.
|
|
During the change from the monolithic preferences file to the series of
snippets in preferences.d, one part was left out possibly as an
oversight, which prevents installing packages by mistake that belong to
a release that hasn't been explicitely pinned.
|
|
The file that we call "stable" can make apt actually pin testing or sid
if one of these is the running codename, which is nothing stable.
In order to make this file's name more relevant it should be named
current_codename.
|
|
this file is not used anymore. we've moved all of this to preferences.d
so the template is useless now, but we forgot to remove it.
|
|
|
|
with puppet 4.x when you don't define the debian_nextcodename,
compilation fails saying that the variable is unknown. since we have
unit tests specifically for this fact's behaviour, we want to stub out
the fact's value in other tests so that we can verify the logic of
manifests is actually good.
|
|
In commit 8b45a8a, the release names were moved forward in order to
follow the new Debian release. However, I didn't change the tests
accordingly and thus the tests have been failing since then.
|
|
|
|
Use official ruby docker image
See merge request !63
|
|
|
|
stretch was released
See merge request !62
|
|
buster+1's codename is known, and wheezy has been in LTS for some time
already.
|
|
|
|
The current wording is not super clear on what type of file should be
dropped in `site_apt/...`.
|
|
There are some references to the old `content` parameter (from
preseeded_package) that mistakenly weren't replaced with the new
parameter `seedfile_content`. This meant the documentation was wrong and
the `preseeded_package` wrapper was erroring out because of an unknown
parameter.
|
|
The missing dot made the announcement confusing. There are really two
different informations in there that should be split.
|
|
Move old monolithic preferences files to mutiple preferences.d files (Fix #14)
Closes #14
See merge request !61
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We currently can't use apt::package without preseeding. Also by default
the preseed content is grabbed from an implicit template, which makes
puppet runs fail for a non-obvious reason.
To keep previous functionality, force use of seed file when using the
deprecated apt::preseeded_package type.
|
|
|
|
|
|
|
|
keep a wrapper in place with a deprecation notice for the old name so
that ppl can know about the change and migrate to the new name
|
|
|
|
|