From: justinmattock@gmail.com (Justin P. Mattock) Date: Fri, 11 Mar 2011 12:01:15 -0800 Subject: [refpolicy] firefox and the latest git policy In-Reply-To: <1299711161.6164.4.camel@tesla.lan> References: <4D77F18C.2070306@gmail.com> <1299707036.2974.1.camel@tesla.lan> <4D77F820.20907@gmail.com> <1299708895.2974.14.camel@tesla.lan> <4D77FE35.6060603@gmail.com> <1299711161.6164.4.camel@tesla.lan> Message-ID: <4D7A7F8B.7040008@gmail.com> To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com On 03/09/2011 02:52 PM, Guido Trentalancia wrote: > On Wed, 09/03/2011 at 14.24 -0800, Justin P. Mattock wrote: >> On 03/09/2011 02:14 PM, Guido Trentalancia wrote: >>> Have a look if this helps out (from Sven Vermeulen >>> ): >>> >>> [PATCH 05/15] Allow mozilla/firefox to manage tempfiles >>> timestamped Wed, 9 Mar 2011 22:11:21 +0100 >>> >>> firefox is not the most straightforward thing to build. Sometimes (not >>> very often though) I ended up in an unusable build for example. >>> >>> Symptoms ? Logs ? >>> >>> It might also depend on the specific version, especially if it is a new >>> one. Is 4.0 out ? >>> >>> Regards, >>> >>> Guido >>> >> >> the version I am using is 3.6.13(did look at 4 but decided to just build >> the stable version(which is outdated probably now))without xulrunner >> being the main base for the lib*'s > > I had no problems running that version with refpolicy up to 15022011. If > it is the latest stable version then I cannot see how that would be > outdated. I suppose refpolicy is not based on unstable components. > > Regards, > > Guido > > alright... I went and rewrote all the rules seems fine now(must have been something strange going on!) Justin P. Mattock