Please update this bugzilla to 3.0 and enable support for UTF-8. It would be helpful in bugs concerning locales.
This is on my plate. Should be done within 2-3 weeks.
Could someone attach a patch with the customizations in it, as we did for GCC Bugzilla? I tried cvs -z9 diff -uN -rBUGZILLA-2_17_5 -rHEAD, but this didn't work.
It looks like it refers to the old /cvs/gcc bugzilla tree: -bash-3.00$ cat CVS/Root /cvs/gcc -bash-3.00$ cat CVS/Repository wwwdocs/bugzilla ... but that appears to be gone. I didn't follow the upgrade process closely at all; was the old CVS stuff archived? If so we could pretty easily make the diff. Otherwise, I'm not sure. Also I see: -bash-3.00$ cat CVS/Tag Tsources-bugzilla-branch ... though I am not 100% sure that everything in the working tree was actually committed there.
Subject: Re: Upgrade sourceware.org/bugzilla/ to Bugzilla 3.6 I recommend comparing the checkout to a release tarball, rather than relying on CVS (/sourceware/projects/gcc-home/saved-cvs-wwwdocs-bugzilla) to have had everything checked in.
Created attachment 5003 [details] Initial diff between sourceware and vanilla 2.17.5 code I excluded everything in docs/, data/ and contrib/, which are not relevant. The code in contrib/ *could* be relevant, but I have no intention to read scripts in this directory anyway (this is unsupported code, and most of it is obsolete).
Just to make sure, are the product and component for this bug really correct??
OK, the test installation running Bugzilla 3.6.2 is live at: http://sourceware.org/bugzilla-test/ Please test it as much as possible!!
Created attachment 5005 [details] Upgrade patch for 3.6.2, v1 Here is the patch I applied to the test installation.
Created attachment 5006 [details] GCC extension for 3.6.2, v1 And the GCC extension for sourceware.org (slightly different from the one for gcc.gnu.org, because there are minor differences between both, such as two less custom fields and no linkification for wiki).
Done. Have fun!
Thank you very much for doing this. I did not see a good place to file a follow-on bug, so I am updating this. gdb had a commit script that would update bugzilla. This seems to have stopped working. E.g., I committed a fix for "PR python/11948", but PR 11948 does not show the commit info. Does the commit script need to be updated in some way?
(In reply to comment #11) > Does the commit script need to be updated in some way? I guess the commit script sends emails to Bugzilla? If yes, then it needs to: - the To: field must point to the email address set by #overseers which will redirect the email to email_in.pl. It should be sourceware-bugzilla@sourceware.org. - the Subject: field must start either by [Bug NNN] or [Bug component/NNN]. Both fixes above must be done by #overseers.