User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.8a2) Gecko/20040526 Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.8a2) Gecko/20040526 Compare http://webtools.mozilla.org/bonsai/cvslog.cgi?file=mozilla/configure.in&rev=MOZILLA_1_7_BRANCH&root=/cvsroot with http://webtools.mozilla.org/bonsai/cvslog.cgi?file=mozilla/configure&rev=MOZILLA_1_7_BRANCH&root=/cvsroot Reproducible: Always Steps to Reproduce:
Confirming configure needs to be generated and comitted, not sure why "remote host" did not do this. Marked "new", raising severity to 'major', (those who pull and build without autoconfigure will not be running the 'true' 1.7) could produce noticeable issues, potentially. Requesting 1.7 blocker
Severity: normal → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
CCing leaf & cls
Assignee: nobody → leaf
We've never had auto-update of configure on branches, and it doesn't seem like a priority. I just updated configure using an autoconf that generated exactly what we currently have on the trunk (different from what we used to do on the trunk before the move to MF), so I think this is as fixed as we need. I'll update the aviary 1.0 branch shortly if it needs it.
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.