This site has been retired. For up to date information, see handbook.gnome.org or gitlab.gnome.org.


[Home] [TitleIndex] [WordIndex

Status

Attachment creation time

Lots and lots of: Warning - could not determine correct creation time for attachment 47207 on bug 121111

Note:

Flags / patch statuses

[Old: add a

Elijah: This should not be necessary anymore, as show_bug.cgi & attachment.cgi have been modified to ignore flaginclusions altogether.]

flags are now totally ignored, as are flaginclusions and flagexclusions; the tables exist but they aren't updated or used anywhere that we have remembered to get rid of them. The flagtypes table is still used, but mostly only for id, name pairing.

This stuff has been replaced with a simple status_id field in the attachment table that is much nicer.

UTC

Bugzilla has been hacked to set the database timezone to UTC.

Group settings

ismailinglist group needs to have 'Use for bugs' unchecked.

Private comments

There is a insidersgroup param. It allows one or more comments of a bug to be hidden. I've currently set this to gnomehackers.

X-Bugzilla-*

Bugzilla CVS can support X-Bugzilla-Product and -Component, made sure rest is also possible.

Patch viewer

Configured the patch viewer cvsroot and cvsroot_get. Allows to do more advanced stuff / layouts of a patch, see as example: http://bugzilla-test.gnome.org/attachment.cgi?id=48528&action=diff

Also set the bonsai_url, click on the 'Lines xxx-xxx' in the attachment above to see what it does.

Note: now uses the read-only NFS mount! Should be faster.

Watching

The X-Bugzilla-Reason header has been modified like 2.16.x bugzilla.gnome.org. When watching the AssignedTo X-Bugzilla-Reason will have WatchAssignedTo. Same when watching any other reason.

The X-Bugzilla-Watching is a comma separated list of the email addresses you are watching on this bugreport. The header only exists when watching an account for this bugreport.

Custom fields

Bugzilla.gnome.org before 2.16 had GNOME version and GNOME milestone as extra fields in the bugs table. In 2.16 customfields are used. In 2.20 I don't want to rely on a custom fields patch (mostly because it doesn't exist and I'm not sure when it will be). I want to add the fields again to the bugs table. Bugzilla 2.20 has a webinterface to change OS / Hardware / Priority / Severity. I want to support that for these fields. Unfortunate that we need 2 fields, otherwise I could've hijacked Hardware (we hide that anyway).

Unknown Alias & bug-buddy-import

This is pretty much a hack in Bugzilla 2.20. In 2.20 everything uses userids. As an externalcc doesn't have an bugzilla userid, I remember the Reporters userid. Just before calling the sendMail routine I change the $user->{'login'} with externalcc (if defined). Ugly but works.

Note: This is slightly different from 2.16.x. Before when having an externalcc, unknown@b.g.o as reporter + in the cc-list; unknown@b.g.o would still receive a copy (because of usage of email addresses + unknown@b.g.o appearing in the CC-list). In 2.20 unknown@b.g.o will not receive a copy anymore. Watching unknown@b.g.o will still work. The change doesn't cause any problems, but there is a very small change someone might get confused.

Note: Bug-buddy-import.pl will now create accounts instead of using the externalcc hack. Reports could still be assigned to the exporter (unknown@gnome.bugs), but only if the email address is invalid. Next Bugzilla upgrade externalcc stuff shouldn't be needed. Message is at:

Classifications / isgnome

Current classifications:

Status:

TODO:

Porting existing customization

Porting reports

check-assignedto.cgi has the cleanest code.. use that as an example for the rest...

%s/::FORM{\([^}]\+\)}/cgi->param(\1)/g

Most reports should still be cleaned up further (templates).

Conversion means at least:

File

Porting status

boogle.cgi

done

check-assignedto.cgi

done

clean-20-report.cgi

obsolete

core-bugs-today.cgi

done - should be cleaned up at some stage though (classifications etc)

d2-qreport.cgi

wont port

d2-test-report.cgi

wont port

d2-ximian-report.cgi

wont port

email_gnome_summary_report.pl

See Note 2

g2-progress-utils.pl

wont port

gnome-20-report.cgi

wont port, doesn't work in 2.16

gnome-20-report-test.cgi

wont port, doesn't work in 2.16

gnome-love.cgi

Just a redirect... - ElijahNewren
I'm still proud of my port - OlavVitters

gnome-report.cgi

Ported -- Still need to add patch status

keyword-search.cgi

done

keyword-search-rss.cgi

done

keyword-search-utils.pl

done

mostfrequent.cgi

See Note 3

needinfo-updated.cgi

done

old-bugs-needing-love.cgi

questionable...

old-gnome2-needing-love.cgi

wont port, doesn't work in 2.16

patch-diligence-report.cgi

ported by Elijah + uses templates

patch-report.cgi

Ported + uses templates - See Note 4

patch-report-utils.pl

Ported - See Note 4

patch-status.cgi

Ported - See Note 4

product-keyword-report.cgi

wont port, doesn't work in 2.16

product-mostfrequent.cgi

See Note 3

product-mustfix-report.cgi

wont port, doesn't work in 2.16

product-target-report.cgi

wont port, doesn't work in 2.16

recent-mostfrequent.cgi

See Note 3

recent-mostfrequent-utils.pl

Done and removed stuff not needed by create-mostfreq-xml.pl cronjob. See also Note 3

reports.cgi

