| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
for added comment
|
|
|
|
|
|
1.4.0:
Added
* Turn off session tickets for apache plugin by default when appropriate.
* Added serial number of certificate to the output of `certbot certificates`
* Expose two new environment variables in the authenticator and cleanup scripts used by
the `manual` plugin: `CERTBOT_REMAINING_CHALLENGES` is equal to the number of challenges
remaining after the current challenge, `CERTBOT_ALL_DOMAINS` is a comma-separated list
of all domains challenged for the current certificate.
* Added TLS-ALPN-01 challenge support in the `acme` library. Support of this
challenge in the Certbot client is planned to be added in a future release.
* Added minimal proxy support for OCSP verification.
* On Windows, hooks are now executed in a Powershell shell instead of a CMD shell,
allowing both `*.ps1` and `*.bat` as valid scripts for Certbot.
Changed
* Reorganized error message when a user entered an invalid email address.
* Stop asking interactively if the user would like to add a redirect.
* `mock` dependency is now conditional on Python 2 in all of our packages.
* Deprecate certbot-auto on Gentoo, macOS, and FreeBSD.
Fixed
* When using an RFC 8555 compliant endpoint, the `acme` library no longer sends the
`resource` field in any requests or the `type` field when responding to challenges.
* Fix nginx plugin crash when non-ASCII configuration file is being read (instead,
the user will be warned that UTF-8 must be used).
* Fix hanging OCSP queries during revocation checking - added a 10 second timeout.
* Standalone servers now have a default socket timeout of 30 seconds, fixing
cases where an idle connection can cause the standalone plugin to hang.
* Parsing of the RFC 8555 application/pem-certificate-chain now tolerates CRLF line
endings. This should fix interoperability with Buypass' services.
More details about these changes can be found on our GitHub repo.
|
|
v3.3.22
Additional security to prevent unexpected DNS change
prevent merge issues
make the pylint happy
some more pylint fixes
Fix lint
Finish the new implementation
Fix lint
v3.3.21
With apologies to the linter
Update and fix tests
Fix lint
v3.3.20
Fix lint error
Adding a new hetzner provider compatible with dns.hetzner.com
|
|
|
|
|
|
|
|
Version 2.13
* New Features:
- Add `jansson_version_str()` and `jansson_version_cmp()` for runtime
version checking
- Add `json_object_update_new()`, `json_object_update_existing_new()`
and `json_object_update_missing_new()` functions
- Add `json_object_update_recursive()`
* Build:
- Add ``-Wno-format-truncation`` to suppress format truncation warnings
* Bug fixes:
- Remove ``strtod`` macro definition for MinGW
- Add infinite loop check in `json_deep_copy()`
- Add ``pipe`` macro definition for MinGW
- Enhance ``JANSSON_ATTRS`` macro to support earlier C standard(C89)
- Update version detection for sphinx-build
* Documentation:
- Fix typos
- Document that call the custom free function to free the return value
of `json_dumps()` if you have a custom malloc/free
- Add vcpkg installation instructions
- Document that non-blocking file descriptor is not supported on
|
|
3.6.4:
Fix parenthesization for selector schema and real parents
Add deprecation warning for global variable creation
Ensure correct output order of compound selectors
Handle loaded source code as shared objects
New custom memory allocator - disabled for now
Add back C-API getters for plugin paths
Fix abspath handling on windows without directory
Fix various edge case crashes
Fix segfault on directive ruleset
Fix heap-buffer-overflow in lexer
Fix stack-overflow in parser
Fix memory leak in parser
Fix memory leak in evaluation
Fix memory handling edge case
Fix some null pointer access crashes
Preparations for ongoing refactoring
|
|
|
|
|
|
3.24.2 (stable):
Gdk:
* Window::create_similar_surface(): Fix a memory leak.
* Suppress warnings from deprecated GTimeVal in
PixbufAnimation::get_iter()
PixbufAnimationIter::advance()
Gtk:
* Fix memory leaks in
IconTheme::list_icons()
IconView::get_selected_icons()
RecentManager::get_items()
Documentation:
* Gtk::Builder: Describe how to use it together with Glib::Property.
Demos:
* Fix the source code listing.
|
|
2.42.1 (stable):
* Coverage: Ignore deprecations of pango functions
(so it can be used with the latest versions of pango)
* Layout::get_lines(): Fix ownership of the GSList
* pango/src/color.hg: Fix call to _CLASS_BOXEDTYPE_STATIC
Build:
* tools/gen_scripts: Update for non-source-dir builds
* Add support for building pangomm with Meson
* meson.build: Check if .git is a directory or file
* NMake Makefiles: Allow builds from a GIT checkout
* The fixed call to _CLASS_BOXEDTYPE_STATIC in color.hg
is necessary in order to use glibmm 2.64.0 or later,
combined with maintainer-mode in pangomm.
|
|
|
|
Upstream changes:
0.022 2020-05-04 22:34:48+02:00 Europe/Amsterdam
- Skip tests when needed, to allow installation on <5.10
|
|
|
|
- add and enable p5-RT-Extension-ArticleTemplates
|
|
|
|
|
|
This fixes the build with GNU_CONFIGURE_STRICT=yes.
|
|
|
|
0.26.1:
Fixed a performance regression introduced in 0.26.0
|
|
4.5.2:
Fixes:
- silence spurious error message when stopping ProcessPool.
|
|
|
|
Changes in MySQL 5.7.30:
JSON Notes
The rapidjson library included with MySQL has been upgraded to the GitHub snapshot of 16 January 2020. A fix for a compiler error encountered when building from the snapshot on Mac OS X has been added.
Packaging Notes
Binary packages that include curl rather than linking to the system curl library have been upgraded to use curl 7.69.0.
The bundled libedit library was upgraded to version 3.1.
Bugs Fixed
InnoDB: The row_upd_clust_rec_by_insert function, which marks a clustered index record as deleted and inserts an updated version of the record into the clustered index, passed an incorrect n_ext value (the total number of external fields) to lower level functions, causing an assertion failure.
InnoDB: An operation performed with the innodb_buffer_pool_evict debug variable set to uncompressed caused an assertion failure.
InnoDB: An add column operation caused an assertion failure. The failure was due to a dangling pointer.
InnoDB: Updating certain InnoDB system variables that take string values raised invalid read errors during Valgrind testing.
InnoDB: An insert statement on a table with a spatial index raised a record type mismatch assertion due to a tuple corruption.
InnoDB: A function that calculates undo log record size could calculate an incorrect length value in the case of a corrupted undo log record, resulting in a malloc failure. Assertion code was added to detect incorrect calculations.
Replication: While an SQL statement was in the process of being rewritten for the binary log so that sensitive information did not appear in plain text, if a SHOW PROCESSLIST statement was used to inspect the query, the query could become corrupted when it was written to the binary log, causing replication to stop. The process of rewriting the query is now kept private, and the query thread is updated only when rewriting is complete.
Replication: When a GRANT or REVOKE statement is only partially executed, an incident event is logged in the binary log, which makes the replication slave's applier thread stop so that the slave can be reconciled manually with the master. Previously, if a failed GRANT or REVOKE statement was the first statement executed in the session, no GTID was applied to the incident event (because the cache manager did not yet exist for the session), causing an error on the replication slave. Also, no incident event was logged in the situation where a GRANT statement created a user but then failed because the privileges had been specified incorrectly, again causing an error on the replication slave. Both these issues have now been fixed.
Replication: When a replication slave has a generated column that the master does not have in that table, with a secondary index on the generated column, the generated expression should be evaluated and the value stored by the storage engine in the secondary index. When row-based binary logging is in use, the replication slave assigns default values to any fields that are not in the master's definition of the table. In the case of a generated column, which does not have a default value, the slave was previously assigning a null or a zero value to the column. This value was then stored by the storage engine in the secondary index, causing both the table and the index to become corrupted. To fix this issue, generated columns in a table on a replication slave are now re-evaluated before the values are sent to the storage engine.
Replication: In the event of an unplanned disconnection of a replication slave from the master, the reference to the master's dump thread might not be removed from the list of registered slaves, in which case statements that accessed the list of slaves would fail. The issue has now been fixed.
Replication: With the settings binlog_format=MIXED, tx_isolation=READ-COMMITTED, and binlog_row_image=FULL, an INSERT ... SELECT query involving a transactional storage engine omitted any columns with a null value from the row image written to the binary log. This happened because when processing INSERT ... SELECT statements, the columns were marked for inserts before the binary logging format was selected. The issue has now been fixed.
The -libs-compat RPM package is now built with system zlib to avoid problems with unrestricted export of symbols in libmysqlclient.so.18.
The Event Scheduler had a memory leak.
Under certain circumstances, a memcached command could result in reading an uninitialized memory buffer, causing a failure.
Using ALTER USER to reset an account MAX_USER_CONNECTIONS value did not take effect until all current account connections terminated, if there were any.
A materialized subquery including a condition in which a column value was used as input to a nondeterministic function produced incorrect results.
CONCAT() and CONCAT_WS() could produce incorrect results in rare cases due to incorrect substring handling.
Scheduling of events could be disturbed by removing events.
Client programs could load authentication plugins from outside the plugin library.
The server did not handle correctly a UNION in which one of the queries contained a subquery that used ORDER BY.
A query with a WHERE clause whose predicate contained a numeric value in scientific notation was not handled correctly.
In addition, attempting to insert a particular integer specified as a string caused a server exit when the string-to-integer conversion was not successful.
Previously, mysqlpump read the [mysql_dump] and [client] groups from option files. mysqlpump now additionally reads the [mysqlpump] group. The [mysql_dump] group is still accepted but is deprecated.
A multi-table UPDATE statement which updated a table joined to a derived table that joined two other tables was not optimized properly as it had been in MySQL 5.6, instead being treated as if STRAIGHT_JOIN had been used with the subquery creating the derived table.
|
|
security/py-google-auth
|
|
1.14.2:
Bug Fixes
support string type response.data
|
|
0.2.1:
* Add missing dependencies in setup.py.
* Fix syntax errors in xandikos/store/vdir.py.
(Unused, but breaks bytecompilation).
|
|
4.0.6:
Bug fixes:
- Use ``vText`` as default type, when convert recurrence definition to ical string.
|
|
0.15.6:
- [NEW] Added support for parsing and formatting `ISO 8601 week dates <https://en.wikipedia.org/wiki/ISO_week_date>`_ via a new token ``W``, for example:
.. code-block:: python
>>> arrow.get("2013-W29-6", "W")
<Arrow [2013-07-20T00:00:00+00:00]>
>>> utc=arrow.utcnow()
>>> utc
<Arrow [2020-01-23T18:37:55.417624+00:00]>
>>> utc.format("W")
'2020-W04-4'
- [NEW] Formatting with ``x`` token (microseconds) is now possible, for example:
.. code-block:: python
>>> dt = arrow.utcnow()
>>> dt.format("x")
'1585669870688329'
>>> dt.format("X")
'1585669870'
- [NEW] Added ``humanize`` week granularity translation for German, Italian, Polish & Taiwanese locales.
- [FIX] Consolidated and simplified German locales.
- [INTERNAL] Moved testing suite from nosetest/Chai to pytest/pytest-mock.
- [INTERNAL] Converted xunit-style setup and teardown functions in tests to pytest fixtures.
- [INTERNAL] Setup Github Actions for CI alongside Travis.
- [INTERNAL] Help support Arrow's future development by donating to the project on `Open Collective <https://opencollective.com/arrow>`_.
|
|
p5-ExtUtils-Depends is a build dependency, and this fails to build in a
sandbox (at least, for me) without USE_LANGUAGES=c defined.
|
|
|
|
|
|
ChangeLog:
Version 2.86.7 (April 4, 2020)
- Using pkg-config (if available) to locate libffi
|
|
|
|
ChangeLog:
### libopenmpt 0.4.12 (2020-04-13)
* IT: Vibrato was too fast in Old Effects mode since libopenmpt 0.3.
* XM: Treat 8bitbubsy's FT2 clone exactly like Fasttracker 2 with respect to
compatibility and playback flags. For example, FT2 Pan Law was not applied.
* DMF: Some files had a wrong tempo since libopenmpt 0.2.5705-beta15.
|
|
Fixes issue seen bootstrapping on Solaris 9 when bash is available and being
used for SH, bmake was still defaulting to /usr/xpg4/bin/sh which dumps core
with some of the mk/check infrastructure.
Note this is only for the bmake used during the initial bootstrap, the final
bmake package will still use the defshell logic in its Makefile.
|
|
Clean up Makefile, no functional change.
|
|
Clean up Makefile, no functional change.
|
|
devel/ruby-redmine_bootstrap_kit
devel/ruby-redmine_jenkins
devel/ruby-redmine_startpage
|
|
Remove a redmine plugin which dose not support Redmine 4.0 and later.
|
|
Remove a redmine plugin which dose not support Redmine 4.0 and later.
|
|
Remove a redmine plugin which dose not support Redmine 4.0 and later.
|
|
Remove some redmine plugins:
ruby-redmine_bootstrap_kit
ruby-redmine_jenkins
ruby-redmine_startpage
|
|
|
|
Update ruby-redmine-plugins to 1.3.0.
Drop some plugins which do not support Redmine 4.0 and later.
|
|
Add "used by" lines in comments for newer ruby-redmine theme pacakges.
|
|
|
