Fix for bug 7873: Duplicate marking now happens AFTER privs are checked to make sure a) the user is allowed to dupe it, and b) the change hasn't caused a midair collision.

we now search each list (dependson, blocks) to see if a bug number shows
up in each list. a bug can't be dependent upon and block the same bug.
also make it so you can't set a bug blocking or dependent on itself.

based on patch submitted by baulig@suse.de (Martin Baulig).

When a bug is marked duplicate, the reporter should be added to the bug that it duplicated.
patch submitted by jake@acutex.net (Jake).

fix for bug found in original 17464 patch, where removal from the CC list was not generating a mail.  r=donm@bluemartini.com

is done for the dup id field, but not for the originating bug id.
now checks to see if the original bug id is valid as well, although i don't
understand how this could get corrupted in the first place

patches by zach@zachlipton.com. Thanks!

Bug moving code is now fully implemented. To use it, turn on the param and set the move related params.

Keywords were already enforced to never differ only in capitalization.  So, changed the code so that case no longer matters when typing in the name of a keyword.

original bug found by timeless@bemail.org

contributed by dave@intrec.com (Dave Miller)

allow the reporter of a bug to change the status of a bug (e.g. reopen it) even if they don't have the editbug bit set.

set the target milestone when accepting a bug.

of different target milestones by product.

midair collision happens which needs to generate text which needs to
look at the attachments table.  Sigh.

the difference between new comments and people copying stuff in from
old comments.

have a universal (and more noticable) way of displaying them.

bug queries can be run against it, so that these slow queries won't be
able to tie up the rest of the system.

were changing the resolution, even if they weren't.

logged in.  Since they haven't logged in, we don't know what they will
be allowed to do.  And users who disable cookies tend to pretty often
not be logged in.

someone changed something.

"editbugs" and "canconfirm".  People without these states are now much
more limited in what they can do.

For backwards compatability, by default all users will have the
editbugs and canconfirm bits on them.  Installing this changes as is
should only have one major visible effect -- an UNCONFIRMED state
will appear in the query page.  But no bugs will become in that state,
until you tweak some of the new voting-related parameters you'll find
when editing products.

Lock the tables as low-priority when writing.  Maybe makes people making changes wait longer, but people doing read-only stuff should now never block for very long.

bug was actually a legal bug number.

should have always had this behavior.