I'm voting for putting all your notes somewhere very easy to find in the
future and then leaving everything the way it has been working.
This way, we can start up where you left off if necessary and, otherwise,
continue on with more pressing issues.
Thanks,
Trevor
On Thu, Sep 11, 2014 at 9:12 P
> Instead of continuing on the old thread "A question about numbers and
> representation", I decided to open a new thread avout BigDecimal to see if
> we can come to closure on that separately.
>
> Digging a bit more into Ruby, and how it handles floating point reveals that
> there is in fact no au
Hi,
Instead of continuing on the old thread "A question about numbers and
representation", I decided to open a new thread avout BigDecimal to see
if we can come to closure on that separately.
Digging a bit more into Ruby, and how it handles floating point reveals
that there is in fact no auto
This is why it has been a recommended best common practice [1] to add
the following to your ~/.gnupg/gpg.conf:
fixed-list-mode
keyid-format 0xlong
with-fingerprint
The other BCP that the Puppet Labs Release Key doesn't follow is that
it is using a SHA1 self-sig hash. The current
Recently, we were alerted that when receiving the Puppet Labs gpg
signing key from a keyserver, a user was offered two keys.
The key exchange went something like this:
# gpg --fingerprint --search-keys 0x4BD6EC30
gpg: searching for "0x4BD6EC30" from hkp server pgp.mit.edu
(1) Puppet Labs Release K
On 10 September 2014 09:12, Spencer Krum wrote:
> Yes integration would have to be opt-in. I'm sure the maintainers of those
> tools would want it that way anyways. And everything would have to respect
> the http_proxy variable, everyone's favorite variable in corporate settings.
>
> On Wed, Sep 1
Hello,
I have data in machine.yaml :
sitedefinition:
- website: "site.one.com"
ipadress: "192.168.0.2"
protocol: "http"
port: "80"
- website : "site.two.com"
ipadress : "192.168.0.2"
protocol : "http"
port : "80"
Well if I try get the da
