mozilla-1.0-rc3.ebuild merges but with several problems, both using gtk2 or not. I also used NO_MAIL="yes". I'll attach the emerge logs. Check for '***' and the end of the logs to see the reported problems
Created attachment 2253 [details] mozilla-logs.tar.bz2 tarball with the the both logs. 300Kb, uncompresses to 8Mb
Unmerge totally, rm -rf /usr/lib/mozilla, and remerge ? I know with the nomail setting, due to stale chrome files weird things can happen. This "should" be fixed from -r3, but I guess anything is possible.
I've done as suggested but the ebuild still has those errors. I'll try to emerge without nomail to see if it changes anything.
Nop. Nothing seems to have effect. I suppose it was some change made in this release. I wish I could help more but this just take so much time to build... and it works for my more immediate needs, so it's probably better address this again when there is a new version of Mozilla, which should hopefully require less patches.
And here's the one for bumpbing mozilla-1.0-r3.ebuild to mozilla-1.0.1.ebuild 203a204,219 > if [ "`use ipv6`" ] ; then > myconf="${myconf} --enable-ipv6" > fi > > if [ "`use crypt`" ] ; then > myconf="${myconf} --enable-crypto" > fi > > if [ "`use zlib`" ] ; then > myconf="${myconf} --with-system-zlib" > fi > > if [ "`use java`" ] ; then > myconf="${myconf} --with-java-supplement" > fi > 210,211d225 < --with-system-zlib \ < --enable-ipv6 \ 213d226 < --enable-crypto \ 216d228 < --with-java-supplement \
I'm closing this bug now as I'm using mozilla-1.2_beta and I didn't noticed this problem when emerging it. Thanx for the feedback anyway.
