Bug 168389 – mozilla-firefox-2.0.0.2 needs a manual reemerge of noscript

• Status: RESOLVED CANTFIX
• Product: Gentoo Linux

[Description Daniel Pielmeier 2007-02-25 22:43:56 UTC]

Updating mozilla-firefox with restrict-javascript USE flag enabled needs a manual reemerge of noscript to make it work again.


Steps to Reproduce:

Updating from mozilla-firefox-2.0.0.1-r4 to mozilla-firefox-2.0.0.2 with enabled restrict-javascript USE flag

Actual Results:

The noscript addon did not work immediately.

Expected Results:

Plugins which are installed per USE flag and so as a dependency should work without a manual reemerge.

[Comment 1 Daniel Pielmeier 2007-02-25 22:52:28 UTC]

*** Bug 168392 has been marked as a duplicate of this bug. ***

[Comment 2 Raúl Porcel (RETIRED) 2007-02-26 12:10:16 UTC]

From the ebuild:

	elog "Please remember to rebuild any packages that you have built"
	elog "against firefox."

Obviously it needs a manual reemerge...because there's no way to do it automatically. When you upgrade your kernel, you need to rebuild the modules, don't you? :)

The same applies to this.

[Comment 3 Daniel Pielmeier 2007-02-26 14:00:17 UTC]

(In reply to comment #2)

So i can use module-rebuild to do build my modules against the new kernel. Won't revdep-rebuild recognize that noscript must be compiled against the new version of firefox? I think i ran revdep-rebuild after that update, and it didn't advise me to rebuild noscript.

[Comment 4 Jakub Moc (RETIRED) 2007-02-26 15:59:58 UTC]

No, revdep-rebuild won't recognize broken FF plugins, definitely outside of scope of the tool.

CANTFIX.