Age | Commit message (Collapse) | Author | Files | Lines |
|
06 Aug 2015 PHP 5.4.44
- Core:
. Fixed bug #69793 (Remotely triggerable stack exhaustion via recursive
method calls). (Stas)
. Fixed bug #69892 (Different arrays compare indentical due to integer key
truncation). (Nikita)
. Fixed bug #70121 (unserialize() could lead to unexpected methods execution
/ NULL pointer deref). (Stas)
- OpenSSL:
. Fixed bug #70014 (openssl_random_pseudo_bytes() is not cryptographically
secure). (Stas)
- Phar:
. Improved fix for bug #69441. (Anatol Belski)
. Fixed bug #70019 (Files extracted from archive may be placed outside of
destination directory). (Anatol Belski)
- SOAP:
. Fixed bug #70081 (SoapClient info leak / null pointer dereference via
multiple type confusions). (Stas)
- SPL:
. Fixed bug #70068 (Dangling pointer in the unserialization of ArrayObject
items). (sean.heelan)
. Fixed bug #70166 (Use After Free Vulnerability in unserialize() with
SPLArrayObject). (taoguangchen at icloud dot com)
. Fixed bug #70168 (Use After Free Vulnerability in unserialize() with
SplObjectStorage). (taoguangchen at icloud dot com)
. Fixed bug #70169 (Use After Free Vulnerability in unserialize() with
SplDoublyLinkedList). (taoguangchen at icloud dot com)
|
|
something in op.c (as miniop.c) is mis-compiled with this option which
is enabled by -O2, when using GCC 4.5. i didn't try to figure out
exactly what as op.c is 419,359 bytes long and the assembler output
is almost 100% different and approximiately 1.5MB either way (the
diff of the asm output is larger than the combined inputs), so for now
we have this hack. this problem doesn't appear to occur in newer GCC.
XXX: pullup to 2015Q2.
|
|
|
|
Upstream changes:
2.201 2015-03-05
** PLEASE CONSIDER USING EMAIL-SENDER INSTEAD **
add x_deprecated metadata
|
|
|
|
Add LICENSE
Upstream changes:
2.19 2013/19/03
+ RT82713 - version number contains a space.
|
|
|
|
Upstream changes:
1.907 2015-02-03 17:48:10-05:00 America/New_York
- restore 5.8.x compatibility
1.906 2015-02-03 16:48:11-05:00 America/New_York
- the test suite tests parses more directly, which eliminates a number
of misleading (and possibly wrong) test cases
- escaped characters in a quoted string are now properly unescaped
for the ->phrase method, which means things should round trip better
from their decomposed form
|
|
|
|
|
|
except that camlp5 is now compatible with ocaml 4.02.3.
|
|
|
|
include:
Bug fixes:
- Top-level custom printing for GADTs: interface change in 4.02.2
(Grégoire Henry, report by Jeremy Yallop)
- corrupted final_table (ygrek)
- R#6926: Regression: ocamldoc lost unattached comment
(Damien Doligez, report by François Bobot)
- Aliased result type of GADT constructor results in assertion failure
(Jacques Garrigue)
Feature wishes:
- PR#6691: install .cmt[i] files for stdlib and compiler-libs
(David Sheets, request by Gabriel Radanne)
- New primitive: caml_alloc_dummy_function
(Hugo Heuzard)
|
|
Noted by Matthias Ferdinand on pkgsrc-users.
|
|
Fixes pkg/50084.
|
|
|
|
Upstream changes:
# Version 0.3.1
* Actually export `dbIsValid()` :/
* `dbGetQuery()` uses `dbFetch()` in the default implementation.
# Version 0.3.0
## New and enhanced generics
* `dbIsValid()` returns a logical value describing whether a connection or
result set (or other object) is still valid. (#12).
* `dbQuoteString()` and `dbQuoteIdentifier()` to implement database specific
quoting mechanisms.
* `dbFetch()` added as alias to `fetch()` to provide consistent name.
Implementers should define methods for both `fetch()` and `dbFetch()` until
`fetch()` is deprecated in 2015. For now, the default method for `dbFetch()`
calls `fetch()`.
* `dbBegin()` begins a transaction (#17). If not supported, DB specific
methods should throw an error (as should `dbCommit()` and `dbRollback()`).
## New default methods
* `dbGetStatement()`, `dbGetRowsAffected()`, `dbHasCompleted()`, and
`dbGetRowCount()` gain default methods that extract the appropriate elements
from `dbGetInfo()`. This means that most drivers should no longer need to
implement these methods (#13).
* `dbGetQuery()` gains a default method for `DBIConnection` which uses
`dbSendQuery()`, `fetch()` and `dbClearResult()`.
## Deprecated features
* The following functions are soft-deprecated. They are going away,
and developers who use the DBI should begin preparing. The formal deprecation
process will begin in July 2015, where these function will emit warnings
on use.
* `fetch()` is replaced by `dbFetch()`.
* `make.db.names()`, `isSQLKeyword()` and `SQLKeywords()`: a black list
based approach is fundamentally flawed; instead quote strings and
identifiers with `dbQuoteIdentifier()` and `dbQuoteString()`.
* `dbGetDBIVersion()` is deprecated since it's now just a thin wrapper
around `packageVersion("DBI")`.
* `dbSetDataMappings()` (#9) and `dbCallProc()` (#7) are deprecated as no
implementations were ever provided.
## Other improvements
* `dbiCheckCompliance()` makes it easier for implementors to check that their
package is in compliance with the DBI specification.
* All examples now use the RSQLite package so that you can easily try out
the code samples (#4).
* `dbDriver()` gains a more effective search mechanism that doesn't rely on
packages being loaded (#1).
* DBI has been converted to use roxygen2 for documentation, and now most
functions have their own documentation files. I would love your feedback
on how we could make the documentation better!
|
|
|
|
Add LICENSE
Upstream changes:
Version 0.8.21
- fixed the case in the header names (Content-type -> Content-Type)
- fixed the encoding of non-ascii stuff in headers (RFC 2047)
- fixed using the ctype even for body with MailFile
Version 0.8.23
- fixed problems with long subjects containing accentuated characters
- fixed problems with IO::Socket::SSL
- trims addresses passed in an array (per request)
- changed licence per request from Fedora
- fix to allow very long passwords
- fix error in TestServer()
|
|
|
|
Upstream changes:
1.25 2015.05.25
- Rename test files to have number prefix.
- Move test reqirements to TEST_REQUIRES or BUILD_REQUIRES for older EUMM
- Older versions of EU::MM require quotes around 2-dot versions (CHORNY)
1.24 2015.05.22
- Include the rc files in the distribution to use the proper
Perl::Critic configuration.
- use Test::Version to make sure we have the same version number
in every module.
- Configure Perl::Critic to be level 4.
- Lots of other refactorings.
|
|
|
|
Upstream changes:
Version 0.77 (2015-07-22)
-------------------------
* ensure consistent order of enums when generating code; this was
a real bug and caused the configuration part of C::B::C to report
wrong (even invalid) configurations back to the user when built
using a recent version of Perl that randomises hash keys
* fix cpan #85264: the POD test was reporting a missing =back tag
in one of the support modules; the ultimate fix was to ensure only
the provided modules were POD checked
* fix cpan #83167: an artificially low refcnt for immortal variables
introduced recently for debug Perl builds was causing the refcnt
tests to fail for SvNULLs; thanks to Reini Urban for his patch;
also thanks to Nicholas Clark for pointing me to the Perl commit
* fix cpan #78165: spelling errors in the documentation; thanks to
gregor herrmann for providing a patch
* fix deprecated use of unescaped braces in regex
* fix some gcc and Perl warnings
* switch from SnapshotCM to git repo: github.com/mhx/Convert-Binary-C/
|
|
Fix PR pkg/50130.
|
|
|
|
Upstream changes:
2015-08-05 - 5.2
Use Module::Runtime if it's installed (thanks to Olivier Mengu茅)
Switch to using ExtUtils::MakeMaker (thanks to Karen Etheridge and Tim Orling)
|
|
No functional change intended.
|
|
No functional change intended.
|
|
No functional change intended.
|
|
|
|
Suggested by Michael McConville to get rid of the x11 dependency
in finch, which you really don't want. Use chat/pidgin for X11.
Bump PKGREVISION.
|
|
|
|
|
|
Python interface to Firebase's REST API.
|
|
|
|
libgsf 1.14.34
Morten:
* Fix OLE2 property parsing problem. [#748528]
* Fuzzed file fixes. [#749120] [#749169] [#749183] [#750809]
[#751273]
* xlsx: fix problem with absolute relation targets. [#751120]
* Fix text line problem with very long lines.
--------------------------------------------------------------------------
libgsf 1.14.33
Morten:
* Ensure floats roundtrip through our xml functions.
* Improve handling of unknown xml tags.
* xml parser improvements.
* xml pretty-printing improvements.
--------------------------------------------------------------------------
libgsf 1.14.32
Morten:
* Fix obscure problem with xml parser.
* Add vml to openpkg utils.
* Allow NULL content type for openpkg.
* Plug leak.
--------------------------------------------------------------------------
libgsf 1.14.31
Andreas:
* Add two new localc name spaces to gsf-opendoc-utils
Allin Cottrell:
* Add support for non-default zip compression level. [#722470]
Morten:
* Plug leaks.
* Dead kittens.
* Reduce number of CRITICALs for corrupted files.
* Read zip files with 64k+ members. [Part of #732209]
* Read zip files members larger than 4G. [Part of #732209]
* Speed up zip file reading for lots of members.
* Speed up stdio directory handling with large number of files.
* Fix various issues with files larger than 4G.
* Fix minor zip file issues.
* Write zip archives with more than 64k+ members.
* Store unix modtime in zip. (Until that overflows.)
* Fix seekability checks in GsfOutputIOChannel.
* Avoid implementation defined behaviour of shifts.
* Start a test suite.
|
|
|
|
0.9.9 20141019 Bugfix in HTML4 target. Updated toolchain.
Support for GraphicsMagick. Updated manual page psiconv(1).
0.9.8 20051115 Small bug fixes
|
|
|
|
Major changes in 0.12.9
=======================
* rename newly introduced SpiceImageCompress enum to SpiceImageCompression
as otherwise it was clashing with the definition used by older spice-server
releases, breaking QEMU build
Major changes in 0.12.8
=======================
* add LZ4 support
* add audio volume synchronization
* deprecate unused vdi-dev
* add 'preferred-compression' message/capability
* add a new Windows driver escape code to send
monitors capability from guest to client
|
|
|
|
3.07 2015-07-17
- Net::FTP::rmdir() has been made more robust by making use of the MLSD
command in addition to the NLST command since the latter is known not to
be processed correctly by some FTP servers.
[Chris Lindee, CPAN RT#100694]
- Net::FTP, Net::NNTP, Net::POP3 and Net::SMTP can now restrict domain to
IPv4 even if IPv6 is available by using the new Domain or Family argument.
Net::NNTP now supports the LocalPort argument in addition to LocalAddr.
Net::POP3 now supports the LocalAddr and LocalPort arguments in addition
to ResvPort (which is retained for backwards compatibility).
[Steffen Ullrich, PR#18]
- Fixed a bug in Net::Cmd::datasend() which caused octets in [\x80-\xFF]
stored in a "binary string" to be replaced with their UTF-8 encodings if
the string happened to be stored internally in an "upgraded" state (i.e.
with the UTF-8 flag on). (As noted below, strings passed to datasend()
should always be encoded first, and therefore not stored in such a state
anyway, but it is all too easy for perl to change this internal state
unless the encodeing is done at the very last minute before calling
datasend(), so it helps if datasend() plays more nicely in this case. In
particular, it was wrong of datasend() to treat upgraded and downgraded
strings differently when their contents were identical at the Perl level.)
This bugfix results in a breaking change to the case of a "text string"
with characters in U+0080..U+00FF stored internally in an upgraded state
since those characters are likewise no longer encoded to UTF-8 by
datasend(), but callers of datasend() should not have been relying on this
behaviour anyway: In general, datasend() has no idea what encoding is
required for output so callers should always encode the data to be output
to whatever encoding is required first. This has now been clarified in
the documentation.
Finally, a text string with characters >= U+0100 will now cause a "Wide
character in print" warning from datasend() since such characters cannot
be output as bytes and datasend() no longer encodes to UTF-8. In this
case, UTF-8 bytes will still be output as before since that happens to be
the internal representation of such characters, but the warning is new.
Callers should heed this warning and encode such strings to whatever
encoding is required before calling datasend(), as noted above.
[Ricardo Signes, CPAN RT#104433]
|
|
|
|
Version 1.24 - 08 Apr 2013
* Better portability for tests.
* Updated documentation.
* License changed to GPLv3.
* Bugs fixed:
https://rt.cpan.org/Ticket/Display.html?id=98109
https://rt.cpan.org/Ticket/Display.html?id=47968
https://rt.cpan.org/Ticket/Display.html?id=83980
https://rt.cpan.org/Ticket/Display.html?id=102288
|
|
|
|
0.16 2015-06-29T15:55:13Z
- Fix regexp of _gcc_version for Ubuntu and Debian
(syohex)
- Set -std=c99 explicitly for older GCC
(syohex)
|
|
|
|
0.4214 - Fri Jun 12 00:25:00 CEST 2015
- Released 0.42_13 as 0.4214
0.42_13 - Sat Jun 6 21:18:24 CEST 2015
[BUG FIXES]
- Handle failure to guess license from key better
[ENHANCEMENTS]
- Output data in a stable order [Jérémy Bobbio]
|
|
|
|
|