diff options
| author | aszlig <aszlig@redmoonstudios.org> | 2015-10-26 20:47:16 +0100 |
|---|---|---|
| committer | aszlig <aszlig@redmoonstudios.org> | 2015-10-26 20:56:42 +0100 |
| commit | 82d88b5bcb68d7c039aa689210512cf08aedb22c (patch) | |
| tree | f04b59ee300f9479148c8c8f158bc227eedd85de /pkgs/development/python-modules/python-sql | |
| parent | 3b85cf704cd49dcaa1d9ae6b1fdf429172934b38 (diff) | |
vmTools.commonDebPackages: Add "mawk".
While debugging an issue with running NixOps tests, I found out that the
output from debClosureGenerator is not deterministic.
The reason behind this is the way how Provides and Replaces fields are
handled. I haven't yet found out what's the exact issue, but so far
packages "Provides" are more or less picked at random.
So, running the NixOps Hetzner tests we get either mawk, original-awk or
gawk altering on every invocation.
While for the test it isn't poisionous whether wi have mawk or gawk,
having original-awk certainly is, because live-build only works with
mawk or gawk.
The best solution would obviously be to make debClosureGenerator
deterministic, but in the case of "Provides: awk", we can safely pick
mawk by default, because the latter has a "Priority: required" in its
package description.
This also has the advantage that we can safely cherry-pick this to
release-15.09 because it's very unlikely that we'll break the
debClosureGenerator by adding a dependency to commonDebPackages.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Diffstat (limited to 'pkgs/development/python-modules/python-sql')
0 files changed, 0 insertions, 0 deletions
