Allow to additional post-processing PLIST with PLIST_AWK and PLIST_AWK_ENV.
prepare Python>=32 bytecode file location change
Update mysql51-{client,server} to 5.1.63 (MySQL 5.1.63).

Changes (http://dev.mysql.com/doc/refman/5.1/en/news-5-1-63.html):

     * Security Fix: Bug #64884 was fixed.

     * Security Fix: Bug #59387 was fixed.

     * InnoDB: Deleting a huge amount of data from InnoDB tables
       within a short time could cause the purge operation that
       flushes data from the buffer pool to stall. If this issue
       occurs, restart the server to work around it. This issue is
       only likely to occur on 32-bit platforms. (Bug #13847885)

     * InnoDB: If the server crashed during a TRUNCATE TABLE or
       CREATE INDEX statement for an InnoDB table, or a DROP DATABASE
       statement for a database containing InnoDB tables, an index
       could be corrupted, causing an error message when accessing
       the table after restart:
       InnoDB: Error: trying to load index index_name for table
       table_name
       InnoDB: but the index tree has been freed!
       In MySQL 5.1, this fix applies to the InnoDB Plugin, but not
       the built-in InnoDB storage engine. (Bug #12861864, Bug
       #11766019)

     * InnoDB: When data was removed from an InnoDB table, newly
       inserted data might not reuse the freed disk blocks, leading
       to an unexpected size increase for the system tablespace or
       .ibd file (depending on the setting of innodb_file_per_table.
       The OPTIMIZE TABLE could compact a .ibd file in some cases but
       not others. The freed disk blocks would eventually be reused
       as additional data was inserted. (Bug #11766634, Bug #59783)

     * Partitioning: After updating a row of a partitioned table and
       selecting that row within the same transaction with the query
       cache enabled, then performing a ROLLBACK, the same result was
       returned by an identical SELECT issued in a new transaction.
       (Bug #11761296, Bug #53775)

     * Replication: The --relay-log-space-limit option was sometimes
       ignored.
       More specifically, when the SQL thread went to sleep, it
       allowed the I/O thread to queue additional events in such a
       way that the relay log space limit was bypassed, and the
       number of events in the queue could grow well past the point
       where the relay logs needed to be rotated. Now in such cases,
       the SQL thread checks to see whether the I/O thread should
       rotate and provide the SQL thread a chance to purge the logs
       (thus freeing space).
       Note that, when the SQL thread is in the middle of a
       transaction, it cannot purge the logs; it can only ask for
       more events until the transaction is complete. Once the
       transaction is finished, the SQL thread can immediately
       instruct the I/O thread to rotate. (Bug #12400313, Bug #64503)
       References: See also Bug #13806492.

     * Mishandling of NO_BACKSLASH_ESCAPES SQL mode within stored
       procedures on slave servers could cause replication failures.
       (Bug #12601974)

     * If the system time was adjusted backward during query
       execution, the apparent execution time could be negative. But
       in some cases these queries would be written to the slow query
       log, with the negative execution time written as a large
       unsigned number. Now statements with apparent negative
       execution time are not written to the slow query log. (Bug
       #63524, Bug #13454045) References: See also Bug #27208.

     * mysql_store_result() and mysql_use_result() are not for use
       with prepared statements and are not intended to be called
       following mysql_stmt_execute(), but failed to return an error
       when invoked that way in libmysqld. (Bug #62136, Bug
       #13738989) References: See also Bug #47485.

     * SHOW statements treated stored procedure, stored function, and
       event names as case sensitive. (Bug #56224, Bug #11763507)

     * On Windows, mysqlslap crashed for attempts to connect using
       shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug
       #11766072)
Note update of mysql51-{client,server} to 5.1.63.
Update mysql55-{client,server} to 5.55.24.

Changes (http://dev.mysql.com/doc/refman/5.5/en/news-5-5-24.html):

Functionality Added or Changed

    * Important Change: Replication: INSERT ON DUPLICATE KEY UPDATE is now
      marked as unsafe for statement-based replication if the target table has
      more than one primary or unique key. For more information, see Section
      16.1.2.3, "Determination of Safe and Unsafe Statements in Binary
      Logging".

Bugs Fixed

    * Security Fix: Bug #64884 was fixed.

    * InnoDB: Replication: When binary log statements were replayed on the
      slave, the Com_insert, Com_update, and Com_delete counters were
      incremented by BEGIN statements initiating transactions affecting InnoDB
      tables but not by COMMIT statements ending such transactions. This
      affected these statements whether they were replicated or they were run
      using mysqlbinlog. (Bug #12662190)

    * If the --bind-address option was given a host name value and the host
      name resolved to more than one IP address, the server failed to
      start. For example, with --bind-address=localhost, if localhost resolved
      to both 127.0.0.1 and ::1, startup failed. Now the server prefers the
      IPv4 address in such cases. (Bug #61713, Bug #12762885)

    * mysql_store_result() and mysql_use_result() are not for use with
      prepared statements and are not intended to be called following
      mysql_stmt_execute(), but failed to return an error when invoked that
      way in libmysqld. (Bug #62136, Bug #13738989)

      References: See also Bug #47485.

    * On Windows, mysqlslap crashed for attempts to connect using shared
      memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)
Note update of mysql55-{client,server} to 5.55.24.
Updated pkgtools/pkg_chk to 2.0.1

ensure OS and arch tags are set in the binary package case as well as source
set x11 for R7 as ell as R6
Updated pkgtools/pkg_chk to 2.0.1