summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2012-01-13need to buildlink with openssl for QtNetwork.obache1-1/+2
2012-01-13Updated filesystems/tahoe-lafs to 1.9.1gdt1-1/+2
2012-01-13Update to 1.9.1 (security fix):gdt3-15/+20
Release 1.9.1 (2012-01-12) -------------------------- Security-related Bugfix ''''''''''''''''''''''' - Fix flaw that would allow servers to cause undetected corruption when retrieving the contents of mutable files (both SDMF and MDMF). (`#1654`_) .. _`#1654`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1654
2012-01-12Updated x11/qt4 to 4.8.0adam1-1/+11
2012-01-12Changes 4.8.0:adam53-389/+300
Featuring Qt Platform Abstraction, threaded OpenGL support, multithreaded HTTP and optimized file system access.
2012-01-12This package's licence is NOT a "modified BSD" in a common sense.asau1-2/+4
Reset LICENSE, bump package revision.
2012-01-12Fix build on SunOS.hans2-6/+8
2012-01-12Updated security/oath-toolkit to 1.10.5pettai1-1/+2
2012-01-12Version 1.10.5pettai2-6/+6
* Build fixes from Linus Nordberg and Arno Hautala. * Update gnulib files.
2012-01-12Updated www/ap2-authn-otp to 1.1.4pettai1-1/+2
2012-01-12Version 1.1.4:pettai2-6/+6
- Always allow stale time-based offsets to re-synchronize (issue #14) - Added "OTPAuthMaxOTPFailure" to lock accounts after repeated wrong OTP's
2012-01-12+ py-django-mpttjoerg1-1/+3
+ py-django-sekizai
2012-01-12Simplify. Don't allow Python 3 due to unsupported setuptools dependency.joerg2-10/+6
2012-01-12py-sqlite3 doesn't exist for Python 2.4.joerg1-3/+5
2012-01-12Catch up with PHP 5.3 base.joerg1-2/+2
2012-01-12Updated graphics/pngcrush to 1.7.24; audio/libaudiofile to 0.3.3; ↵adam1-1/+7
databases/mysql55-{client,server} to 5.5.20; databases/mysql51-{client,server} to 5.1.61
2012-01-12Changes 5.1.61:adam4-11/+18
* 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.
2012-01-12Fix build on SunOS.hans3-3/+9
2012-01-12SunOS lacks strmode(), so get it from libnbcompat.hans1-1/+4
2012-01-12Note update of meta-pkgs/php53-extensions to 5.3.9nb2.taca1-1/+2
2012-01-12Fix build problem along with update of php53; overhaul.taca1-52/+52
* 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.
2012-01-12Changes 0.3.3:adam4-78/+20
* Update library's soname version. * Link against libm.
2012-01-12Changes 5.5.20:adam3-7/+15
* 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.
2012-01-12Changes 1.7.24:adam2-6/+6
* 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.
2012-01-12+mp3gaindrochner1-1/+2
2012-01-12add mp3gain-1.5.2, a Loudness normalizer for MP3 files, from Simon Schubertdrochner4-0/+37
per pkgsrc-wip
2012-01-12Fix build on SunOS.hans3-2/+28
2012-01-12Uses pod2man and pod2html.hans1-2/+2
2012-01-12Fix build on SunOS.hans1-1/+3
2012-01-12Add pod2text as host tool.hans1-2/+2
2012-01-12fix build and PLIST problems with the (optional) SDL plugin,drochner5-7/+31
mostly from PR pkg/45209 by Matthew Mondor
2012-01-12Default to lesstif instead of dt if X11_TYPE != native.hans1-2/+6
2012-01-12Look for /usr/dt only if X11_TYPE == native.hans1-2/+3
2012-01-12Fix build on SunOS.hans3-3/+35
2012-01-12Uses pod2man.hans1-2/+2
2012-01-12Fix build on SunOS.hans3-2/+14
2012-01-12Uses perl.hans1-2/+2
2012-01-12Uses pod2man.hans1-2/+2
2012-01-12Fix build on SunOS.hans6-9/+27
2012-01-12Fix build problem of databases/php-mssql.taca2-16/+1
2012-01-12Fix build with gfortran on SunOS and possibly others.hans3-560/+8101
Also tested on NetBSD/i386 5.1 with f2c.
2012-01-12Updated www/py-blosxom to 1.5.2hauke1-1/+2
2012-01-12Upgrade package to 1.5.2. From WHATSNEW:hauke3-177/+143
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.
2012-01-12sync w/ base pkgdrochner2-7/+6
2012-01-12update to 2.6drochner2-7/+6
changes: -based on Scintilla v2.29 -improved support for rebinding keys to commands
2012-01-12update to 2.29drochner4-32/+14
many fixes and improvements
2012-01-12update to 2.29drochner2-8/+7
many fixes and improvements, see the "History" file
2012-01-12update to 2.2.1drochner6-106/+84
new major release, many changes, most notably: -syntax scanner speed improvement -UI and feature improvements -new languages: Google Go, Vala and Ada -zencoding support
2012-01-12update to 0.4.3drochner3-8/+8
changes: -performance improvement -minor bugfixes -minor UI improvements
2012-01-12+ abcm2ps-6.6.2, aria2-1.14.1, libxcb-1.8, scrotwm-0.10.0,wiz1-4/+7
xcb-proto-1.7, xf86-video-vmware-11.1.0.
generated by cgit v1.2.3 (git 2.39.1) at 2024-10-04 07:06:44 +0000