contents moved to templates/en/custom/pages/reports.html.tmpl. /report.cgi requires login :(

simple-dup-finder.cgi

It's just a redirect...

sql-scratch.cgi

wont port

temporary.cgi

wont port

unconfirmed-bugs.cgi

ported -- still needs to use templates

weekly-bug-summary.cgi

ported + uses templates

weekly-summary-utils.pl

ported + uses templates + very big cleanup

TODO:

Simple-dup-finder

Has been ported, accelerated + uses templates.

Booglerific simple query form

Changes

Enhancements that could be made

Browse (Overview page)

This page has been stuffed full with all kinds of junk all over the place. There's some more stuff we want to throw into it too. Then we need to get someone who can make it pretty. We really need someone to make it pretty. ;-)

Possible further changes still not incorporated:

Bug-buddy and XML-RPC

Bug-buddy using email allowed you to:

Bug-buddy and XML-RPC should be made smart.

When a program crashes, bug-buddy should:

TODO:

Short IRC discussion

<bkor> fer: do you have time to write xml-rpc stuff for bug-buddy 2.14? there is nothing on the server yet though, hope to do that within a few weeks
<fer> bkor, I think I'll haqve time!!!
<fer> for that and for the backtalk project
<bkor> great! I want bug-buddy to not need the bugzilla.gnome.org/ files (the 3 xml files describing products, etc)
<bkor> with xml-rpc we should be able to make a function that'll just gets the products (less data)
<bkor> and for crashers bug-buddy should give the program name, then b.g.o should decide where it goes (product)
<fer> yup, I think that's the right approach
<bkor> my only doubt is the requirement Bugzilla account.. xml-rpc runs one function every time, I think... so how to handle creating a Bugzilla account? with the webinterface it mails the password
<fer> humm
<bkor> I'd like to use that still for xml-rpc, but that might be irritating for new users, but on the other hand.. allowing xml-rpc to specify the new password = bad! (no validation on the email address)
<fer> an xml-rpc function to get a new account would be great I guess
<fer> humm
<fer> good point
<fer> but waiting for mail = boring poor users and don't get them sending the report
<bkor> ideally I want something that allows you to make a bug-buddy report + account in one go without a password
<bkor> next time they should use the password
<bkor> then use gconf / keyring manager to store the email address + password
<fer> humm
<fer> this is your second report, so go through your mail and search your f*cking password?
<bkor> yeah.. not too great :-(
<bkor> ok.. another one then... remember in b.g.o if user was created using bug-buddy (well.. xml-rpc).. if so, password = optional, otherwise not
<fer> humm

TODO

Stuff to be fixed before switching bugzilla.gnome.org to bugzilla-newer:

Nagging issues that would be nice to be fixed before switching over but could wait if necessary

To be done after bugzilla.gnome.org runs 2.20 (or before, given sufficient time before the 18th):

Features

Why bugzilla-newer is better:

Step-by-step upgrade guide

Time to complete

Task

Disable web interface b.g.o

Disable web interface b-t.g.o

Disable bug-buddy-import

Disable cronjobs

6min

Make backup of bugs database

Make backup of ~/bugzilla

Put copy of bugzilla-test sources in ~/bugzilla

Modify ~/bugzilla/localconfig to point to bugs database

3h30min

Convert database structure to 2.20 format using ./checksetup.pl

Enable limited access to b.g.o (restricted on IP address)

2min

Goto https://bugzilla.gnome.org/editsettings.cgi and disable quip option

Check bugzilla status

Check b.g.o status

Enable access to b.g.o

Enable bug-buddy-import

Enable cronjobs

Detailed step-by-step guide

Disabling web interfaces:

Via .htaccess as the Bugzilla software will be upgraded. The Bugzilla way of disabling will not be reliable enough

vim ~/bugzilla/.htaccess, add: deny from all
vim ~/test/.htaccess, add: deny from all

Disabling bug-buddy import:

$ vim ~/.procmailrc
change ':0c' after '# I want a copy' to ':0'

Disabling cronjobs:

$ crontab -e
put ### in front of commands

Make backup of bugs database:

$ mysqldump --opt -h button-back -u bugzilla -p bugs  | gzip > bugs-216.sql.gz

Make backup of ~/bugzilla:

$ cd ~/
$ cp -a bugzilla backup216

Put copy of bugzilla-test sources in ~/bugzilla:

$ cd ~/bugzilla
$ rm -rf *
$ cp -a ~/test/* .
$ cp -f ~/backup216/localconfig .
ADD MORE STUFF

Convert database structure to 2.20 format using ./checksetup.pl

$ ./checksetup.pl

Enable limited access to b.g.o (restricted on IP address)

$ vim ~/bugzilla/.htaccess
add as appriopriate: allow from 1.2.3.4

Make changes to setup

Visit https://bugzilla.gnome.org/editparams.cgi
 - change urlbase to: https://bugzilla.gnome.org/
 - change mail_delivery_method to: sendmail
Goto https://bugzilla.gnome.org/editsettings.cgi
 - disable quip option
Goto https://bugzilla.gnome.org/editgroups.cgi
 - Edit ismailinglist group
  - Disable 'Use For Bugs'
  - Remove inherit for 'admin' group
 - Edit admin group
  - Add inherit/grant for 'maintainers' group

Issue to investigate/fix before 18th

Note: conversion hangs in 'Updating column qa_contact in table bugs'

Stuff after that:

Updating column qa_contact in table bugs ...
Old: mediumint NOT NULL
New: mediumint



Deleting unused column emailflags from table profiles ...
Updating column initialowner in table components ...
Old: mediumint
New: mediumint NOT NULL
Updating column value in table versions ...
Old: tinytext
New: varchar(64) NOT NULL
Adding new index 'versions_product_id_idx' to the versions table ...
Updating column creation_ts in table bugs ...
Old: datetime NOT NULL
New: datetime
Adding group editclassifications ...
Adding group admin ...

2024-10-23 11:17