summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2015-02-09Recursive bump for SDL2-using packages.snj13-17/+26
2015-02-09Updated devel/SDL2 to 2.0.3nb5snj1-1/+2
2015-02-09Switch SDL2 to the standard autotools build system. Upstream considerssnj7-125/+47
the CMake build system to be experimental. This gets us working joystick support on NetBSD, avoids installing bogus headers, and moves us to a sane library major (which is highly unlikely to ever change again). Bump PKGREVISION to 5 and set BUILDLINK_ABI_DEPENDS accordingly. Recursive revbump coming up. While here, tidy up this package's options a bit: - instead of providing six (!) options for standard modern X libraries, simply lump them all into the existing x11 option - provide a dbus option
2015-02-09Requires C99fhajny1-1/+2
2015-02-09Updated databases/mysql-cluster to 7.3.8jnemeth1-1/+2
2015-02-09Update to MySQL Cluster 7.3.8:jnemeth3-9/+73
Changes in MySQL Cluster NDB 7.3.8 (5.6.22-ndb-7.3.8) (2015-01-21) MySQL Cluster NDB 7.3.8 is a new release of MySQL Cluster, based on MySQL Server 5.6 and including features from version 7.3 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous MySQL Cluster releases. This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.22 (see Changes in MySQL 5.6.22 (2014-12-01)). Functionality Added or Changed * Performance: Recent improvements made to the multithreaded scheduler were intended to optimize the cache behavior of its internal data structures, with members of these structures placed such that those local to a given thread do not overflow into a cache line which can be accessed by another thread. Where required, extra padding bytes are inserted to isolate cache lines owned (or shared) by other threads, thus avoiding invalidation of the entire cache line if another thread writes into a cache line not entirely owned by itself. This optimization improved MT Scheduler performance by several percent. It has since been found that the optimization just described depends on the global instance of struct thr_repository starting at a cache line aligned base address as well as the compiler not rearranging or adding extra padding to the scheduler struct; it was also found that these prerequisites were not guaranteed (or even checked). Thus this cache line optimization has previously worked only when g_thr_repository (that is, the global instance) ended up being cache line aligned only by accident. In addition, on 64-bit platforms, the compiler added extra padding words in struct thr_safe_pool such that attempts to pad it to a cache line aligned size failed. The current fix ensures that g_thr_repository is constructed on a cache line aligned address, and the constructors modified so as to verify cacheline aligned adresses where these are assumed by design. Results from internal testing show improvements in MT Scheduler read performance of up to 10% in some cases, following these changes. (Bug #18352514) * Cluster API: Two new example programs, demonstrating reads and writes of CHAR, VARCHAR, and VARBINARY column values, have been added to storage/ndb/ndbapi-examples in the MySQL Cluster source tree. For more information about these programs, including source code listings, see NDB API Simple Array Example, and NDB API Simple Array Example Using Adapter. Bugs Fixed * The global checkpoint commit and save protocols can be delayed by various causes, including slow disk I/O. The DIH master node monitors the progress of both of these protocols, and can enforce a maximum lag time during which the protocols are stalled by killing the node responsible for the lag when it reaches this maximum. This DIH master GCP monitor mechanism did not perform its task more than once per master node; that is, it failed to continue monitoring after detecting and handling a GCP stop. (Bug #20128256) References: See also Bug #19858151. * When running mysql_upgrade on a MySQL Cluster SQL node, the expected drop of the performance_schema database on this node was instead performed on all SQL nodes connected to the cluster. (Bug #20032861) * A number of problems relating to the fired triggers pool have been fixed, including the following issues: + When the fired triggers pool was exhausted, NDB returned Error 218 (Out of LongMessageBuffer). A new error code 221 is added to cover this case. + An additional, separate case in which Error 218 was wrongly reported now returns the correct error. + Setting low values for MaxNoOfFiredTriggers led to an error when no memory was allocated if there was only one hash bucket. + An aborted transaction now releases any fired trigger records it held. Previously, these records were held until its ApiConnectRecord was reused by another transaction. + In addition, for the Fired Triggers pool in the internal ndbinfo.ndb$pools table, the high value always equalled the total, due to the fact that all records were momentarily seized when initializing them. Now the high value shows the maximum following completion of initialization. (Bug #19976428) * Online reorganization when using ndbmtd data nodes and with binary logging by mysqld enabled could sometimes lead to failures in the TRIX and DBLQH kernel blocks, or in silent data corruption. (Bug #19903481) References: See also Bug #19912988. * The local checkpoint scan fragment watchdog and the global checkpoint monitor can each exclude a node when it is too slow when participating in their respective protocols. This exclusion was implemented by simply asking the failing node to shut down, which in case this was delayed (for whatever reason) could prolong the duration of the GCP or LCP stall for other, unaffected nodes. To minimize this time, an isolation mechanism has been added to both protocols whereby any other live nodes forcibly disconnect the failing node after a predetermined amount of time. This allows the failing node the opportunity to shut down gracefully (after logging debugging and other information) if possible, but limits the time that other nodes must wait for this to occur. Now, once the remaining live nodes have processed the disconnection of any failing nodes, they can commence failure handling and restart the related protocol or protocol, even if the failed node takes an excessiviely long time to shut down. (Bug #19858151) References: See also Bug #20128256. * A watchdog failure resulted from a hang while freeing a disk page in TUP_COMMITREQ, due to use of an uninitialized block variable. (Bug #19815044, Bug #74380) * Multiple threads crashing led to multiple sets of trace files being printed and possibly to deadlocks. (Bug #19724313) * When a client retried against a new master a schema transaction that failed previously against the previous master while the latter was restarting, the lock obtained by this transaction on the new master prevented the previous master from progressing past start phase 3 until the client was terminated, and resources held by it were cleaned up. (Bug #19712569, Bug #74154) * When using the NDB storage engine, the maximum possible length of a database or table name is 63 characters, but this limit was not always strictly enforced. This meant that a statement using a name having 64 characters such CREATE DATABASE, DROP DATABASE, or ALTER TABLE RENAME could cause the SQL node on which it was executed to fail. Now such statements fail with an appropriate error message. (Bug #19550973) * When a new data node started, API nodes were allowed to attempt to register themselves with the data node for executing transactions before the data node was ready. This forced the API node to wait an extra heartbeat interval before trying again. To address this issue, a number of HA_ERR_NO_CONNECTION errors (Error 4009) that could be issued during this time have been changed to Cluster temporarily unavailable errors (Error 4035), which should allow API nodes to use new data nodes more quickly than before. As part of this fix, some errors which were incorrectly categorised have been moved into the correct categories, and some errors which are no longer used have been removed. (Bug #19524096, Bug #73758) * When executing very large pushdown joins involving one or more indexes each defined over several columns, it was possible in some cases for the DBSPJ block (see The DBSPJ Block) in the NDB kernel to generate SCAN_FRAGREQ signals that were excessively large. This caused data nodes to fail when these could not be handled correctly, due to a hard limit in the kernel on the size of such signals (32K). This fix bypasses that limitation by breaking up SCAN_FRAGREQ data that is too large for one such signal, and sending the SCAN_FRAGREQ as a chunked or fragmented signal instead. (Bug #19390895) * ndb_index_stat sometimes failed when used against a table containing unique indexes. (Bug #18715165) * Queries against tables containing a CHAR(0) columns failed with ERROR 1296 (HY000): Got error 4547 'RecordSpecification has overlapping offsets' from NDBCLUSTER. (Bug #14798022) * In the NDB kernel, it was possible for a TransporterFacade object to reset a buffer while the data contained by the buffer was being sent, which could lead to a race condition. (Bug #75041, Bug #20112981) * mysql_upgrade failed to drop and recreate the ndbinfo database and its tables as expected. (Bug #74863, Bug #20031425) * Due to a lack of memory barriers, MySQL Cluster programs such as ndbmtd did not compile on POWER platforms. (Bug #74782, Bug #20007248) * In some cases, when run against a table having an AFTER DELETE trigger, a DELETE statement that matched no rows still caused the trigger to execute. (Bug #74751, Bug #19992856) * A basic requirement of the NDB storage engine's design is that the transporter registry not attempt to receive data (TransporterRegistry::performReceive()) from and update the connection status (TransporterRegistry::update_connections()) of the same set of transporters concurrently, due to the fact that the updates perform final cleanup and reinitialization of buffers used when receiving data. Changing the contents of these buffers while reading or writing to them could lead to "garbage" or inconsistent signals being read or written. During the course of work done previously to improve the implementation of the transporter facade, a mutex intended to protect against the concurrent use of the performReceive() and update_connections()) methods on the same transporter was inadvertently removed. This fix adds a watchdog check for concurrent usage. In addition, update_connections() and performReceive() calls are now serialized together while polling the transporters. (Bug #74011, Bug #19661543) * ndb_restore failed while restoring a table which contained both a built-in conversion on the primary key and a staging conversion on a TEXT column. During staging, a BLOB table is created with a primary key column of the target type. However, a conversion function was not provided to convert the primary key values before loading them into the staging blob table, which resulted in corrupted primary key values in the staging BLOB table. While moving data from the staging table to the target table, the BLOB read failed because it could not find the primary key in the BLOB table. Now all BLOB tables are checked to see whether there are conversions on primary keys of their main tables. This check is done after all the main tables are processed, so that conversion functions and parameters have already been set for the main tables. Any conversion functions and parameters used for the primary key in the main table are now duplicated in the BLOB table. (Bug #73966, Bug #19642978) * Corrupted messages to data nodes sometimes went undetected, causing a bad signal to be delivered to a block which aborted the data node. This failure in combination with disconnecting nodes could in turn cause the entire cluster to shut down. To keep this from happening, additional checks are now made when unpacking signals received over TCP, including checks for byte order, compression flag (which must not be used), and the length of the next message in the receive buffer (if there is one). Whenever two consecutive unpacked messages fail the checks just described, the current message is assumed to be corrupted. In this case, the transporter is marked as having bad data and no more unpacking of messages occurs until the transporter is reconnected. In addition, an entry is written to the cluster log containing the error as well as a hex dump of the corrupted message. (Bug #73843, Bug #19582925) * Transporter send buffers were not updated properly following a failed send. (Bug #45043, Bug #20113145) * ndb_restore --print_data truncated TEXT and BLOB column values to 240 bytes rather than 256 bytes. * Disk Data: An update on many rows of a large Disk Data table could in some rare cases lead to node failure. In the event that such problems are observed with very large transactions on Disk Data tables you can now increase the number of page entries allocated for disk page buffer memory by raising the value of the DiskPageBufferEntries data node configuration parameter added in this release. (Bug #19958804) * Disk Data: When a node acting as a DICT master fails, the arbitrator selects another node to take over in place of the failed node. During the takeover procedure, which includes cleaning up any schema transactions which are still open when the master failed, the disposition of the uncommitted schema transaction is decided. Normally this transaction be rolled back, but if it has completed a sufficient portion of a commit request, the new master finishes processing the commit. Until the fate of the transaction has been decided, no new TRANS_END_REQ messages from clients can be processed. In addition, since multiple concurrent schema transactions are not supported, takeover cleanup must be completed before any new transactions can be started. A similar restriction applies to any schema operations which are performed in the scope of an open schema transaction. The counter used to coordinate schema operation across all nodes is employed both during takeover processing and when executing any non-local schema operations. This means that starting a schema operation while its schema transaction is in the takeover phase causes this counter to be overwritten by concurrent uses, with unpredictable results. The scenarios just described were handled previously using a pseudo-random delay when recovering from a node failure. Now we check before the new master has rolled forward or backwards any schema transactions remaining after the failure of the previous master and avoid starting new schema transactions or performing operations using old transactions until takeover processing has cleaned up after the abandoned transaction. (Bug #19874809, Bug #74503) * Disk Data: When a node acting as DICT master fails, it is still possible to request that any open schema transaction be either committed or aborted by sending this request to the new DICT master. In this event, the new master takes over the schema transaction and reports back on whether the commit or abort request succeeded. In certain cases, it was possible for the new master to be misidentified--that is, the request was sent to the wrong node, which responded with an error that was interpreted by the client application as an aborted schema transaction, even in cases where the transaction could have been successfully committed, had the correct node been contacted. (Bug #74521, Bug #19880747) * Cluster Replication: When an NDB client thread made a request to flush the binary log using statements such as FLUSH BINARY LOGS or SHOW BINLOG EVENTS, this caused not only the most recent changes made by this client to be flushed, but all recent changes made by all other clients to be flushed as well, even though this was not needed. This behavior caused unnecessary waiting for the statement to execute, which could lead to timeouts and other issues with replication. Now such statements flush the most recent database changes made by the requesting thread only. As part of this fix, the status variables Ndb_last_commit_epoch_server, Ndb_last_commit_epoch_session, and Ndb_slave_max_replicated_epoch, originally implemented in MySQL Cluster NDB 7.4, are also now available in MySQL Cluster NDB 7.3. For descriptions of these variables, see MySQL Cluster Status Variables; for further information, see MySQL Cluster Replication Conflict Resolution. (Bug #19793475) * Cluster Replication: It was possible using wildcards to set up conflict resolution for an exceptions table (that is, a table named using the suffix $EX), which should not be allowed. Now when a replication conflict function is defined using wildcard expressions, these are checked for possible matches so that, in the event that the function would cover an exceptions table, it is not set up for this table. (Bug #19267720) * Cluster API: It was possible to delete an Ndb_cluster_connection object while there remained instances of Ndb using references to it. Now the Ndb_cluster_connection destructor waits for all related Ndb objects to be released before completing. (Bug #19999242) References: See also Bug #19846392. * Cluster API: The buffer allocated by an NdbScanOperation for receiving scanned rows was not released until the NdbTransaction owning the scan operation was closed. This could lead to excessive memory usage in an application where multiple scans were created within the same transaction, even if these scans were closed at the end of their lifecycle, unless NdbScanOperation::close() was invoked with the releaseOp argument equal to true. Now the buffer is released whenever the cursor navigating the result set is closed with NdbScanOperation::close(), regardless of the value of this argument. (Bug #75128, Bug #20166585) * ClusterJ: The following errors were logged at the SEVERE level; they are now logged at the NORMAL level, as they should be: + Duplicate primary key + Duplicate unique key + Foreign key constraint error: key does not exist + Foreign key constraint error: key exists (Bug #20045455) * ClusterJ: The com.mysql.clusterj.tie class gave off a logging message at the INFO logging level for every single query, which was unnecessary and was affecting the performance of applications that used ClusterJ. (Bug #20017292) * ClusterJ: ClusterJ reported a segmentation violation when an application closed a session factory while some sessions were still active. This was because MySQL Cluster allowed an Ndb_cluster_connection object be to deleted while some Ndb instances were still active, which might result in the usage of null pointers by ClusterJ. This fix stops that happening by preventing ClusterJ from closing a session factory when any of its sessions are still active. (Bug #19846392) References: See also Bug #19999242.
2015-02-09I might as well un-abandon this package.snj1-2/+2
2015-02-09Updated graphics/jasper to 1.900.1nb10snj1-1/+2
2015-02-09These go to eleven.snj7-12/+43
revbump-2.11: - Honor PKGSRCDIR in check-cvs-diff and replace-commonbump - Document PKGSRCDIR all the man pages, not just in finddepends(1)
2015-02-09Clean up +UseSerialGC handling and ensure it is set for the entire build.tnn14-49/+84
(has anyone analyzed the concurrent GC memory allocation problem?) Bump PKGREVISION for this and previous changes.
2015-02-08Optionalize debug, X11 and ZeroVM similar to lang/openjdk8 + minor cleanupstnn8-168/+157
2015-02-08Fix CVE-2014-8157 and CVE-2014-8158. Bump PKGREVISION to 10.snj4-4/+350
2015-02-08Updated graphics/ImageMagick to 6.9.0.5snj1-1/+2
2015-02-08Update ImageMagick to 6.9.0-5. Changes:snj2-6/+6
2015-02-08 6.9.0-5 Cristy <quetzlzacatenango@image...> * New version 6.9.0-5, SVN revision 17946. 2015-01-30 6.9.0-5 Glenn Randers-Pehrson <glennrp@image...> * In coders/gif.c, quiet two warnings. 2015-01-24 6.9.0-5 Dirk Lemstra <dirk@lem.....org> * Fixed iccColorProfile() in Magick++ (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=2&t=26910). * Fixed infinite loop in HDR reader (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=26929). 2015-01-23 6.9.0-5 Glenn Randers-Pehrson <glennrp@image...> * Check lengths of certain MNG chunks before reading them. * In the PNG codec, check status wherever a function returns it. 2015-01-18 6.9.0-5 Cristy <quetzlzacatenango@image...> * Remove possible resource memory leak in a multi-threaded program (bug report and patch from David Chapman <d...@acm.org>. * Small optimization to pixel cache. * More image sanity checks. * Support writing base64-encoded images (e.g convert logo: inline:jpeg:logo.txt). * Repair small TIFF leak when pinging (patch provided by Andrey Cherniy). 2015-01-16 6.9.0-4 Cristy <quetzlzacatenango@image...> * New version 6.9.0-4, SVN revision 17697. 2015-01-07 6.9.0-4 Cristy <quetzlzacatenango@image...> * Additional coder sanity checks (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=26842, http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=26682). 2015-01-05 6.9.0-4 Dirk Lemstra <dirk@lem.....org> * Report Ghostscript version when -verbose is used and when an exception is raised. * Fixed invalid path check in MagickCoreGenesis under Windows and disabled ProvideDllMain by default (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&p=118875). 2015-01-01 6.9.0-3 Cristy <quetzlzacatenango@image...> * New version 6.9.0-3, SVN revision 17537. 2015-01-01 6.9.0-3 Cristy <quetzlzacatenango@image...> * ImageMagick builds when HDRI is enabled (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=26803). 2014-12-31 6.9.0-3 Glenn Randers-Pehrson <glennrp@image...> * Don't read beyond the end of a tEXt keyword when checking for Raw profile. 2014-12-27 6.9.0-2 Cristy <quetzlzacatenango@image...> * New version 6.9.0-2, SVN revision 17468. 2014-12-14 6.9.0-1 Dirk Lemstra <dirk@snakeware...> * Added support for reading EXR files to the Windows distribution. * Fixed enabling alpha in 32-bit BMP files (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=26662). * Added support for writing 16-bit TGA files (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=1&t=26693). * Improved performance of dds:cluster-fit when OpenMP is enabled. * Added support for distributed pixel cache to the Windows distribution. 2014-12-04 6.9.0-1 Alexey Dolgavin <dolgavin.alexey@gmail...> * Fix ImageMagick crashes while read EXIF from TIFF. 2014-11-20 6.9.0-1 Glenn Randers-Pehrson <glennrp@image...> * Don't handle a "previous" image in the PNG or JNG decoder. * Don't override gamma with 1.0 when reading a grayscale PNG image (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=26576). * Update progress monitor for every PNG row instead of every pass (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=1&t=26589). * Reject input PNG with dimensions larger than specified with -limit width and -limit height. 2014-11-20 6.9.0-1 Cristy <quetzlzacatenango@image...> * Fix double free / invalid read when converting jpg to pdb (thanks to Hanno). * Maximum XWD image size is 64Kx64K (thanks to Hanno). * Maximum DPX number of elements is 8 (thanks to Hanno). * Transient problem with SVG (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=26587). * Numerous buffer overflow fixes (thanks to Gynvael Coldwind and Mateusz Jurczyk of the Google Security Team). * Additional PNM sanity checks (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=26682). * The SetImageBias() bias value is no longer ignored (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=25732). * Area crop now returns the expected number of tiles (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=26701). * Respect TGA ColorMapIndex field (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=26738). * Clang does not support __alloc_size__, fix fabs() (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=26739). * Support width and height resource limits. * Don't read TIFF profiles when pinging (reference http://www.imagemagick.org/discourse-server/viewtopic.php?f=2&t=26670).
2015-02-08Try improving DESCR for joerg.wiz1-3/+3
2015-02-08Set WRKSRC a bit safer. Fixes build with PHP_VERSION_DEFAULT=53.fhajny1-2/+2
2015-02-08Updated to httpie 0.9.1imil3-15/+41
0.9.1 (2015-02-07) * Added support for Requests transport adapter plugins to enable plugin-provided features such as unix socket communication and HTTP/2. 0.9.0 (2015-01-31) * Added --cert and --cert-key parameters to specify a client side certificate and private key for SSL * Improved unicode support. * Improved terminal color depth detection via curses. * To make it easier to deal with Windows paths in request items, \ now only escapes special characters (the ones that are used as key-value separators by HTTPie). * Switched from unittest to pytest. * Added Python wheel support. * Various test suite improvements. * Added CONTRIBUTING. * Fixed User-Agent overwriting when used within a session. * Fixed handling of empty passwords in URL credentials. * Fixed multiple file uploads with the same form field name. * Fixed --output=/dev/null on Linux. * Miscellaneous bugfixes.
2015-02-08Also specify linker search path. Fixes build on at least SunOS.fhajny1-2/+2
2015-02-08Fix build on SunOS.fhajny2-1/+19
2015-02-08Added net/tigervnc version 1.3.1wiz1-1/+2
2015-02-08+ tigervnc.wiz1-1/+2
2015-02-08Import tigervnc-1.3.1 as net/tigervnc, packaged for wip by myselfwiz11-0/+408
and mwdavies, who added the Xvnc build. TigerVNC is a high-performance, platform-neutral implementation of VNC (Virtual Network Computing), a client/server application that allows users to launch and interact with graphical applications on remote machines. TigerVNC provides the levels of performance necessary to run 3D and video applications, and it attempts to maintain a common look and feel and re-use components, where possible, across the various platforms that it supports. TigerVNC also provides extensions for advanced authentication methods and TLS encryption.
2015-02-08Fix strict aligment issue. While here, update homepage.tnn4-3/+44
2015-02-08Strict alignment. Upstream issue #273tnn4-3/+35
2015-02-08Choose to trust upstream about this being fixed.gdt1-41/+0
Also, avoid setting a questionable precedent of leaving unused patch files around.
2015-02-08Infrastructure glue for openjdk8tnn2-10/+25
2015-02-08Add some bug report URLs.wiz3-4/+6
2015-02-08Added shells/autojump version 22.2.4wiz1-1/+2
2015-02-08+ autojump.wiz1-1/+2
2015-02-08Import autojump-22.2.4 as shells/autojump.wiz5-0/+74
autojump is a faster way to navigate your filesystem. It works by maintaining a database of the directories you use the most from the command line. Directories must be visited first before they can be jumped to.
2015-02-08fix hilarious typotnn1-2/+2
2015-02-08FreeBSD/clang build fixtnn1-1/+3
2015-02-08Added sysutils/rmtrash version 1.8wiz1-1/+2
2015-02-08+ rmtrash.wiz1-1/+2
2015-02-08Import rmtrash-1.8 as sysutils/rmtrash.wiz4-0/+38
Put files (and directories) in trash using the trash-put command in a way that is, otherwise as trash-put itself, compatible to GNUs rm and rmdir.
2015-02-08Added shells/git-sh version 1.3wiz1-1/+2
2015-02-08+ git-sh.wiz1-1/+2
2015-02-08Import git-sh-1.3 as shells/git-sh.wiz4-0/+44
git-sh is a customized bash shell suitable for git work. The git-sh command starts an interactive bash shell tweaked for heavy git interaction: * All git commands available at top-level (checkout master = git checkout master) * All git aliases defined in the [alias] section of ~/.gitconfig available at top-level. * Shawn O. Pearce's excellent bash completion strapped onto all core commands and git aliases. * Custom prompt with current branch, repository, and work tree dirty indicator. * Customizable via /etc/gitshrc and ~/.gitshrc config files; for creating aliases, changing the prompt, etc. * Runs on top of normal bash (~/.bashrc) and readline (~/.inputrc) configurations.
2015-02-08Drop patch as superceded by upstream changes.gdt3-29/+35
Upstream says that this patch is no longer necessary because an equivalent change was applied elsewhere in the code. Until we're sure, park the patch by dropping from distinfo and commenting out the patch contents, leaving a note in the patchfile about why.
2015-02-08Updated devel/py-virtualenv to 12.0.7wiz2-3/+3
2015-02-08Update to 12.0.7:wiz3-8/+8
12.0.7 (2015-02-04) ~~~~~~~~~~~~~~~~~~~ * Upgrade pip to 6.0.8
2015-02-08Updated security/py-keyring to 5.0wiz2-3/+3
2015-02-08Update to 5.0:wiz2-6/+6
--- 5.0 --- * Version numbering is now derived from the code repository tags via `hgtools <https://pypi.python.org/pypi/hgtools>`_. * Build and install now requires setuptools.
2015-02-08Updated devel/py-tortoisehg to 3.3wiz2-3/+3
2015-02-08Update to 3.3:wiz3-7/+11
TortoiseHg 3.3 TortoiseHg 3.3 is a regularly scheduled feature release Bug Fixes annotate: fetch line information by command (fixes unsafe thread access) cmdcore: handle ui labels in unicode to avoid possible exception (fixes #3988) guifork: use real fork() on posix to run GUI in background (fixes #3701) init: open repo in existing workbench process if any (fixes #3922) init: run "hg init" in command process (fixes #3931) lfprompt: parse minsize as float value (fixes #1901 again) qtapp: handle SIGINT more gracefully by sending close event to all windows repomodel: work around RepoLookupError that may occur while reload is pending repowidget: switch to default task tab after initial revision is selected sync: drop "recurse into subrepositories" option (closes #1645) workbench: disable back/forward actions when all repositories are closed workbench: make sure to run workbench by "New Workbench" action workbench: narrow --newworkbench option to command scope workbench: show busy indicator while command is running (fixes #1186) Improvements clone, init: open workbench after repository created by standalone dialog filectxactions: open file history dialog in annotate mode (closes #3760) init: add option to copy user files instead of empty .hgignore (closes #3569) reporegistry: mark shared repositories with a link icon overlay repotab: stop filesystem watcher of background tabs sync: never switch task tabs on revision selected sync: provide standalone dialog by LightRepoWindow workbench: forcibly reload models and views by Ctrl+refresh workbench: make it possible to restore the selected sync path across restarts workbench: restore last open repositories without loading them workbench: resurrect docked console widget (closes #3984) graph: color: use "color hashing" to pick a color for each branch (closes #3490) color: use "color hashing" to pick a color for each user graph: support the branch grouping experiment from mercurial core repomodel: hide all revisions if no matches found for the given revset query repomodel: rerun last revset query on reload (closes #1705) repoview: use a square shape for secret changesets repoview: use a pentagon shape for draft changesets command: log: add -r option to specify the initial revision to be selected log: add -k/--query option to filter changesets by keyword or revset nautilus/caja: add Python Caja extension support (fixes #3936)
2015-02-08Updated databases/shared-mime-info to 1.4wiz2-3/+3
2015-02-08Update to 1.4:wiz3-7/+16
shared-mime-info 1.4 (2015-02-05) * Add glob for low-resolution videos from GoPro * Add mime-type for partially downloaded files * Use IANA registered mime-type for Debian packages * Add another magic for OTF fonts * Add support for Adobe PageMaker * Remove the Apple iOS PNG variant * Add *.dbk glob for DocBook * Use IANA registered mime-type for Vivo * Remove obsolete application/x-gmc-link mime-type * Make application/x-wais-source a subclass of text/plain * Flip application/smil+xml and application/smil type/alias * Add Nintendo 64 ROM magic * Add qpress archive support * Add image/x-tiff-multipage mime-type * Rename "Microsoft icon" to "Windows icon" * Add magic for ODB files * Use IANA registered text/markdown for Markdown * New mimetype for SCons scripts as subclass of x-python * Make application/pgp-encrypted a subclass of text/plain * Associate *.qmltypes and *.qmlproject files with the text/x-qml mime type * Add text/x-genie mime type for Genie source code * Disable fdatasync() usage if PKGSYSTEM_ENABLE_FSYNC is set * Skip mime database update if packages are older than cache * Add "-n" option to update-mime-database to only update if "newer"
2015-02-08Updated www/py-tornado to 4.1wiz2-3/+3
2015-02-08Update to 4.1:wiz3-7/+10
Highlights If a Future contains an exception but that exception is never examined or re-raised (e.g. by yielding the Future), a stack trace will be logged when the Future is garbage-collected. New class tornado.gen.WaitIterator provides a way to iterate over Futures in the order they resolve. The tornado.websocket module now supports compression via the âpermessage-deflateâ extension. Override WebSocketHandler.get_compression_options to enable on the server side, and use the compression_options keyword argument to websocket_connect on the client side. When the appropriate packages are installed, it is possible to yield asyncio.Future or Twisted Defered objects in Tornado coroutines. Backwards-compatibility notes HTTPServer now calls start_request with the correct arguments. This change is backwards-incompatible, afffecting any application which implemented HTTPServerConnectionDelegate by following the example of Application instead of the documented method signatures. tornado.concurrent If a Future contains an exception but that exception is never examined or re-raised (e.g. by yielding the Future), a stack trace will be logged when the Future is garbage-collected. Future now catches and logs exceptions in its callbacks. tornado.curl_httpclient tornado.curl_httpclient now supports request bodies for PATCH and custom methods. tornado.curl_httpclient now supports resubmitting bodies after following redirects for methods other than POST. curl_httpclient now runs the streaming and header callbacks on the IOLoop. tornado.curl_httpclient now uses its own logger for debug output so it can be filtered more easily. tornado.gen New class tornado.gen.WaitIterator provides a way to iterate over Futures in the order they resolve. When the singledispatch library is available (standard on Python 3.4, available via pip install singledispatch on older versions), the convert_yielded function can be used to make other kinds of objects yieldable in coroutines. New function tornado.gen.sleep is a coroutine-friendly analogue to time.sleep. gen.engine now correctly captures the stack context for its callbacks. tornado.httpclient tornado.httpclient.HTTPRequest accepts a new argument raise_error=False to suppress the default behavior of raising an error for non-200 response codes. tornado.httpserver HTTPServer now calls start_request with the correct arguments. This change is backwards-incompatible, afffecting any application which implemented HTTPServerConnectionDelegate by following the example of Application instead of the documented method signatures. HTTPServer now tolerates extra newlines which are sometimes inserted between requests on keep-alive connections. HTTPServer can now use keep-alive connections after a request with a chunked body. HTTPServer now always reports HTTP/1.1 instead of echoing the request version. tornado.httputil New function tornado.httputil.split_host_and_port for parsing the netloc portion of URLs. The context argument to HTTPServerRequest is now optional, and if a context is supplied the remote_ip attribute is also optional. HTTPServerRequest.body is now always a byte string (previously the default empty body would be a unicode string on python 3). Header parsing now works correctly when newline-like unicode characters are present. Header parsing again supports both CRLF and bare LF line separators. Malformed multipart/form-data bodies will always be logged quietly instead of raising an unhandled exception; previously the behavior was inconsistent depending on the exact error. tornado.ioloop The kqueue and select IOLoop implementations now report writeability correctly, fixing flow control in IOStream. When a new IOLoop is created, it automatically becomes âcurrentâ for the thread if there is not already a current instance. New method PeriodicCallback.is_running can be used to see whether the PeriodicCallback has been started. tornado.iostream IOStream.start_tls now uses the server_hostname parameter for certificate validation. SSLIOStream will no longer consume 100% CPU after certain error conditions. SSLIOStream no longer logs EBADF errors during the handshake as they can result from nmap scans in certain modes. tornado.options parse_config_file now always decodes the config file as utf8 on Python 3. tornado.options.define more accurately finds the module defining the option. tornado.platform.asyncio It is now possible to yield asyncio.Future objects in coroutines when the singledispatch library is available and tornado.platform.asyncio has been imported. New methods tornado.platform.asyncio.to_tornado_future and to_asyncio_future convert between the two librariesâ Future classes. tornado.platform.twisted It is now possible to yield Deferred objects in coroutines when the singledispatch library is available and tornado.platform.twisted has been imported. tornado.tcpclient TCPClient will no longer raise an exception due to an ill-timed timeout. tornado.tcpserver TCPServer no longer ignores its read_chunk_size argument. tornado.testing AsyncTestCase has better support for multiple exceptions. Previously it would silently swallow all but the last; now it raises the first and logs all the rest. AsyncTestCase now cleans up Subprocess state on tearDown when necessary. tornado.web The asynchronous decorator now understands concurrent.futures.Future in addition to tornado.concurrent.Future. StaticFileHandler no longer logs a stack trace if the connection is closed while sending the file. RequestHandler.send_error now supports a reason keyword argument, similar to tornado.web.HTTPError. RequestHandler.locale now has a property setter. Application.add_handlers hostname matching now works correctly with IPv6 literals. Redirects for the Application default_host setting now match the request protocol instead of redirecting HTTPS to HTTP. Malformed _xsrf cookies are now ignored instead of causing uncaught exceptions. Application.start_request now has the same signature as HTTPServerConnectionDelegate.start_request. tornado.websocket The tornado.websocket module now supports compression via the âpermessage-deflateâ extension. Override WebSocketHandler.get_compression_options to enable on the server side, and use the compression_options keyword argument to websocket_connect on the client side. WebSocketHandler no longer logs stack traces when the connection is closed. WebSocketHandler.open now accepts *args, **kw for consistency with RequestHandler.get and related methods. The Sec-WebSocket-Version header now includes all supported versions. websocket_connect now has a on_message_callback keyword argument for callback-style use without read_message().
2015-02-08Updated textproc/py-lxml to 3.4.2wiz2-3/+3
generated by cgit v1.2.3 (git 2.39.1) at 2025-03-11 00:22:28 +0000