* InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for
InnoDB tables from concurrent threads could cause a deadlock, particularly
with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks
caused by the same row being accessed by more than one transaction. Deadlocks
could still occur when multiple rows are inserted and updated simultaneously
by different transactions in inconsistent order; those types of deadlocks
require the standard error handling on the application side, of re-trying the
transaction.
* An incorrect InnoDB assertion could cause the server to halt. This issue only
affected debug builds. The assertion referenced the source file btr0pcur.ic
and the variable cursor->pos_state.
* The handle_segfault() signal-handler code in mysqld could itself crash due to
calling unsafe functions.
* ARCHIVE tables with NULL columns could cause server crashes or become corrupt
under concurrent load.
* Enabling myisam_use_mmap could cause the server to crash.
* Concurrent access to ARCHIVE tables could cause corruption.
* Don't specify upper limit version to depend. Since PHP extensions are
prefixed with PHP_PKG_PREFIX, it is no need to specify.
* Relax lower limit version to depend for php extensions which aren't
bundled in PHP 5.3.9 distribution file; reflecting recent change of
lang/php/ext.mk
To be safer, bump PKGREVISION.
* A new server option, --slow-start-timeout, controls the Windows service
control manager's service start timeout. The value is the maximum number of
milliseconds that the service control manager waits before trying to kill the
MySQL service during startup. The default value is 15000 (15 seconds). If the
MySQL service takes too long to start, you may need to increase this value.
A value of 0 means there is no timeout.
Bugs Fixed:
* Important Change: Replication: Setting an empty user in a CHANGE MASTER TO
statement caused an invalid internal result and is no longer permitted. Trying to use MASTER_USER='' or setting MASTER_PASSWORD while leaving MASTER_USER
unset causes the statement to fail with an error.
* Important Change: Replication: Moving the binary log file, relay log file, or
both files to a new location, then restarting the server with a new value for
--log-bin, --relay-log, or both, caused the server to abort on start. This
was because the entries in the index file overrode the new location. In
addition, paths were calculated relative to datadir (rather than to the
--log-bin or --relay-log values).
* InnoDB Storage Engine: When doing a live downgrade from MySQL 5.6.4 or later, with innodb_page_size set to a value other than 16384, now the earlier MySQL
version reports that the page size is incompatible with the older version,
rather than crashing or displaying a “corruption” error.
* InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for
InnoDB tables from concurrent threads could cause a deadlock, particularly
with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks
caused by the same row being accessed by more than one transaction. Deadlocks
could still occur when multiple rows are inserted and updated simultaneously
by different transactions in inconsistent order; those types of deadlocks
require the standard error handling on the application side, of re-trying the
transaction.
* An incorrect InnoDB assertion could cause the server to halt. This issue only
affected debug builds. The assertion referenced the source file btr0pcur.ic
and the variable cursor->pos_state.
* Locale information for FORMAT() function instances was lost in view
definitions.
* The handle_segfault() signal-handler code in mysqld could itself crash due to
calling unsafe functions.
* Enabling myisam_use_mmap could cause the server to crash.
* Concurrent access to ARCHIVE tables could cause corruption.
* Do not append a slash to the directory name if it already has one.
Changes 1.7.23:
* Ignore any attempt to use "-ow" with the "-d" or "-e" options, with warning.
* Include zlib.h if ZLIB_H is not defined (instead of checking the libpng
version; see entry below for pngcrush-1.7.14), and include string.h
if _STRING_H_ is not defined (because libpng-1.6 does not include string.h)
* Define SLASH = backslash on Windows platforms so the "-d" option will work.
What's new in 1.5.2 (December 2011)
===================================
Pertinent to users:
1. Fixed a warning that pops up when doing ``pip install pyblosxom``
2. Removed debug logging from pycategories
What's new in 1.5.1 (December 2011)
===================================
Pertinent to users:
-------------------
1. Fixed a problem with the manifest so ``python setup.py install``
works again.
2. Fixed the WHATSNEW so it shows correct version and date for
1.5 release.
What's new in 1.5 (December 2011)
=================================
Pertinent to users:
-------------------
1. Renamed the project from PyBlosxom to Pyblosxom (no more CamelCase).
2. I moved all the plugins again. This time, instead of being in
``plugins/``, they're now in ``Pyblosxom/plugins/``.
You no longer have to copy core plugins into your plugins
directory. Instead of copying core plugin files, refer to the
plugins in your ``config.py`` file using their full Python path in
the Pyblosxom package.
For example, the pycalendar plugin is now in
``Pyblosxom/plugins/pycalendar.py`` and thus its Pyblosxom
package path is ``Pyblosxom.plugins.pycalendar``. Your
``config.py`` file would look have this::
py["load_plugins"] = [
...
"Pyblosxom.plugins.pycalendar",
...
]
If you do this, then the next time you upgrade PyBlosxom, the
plugins will be upgraded automatically.
Further, documentation for plugins is at the top of the individual
plugin files, but also in the documentation. This includes a list
of the plugins available in the core.
.. only:: text
You can see the plugin documentation in docs/plugins/.
.. only:: html
You can see the plugin documentation at :ref:`part-two`.
3. Plugins added: markdown_parser, readmore
4. Plugins changed:
pages
* Fixed documentation and error messages for ``pagesdir``.
* Fixed frontpage checking. Should catch / as well as /index
now.
* Adds more examples to documentation.
tags
* Increased tag cloud range from 3 sizes to 5.
* Adds truncate support.
* Fixes problems with initialization when building tags so that
it initializes plugins allowing them to do startup things.
This fixes problems with plugins that augment entry parsers.
rst
* renamed it to rst_parser so it's clearer what it is
pycategories
* fixed category_start/category_begin behavior for root category
* fixed the first example of settings in the documentation
the rest of the plugins: pep8 fixes and documentation updates
5. Plugins removed from Pyblosxom: commentAPI
6. Fixes error handling for loading plugins. When doing
``pyblosxom-cmd test`` and a plugin fails to load, it'll now tell
you. When using the debug renderer and a plugin fails to load,
it'll now tell you.
7. Lot of work on simplifying and improving the documentation.
8. Added a ``static_yearindexes`` setting. Set it to True to generate
year indexes and False to not generate year indexes.
Pertinent to developers
-----------------------
1. I removed all the extra infrastructure for testing plugins.
Plugins that come with the core are now in the Pyblosxom package
and their tests are in ``Pyblosxom/tests/``.
2. Adds *generate* subcommand to pyblosxom-cmd. This makes it easier
to test blogs and plugins that do things with entries.
3. Renamed ``PyBlosxomWSGIApp`` class to ``PyblosxomWSGIApp``.
4. Renamed ``PyBlosxom`` class to ``Pyblosxom``.
5. Moved the project from gitorious to github. The new git repository
is at `<http://github.com/willkg/pyblosxom>`_.
6. Removed ``VERSION_DATE`` and ``VERSION_SPLIT``. They're kind of
silly and don't really help much.
I moved the version to ``Pyblosxom/_version.py``. Use it like
this::
from Pyblosxom import __version__
print __version__
I updated the documentation accordingly.
new major release, many changes, most notably:
-syntax scanner speed improvement
-UI and feature improvements
-new languages: Google Go, Vala and Ada
-zencoding support
