seamonkey version 2.0.13+nobinonly-0ubuntu1 failed to build in oneiric
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
seamonkey (Ubuntu) |
Fix Released
|
High
|
Micah Gersten | ||
Oneiric |
Fix Released
|
High
|
Micah Gersten |
Bug Description
seamonkey version 2.0.13+
Link to failed build: https:/
Details about the rebuild:
http://
Direct link to the build log: https:/
This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 4427 lines into the build log:
nsEnumeratorUti
make[6]: *** [nsEnumeratorUt
make[6]: Leaving directory `/build/
make[5]: *** [libs] Error 2
make[5]: Leaving directory `/build/
make[4]: *** [libs_tier_xpcom] Error 2
make[4]: Leaving directory `/build/
make[3]: *** [tier_xpcom] Error 2
make[3]: Leaving directory `/build/
make[2]: *** [default] Error 2
make[2]: Leaving directory `/build/
make[1]: *** [default] Error 2
make[1]: Leaving directory `/build/
make: *** [debian/
dpkg-buildpackage: error: debian/rules build gave error exit status 2
*******
Build finished at 20110823-0933
FAILED [dpkg-buildpackage died]
Purging chroot-
Changed in seamonkey (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
But are there any reasons to stick to 2.0.13 version instead of upgrading to the current 2.3 tree? Shall we file a bug about that, instead?