Custom Query (196 matches)

im a systems administrator and u suck

Tickets #1 and #2 (at least) in this Trac are broken. We should fix them.

scripts / trac-#127 / adehnert  22:36  (Alex Dehnert)
    adehnert filed a new ticket:
    ttants: 1, 687224

    http://scripts.mit.edu/trac/ should be aware that ticket number 1 is
    not the same as number 687224.
scripts / trac-not-#127 / andersk  01:20  (Anders Kaseorg)
    Huh.
    http://www.google.com/search?q=ticket+687224
    http://www.google.com/search?q=ticket+433633
scripts / trac-not-#127 / andersk  01:21  (Anders Kaseorg)
    Oh, I bet it complains that ticket 687224 doesn’t exist because it’s
    trying to linkify the text “[help.mit.edu #687224]” in the comment.
scripts / trac-not-#127 / quentin  01:22  (Quentin Smith)
    Oh. It's probably trying to check the permissions on that link...
scripts / trac-not-#127 / quentin  01:22  (Quentin Smith)
    (I didn't disable that part of the sensitivetickets plugin...)
scripts / trac-not-#127 / andersk  01:22  (Anders Kaseorg)
    Why… does it care about the permissions on that link?
scripts / trac-not-#127 / quentin  01:23  (Quentin Smith)
    Presumably because it's trying to find out the title and state of the
    tickets so it can put a TITLE on the link?

The sql.mit.edu servers currently have old_passwords=1 set in the mysqld configuration for compatibility with MySQL 3.x and 4.x clients. The ​MySQL native driver in PHP 5.3 only knows how to deal with ​new-style passwords; this will probably bite us hard when we move to PHP 5.3 as part of upgrading to Fedora 13.

We'll need to either figure out if we can do the backward-compatible but insecure hack of making PHP clients able to use old-style passwords (disable the native driver? patch it?), or if we can drop support for MySQL clients that don't support new-style passwords, i.e., 4.0.x and below.