Tom Downes

This basically forces me to use apt-mirror on backports repos. It's a pretty big bug. So I agree - not an "enhancement". I find the code pretty hard to follow...

Here's a basic example of how to do this with post-processors: ```hcl post-processor "manifest" {} post-processor "shell-local" { inline = [ "IMAGE=$(jq -r \".builds[-1].artifact_id\" packer-manifest.json)", "gcloud compute images add-iam-policy-binding $${IMAGE}...

I also observe this behavior when using the `gcs` backend with `0.15.3`.

@zenglhua I resolved this in https://forge.puppet.com/tpdownes/sysctl You just have to follow the docs and use single spaces between the fields.

No. Deliberately not so. You might choose it for inspiration. But... I've decided to adopt https://forge.puppet.com/herculesteam/augeasproviders_sysctl which claims Puppet 3.x compatibility. Then I build a really simple profile around it....

Well, you're doing at least 1 thing wrong. It should be ``` classes: - roles - sysctl::base sysctl::base:values: 'net.ipv4.ip_forward': value: '1' ``` But I'm running into a propblem with automatic...

For anything puppet4, you might want to look at my pull request #46 or the fork that it comes from. It isn't backwards-compatible, but it doesn't have the weirdness of...

I am seeing the same problem. Suspect use of libstdc++6 vs libstdc++5 is part of the story.

@geosone I still see a segfault with =2.05.3-1~20171111184405.17+jessie= ``` root@pcdev1:~# arcconf GETCONFIG 1 Controllers found: 1 Segmentation fault ``` It seems to be looking for a [filename that does not...

I think that linking is probably better handled during the build process. Either way, it's not important enough to me to pursue much further. The "old" package works just fine...