Bugzilla cleanup: unassigning "abandoned" bugs

[denise]

We currently have 196 bugs in the ASSIGNED state, many of which have been assigned for a while, or are assigned to people who seem to have left DW development. In order to clean up Bugzilla a bit, and in order to make sure that wanted features don't wind up languishing further, I will be going through Bugzilla sometime in the next week or two and unassigning "abandoned" bugs -- bugs that are in the ASSIGNED state that have had no activity on them since 1 January 2011.

If you have a bug assigned to you that has had no activity since then, and you do still intend to work on the bug, just leave a comment on it saying "Still working on this!" If I unassign a bug for appearing abandoned and you're still intending to work on it, feel free to reassign it back to you.

If there's a bug you have a partial patch written for and have gotten stuck, and the reason the bug looks abandoned is that you haven't been able to get past the stuck-ness, you can attach the patch to the bug without adding either the review or commit flags. Be sure to label the patch "partial implementation", or note in the comments when you attach the patch that it's not a working patch!

If there's a bug that you wrote a patch for and the patch didn't pass review, and the bug hasn't been touched since 1 January 2011 to revise the patch based on the review, I'll unassign the bug for someone to come along and update the patch and revise it based on the review feedback. If this happens, you'll still be credited for the patch!

installing: $LJHOME/cvs/LJ-UserSearch/install-into-ljhome has wrong location for thread-multi

[denise]

Found by AgentCooper in irc:

$LJHOME/cvs/LJ-UserSearch/install-into-ljhome, on line 24, points to $LJHOME/cgi-bin/x86_64-linux-thread-multi/.... ... but the file is actually x86_64-linux-gnu-thread-multi .

This is an upstream bug -- we don't have a local fork of that repository -- and so the information has been passed upstream. In the meantime, install issues revolving around this can be fixed by changing the name to be the proper location.

is this a bug, or is this something busted on my 'hack?

[denise]

While working tonight, I noticed that something may have broken comment email notification. I'm not getting any notifications of comments made to any journal (even when I was getting those notifications before -- that is, it's not a problem with the ESN workers not running) and in my Apache logs, whenever a comment is posted, I get:

( error messages in apache logs )

Did we break something, or did I break my 'hack somehow? *g* (I'm using the most recent code, I swear!)