This bug was fixed in the package seamonkey - 2.0.6+build1+nobinonly-0ubuntu1
--------------- seamonkey (2.0.6+build1+nobinonly-0ubuntu1) maverick; urgency=low
* New upstream release v2.0.6 (SEAMONKEY_2_0_6_BUILD1) * Fix LP: #593571 - searching for am-newsblog.xul in the wrong chrome package Install the newsblog.js XPCOM component - update debian/seamonkey-browser.install * Fix some Lintian warnings - update debian/control - add debian/README.source -- Chris Coulson <email address hidden> Wed, 14 Jul 2010 14:45:32 +0100
This bug was fixed in the package seamonkey - 2.0.6+build1+ nobinonly- 0ubuntu1
--------------- build1+ nobinonly- 0ubuntu1) maverick; urgency=low
seamonkey (2.0.6+
* New upstream release v2.0.6 (SEAMONKEY_ 2_0_6_BUILD1) seamonkey- browser. install README. source
* Fix LP: #593571 - searching for am-newsblog.xul in the wrong chrome package
Install the newsblog.js XPCOM component
- update debian/
* Fix some Lintian warnings
- update debian/control
- add debian/
-- Chris Coulson <email address hidden> Wed, 14 Jul 2010 14:45:32 +0100