pkgsrc change: update HOMEPAGE.
Version 2.0.1
* A few bug fixes.
Version 2.0.0
* bump to 2.0 to mark the change of maintainership. I hope I won't disappoint.
* require 'flexmock' no longer pulls test_unit_integration. Require the latter
explicitely
* dropped support for pre-2.0 Rubies
* added explicit minitest support. This makes the minitest integration much
nicer to work with (in particular, the flexmock_teardown is now executed "just
at the right place"), and fixes issues with minitest 5. Just require
flexmock/minitest to get it.
* partial mocks now supports prepended modules
* validation errors that happen when a method is called (i.e. unexpected
arguments, wrong call count) are reported with the backtrace of the call
instead of with the backtrace of the expectation definition.
0.17.2 (2015-09-30)
-----
* Revamped test suite, using shared RSpec configuration layer provided by Celluloid itself.
* Updated gem dependencies provided by Celluloid::Sync... extraneous gems removed, or marked as development dependencies.
- Clean up deprecation notes.
0.20.5 (2015-09-30)
-----
* Resumed updating changelog.
* Revamped test suite, using shared RSpec configuration layer provided by Celluloid itself.
* Updated gem dependencies provided by Celluloid::Sync... extraneous gems removed, or marked as development dependencies.
0.20.5 (2015-09-30)
-----
* Resumed updating changelog. Not much as changed -- mostly keeping version sync with other gems.
* Revamped test suite, using shared RSpec configuration layer provided by Celluloid itself.
* Updated gem dependencies provided by Celluloid::Sync... extraneous gems removed, or marked as development dependencies.
0.20.5 (2015-09-30)
-----
* Revamped test suite, using shared RSpec configuration layer provided by Celluloid itself.
* Updated gem dependencies provided by Celluloid::Sync... extraneous gems removed, or marked as development dependencies.
0.20.5 (2015-09-30)
-----
* Revamped test suite, using shared RSpec configuration layer provided by Celluloid itself.
* Updated gem dependencies provided by Celluloid::Sync... extraneous gems removed, or marked as development dependencies.
Upstream changes:
[Changes for 0.79 - Mon May 18 23:02:11 CST 2015]
* Restore "cpansign --skip" functionality.
Contributed by: CLOOS
[Changes for 0.78 - Thu Apr 9 16:58:27 CST 2015]
* Fix verify() use from cpanm and CPAN.pm.
Contributed by: ANDK
[Changes for 0.77 - Wed Apr 8 19:36:50 CST 2015]
* Include the latest public keys of PAUSE, ANDK and AUDREYT.
* Clarify scripts/cpansign copyright to CC0.
Reported by: @pghmcfc
[Changes for 0.76 - Wed Apr 8 18:05:48 CST 2015]
* Fix signature tests by defaulting to verify(skip=>1)
when $ENV{TEST_SIGNATURE} is true.
Reported by: @pghmcfc
[Changes for 0.75 - Tue Apr 7 04:56:09 CST 2015]
Two more issues reported by John Lightsey:
* Update ChangeLog.
* More protection of @INC from relative paths.
Fix various issues reported by John Lightsey:
[Changes for 0.74 - Tue Apr 7 02:39:14 CST 2015]
Fix various issues reported by John Lightsey:
* Fix GPG signature parsing logic.
* MANIFEST.SKIP is no longer consulted unless --skip is given.
* Properly use open() modes to avoid injection attacks.
Upstream changes:
2.025 2015-09-23
- The previous release included a patch that broke compatibility
with Perl 5.8.x. The minimum supported version is now Perl
5.8.5, and there is a .perl-version file to facilitate testing
using plenv.
2.024 2015-09-18
- [RT #104133] Include all bounding boxes when importing a page
(patch by Don Huettl of Grant Street Group).
- [RT #104133] When retrieving bounding boxes for a page, fall
back according to the defaults listed in the PDF spec (patch by
Don Huettl of Grant Street Group).
- Barcodes now take an optional -caption argument that will be
printed beneath the barcode. This can replace or be used in
conjunction with the text representation of the barcode
(requested by Gareth Tunley).
- [RT #105581] Calls to width() in BaseFont are now significantly
faster (patch by Dmitri Tikhonov).
=== 4.27.0 (2015-10-01)
* Don't stub Sequel.synchronize on MRI (YorickPeterse) (#1083)
* Make bin/sequel warn if given arguments that it doesn't use (jeremyevans)
* Fix the order of referenced composite keys returned by Database#foreign_key_list on PostgreSQL (jeremyevans) (#1081)
* Recognize another disconnect error in the jdbc/postgresql adapter (jeremyevans)
* In the active model plugin, make Model#persisted? return false if the transaction used for creation is rolled back (jeremyevans) (#1076)
* Use primary_key :keep_order option in the schema dumper if the auto incrementing column is not the first column in the table (jeremyevans)
* Set :auto_increment option correctly in the schema parser when the auto incrementing column is not the first column in the table (jeremyevans)
* Support :keep_order option to primary_key in schema generator, to not automatically make the primary key the first column (jeremyevans)
* Add new jsonb/json functions and operators supported in PostgreSQL 9.5+ (jeremyevans)
* Add before_after_save plugin, for refreshing created objects and resetting modified flag before calling after_create/update/save hooks (jeremyevans)
* Add Dataset#single_record! and #single_value! which don't require cloning the receiver (jeremyevans)
* Dataset#with_sql_single_value now works correctly for model datasets (jeremyevans)
* Optimize Dataset#single_value and #with_sql_single_value to not create an unnecessary array (jeremyevans)
* Make postgres adapter work with postgres-pr 0.7.0 (jeremyevans) (#1074)
0.4.1
0.4.0
@sodabrew sodabrew released this 26 days ago · 54 commits to master since this
release
New Features
* Support for Prepared Statements!
* Add connection option :sslverify
* Use mariadb_config for MariaDB builds
Bugfixes
* Fix Mysql2::Result#count always returns 0 when using stored procedures and
MULTI_STATEMENTS
Changes
* Prevent Timeout::timeout from interrupting query execution
* Use Ruby's String#encode to remove unrecognized characters from error messages
* Convert specs to RSpec 3 expect sytnax
* Refactored the Travis CI test scripts
* Misc cleanups with Rubocop
* Stricter CFLAGS
0.3.20
@sodabrew sodabrew released this on 25 Aug · 205 commits to master since this
release
Bugfixes
* Check if O_CLOEXEC is defined before using it in open()
* Fix an infinite loop while searching for libmysqlclient when mysql_config is
not found
Changes
* Call RakeCompilerDock.sh twice, once for 32-bit and once for 64-bit, when
building Windows binary gems
0.3.19
@sodabrew sodabrew released this on 30 Jul · 205 commits to master since this
release
New Features
* Mysql2::Client#info class method for easier debugging, and both the class
and instance method return US_ASCII output rather than using the connection
encoding.
* When streaming results, continue result.count across calls to result.each
Bugfixes
* Search for mariadb_config on compile
* Update to Connector/C 6.1.6 in the Windows builds
* Fix Mysql2::Client#escape to set the encoding even if the string was not
modified
* Fix LICENSE filename in gem file list
* Make the result.count return type consistent and match the source type
Changes
* Rename macro GetMysql2Result to GET_RESULT
* Convert StringValuePtr to either RSTRING_PTR or StringValueCStr
* Fix unused variable warning on Windows in rb_mysql_client_socket
* Add Ruby 2.2 to the AppVeyor matrix
* Test default client flag equality instead of bitwise truthiness
* Add rake-compiler-dock for building Windows binary gems
* Friendly ext build error <3
* Process :stream option in rb_mysql_result_to_obj once instead of
rb_mysql_result_each for each call to each
* Tests for streaming and stored procedures with multiple result sets
is not, from what I can tell by building and using (also from the repo),
broken under py3x. Therefore, dependencies marked as broken under py3x due to
paramiko will be unmarked (unless they are broken for lack of py3x support).
From sites/www/changelog.rst:
:support:`554 backported` Fix inaccuracies in the docstring for the ECDSA key class. Thanks to Jared Hance for the patch.
:support:`516 backported` Document ~paramiko.agent.AgentRequestHandler. Thanks to @toejough for report & suggestions.
🐛`496` Fix a handful of small but critical bugs in Paramiko's GSSAPI support (note: this includes switching from PyCrypo's Random to os.urandom). Thanks to Anselm Kruis for catch & patch.
🐛`491` (combines :issue:`62` and :issue:`439`) Implement timeout functionality to address hangs from dropped network connections and/or failed handshakes. Credit to @vazir and @dacut for the original patches and to Olle Lundberg for reimplementation.
🐛`490` Skip invalid/unparseable lines in known_hosts files, instead of raising ~paramiko.ssh_exception.SSHException. This brings Paramiko's behavior more in line with OpenSSH, which silently ignores such input. Catch & patch courtesy of Martin Topholm.
🐛`404` Print details when displaying ~paramiko.ssh_exception.BadHostKeyException objects (expected vs received data) instead of just "hey shit broke". Patch credit: Loic Dachary.
🐛`469` (also :issue:`488`, :issue:`461` and like a dozen others) Fix a typo introduced in the 1.15 release which broke WinPageant support. Thanks to everyone who submitted patches, and to Steve Cohen who was the lucky winner of the cherry-pick lottery.
🐛`353` (via :issue:`482`) Fix a bug introduced in the Python 3 port which caused OverFlowError (and other symptoms) in SFTP functionality. Thanks to @dboreham for leading the troubleshooting charge, and to Scott Maxwell for the final patch.
:support:`582` Fix some old setup.py related helper code which was breaking bdist_dumb on Mac OS X. Thanks to Peter Odding for the patch.
🐛`22 major` Try harder to connect to multiple network families (e.g. IPv4 vs IPv6) in case of connection issues; this helps with problems such as hosts which resolve both IPv4 and IPv6 addresses but are only listening on IPv4. Thanks to Dries Desmet for original report and Torsten Landschoff for the foundational patchset.
🐛`402` Check to see if an SSH agent is actually present before trying to forward it to the remote end. This replaces what was usually a useless TypeError with a human-readable ~paramiko.ssh_exception.AuthenticationException. Credit to Ken Jordan for the fix and Yvan Marques for original report.
Syncthing replaces proprietary sync and cloud services with something open,
trustworthy and decentralized.
Features include:
- web admin console
- directory watcher
- authentication with x509 certificates
- node discovery
- written in "go"
This release brings:
- general code review
- more consistent error management (applets, panel-notify(1)...)
- uninitialized variable fix in the "close" applet
- stricter invocation of helper binaries ("mixer" applet, run(1)...)
- improved "network" applet
- avoid potential crashes in the "pager", "systray" and "tasks" applets
- rid some compilation and run-time warnings (run(1)...)
- updated translations
Additional thanks to bouyer@ for the bug reports.
* Connector/Python is now compatible with Django 1.8.
* When using the C Extension with raise_on_warnings=True, errors were not thrown as exceptions when an executed statement produced an error, and it was not possible to reuse the cursor if the statement produced a result set.
* When using the C Extension, character decoding of identifiers (database, table, column names) in result sets could fail.
* When using the C Extension with the auth_plugin option, connect() calls failed.
* In connections for which consume_results=True, callproc() could hang.
* Connections failed if the password began or ended with spaces because they were being stripped before the connection attempt.
* Connection failure occurred for accounts authenticated with the sha256_password authentication plugin that had a blank password.
* The Connector/Python C Extension could exit when fetching a result set containing many NULL values.
* Connector/Python failed to complete the connection handshake with MySQL Server 5.5.8.
* InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems.
* yaSSL was upgraded to version 2.3.8.
* RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed.
* InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset.
* InnoDB: Memory allocation sanity checks were added to the memcached code.
* InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code.
* InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word.
* InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20.
* InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation.
* InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available.
* InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system.
* InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied.
* InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format.
* Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected.
* Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly
* Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE.
* Replication: Repeatedly checking for ERR_LOCK_WAIT_TIMEOUT (as done, for example by repeatedly executing SHOW SLAVE STATUS) during a prolonged write lock on a table led to an assert.
* Replication: If statement based logging was in use, when updating multiple tables in a single statement, a single transaction could be logged as two different transactions. This was due to the binary logging process not properly identifying statements which were operating over transactional tables. The fix ensures that they are correctly identified, even if such statements do not change the contents of the tables.
* yaSSL was upgraded to version 2.3.8.
* InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word.
* InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. Thanks to Alexey Kopytov for the patch.
* InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available.
* InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system.
* Partitioning: CREATE TABLE statements that used an invalid function in a subpartitioning expression did not always fail gracefully as expected.
* Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE.
* Certain subqueries as arguments to PROCEDURE ANALYSE() could cause a server exit.
* mysql_ssl_rsa_setup could create an unwanted .rnd file in the data directory. (The file is actually created by openssl, which mysql_ssl_ras_setup invokes. mysql_ssl_rsa_setup now cleans up the file.)
* An assertion could be raised due to incorrect error handling if a SELECT ... FOR UPDATE subquery resulted in deadlock and caused a rollback.
* Servers linked against yaSSL and compiled with GCC 4.8.2 could fail to respond correctly to connection attempts until several seconds after startup.
* For tables with subpartitions, the server could exit due to incorrect error handling during partition pruning if the partition could be identified but not the subpartition.
* DELETE could check privileges for the wrong database when table aliases were used.
* Within a trigger, use of a cursor that accessed OLD or NEW values from a row could cause a server exit.
* MySQL sometimes produced no warning when it was unable to interpret a character in a given character set.
* For MySQL distributions linked against yaSSL, a corrupt client key file could cause clients to exit.
* Execution of certain BINLOG statements while temporary tables were open by HANDLER statements could cause a server exit.
