On 20.01.2014 17:07, Mark Haney wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/20/2014 11:01 AM, Michael Friedrich wrote:
Icinga 2 doesn't care as long as it's included. The config parser
reads all objects into memory and then tries to find relationships
- so the order of inclusion
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/20/2014 11:01 AM, Michael Friedrich wrote:
>
> Icinga 2 doesn't care as long as it's included. The config parser
> reads all objects into memory and then tries to find relationships
> - so the order of inclusion doesn't matter, as long as it's
>
On 20.01.2014 16:55, Mark Haney wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/20/2014 10:43 AM, Michael Friedrich wrote:
Both work. While the snapshot package will show the timestamp it
was built, the binary version will tell about the git commit hash
it's sources are based on.
An
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/20/2014 10:43 AM, Michael Friedrich wrote:
> Both work. While the snapshot package will show the timestamp it
> was built, the binary version will tell about the git commit hash
> it's sources are based on.
>
> And you should provide both so t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/20/2014 10:43 AM, Michael Friedrich wrote:
> Both work. While the snapshot package will show the timestamp it
> was built, the binary version will tell about the git commit hash
> it's sources are based on.
>
> And you should provide both so tha
On 20.01.2014 16:01, Mark Haney wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/17/2014 3:51 PM, Michael Friedrich wrote:
The only notable difference in regards of the
package name is the additional 'snapshot-' suffix but
that will only help to identify the version installed in case
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/17/2014 3:51 PM, Michael Friedrich wrote:
The only notable difference in regards of the
> package name is the additional 'snapshot-' suffix but
> that will only help to identify the version installed in case of a
> found bug. The easiest way is r
On 17.01.2014 18:21, Mark Haney wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/16/2014 4:13 PM, Michael Friedrich wrote:
I didn't see if there was a temporary work around for 0.0.6, not
that it matters.
While the Icinga 2 releases happen on a 3 weeks schedule for our
development sp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/16/2014 4:13 PM, Michael Friedrich wrote:
>
>> I didn't see if there was a temporary work around for 0.0.6, not
>> that it matters.
> While the Icinga 2 releases happen on a 3 weeks schedule for our
> development sprints, this is not true for h
On 16.01.2014 19:06, Mark Haney wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/16/2014 12:48 PM, Michael Friedrich wrote:
Dang. You guys are on it. Nice work.
Thanks to my photographic memory. Otherwise you should've just opened an
issue. Rejecting issues marked as duplicate do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/16/2014 12:48 PM, Michael Friedrich wrote:
Dang. You guys are on it. Nice work. I didn't see if there was a
temporary work around for 0.0.6, not that it matters. I'm more
curious as to what the fix is.
- --
Mark Haney
Network Administrat
On 16.01.2014 18:41, Mark Haney wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is probably pretty easy to fix, but I wanted to ask in case it's
already been asked and answered. I am not getting any icons
displaying properly in Icinga2. The icon near the host and the
services all sho
12 matches
Mail list logo
