$(DLLIB): $(OBJS) Makefile
...
$(Q) $(POSTLINK)
And POSTLINK is empty macro. In such case, GNU make ignore empty command
line but BSD make tries to execute it and causes error.
Bump PKGREVISION.
$(DLLIB): $(OBJS) Makefile
...
$(Q) $(POSTLINK)
And POSTLINK is empty macro. In such case, GNU make ignore empty command
line but BSD make tries to execute it and causes error.
Bump PKGREVISION.
Hijk is a fast & minimal low-level HTTP client intended to be used
where you control both the client and the server, e.g. for talking to
some internal service from a frontend user-facing web application.
It is NOT a general HTTP user agent, it doesn't support redirects,
proxies, SSL and any number of other advanced HTTP features like (in
roughly descending order of feature completeness) LWP::UserAgent,
WWW::Curl, HTTP::Tiny, HTTP::Lite or Furl. This library is basically
one step above manually talking HTTP over sockets.
Having said that it's lightning fast and extensively used in
production at Booking.com where it's used as the go-to transport layer
for talking to internal services. It uses non-blocking sockets and
correctly handles all combinations of connect/read timeouts and other
issues you might encounter from various combinations of parts of your
system going down or becoming otherwise unavailable.
The purpose of this module is to replace
use FindBin;
use lib "$FindBin::Bin/../bootstrap/lib";
with something shorter. This is specially useful if your project has a
lot of scripts (For instance tests scripts).
* Use GITHUB framework.
Changelog:
2015-04-26 v3.6.3 allow limited use of 'git config' using the new 'config'
command
accept openssh 6.8's new fingerprint output format
(finally!) allow limited symlinks within ~/repositories;
see commit 8e36230 for details
perms command now lists available roles
minor backward compat breakage: 'perms -l repo' no longer
works; see 'perms -h' for new usage
allow gitolite-shell to be used as $SHELL (experts only;
no support, no docs; see commit 9cd1e37 for details)
help with 'git push --signed' using a post-receive hook to
adopt push certs into 'refs/push-certs'; for details see
contrib/hooks/repo-specific/save-push-signatures
new 'transparent proxy' feature for git repos; see
src/lib/Gitolite/Triggers/TProxy.pm for details
Changelog:
* Support for 32-bit KVM guests on 64-bit ARM hosts
* Support for running KVM under valgrind
* New IvyBridge CPU model for x86 guests
* Xen: support for ioreq-server API
* New 5KEc and 5KEf MIPS64r2, and M14K and M14Kc MIPS32r2
microMIPS CPU models for MIPS guests
* Basic support for transactional memory extentions in PowerPC guests
* Improved VGA support for little-endian PPC/pSeries guests
* PCI bus support for s390x guests
* Support for automatic guest device unplug when passthrough devices
are unbound from VFIO host driver
* Improved UI performance/support for GTK+/VNC/SDL/Spice, and VNC
support for multiseat
* Performance improvements for virtio-blk emulation: asynchronous SCSI
request handling, and disk read merging.
* QEMU Guest Agent: now also supports file operations in Windows guests,
can be used to enable/disable memory blocks in linux guests in
support for memory hotplug.
* Migration can now include a JSON description of migration stream to aid
in identifying incompatibilities betweens guests/hosts.
* And lots more...
-------------------
1.17 - 2015-04-24, H.Merijn Brand
- Enable overruling $csv in csv ()
- Allow encoding to be shortened to enc in csv ()
- Allow filter to alter content
- Add say (print with default eol => $\)
- Allow MS sep=; on first line (RT#100304)
1.16 - 2015-03-02, H.Merijn Brand
* filter made more useful (access to other fields)
1.15 - 2015-02-11, H.Merijn Brand
* Remove perl recommendation from META as it breaks cpan clients
1.14 - 2015-02-02, H.Merijn Brand
* Move to github
* Add csv (filter => {});
* Change csv ()'s void context behavior
1.13 - 2015-01-03, H.Merijn Brand
* Simplify code path for old perl
* Fix quote_binary (#RT100676)
* Fix csv () for hashrefs with aliased headers
* Update copyright to 2015
----------------------
2014-03-25 Chris Travers <chris.travers@gmail.com>
* version 0.091.3
* Further regexp fixes for 5.19 bracket handling
2014-03-24 Chris Travers <chris.travers@gmail.com>
* version 0.091.1
* Fixed Test Cases failing taint mode under Perl 5.12 and lower.
2014-03-23 Chris Travers <chris.travers@gmail.com>
* version 0.09
* Added additional test case for some entities to make verify table
* Merged in LaTeX::Encode::EncodingTable
2012-09-30 Andrew Ford <a.ford@ford-mason.co.uk>
* version 0.08
* change t/11-unmatched-chars.t to use an unmatched ideographic character instead
of 0x{ffff} as some versions of perl protest about having an illegal Unicode
character in a string.
2012-09-23 Andrew Ford <a.ford@ford-mason.co.uk>
* version 0.07
* remove use of 'parent' in generated module
* add handling of unmatched characters
* add note about Unicode data that does not have the UTF8 flag set
(needed to build DRI3 support in MesaLib and modular-xorg-server on Linux)
This library offers a CPU-based synchronization primitive compatible
with the X SyncFence objects that can be shared between processes
using file descriptor passing.
There are three underlying implementations:
1) On Linux, the library uses futexes
2) On FreeBSD, the library uses umtx
3) On other systems, the library uses posix mutexes and condition
variables.
--------------
1.33 Tue Mar 3 14:13:41 2015
- Fix some reported bugs with handling fields with zeros.
https://rt.cpan.org/Public/Bug/Display.html?id=93518https://rt.cpan.org/Public/Bug/Display.html?id=92509
patched by shlomif
- catch up Text::CSV_XS 1.02
* add decode_utf8 attribute by ktat
- fix warnings: $. is undefined by ktat
- typo fixes in doc by anirvan, dsteinbrunner and pdl.
- parse() supports bind_columns()
* TODO: Updating documents and adding diag_verbose in the next version.
Catching up CSV_XS 1.04.
---------------------------
1.669005 Fri Oct 3 16:56:12 2014
- Added Lisp-style leading ; as a quoter (thanks Roland)
- Added 'quoter' option to allow user to specify a regex
to be used to recognize quoters (thanks Peter)
1.669006 Sat Oct 4 07:32:33 2014
- Improved 'quoter' option to allow augmenting quoter regex,
rather than just replacing it (thanks Peter)
performed all installed files should have their correct mode set, and there are
no INSTALL scripts that currently change file modes under PREFIX after
installation (nor should they ever).
This change considerably speeds up the test. For example in www/firefox-l10n
the time to run the test reduces from 181 seconds (135 seconds of system time)
down to 10 seconds (6 seconds system time) on my SmartOS build systems.
--------------
0.26 Tue 28 Apr 2015 12:31:17 BST
- There is a new experimental option in bleadperl under which one ought not to use
the op_sibling field directly. Quoting from perlguts.pod:
Starting in version 5.21.2, perls built with the experimental
define C<-DPERL_OP_PARENT> add an extra boolean flag for each op,
C<op_moresib>. When not set, this indicates that this is the last op in an
C<OpSIBLING> chain. This frees up the C<op_sibling> field on the last
sibling to point back to the parent op. Under this build, that field is
also renamed C<op_sibparent> to reflect its joint role. The macro
C<OpSIBLING(o)> wraps this special behaviour, and always returns NULL on
the last sibling. With this build the C<op_parent(o)> function can be
used to find the parent of any op. Thus for forward compatibility, you
should always use the C<OpSIBLING(o)> macro rather than accessing
C<op_sibling> directly.
Thanks to Reini Urban for the patch.
- Drop patch-CVE-2014-8964 (now included)
(upstream)
- Update to 8.37
Version 8.37 28-April-2015
--------------------------
1. When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
for those parentheses to be closed with whatever has been captured so far.
However, it was failing to mark any other groups between the hightest
capture so far and the currrent group as "unset". Thus, the ovector for
those groups contained whatever was previously there. An example is the
pattern /(x)|((*ACCEPT))/ when matched against "abcd".
2. If an assertion condition was quantified with a minimum of zero (an odd
thing to do, but it happened), SIGSEGV or other misbehaviour could occur.
3. If a pattern in pcretest input had the P (POSIX) modifier followed by an
unrecognized modifier, a crash could occur.
4. An attempt to do global matching in pcretest with a zero-length ovector
caused a crash.
5. Fixed a memory leak during matching that could occur for a subpattern
subroutine call (recursive or otherwise) if the number of captured groups
that had to be saved was greater than ten.
6. Catch a bad opcode during auto-possessification after compiling a bad UTF
string with NO_UTF_CHECK. This is a tidyup, not a bug fix, as passing bad
UTF with NO_UTF_CHECK is documented as having an undefined outcome.
7. A UTF pattern containing a "not" match of a non-ASCII character and a
subroutine reference could loop at compile time. Example: /[^\xff]((?1))/.
8. When a pattern is compiled, it remembers the highest back reference so that
when matching, if the ovector is too small, extra memory can be obtained to
use instead. A conditional subpattern whose condition is a check on a
capture having happened, such as, for example in the pattern
/^(?:(a)|b)(?(1)A|B)/, is another kind of back reference, but it was not
setting the highest backreference number. This mattered only if pcre_exec()
was called with an ovector that was too small to hold the capture, and there
was no other kind of back reference (a situation which is probably quite
rare). The effect of the bug was that the condition was always treated as
FALSE when the capture could not be consulted, leading to a incorrect
behaviour by pcre_exec(). This bug has been fixed.
9. A reference to a duplicated named group (either a back reference or a test
for being set in a conditional) that occurred in a part of the pattern where
PCRE_DUPNAMES was not set caused the amount of memory needed for the pattern
to be incorrectly calculated, leading to overwriting.
10. A mutually recursive set of back references such as (\2)(\1) caused a
segfault at study time (while trying to find the minimum matching length).
The infinite loop is now broken (with the minimum length unset, that is,
zero).
11. If an assertion that was used as a condition was quantified with a minimum
of zero, matching went wrong. In particular, if the whole group had
unlimited repetition and could match an empty string, a segfault was
likely. The pattern (?(?=0)?)+ is an example that caused this. Perl allows
assertions to be quantified, but not if they are being used as conditions,
so the above pattern is faulted by Perl. PCRE has now been changed so that
it also rejects such patterns.
12. A possessive capturing group such as (a)*+ with a minimum repeat of zero
failed to allow the zero-repeat case if pcre2_exec() was called with an
ovector too small to capture the group.
13. Fixed two bugs in pcretest that were discovered by fuzzing and reported by
Red Hat Product Security:
(a) A crash if /K and /F were both set with the option to save the compiled
pattern.
(b) Another crash if the option to print captured substrings in a callout
was combined with setting a null ovector, for example \O\C+ as a subject
string.
14. A pattern such as "((?2){0,1999}())?", which has a group containing a
forward reference repeated a large (but limited) number of times within a
repeated outer group that has a zero minimum quantifier, caused incorrect
code to be compiled, leading to the error "internal error:
previously-checked referenced subpattern not found" when an incorrect
memory address was read. This bug was reported as "heap overflow",
discovered by Kai Lu of Fortinet's FortiGuard Labs and given the CVE number
CVE-2015-2325.
23. A pattern such as "((?+1)(\1))/" containing a forward reference subroutine
call within a group that also contained a recursive back reference caused
incorrect code to be compiled. This bug was reported as "heap overflow",
discovered by Kai Lu of Fortinet's FortiGuard Labs, and given the CVE
number CVE-2015-2326.
24. Computing the size of the JIT read-only data in advance has been a source
of various issues, and new ones are still appear unfortunately. To fix
existing and future issues, size computation is eliminated from the code,
and replaced by on-demand memory allocation.
25. A pattern such as /(?i)[A-`]/, where characters in the other case are
adjacent to the end of the range, and the range contained characters with
more than one other case, caused incorrect behaviour when compiled in UTF
mode. In that example, the range a-j was left out of the class.
26. Fix JIT compilation of conditional blocks, which assertion
is converted to (*FAIL). E.g: /(?(?!))/.
27. The pattern /(?(?!)^)/ caused references to random memory. This bug was
discovered by the LLVM fuzzer.
28. The assertion (?!) is optimized to (*FAIL). This was not handled correctly
when this assertion was used as a condition, for example (?(?!)a|b). In
pcre2_match() it worked by luck; in pcre2_dfa_match() it gave an incorrect
error about an unsupported item.
29. For some types of pattern, for example /Z*(|d*){216}/, the auto-
possessification code could take exponential time to complete. A recursion
depth limit of 1000 has been imposed to limit the resources used by this
optimization.
30. A pattern such as /(*UTF)[\S\V\H]/, which contains a negated special class
such as \S in non-UCP mode, explicit wide characters (> 255) can be ignored
because \S ensures they are all in the class. The code for doing this was
interacting badly with the code for computing the amount of space needed to
compile the pattern, leading to a buffer overflow. This bug was discovered
by the LLVM fuzzer.
31. A pattern such as /((?2)+)((?1))/ which has mutual recursion nested inside
other kinds of group caused stack overflow at compile time. This bug was
discovered by the LLVM fuzzer.
32. A pattern such as /(?1)(?#?'){8}(a)/ which had a parenthesized comment
between a subroutine call and its quantifier was incorrectly compiled,
leading to buffer overflow or other errors. This bug was discovered by the
LLVM fuzzer.
33. The illegal pattern /(?(?<E>.*!.*)?)/ was not being diagnosed as missing an
assertion after (?(. The code was failing to check the character after
(?(?< for the ! or = that would indicate a lookbehind assertion. This bug
was discovered by the LLVM fuzzer.
34. A pattern such as /X((?2)()*+){2}+/ which has a possessive quantifier with
a fixed maximum following a group that contains a subroutine reference was
incorrectly compiled and could trigger buffer overflow. This bug was
discovered by the LLVM fuzzer.
35. A mutual recursion within a lookbehind assertion such as (?<=((?2))((?1)))
caused a stack overflow instead of the diagnosis of a non-fixed length
lookbehind assertion. This bug was discovered by the LLVM fuzzer.
36. The use of \K in a positive lookbehind assertion in a non-anchored pattern
(e.g. /(?<=\Ka)/) could make pcregrep loop.
37. There was a similar problem to 36 in pcretest for global matches.
38. If a greedy quantified \X was preceded by \C in UTF mode (e.g. \C\X*),
and a subsequent item in the pattern caused a non-match, backtracking over
the repeated \X did not stop, but carried on past the start of the subject,
causing reference to random memory and/or a segfault. There were also some
other cases where backtracking after \C could crash. This set of bugs was
discovered by the LLVM fuzzer.
39. The function for finding the minimum length of a matching string could take
a very long time if mutual recursion was present many times in a pattern,
for example, /((?2){73}(?2))((?1))/. A better mutual recursion detection
method has been implemented. This infelicity was discovered by the LLVM
fuzzer.
40. Static linking against the PCRE library using the pkg-config module was
failing on missing pthread symbols.
Upstream changes:
- R16B03-1 is now the minimal required Erlang/OTP version
- SQLite support
- Default db_type can be specified with global default_db option
- Included mod_muc_admin, mod_admin_extra and mod_multicast modules
- Removed ejabberd_http_poll
- Pubsub improvements
- Better RFC compliance
- Several other bugfixes
* [Makefile] Fix minor issues with ocamlfind and 'make install' (from
Christopher Zimmermann).
o [Printer] In function from_fstring of sub-module Ftime, Fcalendar, and
Precise_Fcalendar, the number of seconds corresponding to %S may be a floating
point number (from Christophe Troestler' suggestion).
Added buildlink file, and updated package to use ocaml.mk framework.
When building in pkg_comp, this option cause the real UID/GID to
be used at install time within the chroot. But the user that exists
in the root filesystem may not exist in the chroot, causing an
installation failure.
