This is not a good solution as we are dropping xulrunner-1.9.1 from Lucid.
On 04/19/2010 04:31 PM, Ben Dean-Kawamura wrote:
> I don't think it was upgrading that fixed the issue directly. What
> happened is that Miro started using xulrunner-1.9.1 rather than
> xulrunner 1.9.2. I'm not sure why that happened exactly, but I just
> checked in some code that forces it to happen and I think that does the
> trick.
>
> So here's what I think is the correct solution:
>
> 1) Get the latest version of the 3.0 branch, make sure it includes this
changeset:
> http://git.pculture.org/miro/commit/?h=Miro-3.0&id=318bad719793114443bd97746c7a24a00cd1794d
>
> 2) Apply this patch to force Miro to link to xulrunner-1.9.1:
> http://bugzilla.pculture.org/attachment.cgi?id=2395
>
> As far as I can tell that solves the problem, can others test it out? I
> think it's much cleaner than my original patch.
>
This is not a good solution as we are dropping xulrunner-1.9.1 from Lucid.
On 04/19/2010 04:31 PM, Ben Dean-Kawamura wrote: git.pculture. org/miro/ commit/ ?h=Miro- 3.0&id= 318bad719793114 443bd97746c7a24 a00cd1794d bugzilla. pculture. org/attachment. cgi?id= 2395
> I don't think it was upgrading that fixed the issue directly. What
> happened is that Miro started using xulrunner-1.9.1 rather than
> xulrunner 1.9.2. I'm not sure why that happened exactly, but I just
> checked in some code that forces it to happen and I think that does the
> trick.
>
> So here's what I think is the correct solution:
>
> 1) Get the latest version of the 3.0 branch, make sure it includes this
changeset:
>
http://
>
> 2) Apply this patch to force Miro to link to xulrunner-1.9.1:
> http://
>
> As far as I can tell that solves the problem, can others test it out? I
> think it's much cleaner than my original patch.
>