Prev: net-im/ejabberd 2.0.5 to 2.1.0
Next: net/samba34 does not create all required directories
From: Sascha Holzleiter on 4 Feb 2010 09:30
On Thursday 04 February 2010 01:19:33 Martin Wilke wrote:
> Howdy,
>
> We know that a lot people are waiting for Firefox 3.6,
> but nox@ found a strange bug which is now solved.
> The problem was that starting Firefox 3.6 with certain
> addons installed was not possible. Now it looks like all
> problems are solved and we can start a CFT.
> If everything works fine we plan to commit Firefox 3.6 next
> weekend. We should also note that the java plugin currently
> does not work with 3.6.
>

Thanks for fixing it and porting it over, it works great so far!
I had to adjust the weave port a bit as it seems that the location of the idl
files has changed. The former path was /usr/local/share/idl/firefox3/stable
and /usr/local/share/idl/firefox3/unstable which now just seems to be
/usr/local/share/idl/firefox3. I'll append a simple diff if someone is
interested.

From: Gary Jennejohn on 4 Feb 2010 11:11
On Thu, 4 Feb 2010 01:19:33 +0100
Martin Wilke <miwi(a)FreeBSD.org> wrote:

> Please make sure all your addons are compatible with firefox 3.6,
> backup your $HOME/.mozilla dir, also you need to reinstall
> www/linux-f10-flashplugin10.
>

Works extremely well. Thanks!

BTW I did not need to reinstall www/linux-f10-flashplugin10. The old
installation from August 2009 just worked OOTB.

---
Gary Jennejohn
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Peter Jeremy on 4 Feb 2010 15:48
On 2010-Feb-04 01:19:33 +0100, Martin Wilke <miwi(a)FreeBSD.org> wrote:
>The problem was that starting Firefox 3.6 with certain
>addons installed was not possible. Now it looks like all
>problems are solved and we can start a CFT.

Thanks to all for your efforts.

>weekend. We should also note that the java plugin currently
>does not work with 3.6.

This is a blocker for me. What is involved in building a
java plugin to suit the new FF36 interface? Please let me know
if there's anything I can do to assist the effort.

--
Peter Jeremy
From: Juergen Lock on 4 Feb 2010 16:13
In article <20100204001933.GA11586(a)bsdcrew.de> you write:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Howdy,
>
>We know that a lot people are waiting for Firefox 3.6,
>but nox@ found a strange bug which is now solved.
>The problem was that starting Firefox 3.6 with certain
>addons installed was not possible. Now it looks like all
>problems are solved and we can start a CFT.
>[...]

..and in case anyone is wondering what the issue was, the problem was a
filename handling change that basically caused all .xpt files (XPCOM type
libraries) failing to load when there where symlinks in paths to one of
them - like the ones from addons when /home is a symlink like it usually
is on FreeBSD - and thus ff couldn't start. Here is the mozilla ticket:
https://bugzilla.mozilla.org/show_bug.cgi?id=530793

Cheers,
Juergen
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Heino Tiedemann on 4 Feb 2010 16:28
Juergen Lock <nox(a)jelal.kn-bremen.de> wrote:

> In article <20100204001933.GA11586(a)bsdcrew.de> you write:
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Howdy,
>>
>>We know that a lot people are waiting for Firefox 3.6,
>>but nox@ found a strange bug which is now solved.
>>The problem was that starting Firefox 3.6 with certain
>>addons installed was not possible. Now it looks like all
>>problems are solved and we can start a CFT.
>>[...]
>
> ..and in case anyone is wondering what the issue was, the problem was a
> filename handling change that basically caused all .xpt files (XPCOM type
> libraries) failing to load when there where symlinks in paths to one of
> them - like the ones from addons when /home is a symlink like it usually
> is on FreeBSD - and thus ff couldn't start. Here is the mozilla ticket:
> https://bugzilla.mozilla.org/show_bug.cgi?id=530793

Aha, und das alles klappte dei dem www/firefox3-devel bisher nicht?

Krass. Ma gut, das ich nie Addonns verwende ;-)

Und ja, /home ist bei mir ein Symlink.


Heino

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

 |  Next  |  Last
Pages: 1 2 3
Prev: net-im/ejabberd 2.0.5 to 2.1.0
Next: net/samba34 does not create all required directories