problems understanding the output of dbus-monitor (security policy)

[Havoc Pennington]

On Tue, 2005-01-11 at 11:17 +0100, Ikke wrote:
> On Tue, 2005-01-11 at 10:49 +0100, Ikke wrote:
> > ...
> 
> Ok, did a CVS checkout, ./autogen.sh (no more options enabled/disabled)
> and make
> 
> Then make check:
> 
> Making check in dbus
> <snip>
> Test data in ../test/data
> dbus-test: running string tests
> dbus-test: checking for memleaks
> dbus-test: running sysdeps tests
> Failed to parse 0xff correctly, got: 255.000000FAIL: dbus-test
> ===================
> 1 of 1 tests failed
> ===================
> <snip>
> 
> which is not good I guess ;-)
> 

Yeah that's just a dorky thing I broke the other day. There's a < that
should be > or something. I haven't committed the fix since I have 400K
of outstanding patch.

Try "cvs co -D2004-12-25" to avoid recent bustage.

> 
> So the testcase that fails when I compiled it myself succeeded here.
> 

Because it depends on having some context (test directories or whatever)

Havoc