-
Notifications
You must be signed in to change notification settings - Fork 166
Add new package p5-Net-Patricia #15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Patricia Trie perl module for fast IP address lookups
Hello Thomas,
Thomas Merkel writes:
Patricia Trie perl module for fast IP address lookups
You can view, comment on, or merge this pull request online at:
#15
-- Commit Summary --
* Add new package p5-Net-Patricia
-- File Changes --
A net/p5-Net-Patricia/DESCR (3)
A net/p5-Net-Patricia/Makefile (19)
A net/p5-Net-Patricia/distinfo (6)
-- Patch Links --
https://github.com/NetBSD/pkgsrc/pull/15.patch
https://github.com/NetBSD/pkgsrc/pull/15.diff
I have just imported it as net/p5-Net-Patricia with two very tiny
changes:
- Added a dependency to p5-Socket6 (spotted after looking at
${WRKSRC}/META*)
- Changed LICENSE to `gnu-gpl-v2 AND 2-clause-bsd'. The package itself
seems under GNU GPL v2 or later (PERL5_LICENSE is `gnu-gpl-v2 OR
artistic'). Apart that, it seems that code under
${WRKRSC}/libpatricia is under a 2-clause BSD license.
Thank you very much for packaging it!
|
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Aug 31, 2017
This module uses a Patricia Trie data structure to quickly perform IP address prefix matching for applications such as IP subnet, network or routing table lookups. Packaged by Thomas Merkel and patches provided via NetBSD/pkgsrc pullup request #15.
Thank you :-) |
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Nov 8, 2017
0.12 2017-10-26 MANWAR - Added META.yml back to MANIFEST file. 0.11 2017-10-26 MANWAR - [2017-10-26]: Tidied up .gitignore, Changes and MANIFEST file. - [2017-10-26]: Merge pull request #15 from kiwiroy/rt-76160 - [2017-01-02]: Merge pull request #14 from manwar/fix-cpants-issues - [2016-10-04]: Merge pull request #13 from pauloscustodio/pscust_1 - [2015-10-18]: Merge pull request #12 from nichtich/master
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Nov 8, 2017
0.12 2017-10-26 MANWAR - Added META.yml back to MANIFEST file. 0.11 2017-10-26 MANWAR - [2017-10-26]: Tidied up .gitignore, Changes and MANIFEST file. - [2017-10-26]: Merge pull request #15 from kiwiroy/rt-76160 - [2017-01-02]: Merge pull request #14 from manwar/fix-cpants-issues - [2016-10-04]: Merge pull request #13 from pauloscustodio/pscust_1 - [2015-10-18]: Merge pull request #12 from nichtich/master
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Nov 24, 2017
2.03 2017-11-18 - If all frames in the trace were skipped (via skip_frames, frame_filter, ignore_*, etc.), then the stringified stack trace would be an empty string. Now this has been changed to always return the message given to the constructor or the string "Trace begun". Fixes GH #15, reported by Karen Etheridge.
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jun 9, 2018
Upstream changes: 6.72 2018-06-06 - Fixed recurrence bug The fix in the previous version for a rare recurrence problem broke another recurrence form. It is now corrected. Michael Schout (GitHub #20) - Fixed version problem The wrong version was included in two files for some reason. This is fixed. - Documentation fixes Fixed a grammatical error reported by Xavier Guimard (GitHub #19). 6.71 2018-06-01 - Fixed an extremely rare problem with recurrences It is possible to specify a recurrence that never produces a valid date. In these cases, looking for dates went into an infinite loop. The MaxRecurAttempts config variable was added which will stop that from happening. If no occurrence was found, an error condition will be set. Dean Hamstead (RT 123708) - Changes file supported It was requested that I include a valid Changes file. I wrote a simple script to convert the Change6.pod file into a valid Change file. The Changes6.pod file is still the canonical source of this information! Requested by H. Merijn Brand - Fix for timezone determination On MacOS X High Sierra, some of the timezone files were symlinks, but not properly followed. This was fixed by Stu Tomlinson (GitHub #15). - Time zone fixes Newest zoneinfo data (tzdata 2018e) - Documentation fixes Minor fix provided by Mohammad S Anwar (GitHub #17)
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jul 10, 2018
Upstream changes: 1.20180705 2018-07-05 16:47:18-07:00 America/Los_Angeles - added destructor to clear counters (choroboa PR #15, RT #71831)
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Aug 20, 2018
2018-08-18 -- 0.8.6 * Fixed: Bad/NULL .hostText.afterLast when parsing certain rather pathologic but well-formed URIs with empty host (e.g. "//:%aa@") (GitHub #15) Thanks to Kurt Schwehr for the report! * Fixed: Fix uriRemoveBaseUri for case where scheme, host name, IPvFuture address or path segments of the source address were string prefixes of the related counterpart in the base URI. Thanks to Yang Yu for the patch! (GitHub #19, #20) * Fixed: Make UriStringToUnixFilename and UriStringToWindowsFilename support minimal representation a la RFC 8089, e.g. file:/bin/bash (compare to file:///bin/bash with three slashes) (GitHub #12, #14) Thanks to Zane van Iperen for the report! * Fixed: Documentation typos (GitHub #10, #11) Thanks to Graham Percival! * Improved: Made API docs of uriRemoveBaseUri more clear (related to GitHub #19) * Soname: 1:22:0
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Sep 23, 2018
== 1.0.0 (2018-05-20) * *BreakingChange* The XZ module's methods now take any parameters beyond the IO object as real Ruby keyword arguments rather than a long argument list. * *BreakingChange* XZ.decompress_stream now honours Ruby's external and internal encoding concept instead of just returning BINARY-tagged strings. * *BreakingChange* Remove deprecated API on stream reader/writer class and instead sync the API with Ruby's zlib library (Ticket #12 by me). * *BreakingChange* StreamWriter.new and StreamReader.new do not accept a block anymore. This is part of syncing with Ruby's zlib API. * *BreakingChange* StreamReader.open and StreamWriter.open always return the new instance, even if a block is given to the method (previous behaviour was to return the return value of the block). This is part of the syncing with Ruby's zlib API. * *BreakingChange* StreamReader.new and StreamWriter.new as well as the ::open variants take additional arguments as real Ruby keyword arguments now instead of a long parameter list plus options hash. This is different from Ruby's own zlib API as that one takes both a long parameter list and a hash of additional options. ruby-xz is meant to follow zlib's semantics mostly, but not as a drop-in replacement, so this divergence from zlib's API is okay (also given that it isn't possible to replicate all possible options 1:1 anyway, since liblzma simply accepts different options as libz). If you've never used these methods' optional arguments, you should be fine. * *BreakingChange* Stream#close now returns nil instead of the number of bytes written. This syncs Stream#close with Ruby's own IO#close, which also returns nil. * *BreakingChange* Remove Stream#pos=, Stream#seek, Stream#stat. These methods irritated the minitar gem, which doesn't expect them to raise NotImplementedError, but directly to be missing if the object does not support seeking. * *BreakingChange* StreamReader and StreamWriter now honour Ruby's encoding system instead of returning only BINARY-tagged strings. * *Dependency* Remove dependency on ffi. ruby-xz now uses fiddle from the stdlib instead. * *Dependency* Remove dependency on io-like. ruby-xz now implements all the IO mechanics itself. (Ticket #10 by me) * *Dependency* Bump required Ruby version to 2.3.0. * *Fix* libzlma.dylib not being found on OS X (Ticket #15 by s0nspark).
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Oct 20, 2018
Upstream changes: 0.15 2018-09-22 13:40:30 PDT - in LWP adapter, check if Mozilla::CA is installed as well #15
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Nov 3, 2018
Changelog: Removed ARM assembly implementation (ARM will use pure Go implementation now) because it had a bug #15. While there was no changes regarding compiler versions, it doesn't make sense to support Go 1.1.
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jan 20, 2019
=== 1.8.0 (2018-12-18) * Support :yield_returns_buffer option in capture_end for always returning the (potentially modified) buffer in <%|= tags (evanleck) (#15)
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Feb 13, 2019
0.18.7 * Migrate from intltool to gettext [!2] * Fix uninitialized memory returned by secret_item_get_schema_name() [#15] * secret-session: Avoid double-free in service_encode_plain_secret() * Port tap script to Python 3 [!4] * Build and test fixes [#734630] * Updated translations
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Aug 25, 2019
* Readd _OPENBSD_SOURCE explicitly to fix build on NetBSD 9 Changelog: 13 August 2019: Wouter - Fix error message for out of zone data to have more information. 12 August 2019: Wouter - Fix #33: Fix segfault in service of remaining streams on exit. 6 August 2019: Wouter - Tag for 4.2.2rc1. 5 August 2019: Wouter - PR #31: nsd-control: Add missing stdio header. - PR #32: tsig: Fix compilation without HAVE_SSL. - Cleanup tls context on xfrd exit. 31 July 2019: Wouter - Fix #29: SSHFP check NULL pointer dereference. - Fix #30: SSHFP check failure due to missing domain name. - Fix to timeval_add in minievent for remaining second in microseconds. 22 July 2019: Wouter - Set timeout for refetch immediately, only spread load when there are retries. 19 July 2019: Wouter - Set no renegotiation on the SSL context to stop client session renegotiation. 18 July 2019: Wouter - Fix #25: NSD doesn't refresh zones after extended downtime, it refreshes the old zones, with a random delay of a couple of seconds to spread the load. - Fix so that expired zones stay expired when server is down a long time. 17 July 2019: Wouter - Fix that NSD warns for wrong length of the hash in SSHFP records. 15 July 2019: Wouter - PR #23: Fix typo in nsd.conf man-page. 4 July 2019: Wouter - Set version to 4.2.2 in development. - clean memory on exit of nsd-checkzone for memory debug. - Fix #20: CVE-2019-13207 Stack-based Buffer Overflow in the dname_concatenate() function. Reported by Frederic Cambus. It causes the zone parser to crash on a malformed zone file, with assertions enabled, an assertion catches it. - Fix #19: Out-of-bounds read caused by improper validation of array index. Reported by Frederic Cambus. The zone parser fails on type SIG because of mismatched definition with RRSIG. 2 July 2019: Wouter - Tag for 4.2.1rc1 27 June 2019: Wouter - Fix unit test for added options and no dot after zone updated log message. - Fix compile without accept4. 21 June 2019: Wouter - Omit remaining tcp processing if the list is empty. - Fix output of nsd-checkconf -h. 20 June 2019: Wouter - Initialize event structures before event_set, to stop uninitialized values from setting event library lists and assertions, that would sometimes also show after event_del. - Added num.tls and num.tls6 stat counters. - PR #12: send-buffer-size, receive-buffer-size, tcp-reject-overflow options for nsd.conf, from Jeroen Koekkoek. - Do not use symbol from libc, instead use own replacement, if not available, for accept4. - Fix #14, tcp connections have 1/10 to be active and have to work every second, and then they get time to complete during a reload, this is a process that lingers with the old version during a version update. 19 June 2019: Wouter - Fix tls handshake event callback function mistake, reported by Mykhailo Danylenko. 18 June 2019: Wouter - Fix #15: crash in SSL library, initialize variables for TCP access when TLS is configured. 14 June 2019: Wouter - Fix to init event not pointer, in reassignment. 12 June 2019: Wouter - Fix to init event structure for reassignment.
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Aug 25, 2019
Changelog: New Libraries Variant2: A never-valueless, strong guarantee implementation of std::variant, from Peter Dimov. Updated Libraries Align: Support for any integral type in the integral versions of align_up and align_down. Revised the implementation of aligned_allocator to no longer require a specialization for void. Define propagate_on_container_move_assignment and is_always_equal in aligned_allocator. Asio: Improved performance slightly by eliminating a redundant move construction when completed handlers are dispatched. Eliminated a compiler warning by annotating a case fall-through in the free function connect() implementation. Fixed the is_*_buffer_sequence detection traits for user-defined sequence types. Fixed some Windows-specific warnings about an incompatible pointer cast when obtaining the CancelIoEx entry point. Changed to automatically set the defaults when opening a serial port on Windows. Changed the serial port get_option() member function to be const. Fixed a name hiding issue with the WinRT stream-oriented socket backend's shutdown function. Applied a minor fix to the documentation for is_dynamic_buffer. Added some support for Haiku OS. Added wolfSSL compatability. Changed to require C++17 or later for coroutines TS support with clang. Fixed a doxygen generation problem in the tutorial. Ensured example programs are correctly incorporated into the documentation. Any: Static initialization of the default constructed boost::any is now possible. Fixed performance regression in assignment on a compilers without move-semantics. Maintenance work. Beast: This version consists mostly of bug fixes and performance improvements. Substantial work included for the split compilation mode, to reduce compile time when defining BOOST_BEAST_SEPARATE_COMPILATION. We'd love to know how you or your company use Beast, consider adding an item to the Companies and Individuals Using Beast list. See the full Release Notes for a complete list of changes. Circular Buffer: Correct doxygen generated reference to no longer show internal members. (Glen Fernandes) Eliminate ubsan warning on add and sub. (Glen Fernandes) Fix incorrect check in is_uninitialized. (Niklas Fejes) Container: Fixed bugs: GitHub #47: "added alignment specification for small_vector". GitHub #88: "Implement C++17 MoveAssignable requirements for self-move assignments". GitHub #107: "Alignment ignored in resource_adaptor". GitHub #109: "Get rid of integer overflow in copy_move_algo.hpp (-fsanitize=integer)". GitHub #110: "Avoid gcc 9 deprecated copy warnings in new_allocator.hpp". GitHub #112: "vector::resize() compilation error with msvc-10..12: data is not a member of boost::detail::aligned_storage". GitHub #114: "Fix small_vector noexcept specification". GitHub #116: "MSVC + boost 1.70 compilation error when windows.h is already included (detail/thread_mutex.hpp)". GitHub #117: "flat_map/map::insert_or_assign with hint has wrong return types". GitHub #118: "Non-unique inplace_set_difference used in in flat_tree_merge_unique and iterator invalidation in insert_unique". GitHub #122: "Fix has_trivial_destructor_after_move". GitHub #123: "With heterogeneous lookup, equal_range can result in a range with length greater than 1". deque can now have options, using deque_options. The block size/bytes can be be specified. static_vector can now have options, using static_vector_options. Alignment and throwing behaviour can be be specified. small_vector can now have options, using small_vector_options. Alignment and growth factor can be be specified. Context: Add support for RISC-V LP64D #72: Fix ABI violation on ppc64 ELFv2 #99: cleanup of stack if creating ucontext fails Conversion: Maintenance work. Core: Added functions alloc_construct, alloc_construct_n, alloc_destroy, and alloc_destroy_n in <boost/core/alloc_construct.hpp> for allocator aware and exception safe construction and destruction of objects and arrays. (Glen Fernandes) Added constexpr functions first_scalar in <boost/core/first_scalar.hpp> for obtaining a pointer to the first scalar element of an array. Given a pointer of type T* they return a pointer of type remove_all_extents_t<T>*. (Glen Fernandes) Added class template noinit_adaptor in <boost/core/noinit_adaptor.hpp> which is an allocator adaptor that converts any allocator into one whose construct(ptr) performs default initialization via placement new, and whose destroy(ptr) invokes the value_type destructor directly. (Glen Fernandes) Added class template default_allocator in <boost/core/default_allocator.hpp>, which can serve as a minimal default allocator that has interface similar to C++20 std::allocator, supports configurations with disabled exceptions and does not have std as an associated namespace. The allocator uses operator new and operator delete for allocation. (Glen Fernandes) In <boost/core/uncaught_exceptions.hpp> header, added workarounds for better compatibility with QNX SDP 7.0 when libc++/libc++abi libraries are used. (Andrey Semashev, #59) The <boost/detail/sp_typeinfo.hpp> header is now marked as deprecated and will be removed in a future release. <boost/core/typeinfo.hpp> should be used instead. (Peter Dimov) Dynamic Bitset: Enabled hardware-assisted popcount on MSVC (#38). Added support for boost::hash and std::hash (#45). Support copy-initialization with default constructor (#48). Endian: Clarified requirements on the value type template parameter Added support for float and double Added endian_load, endian_store Updated endian_reverse to correctly support all non-bool integral types Moved deprecated names to the deprecated header endian.hpp Fiber: documentation for shared_work updated Filesystem: Fixed incorrect error_code returned from directory iterator increment when readdir_r is used. For path, fixed rvalue-aware operator/ return type to return an rvalue instead of rvalue reference. This fixes leaving a dangling reference in the user's code if the result of operator/ is bound to a const reference. (#110) Fixes for better compatibility with Windows CE. (#24) Added minimal support for CMake. (#106) Flyweight: Maintenance work. Histogram: New features: Support for thread-safe storages and new thread-safe accumulators Support for compiling without exceptions/RTTI (increases performance by 10-20 %) (with Glen Fernandes) Performance improvements for 1D and 2D histograms boost::histogram::indexed now returns forward iterator range instead of input iterator range boost::histogram::indexed_range::accessor is now non-copyable and acts like reference to cell value, making more algorithms from the C++ stdlib work boost::histogram::algorithm::reduce with new slice option and option fusion boost::histogram::algorithm::project accepts runtime indices for static histograms Bug Fixes: boost::histogram::algorithm::reduce also works on histograms that have some axis types without reduction support boost::histogram::axis::traits::update now works correctly for boost::histogram::axis::variant Other: 100 % test coverage Reduced internal Boost dependencies Improved documentation and examples Guaranteed no-throw moves for all builtin axis types Compile cleanly at higher warning levels See changelog for more details. IoStreams: Fixed processing of multi-stream files (#87). Added support for multi-threaded LZMA (#95). Interprocess: GitHub #85 ("warning: Implicit conversion loses integer precision"). GitHub #86 ("warning: Possible misuse of comma operator"). Intrusive: GitHub #42: Documentation does not describe treap priority_of_value changes GitHub #43: Fix tests with BOOST_INTRUSIVE_VARIADIC_TEMPLATES enabled GitHub #45: Disable variadic templates for MSVC-12 to avoid ICEs LexicalCast: Added tests for boost::filesystem::path conversions #25. Maintenance work, including #28. Log: New features: Improved support for C++17 std::string_view in basic_formatting_ostream. The string view can now participate in character code conversion on output. Added auto_newline formatter and stream manipulator. It can be used to ensure that formatted output always ends with a newline while avoiding duplicate newlines. In the output stream, text file and text multi-file sink backends added support for configuring behavior with regard to appending a trailing newline to every formatted log record. Use auto_newline_mode named parameter of the backend constructor or call the set_auto_newline_mode method on the sink backend. Note: The default behavior with regard to trailing newlines added by sink backends has changed slightly compared to the previous Boost.Log releases. The backends will now only add a trailing newline if there isn't one in the formatted log message string already. In previous releases a newline was added unconditionally. Added support for passing arbitrary function objects in the filter and format named parameters to sink constructors and convenience functions for initializing sinks. For example, it is now possible to specify C++11 lambda functions directly in these parameters. (#63) In the default filter and formatter factories used in filter and formatter parsers, added support for severity level attribute values of type boost::log::trivial::severity_level. For filters, the support is limited to attributes with "Severity" name. Bug fixes: Fixed incorrect parsing of components of the rotated file names while scanning for files in the text file sink backend. If the file name pattern ended with a placeholder (for example, a file counter), the scan_for_files method would not find files matching that pattern in the target storage, leaving them unmanaged. In particular, such files would not be deleted to free target storage. (#78) Updated basic_formatting_ostream and basic_record_ostream to make it possible to overload stream output operators for pointers to user-defined types. User-defined operator<< overloads taking std::basic_ostream and a pointer argument should now be picked up by the compiler when the pointer is being written to one of Boost.Log streams. (#84) See changelog for more details. Math: New features: Catmull-Rom interpolator now works in C++11 Cardinal quadratic B-spline interpolation Domain of elliptic integrals extended sin_pi and cos_pi performance improvements Forward-mode automatic differentiation Vector valued barycentric rational interpolation Ooura's method for evaluation of Fourier integrals Bug fixes: Multiple compatibility issues with Multiprecision fixed Lambert-W fixed on a rare architecture Metaparse: New features: In C++11 variadic template support for the following: sequence, one_of_c, one_of, repeated_one_of, repeated_one_of1, one_char_except_c, one_char_except. Bug fixes: BOOST_METAPARSE_STRING does not use out of range character values as template arguments. any_of_c<> does not create empty array in C++14. Move: Git Issue #26: "Invalid iterator increment/decrement in the last iteration of adaptive_sort_combine_blocks". Multi Array: Simplify allocator support by using new alloc_construct_n and alloc_destroy_n facilities from Core. (Glen Fernandes) Multi-index Containers: Added variants of const_mem_fun and mem_fun for differently qualified member functions (issue #24). Terse key specification syntax now correctly handles noexcept-specified member functions (issue #24). Outcome: Enhancements: #184 As per request from Boost release managers, relocated version.hpp and revision.hpp into detail, and added the Boost licence boilerplate to the top of every source file which was missing one (I think). Also took the opportunity to run the licence restamping script over all Outcome, so copyright dates are now up to date. #185 Add FAQ item explaining issue #185, and why we will do nothing to fix it right now. #189 Refactored the OUTCOME_TRY implementation to use more clarified customisation points capable of accepting very foreign inputs. Removed the std::experimental::expected<T, E> specialisations, as those are no longer necessary. Fixed the documentation for the customisation points which previously claimed that they are ADL discovered, which they are not. Added a recipe describing how to add in support for foreign input types. #183 Added a separate motivation/plug_error_code specifically for Boost. Bug fixes: OUTCOME_VERSION_MINOR hadn't been updated to 1. #181 Fix issue #181 where Outcome didn't actually implement the strong swap guarantee, despite being documented as doing so. #190 Fix issue #190 in Boost edition where unit test suite was not runnable from the Boost release distro. #182 Fix issue #182 where trait::is_exception_ptr_available<T> was always true, thus causing much weirdness, like not printing diagnostics and trying to feed everything to make_exception_ptr(). #192 Fix issue #192 where the std::basic_outcome_failure_exception_from_error() was being defined twice for translation units which combine standalone and Boost Outcome's. Parameter: Upgraded keyword generation macro BOOST_PARAMETER_TEMPLATE_KEYWORD (#15). Moved keyword generation macro BOOST_PARAMETER_NESTED_KEYWORD from Accumulators to this library (#28). Added support for std::reference_wrapper and std::ref() (#16). Moved boost::parameter::required, boost::parameter::optional, and boost::parameter::deduced metafunction definitions to their own header files in directory boost/parameter (#18). Added support for Boost.Parameter-enabled function call operators (#20). Added support for parameter category qualifiers "forward", "consume", and "move_from" (current qualifiers are "in", "out", and "in_out") (#21) (#23) based on http://www.modernescpp.com/index.php/c-core-guidelines-how-to-pass-function-parameters. Added new usage syntax BOOST_PARAMETER_NAME((object-name), namespace-name) qualifier(tag-name)) and BOOST_PARAMETER_NAME(qualifier(name)). (Existing code that uses qualifiers directly and correctly with BOOST_PARAMETER_FUNCTION and other code generation macros should remain unaffected for now, so no breaking changes.) The reason for the change in usage is to enable applying of parameter category constraints to Boost.Parameter-enabled functions and constructors invoked through argument composition. (Otherwise, it is currently possible to use argument composition to bypass parameter category constraints applied in BOOST_PARAMETER_FUNCTION et. al.) Added support for perfect forwarding (#23) (#26), so that parameter::parameters::operator() can accept non-const rvalues. As a positive side effect, Boost.Parameter-enabled functions and constructors are no longer bound by BOOST_PARAMETER_MAX_ARITY on compilers that support perfect forwarding. User code can now check for this support by detecting the configuration macro BOOST_PARAMETER_HAS_PERFECT_FORWARDING, or manually turn off this support by defining the configuration macro BOOST_PARAMETER_DISABLE_PERFECT_FORWARDING. Added metafunctions boost::parameter::is_argument_pack (#27), boost::parameter::are_tagged_arguments (#52), and boost::parameter::result_of::compose (#75). Added variadic function template boost::parameter::compose() which takes in named arguments and returns them in an argument pack (#52). For compilers that do not support perfect forwarding, the configuration macro BOOST_PARAMETER_COMPOSE_MAX_ARITY determines the maximum number of arguments that boost::parameter::compose() can take in (#61). Added code generation macros BOOST_PARAMETER_BASIC_FUNCTION_CALL_OPERATOR, BOOST_PARAMETER_BASIC_CONST_FUNCTION_CALL_OPERATOR, BOOST_PARAMETER_NO_SPEC_FUNCTION, BOOST_PARAMETER_NO_SPEC_MEMBER_FUNCTION, BOOST_PARAMETER_NO_SPEC_CONST_MEMBER_FUNCTION, BOOST_PARAMETER_NO_SPEC_FUNCTION_CALL_OPERATOR, BOOST_PARAMETER_NO_SPEC_CONST_FUNCTION_CALL_OPERATOR, BOOST_PARAMETER_NO_SPEC_CONSTRUCTOR, and BOOST_PARAMETER_NO_SPEC_NO_BASE_CONSTRUCTOR (#52). Added support for Boost.MP11 (#47) (#66) (#70). User code can now check for this support by detecting the configuration macro BOOST_PARAMETER_CAN_USE_MP11, or manually turn off this support by defining the configuration macro BOOST_PARAMETER_DISABLE_MP11_USAGE. Improved support for parameter-dependent return types via SFINAE (#73). PtrContainer: Fix a ptr_vector regression introduced in 1.66.0 (#24). PolyCollection: Maintenance work. SmartPtr: Added aliasing constructors to weak_ptr Added weak_ptr<T>::empty() Added enable_shared_from, shared_from, and weak_from Stacktrace: Fixed output of name(), source_location() and source_line() for the default constructed frame with thread sanitizer builds in C++98 mode. Fixed output of long strings from name() and source_location() on MSVC #78. Maintenance work. Test: Boost.test v3.11 see the Changes log for more details. Breaking changes: Boost.Test shows deprecation warnings if some very old headers as deprecated. If you encounter such warnings, please follow the indications: those headers will be removed in a future release. New feature: Now BOOST_TEST can be used to compare abstract types Bug fixes and pull requests: GitHub Issues: #209, #218 GitHub Pull Requests: #219, #224 Utility: Implemented function template ostream_string in <boost/utility/ostream_string.hpp> to optimally write any kind of string content to an output stream. It satisfies the requirements of [ostream.formatted.reqmts]. (Glen Fernandes) Optimized the stream output operators of basic_string_view and basic_string_ref to write directly to the rdbuf stream buffer. (Glen Fernandes) Uuid: Breaking change: MD5 name-based uuid generation was corrected to be identical on all endian systems. Define BOOST_UUID_COMPAT_PRE_1_71_MD5 to keep the result in a format compatible with 1.66 through 1.70. This does not affect the default name-based uuid generation which is based on SHA1. (#109) Variant: Fixed compilation of boost::apply_visitor with variants passed by non const reference in #68. Many thanks to Ed Catmur for providing the fix. Added support for std::hash (#49). Macro BOOST_VARIANT_DO_NOT_SPECIALIZE_STD_HASH could be defined to avoid those specializations. Added micro optimizations for binary size and performance by Nikita Kniazev in #63 and #66. Maintenance work, including #64 by Nikita Kniazev and #67 by Hans Dembinski. YAP: Added an example showing how to make self-evaluating YAP expressions (that is, expressions that don't need an explicit call to evaluate() or transform()).
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Oct 27, 2019
0.44 2019-08-14 - Replaced the use of B with XString if it is installed. The latter is much smaller and provides the one subroutine from B we cared about. Based on GH #15. Implemented by Nicolas R.
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Nov 14, 2019
2.62.1 - October 4, 2019 ======================== - Fix two memory leaks (!71, !72, Claudio Saavedra) 2.62.0 - September 7, 2019 ========================== - Revert broken queued data fix for #15 2.61.92 - September 2, 2019 =========================== - Discard queued data after interrupted writes (#15) - Verify socket timeouts are respected (#18) - Fix a couple broken error messages 2.61.90 - August 5, 2019 ======================== - Fix translations of certain error messages 2.61.2 - July 22, 2019 ====================== - Improve certain handshake error messages (#13) - Fix regressions introduced in 2.61.1 (#91, #92) 2.61.1 - June 9, 2019 ===================== This release contains a major refactoring of the TLS codebase. The GnuTLS backend now shares the same base classes as the OpenSSL backend, to avoid duplicating as much code as possible. The base classes, previously used only by the OpenSSL backend and originally forked from glib-networking several years ago, have been enhanced to achieve feature-parity with the current state of the GnuTLS backend. Please note that the OpenSSL backend remains experimental. Further planned work is required before this backend will be production-ready.
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jan 2, 2020
0.3.18, released 2019-12-04 #27, deprecate maximumDef and friends, fold*1Def #27, add maximumBounded and friends Stop supporting GHC 7.4 to 7.8 0.3.17, released 2018-03-09 Improve the display of errors, less internal callstack Add a few missing Partial constraints 0.3.16, released 2018-01-06 #22, add Safe index 0.3.15, released 2017-06-18 Support QuickCheck 2.10 0.3.14, released 2017-02-15 #20, fix for GHC 7.10.1 0.3.13, released 2017-02-09 #20, require GHC 7.4 or above 0.3.12, released 2017-02-05 #19, add Safe.Partial exposing a Partial typeclass #19, add support for GHC call stacks 0.3.11, released 2017-01-22 #16, add Safe succ and pred #16, add readEitherSafe for better errors than readEither #14, add Safe zip3Exact 0.3.10, released 2016-11-08 #15, add Safe cycle 0.3.9, released 2015-05-09 #9, add Safe toEnum 0.3.8, released 2014-08-10 #8, remove unnecessary Ord constraints from Foldable functions
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jan 14, 2020
0.3.18, released 2019-12-04 #27, deprecate maximumDef and friends, fold*1Def #27, add maximumBounded and friends Stop supporting GHC 7.4 to 7.8 0.3.17, released 2018-03-09 Improve the display of errors, less internal callstack Add a few missing Partial constraints 0.3.16, released 2018-01-06 #22, add Safe index 0.3.15, released 2017-06-18 Support QuickCheck 2.10 0.3.14, released 2017-02-15 #20, fix for GHC 7.10.1 0.3.13, released 2017-02-09 #20, require GHC 7.4 or above 0.3.12, released 2017-02-05 #19, add Safe.Partial exposing a Partial typeclass #19, add support for GHC call stacks 0.3.11, released 2017-01-22 #16, add Safe succ and pred #16, add readEitherSafe for better errors than readEither #14, add Safe zip3Exact 0.3.10, released 2016-11-08 #15, add Safe cycle 0.3.9, released 2015-05-09 #9, add Safe toEnum 0.3.8, released 2014-08-10 #8, remove unnecessary Ord constraints from Foldable functions
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jan 18, 2020
Version 4.2.0 (2019/12/28) - released at SILK New Features: raw Pokey registers recording by Ivo van Poorten new platform supported: FireBee optional hiding of hidden files/folders in the UI file selector libatari800 (Atari800 as a library) by Rob McMullen R: device (many years old feature) enabled by default Fixes: proper check if SDL joysticks are found (fixes #58) Portrait mode for Android (related to #41) RMW for Pokey Improved BASIC LST file loading (#55) ROM OS path changes handled better (#15) improved "Find ROM images" - now Atari800 reboots if necessary (#15) fixed an old bug which caused freezing in the UI on Falcon New command line options: -pokeyrec and its children -atari_files (#29) -saved_files (#29) -kbdjoy0 -kbdjoy1 -nokbdjoy0 -nokbdjoy1 (#29) Plus many Atari Falcon specific fixes and improvements by Mikro. This should be the most complete and bug-free Atari Falcon release in years, so enjoy! :)
netbsd-srcmastr
pushed a commit
that referenced
this pull request
May 4, 2020
(devel/p5-File-LibMagic) Updated 1.16 to 1.22 (pkgsrc) - BUILD_DEPENDS converted to TEST_DEPENDS - dropped :BUILD_DEPENDS+= p5-ExtUtils-MakeMaker>=7.10 (upstream) 1.22 2020-04-26 - This is a stable release with the same changes as 1.21. See the change logs for 1.17 and 1.21 for details of what's new. 1.21 2020-04-04 (TRIAL RELEASE) - Add two class methods that provide introspection on the available limit processing parameters, max_param_constant() and limit_key_is_supported(). Based on a PR from Paul Wise. GH #24. 1.20 2020-03-28 (TRIAL RELEASE) - Fix one last test that assumed a limit parameter was available. Reported by Slaven Rezić. GH #22. 1.19 2020-03-28 (TRIAL RELEASE) - Fix tests that still mistakenly assumed that all limit parameter constants should be exported by File::LibMagic. Reported by Slaven Rezić. GH #22. 1.18 2020-03-28 (TRIAL RELEASE) - Not all versions of libmagic support setting processing limits, and those that do may not support all the limit parameters that the most recent version supports. This release fixes compilation and runtime issues that would occur with older libmagic versions that don't support the same options as the version I have installed locally. Reported by Slaven Rezić. GH #22. 1.17 2020-03-28 (TRIAL RELEASE) - Switched to using GitHub issues. - Removed embedded copy of Config::AutoConf from distro. Instead this is now a configure phase prereq. Implemented by Paul Wise. GH #19. - Moved list of constants in libmagic that we care about to one module. Implemented by Paul Wise. GH #20. - Add support for setting libmagic processing limits. Implemented by Paul Wise. GH #15. - Check all libmagic function return values properly and croak on failure. Implemented by Paul Wise. GH #21.
netbsd-srcmastr
pushed a commit
that referenced
this pull request
May 12, 2020
Patchlevel 7b (Oct 2019) NEW FEATURES: o A X color database is not needed, but can be provided. The location of the database can be given at compile time, default /etc/X11/rgb.txt. BUGS FIXED: Ticket numbers refer to https://sourceforge.net/p/mcj/tickets/#. Debian bug numbers refer to https://bugs.debian.org/#. o Do not clip objects with line-thickness 0 having arrows. Ticket #53. o Do not segfault on circle/half circle arrowheads with a magnification larger 42. Always draw circle arrowheads with 40 points. Ticket #52. o Allow circles or ellipses with negative radii. Ticket #49. o Avoid "dimension too large error" with tikz output by avoiding coordinate values smaller than -16383. o Make tests (test1.c) work with -fsanitize=address compiler option. o Obey join-style of lines in tikz output. o Pass utf8-strings to svg output, escape some chars (<>&). o Accept inclined boxes and change them to polygons. Fixes ticket #43. o Make tests #27 and #33 work on Mac Darwin, failed due to whitespace formatting differences. From Hanspeter Niederstrasser. Ticket #40. o Use only latex, neither etex or tex, to test tikz output. Usage of etex, after hint from Roland Rosenfeld, closed debian bug 920368. o For tikz output, do not draw arrows on a single point line. o Omit spurious showpage when including jpg-file. From Rainer Buchty. o Correct a few memory leaks and corruptions. See commit d1c54f6. o Change negative color numbers to default color. Fixes ticket #30. o A spline with one point would cause segfault. Fixed, see ticket #29. o Allow one char without newline in the last line of an input file. Fixes ticket #28. o Harden input, mainly against files in which an incomplete object would be created and freeing the object would violate memory, i.e, it may cause segfault. See, e.g., ticket #27. o Properly initalize line storage when reading fig files version 1.3. Would segfault when reading incomplete line and trying to free it. Fixes ticket #26, debian bug 906743. o Silently ignore the hundred-first and more comment lines. This fixes ticket #25 and debian bug 906740. o Use SetFigFont, not SetFigFontNFSS in pictex output. Fixes https://bugs.launchpad.net/ubuntu/+source/transfig/+bug/1359485 . o Accept blanks in color names (e.g., fig2dev -L eps -g"Misty Rose"..). o Correct typos in man-pages, debian 30_man_typo.patch. ------------------------------------- Patchlevel 7a (May 2018) NEW FEATURES: o Add option -w, wrap (create stand-alone perl file) for Perl/Tk output. o Distribute the X bitmaps files within fig2dev, no need to install these files. The files were needed for Tk and Perl/Tk output. BUGS FIXED: Ticket numbers refer to https://sourceforge.net/p/mcj/tickets/#. o Fix regression whereupon flipped ellipses were not read. Ticket #23. o Distribute i18n files ru_RU.CP1251.ps and uk_UA.KOI8-U.ps. o Make test "survive debian bug #890016" succeed on 32 bit systems. ------------------------------------- Patchlevel 7 (April 2018) OPTION LETTER CHANGES: o Language previous option current option ------------------------------------------------------------ cgm -b dummy -a epic -A scale -d scale eepic -A scale -d scale eepicemu -A scale -d scale gbx -i on|off -v ibmgl -m mag,xoff,yoff -m mag -x xoff -y yoff mp -I file -d file ps -S dummy -o NEW FEATURES: o Print language-specific help text by using fig2dev -L lang -h. o Add option -M, multipage, for MetaPost output language. o Add option -P, pagemode, and -z to choose a pagesize for pdf output. o Add option -W (scaling of figures not possible) for tikz. o Add option -b, border width, for LaTeX output language. o Add option -f for pstex_t and pdftex_t output language. o Add uk_UA and ru_RU encodings for PostScript output. Ticket #12. BUGS FIXED: o Update help text: Output help for dxf and textyl output language, add description of -g option for Tk/Tcl and Perl/Tk output, allow -f option for pstex_t and pdftex_t output language. Debian bug numbers refer to https://bugs.debian.org/#. Ticket numbers refer to https://sourceforge.net/p/mcj/tickets/#. o Sanitize input. Do not segfault on malformed input files. Fixes debian bugs 881143, 881144, 881396, 890015, 890016, 882021 and also 882022. o Do not put an %%Orientation: comment into PostScript output. Some viewers would rotate the resulting file, others not. o Fix build on NetBSD, which has a _setmode() function different from _setmode() on Windows. Ticket #17. Also, avoid alloca(). Ticket #16. o tikz output: Omit the semicolon after \pgftext[..]{...};. o Define PostScript patterns with larger tiles, may render better. #13 o Fix build in case libXpm is missing. Ticket #15. o Use netpbm programs instead of ghostscript, to produce smaller files. o Correctly embed eps files with binary preview (epsi, typically found on Microsoft systems). Also, allow to embed ps-files. Fixes debian bug 248807, ticket #8. o For compilation, do not depend on PATH_MAX being defined.
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jun 2, 2020
Update to pear-Log to 1.13.2. 1.13.2 (2020-06-02) * Bump pear/pear_exception dependency to version to 1.0.1. (#15)
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jan 22, 2023
v0.3.0 - 21 Jan 2023 - Update syntect dependency to v5.0.0. Thanks to lazy loading, this change makes loading assets at startup about 70% faster. The small benchmark showed hgrep command was 1.7x faster when searching a small file with -p syntect compared to v0.2.8. - Update bat dependency from 0.20 to 0.22. This introduces several improvements and fixes which were recently added to bat when using -p bat. - Add --generate-man-page flag to generate a manual page file. Save the output to your man directory to show the help with man command. If you install hgrep with Homebrew, it will be automatically generated. - Add several syntax highlighting for configuration files (Git configs, Fish history, SSH config, Nginx config, ...). - Wrapp the --help output looking at the terminal width. The output is more compact than v0.2.8. - Improve error handling when failing to enable ANSI color sequences support on Windows. v0.2.8 - 10 Jan 2023 - Fix some command line boolean flags wrongly took an argument. (thanks @Ryooooooga, #15) v0.2.7 - 04 Jan 2023 - Fix crash when reading from rg --vimgrep. Note that --vimgrep flag is not assumed by hgrep. Please use rg -nH. (#13) - Fix errors are not reported when they are caused by the second match or later. - Update dependencies to the latest. Especially migrating to clap v4 improved the --help output. - Migrate to Rust 2021 edition.
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Feb 11, 2023
Change log: 4.18.0 (2023-02-08) ====== - Changed Orage internal time and data strings to GDateTime (MR !20) - In event list, fixed event hiding when event start at 00:00 and end 00:00 in same date (this kind event can be created when creating full day event, save event and then unset full day option). (MR !20) - Removed bundled libical (Issue #5) - Removed panel plugin (Issue #11) - Removed GlobalTime (Issue #12) - Replaced old Orage icons (Issue #16) and removed 160x160 icons - Replaced deprecated dbus-glib with GDBus (Issue #4) - Changed event attach order in day view window (Issue #15) - Added Wayland support (Issue #2) - Fixed orage_persistent_alarms.txt not found messages (MR !35) - Fixed after wakeup tray icon updating (Issue #14) - Changed alarm_structure to reference counted structure. This fixes warnings about memory leaks (MR !38, replaces MR !8) - Changed libnotify minimum version to 0.7.0 (MR !39) - Disabled sound alarm when sound command is not set (MR !40) - Fixed large ical file import (Issue #8) - Translation Updates: Albanian, Amharic, Arabic, Armenian (Armenia), Asturian, Basque, Belarusian, Bulgarian, Catalan, Chinese (China), Chinese (Taiwan), Croatian, Czech, Danish, Dutch, English (Australia), English (United Kingdom), Esperanto, Estonian, Finnish, French, Galician, German, Greek, Hebrew, Hungarian, Icelandic, Indonesian, Italian, Japanese, Kazakh, Korean, Latvian, Lithuanian, Malay, Norwegian Bokml, Norwegian Nynorsk, Occitan (post 1500), Polish, Portuguese, Portuguese (Brazil), Romanian, Russian, Serbian, Slovak, Spanish, Swedish, Thai, Turkish, Ukrainian, Urdu, Urdu (Pakistan), Uyghur, Vietnamese
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Mar 5, 2023
2.1.0 (2023-03-03) What's Changed * Add support for custom RateLimit headers. by @brookemckim in #13 * Fixes retry_block example in README. by @justinlittman in #12 * README: update link to the RateLimit RFC by @olleolleolle in #14 * docs: update link to RFC by @olleolleolle in #15 * Rubocop linting by @olleolleolle in #16 * style: disable Metrics/ClassLength by @olleolleolle in #17 * Adds Ruby 3.2 to the CI matrix by @petergoldstein in #18 * Typo fix :) by @adifsgaid in #19 * Introduce issue templates by @iMacTia in #22 New Contributors * @justinlittman made their first contribution in #12 * @brookemckim made their first contribution in #13 * @petergoldstein made their first contribution in #18 * @adifsgaid made their first contribution in #19
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Apr 3, 2023
What's Changed - Support environment variables BKT_TTL, BKT_SCOPE, and BKT_CACHE_DIR as alternatives for flags --ttl, --scope, and --cache-dir, respectively (#15) - Added support for keying the cache off one or more files' last-modified time via the --modtime flag (#10). - --discard_failures is included in the cache key, meaning bkt -- foo and bkt --discard_failures -- foo will be cached separately. - Added CI test coverage of feature="debug" behavior. - Fixed flaky tests that relied unnecessarily on how file modtimes change (#14) API Changes - Bkt::discard_failures() is now set on CommandDesc, and affects the cache key. - Added a CommandState type, making CommandDesc safe to persist and pass around. Environment details like the working directory and environment variables are captured when the CommandState instance is constructed. - Bkt::retrieve and Bkt::refresh now return more metadata about the cache state (e.g. whether there was a cache hit or miss). - Upgraded to Clap v4 (#25).
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Apr 25, 2023
Release 2.3.0 Added Add no_color and force_color parameters to override env vars (#38) @hugovk Add support for Python 3.12 (#37) @hugovk Changed Publish to PyPI with a Trusted Publisher (#45) @hugovk Release 2.2.0 Added Add light shades, dark grey and black (#32) @hugovk Release 2.1.1 Fixed Add __main__ to re-enable demo via python -m termcolor (#27) @hugovk Release 2.1.0 Added Support FORCE_COLOR and detect tty (#25) @hugovk Deprecated Deprecate __ALL__, use __all__ instead (#23) @hugovk Release 2.0.1 Fixed Update source URL (#21) @felixonmars Release 2.0.0 Added Add support for Python 3.11 and PyPy (#9) @hugovk Add support for Python 3.10 (#5) @hugovk Support NO_COLOR (#7) @hugovk Add type annotations to the project and run mypy on CI (#11) @jdufresne Add tests (#1) @hugovk Changed Refer to GitHub Releases for release notes for 2.0.0+ (#20) @hugovk Autodeploy to TestPyPI and to PyPI for GH releases (#19) @hugovk Migrate from setuptools + setuptools_scm to hatchling + hatch-vcs (#17) @hugovk Replace deprecated license_file with license_files in setup.cfg (#14) @jdufresne Use declarative metadata in setup.cfg (#10) @hugovk Replace 3.9-dev with 3.9 in CI to use Python 3.9 final (#3) @CozyDoomer Removed Drop support for EOL Python <= 3.6 (#9) @hugovk Remove hardcoded VERSION constant (#18) @hugovk Fixed Fix docstring for colored function (#15) @tmetzl Fix typo: ANSII -> ANSI (#8) @hugovk
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jun 12, 2023
What's Changed - Add NetBSD by @0323pin in #3 - Migrate from tui-rs to ratatui by @AmmarAbouZor in #4 - settings improvements by @AmmarAbouZor in #13 - [Documentation] Create README Badges by @kevinmatthes in #14 - CI Improvements by @AmmarAbouZor in #15 - Changed: Help popup improvements by @AmmarAbouZor in #17 - Added: Export current journal's content by @AmmarAbouZor in #18 - Increase Version by @AmmarAbouZor in #19 - Fixed setting backend path from CLI by @AmmarAbouZor in #22 - Added: Release CD action by @AmmarAbouZor in #24 - Fixed: Export journal extension by @AmmarAbouZor in #25 - Changed: Enhance render loop by @AmmarAbouZor in #28 - Added: CITATION.cff by @kevinmatthes in #26 - Added: Edit current journal content in external editor by @AmmarAbouZor in #29 - Added: configure CHANGELOG maintenance utilities by @kevinmatthes in #16 - Added: Tabs and scrolling to help popup by @AmmarAbouZor in #32 - Fixed: bugs in fragment creation by @kevinmatthes in #33 - Added: Multi-selection for journals by @AmmarAbouZor in #34 - Changed: bump baptiste0928/cargo-install to v2.1.0 by @kevinmatthes in #36 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #37 - Added: Export Import functions for multiple journals by @AmmarAbouZor in #39 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #40 - Fixed: Synchronizing problems with sqlite back-end by @AmmarAbouZor in #41 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #42 - Changed: improve GHA linting speed dramatically by @kevinmatthes in #43 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #44 - Addd: Option to Use Git Configured Editor as External editor by @AmmarAbouZor in #45 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #46 - [Aeruginous] Create Missing CHANGELOG Fragments by @AmmarAbouZor in #48 - Chore: Add dependabot by @AmmarAbouZor in #50 - [Aeruginous] Assemble CHANGELOG by @github-actions in #52
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jul 16, 2023
v0.8.0 Features: - garden now supports a grafts feature that allows you to stitch configuration entities from separate garden files into a graft-specific namespace. Trees and variables from grafted configurations can be referenced using graft:: namespace qualifiers. - garden grow can now configure upstream branches. - garden grow can now configure gitconfig settings with multiple values using git config --add <name> <value>. v0.7.0 Features: - Trees, Groups, Gardens and Commands defined in the top-level garden.yaml can now override entries defined via garden.includes. Configuration entities now follow "last one wins" semantics -- if the same entity is defined in multiple includes files then only the final definition will be used. (#14) (#15) - Trees now sparsely override existing entries. This behavior allows a tree definition to replace just the url field, or to replace individual tree commands while retaining the rest. Use replace: true in a Tree definition in order to completely replace the existing entry instead of sparsely overridding it. - Improved shell completions for garden, garden init and garden plant. Packaging - 0323pin packaged garden for pkgsrc/NetBSD and merged the package into the main branch! (#13)
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jul 23, 2023
pkgsrc change: update HOMEPAGE. 1.14.0 (2023-07-18) What's Changed * Prefer GitHub Actions for CI. by @ioquatix in #2 * Prefer lower case headers. by @ioquatix in #3 * Documentation updates by @HeroProtagonist in #7 * Update doc generation and deploy to github pages by @HeroProtagonist in #8 * Fix gh pages workflow by @HeroProtagonist in #9 * Adds Ruby 3.2 to the CI matrix by @petergoldstein in #12 * test: Add explicit 'timeout' require by @thesamesam in #14 * Refer to github not rubyforge in docs [ci skip] by @olleolleolle in #15 * Prefer Rack::Headers for Rack 3. by @ioquatix in #4 * Remove unnecessary duplicate lines by @monfresh in #10 New Contributors * @ioquatix made their first contribution in #2 * @HeroProtagonist made their first contribution in #7 * @petergoldstein made their first contribution in #12 * @thesamesam made their first contribution in #14 * @olleolleolle made their first contribution in #15 * @monfresh made their first contribution in #10
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Oct 10, 2023
v0.1.10 What's Changed - Added -o (print once) flag, fix Cargo.toml categories flag by @Kyllingene in #18 v0.1.9 What's Changed - Use u8::wrapping_* instead of *_u8, add gitignore by @Kyllingene in #15 - 12-hour clock modes by @Kyllingene in #16 v0.1.8 - no release
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Dec 17, 2023
1.13 2022-10-11 - In singleton(), do a check whether class was sent in. There was a shifting issue if called with IPC::Shareable::singleton() as opposed to IPC::Shareable->singleton() - When an exclusive collision occurs and both 'graceful' and 'warn' are set, the warning thrown now includes the segment/semaphore key in use. This makes it easier to clean things up with 'ipcrm' 1.12 2022-03-13 - Add tests in t/07-new.t to test how using tied() against a dereferenced variable returned from new() allows access to the underlying IPC::Shareable object - Reworked how spawn() and unspawn() manage things internally - POD updates, fixes and clarifications - Removed spawn() and unspawn(). There's really no need for these as one can simply create but not destroy 1.11 2022-03-07 - Fix certain tests so they don't throw if we bail early 1.10 2022-03-07 - Fix issue where if segments were created underneath of a parent by an external process other than the process that created the parent, the global register wasn't being updated, therefore those segments weren't being removed when calling clean_up_all() - All test files now check number of segments before and after the entire script has run, verifying that all segments were cleaned up ok - The test suite itself in its entirety makes sure that all segments created during the suite run are cleaned up properly - Added CI_TESTING=1 to coverage CI tests 1.09 2022-03-06 - Made 81-fork_dup_rand_keys.t developer only (but still need to figure out why it only fails on FreeBSD) 1.08 2022-03-04 - Added 'protected' option and clean_up_protected(). If set, the cleanup methods, nor the automatic 'destroy' functionality will remove the segment the option was set in, nor any children created underneath of it. A call to clean_up_protected() is required to remove them - Updated attribute tests to include all available options - _shm_key_rand() now checks EXCLUSIVE_CHECK_LIMIT times to find a key for a free segment. It croaks if not - Added _shm_key_rand_int() so we can mock it to test the dup random key checks - Added build prereq of Mock::Sub to test the random key function 1.07 2022-03-04 - When running in forked environments, _shm_key_rand() was consistently returning the same 'random' key to each forked process. We've fixed this issue, and added tests for it (fixed by adding a call to srand() before rand) - Move $SIG{CHLD} handlers to spawn() and unspawn() instead of having them global (fixes #15) - t/65-seg_size.t fails on 32-bit perls; Add a check and bail if we're on a perl < 64-bit (fixes #14)
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Dec 18, 2023
1.35 2023-11-05 - massive speed up, esp. for scripts using stuff from the Moose ecosystem, thanks to @shawnlaffan: - add package level caches for INC searches (_find_in_inc, _glob_in_inc) - faster add_deps on case insensitive systems AKA Windows 1.34 2023-09-24 - Fix issue #19 (AKA rschupp/PAR-Packer#78): invalid paths in zip file - Restore behaviour from version 1.31 when using "pp --execute ..." or "scandeps.pl --execute ...". When using "scan_deps(execute => 1, ...)", %INC as gleaned from running the script must be sanitized. Contrary to documentation "The key is the filename you specified (with module names converted to pathnames)" %INC *may* contain keys that are *absolute pathnames* (or start with "./relativ/path" when "relative/path" is in @path). Examples are autosplitted modules (for autosplit.ix and *.al files). pp will pack these absolute paths into the zip (Archive::Zip doesn't complain) which results in strange error messages when the packed executable tries to unpack them under CACHEDIR/inc on Windows. Add t/19-autosplit.t to test for this. Add IPC::Run3 to TEST_REQUIRES, used in t/19-autosplit.t - Add GitHub CI 1.33 2023-08-04 - Recognize Moose/Moo/Mouse style inheritance ("extends") or composition ("with") statements. - Add %Preload entries for known dependants of XS::Parse::Keyword. Note: XS::Parse::Keyword is loaded from XS code, grep.metacpan.org for calls of boot_xs_parse_keyword() in *.xs files. 1.32 2023-07-05 - Ensure $inc gets removed from the start of $File::Find::name On Windows, if $inc contains backslashes then it won't always get removed from the start of $File::Find::name because the latter may be canonicalized to only contain forward slashes. - Provide dedicated test scripts for some tests instead of using the test scripts themselves: Test::More draws in all kinds of stuff, totally unpredictable - Rewrite test helpers in t/Utils.pm to use Test::More's subtest feature - Code cleanup; fix detection of 'do STRING' (cf PR #15) - scandeps.pl: sort items in "used by" column - Handle spaces after quote operator, e.g. eval qq {Some::Module} - Fixes #12: share dir not returned when require module is in an eval - Recognize constructs like "eval qq{require Inline::C}". - Recognize idioms like "if (eval { require Foo }) { ..." - Add %preload rules for some Mojo resource files Fixes rschupp/PAR-Packer#44 - Bump perl dependency to guard against ancient perls without FindBin::again() - Add tool to trace when (and from where) Perl searches for a module
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Feb 7, 2024
2.50.2 (stable): * Fontset: Use callback functions with C linkage (Kjell Ahlstedt) Issue glibmm#1 (Murray Cumming) * Coverage: Don't use deprecated pango_coverage_ref/unref() (Kjell Ahlstedt) Documentation: * Doxyfile.in: Don't hide undocumented classes (Kjell Ahlstedt) * README.win32: Convert to MarkDown and rename to README.win32.md Make dependencies clearer (Chun-wei Fan) * Remove AUTHORS, HACKING, README.SUN; add general info to README.md (Kjell Ahlstedt) Issue gtkmm#140 Meson build: * Detect if we build from a git subtree (William Roy) Merge request gtkmm!72 * Don't copy files with configure_file() (Kjell Ahlstedt) * Fix the evaluation of is_git_build on Windows (Kjell Ahlstedt) Issue gtkmm#131 (William Roy) * Don't fail if warning_level=everything (Daniel Boles, Kjell Ahlstedt) Merge request gtkmm!87 2.50.1 (stable): * Context::get_font_map(): Fix reference count (Kjell Ahlstedt) Build: * Meson build: Specify 'check' option in run_command() Will be necessary with future versions of Meson. Require Meson >= 0.55.0 * Meson build: Check if Perl is required for building documentation * Meson build: Avoid unnecessary configuration warnings (Kjell Ahlstedt) * Meson build: Re-organize warning-related compiler flags for MSVC (Chun-wei Fan) 2.50.0 (stable): * AttrList: Add get_attributes(), update(), equal() (Kjell Ahlstedt) Issue #12 (misos1) * Make CairoFontMap::set_resolution() usable by adding the CairoFontMapImpl class (Kjell Ahlstedt) Issue #15 (Ievgenii Meshcheriakov) * Add FontMap::get_family() (Kjell Ahlstedt) * AttrList: Add to_string() and from_string() Attribute: Add TextTransform, BaselineShift and FontScle enums and some create_attr_*() methods (Kjell Ahlstedt) Build: * Don't include individual pango headers (Matthias Clasen, Kjell Ahlstedt) Merge request !22 * Support Visual Studio 2022 builds (Chun-wei Fan) * Require pango >= 1.49.4 (Kjell Ahlstedt) 2.49.1 (unstable) * Layout, LayoutIter: Add get_const_line() and get_const_lines() (Kjell Ahlstedt) Issue #10 (misos1) * GlyphItem: Make most methods public (Kjell Ahlstedt) Issue #11 (Josh Bialkowski)
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Apr 3, 2024
This release fixes a failure to build with the upcoming gcc 14, cleans up several other compiler warnings, fixes a bug in the generation of the xdm.service file for systemd, and removes a lot of dead code checks for platforms & features that have not been supported since the conversion from Imake to autoconf in 2005. Alan Coopersmith (26): gitlab CI: stop requiring Signed-off-by in commits Remove "All rights reserved" from Oracle copyright notices gitlab CI: Update to latest CI templates & Debian stable release configure: Use LT_INIT from libtool 2 instead of deprecated AC_PROG_LIBTOOL Fix -Wincompatible-pointer-types warning from gcc (issue #15) greeter: Handle const qualification differences between Solaris & Linux PAM greeter: Constify value argument to SetValue() unifdef ultrix unifdef sony unifdef PowerMAX_OS unifdef __convex__ unifdef hpux unifdef pegasus unifdef __UNIXOS2__ unifdef QNX4 unifdef AF_CHAOS unifdef AF_DECnet unifdef SYSV unifdef SIGNALS_RESET_WHEN_CAUGHT unifdef UNRELIABLE_SIGNALS unifdef FRAGILE_DEV_MEM Remove support for SVR4 systems other than Solaris/illumos include <shadow.h> on all platforms with HAVE_GETSPNAM set, not just SVR4 unifdef __osf__ session.c: clear -Wredundant-decls warnings on Solaris xdm 1.1.15 Alisson Bruno (1): Fix --with-systemd-daemon option
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jun 27, 2024
Upstream changes: 0.28 2024-06-20T08:17:27Z - Same code as 0.27 - republishing to force CPAN reindexing 0.27 2024-01-09T06:19:12Z - don't have the parser string blanks by default #15 tokuhirom/HTML-TreeBuilder-LibXML#15 - fallback to toString() when toStringC14N(1) gives an empty string #17 tokuhirom/HTML-TreeBuilder-LibXML#17
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Aug 13, 2024
Upstream changes: 3.79 2024-06-01 sbeck - NEW CODE(s) 3.78 2024-03-01 sbeck - NEW CODE(s) 3.77 2023-12-01 sbeck - NEW CODE(s) - Changed RELEASE_TESTING variable Now use a release-specific testing variable rather than RELEASE_TESTING. See GitHub #17 for details. 3.76 2023-09-05 sbeck - Fixed problem in distro Accidentally created a distribution (3.75) that is broken. GitHub #18 3.75 2023-09-01 sbeck - NEW CODE(s) 3.74 2023-06-07 sbeck - NEW CODE(s) 3.73 2023-03-06 sbeck - NEW CODE(s) - Fixed a problem with test failing on windows Reported in GitHub #15 3.72 2022-09-01 sbeck - NEW CODE(s) 3.71 2022-06-01 sbeck - NEW CODE(s) 3.70 2022-03-02 sbeck - NEW CODE(s)
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Aug 13, 2024
Upstream changes: 1.601 2024-07-27T00:58:50Z * changed default DTD header to use "Apple" instead of "Apple Computer" to match what XCode has been doing (Apple changed it's name in 2007). (GitHub #27). 1.505 2024-07-14T17:52:31Z * Don't read binary files in text mode, which has problems on Windows (from joz-k, GitHub #26) * Fix problem with negative integers in WriteBinary. They should always be longs. * First release to use GitHub Attestations (see README.pod) 1.504 2022-07-08T03:16:18Z * @trwyant fixed some stray debugging output (#14 and #15) 1.503 2022-06-30T18:16:29Z * Darren Kulp noted an XML error in one of the test strings (GitHub #12) * No other code changes
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Oct 7, 2024
1.15 -- Wed Oct 02 07:45:07 ADT 2024 [Module Status] Crypt::OpenPGP has a new maintainer. Current work is to merge past PRs that are fairly simple to review and test. Other issues will be reviewed as time permits. [Changes since 1.12] - Release of TRIAL 1.14 as production - PR #15 - (@nielslaukens) Added UserAttribute class (unparsed) - PR #16 - (@nielslaukens) Bugfix: allow multiple 'Preferred hash/compression algorithms' - PR #17 - (@nielslaukens) Added UserAttribute class (unparsed) - PR #18 - (@nielslaukens) Bugfix: parse notation data subpacket of Signature correctly - PR #19 - (@nielslaukens) Support unknown algos - Closed RT#53323: Failing on 64bit machines - Fix RT#123452 Require at least one Random Source - GH PR#29 (@andyjack) Add use strict to increase kwalitee - GH PR#31 (@gozer) ElGamal: key's p can be a large integer, use Bigint - GH PR#32 (@Shildus). Add support for SHA-2 (SHA-512, SHA-256,...) signatures verification [Detailed Changelog] - d23dc25 Fix the version regex in dist.ini - 4acfd00 Add to .gitignore - 2a6c65a Add note on Random Number Module requirements - 46fbd15 Add back the number of tests - 7ef4fda Added SubSignature with notation to test suite - 451bd6e Added support for unknown key algorithms - 548bb07 Added ECC public key to test suite - 6e0c442 Use done testing instead of a test plan - ac14115 Bugfix: parse notation data subpacket of Signature correctly - ffa9e30 Added support for unparsed SubPackets - 66897ea Added SubSignature packet to test suite - a72137e Bugfix: allow multiple 'Preferred hash/compression algorithms' - 50f9a30 Added UserAttribute class (unparsed) - 26632de Added User Attribute test packet to test suite - 9e7d578 Added test to run packets through a parse/save cycle - 0727bbe RT#123452 Require at least one Random Source - a30bc95 Closed RT#53323: Failing on 64bit machines - 67c4ee9 Fix Bignum subtraction - 8c21506 v1.13 - 04010a5 (tag: 1.13) Add some additional Dist::Zilla configuration - 51ae276 Whitespace and alignment changes - 17ad689 Add use strict to increase kwalitee - 4221098 ElGamal: key's p can be a large integer, use Bigint - f3f20a0 Add support for SHA-2 (SHA-512, SHA-256,...) signatures verification. 1.14 -- Tue Oct 01 18:53:32 ADT 2024 [Module Status] Crypt::OpenPGP has a new maintainer. Current work is to merge past PRs that are fairly simple to review and test. Other issues will be reviewed as time permits. @nielslaukens provided a number of PRs at https://github.com/btrott/Crypt-OpenPGP/pulls - PR #15 - Added UserAttribute class (unparsed) - PR #16 - Bugfix: allow multiple 'Preferred hash/compression algorithms' - PR #17 - Added UserAttribute class (unparsed) - PR #18 - Bugfix: parse notation data subpacket of Signature correctly - PR #19 - Support unknown algos - Closed RT#53323: Failing on 64bit machines - Fix RT#123452 Require at least one Random Source [Detailed Changelog] - d23dc25 Fix the version regex in dist.ini - 4acfd00 Add to .gitignore - 2a6c65a Add note on Random Number Module requirements - 46fbd15 Add back the number of tests - 7ef4fda Added SubSignature with notation to test suite - 451bd6e Added support for unknown key algorithms - 548bb07 Added ECC public key to test suite - 6e0c442 Use done testing instead of a test plan - ac14115 Bugfix: parse notation data subpacket of Signature correctly - ffa9e30 Added support for unparsed SubPackets - 66897ea Added SubSignature packet to test suite - a72137e Bugfix: allow multiple 'Preferred hash/compression algorithms' - 50f9a30 Added UserAttribute class (unparsed) - 26632de Added User Attribute test packet to test suite - 9e7d578 Added test to run packets through a parse/save cycle - 0727bbe RT#123452 Require at least one Random Source - a30bc95 Closed RT#53323: Failing on 64bit machines - 67c4ee9 Fix Bignum subtraction 1.13 -- Sun Sep 29 23:13:17 ADT 2024 [Module Status] Crypt::OpenPGP has a new maintainer. Current work is to merge past PRs that are fairly simple to review and test. Other issues will be reviewed as time permits. - GH PR#29 Add use strict to increase kwalitee - GH PR#31 ElGamal: key's p can be a large integer, use Bigint - GH PR#32 Add support for SHA-2 (SHA-512, SHA-256,...) signatures verification.
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Oct 18, 2024
# debugme 1.2.0 * debugme now does not instrumented code multiple times, this could happen if environments were referenced from multiple places (#15). * debugme now correctly instruments functions with attributes, the attributes are kept now. Some packages, e.g. `assertthat` create such functions. * debugme now supports debug levels. Relatedly, `debugme()` has a `level` argument now (#49, @krlmlr). * debugme now correctly instruments functions with `NULL` body and functions with no arguments. * Nested calls are printed better now, with indentation (#44, @krlmlr). * `debugme()` now re-reads the `DEBUGME` environment variable (#45, @krlmlr). * New `DEBUGME_SHOW_TIMESTAMP` environment variable to hide timestamp output for reproducibility (#49, @krlmlr). * debugme now does not change the random seed (#50).
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Nov 24, 2024
Upstream changes: 3.32 2024-08-17 - Fix small typo in documentation (github #18, thanks Damyan Ivanov) - Capitalize Apache in POD (thanks Ed Sabol) - Fix warning due to quoted version in import under Perl 5.40 3.31 2022-01-05 - Fix uninitialized variable warning if "Satisfy" was not set (github #15, thanks yewtc)
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Nov 28, 2024
v0.2.9 What's Changed Migrate to cargo workspaces and introduce github workflows by @triyanox in #14 feat: add directory indicator #11 by @triyanox in #15 chore: fix release workflow by @triyanox in #16 Merge pull request #16 from triyanox/chore/fix-release-workflow by @triyanox in #17 fix release workflow by @triyanox in #18 Merge pull request #18 from triyanox/chore/fix-release-workflow by @triyanox in #19 fix release workflow by @triyanox in #20 Merge pull request #20 from triyanox/chore/fix-release-workflow by @triyanox in #21 Fix release workflow by @triyanox in #22 chore: version crates by @triyanox in #23 chore: fix the syncing issue on the release workflow by @triyanox in #24 chore: fix version check by @triyanox in #25 chore: add explicit version for lla_plugin_interface by @triyanox in #26 chore: fix path for lla_plugin_interface by @triyanox in #27 v0.2.7 What's Changed Add the config --set command to update the lla config by @triyanox in #13
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Dec 10, 2024
1.6-2 (2023-11-28) o Minor bugfixes: invalid format specified in UBiDi error string, incorrect font name passed if the font family name is too long. o Update Windows build to use pkg-config (Thanks to Tomáš Kalibera!) (#43) 1.6-1 (2023-08-17) o The following additional arguments can be used to set PDF metadata: title, author, subject, creator, keywords, create.date and modify.date if cairo version 1.16 or higher is used. (#15) o The `version` argument for PDF back-end is now honored and defaults to 1.4. Note that currently cairo library only supports PDF target versions 1.4 or 1.5. o The xlib back-end no longer requires headers from Xt. (#39)
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Dec 10, 2024
2024-11-24 Slaven Rezic <[email protected]> Release 1.45 Stable release with all changes in 1.44_50..1.44_51 2024-11-23 Slaven Rezic <[email protected]> Release 1.44_51 Added t/ppm_error.t test. 2024-11-20 Slaven Rezic <[email protected]> Release 1.44_50 Stop propagating error on thumbnail image to main image (PR #15, by nanto) Parse SRATIONAL values appropriately (PR #14, by nanto) Replace "use vars" with "our" (PR #13, by JRaspass) Smaller CI improvements.
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jan 12, 2025
… passed 1.2 - jwt_encode_sig() now allows to override the typ field via headers #15 - jwt_decode functions now check the 'exp' and 'nbf' fields and raise and error if token has expired.
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jan 27, 2025
### 1.9.27 - 12 January 2025 * *fix:* turn off IPC support if _sys/shm.h_ is not available, for compilation on Termux * *fix:* bypass valgrind checks on ARM by default due to false positives ### 1.9.25 - 22 December 2024 * *fix:* test failure of **--watchfd** on macOS corrected ([#124](https://codeberg.org/a-j-wood/pv/issues/124)) ### 1.9.24 - 19 December 2024 * *feature:* new **--format** sequences for graphical progress bars - "**%{bar-block}**", "**%{bar-granular}**", and "**%{bar-shaded}**" ([#15](https://codeberg.org/a-j-wood/pv/issues/15)) * *feature:* new **--format** sequence "**%{sgr:colour,...}**" to use ECMA-48 Select Graphic Rendition codes to add colours * *feature:* new **--bar-style** option to change the default bar style ([#15](https://codeberg.org/a-j-wood/pv/issues/15)) * *feature:* allow decimal values such as "1.5G" with "**--size**", "**--rate-limit**", "**--buffer-size**", and "**error-skip-block**" ([#35](https://codeberg.org/a-j-wood/pv/issues/35)) * *cleanup:* improve progress bar granularity on wide displays by internally tracking the transfer percentage as a decimal number * *cleanup:* correct detection of **--remote** usability on GNU Hurd * *cleanup:* reduce likelihood of race conditions in tests when running on slow systems * *cleanup:* reduce memory footprint * *docs:* simplified the synopsis section of the manual ### 1.9.15 - 8 December 2024 * *feature:* new **--format** sequence "**%nL**", showing the most recent line written ([#121](https://codeberg.org/a-j-wood/pv/issues/121)) * *feature:* each **--format** sequence now has a more readable equivalent name, for example "**%r**" can be written as "**%{rate}**" * *feature:* new **--format** sequences "**%{progress-bar-only}**" and "**%{progress-amount-only}**" * *fix:* allow **--format** to include "%nA" more than once, with different "n" values ([#122](https://codeberg.org/a-j-wood/pv/issues/122)) * *fix:* allow **--format** to include "%p" more than once, with optional width prefix * *fix:* calculate width correctly when wide characters are in **--format** strings * *fix:* add _configure_ script fallback for **--remote** check when cross-compiling ([#120](https://codeberg.org/a-j-wood/pv/issues/120)) * *fix:* allow **extra-display** to be changed by **--remote** ([#123](https://codeberg.org/a-j-wood/pv/issues/123)) * *cleanup:* refactored display formatters into separate functions * *cleanup:* improve format parser handling of dangling or invalid "%" sequences
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Jan 31, 2025
## v0.1.2.9 - 2024-05-18 * Bump base bounds to support ghc 9.10 ([#15](maoe/ghc-trace-events#15))
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Feb 24, 2025
0.6.4 (2024-12-25) ===== - Introduce Darwin support - Update copyright year - build: Bump dependency versions and fix deprecation warnings - I18n: Update po/LINGUAS list - I18n: Update po/LINGUAS list - build: Use XDT_VERSION_INIT and get rid of configure.ac.in - scan-build: Fix deadcode.DeadStores - I18n: Update po/LINGUAS list - build: Get rid of intltool - Remove useless size request (Fixes #15) - Fix plugin icon size - Update copyright year and bug report address - build: Add GLib requirement - Use "logo-icon-name" instead of "logo" in about dialog - OpenBSD: rewrite rate calculation to use IFM_BAUDRATE_DESCRIPTIONS - Default "Wifi Manager Command" to NetWorkManager only on Linux - Limit list of interfaces to IEEE 802.11 on OpenBSD and NetBSD - Limit list of interfaces to Ethernet on BSD - Translation Updates: Albanian, Arabic, Armenian (Armenia), Basque, Belarusian, Bulgarian, Catalan, Chinese (China), Chinese (Taiwan), Croatian, Czech, Danish, Dutch, Eastern Armenian, English (Australia), English (Canada), English (United Kingdom), Estonian, Finnish, French, Galician, German, Greek, Hebrew, Hungarian, Icelandic, Indonesian, Interlingue, Irish, Italian, Japanese, Kazakh, Korean, Latvian, Lithuanian, Malay, Norwegian Bokmål, Occitan (post 1500), Polish, Portuguese, Portuguese (Brazil), Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swedish, Thai, Turkish, Ukrainian, Urdu, Urdu (Pakistan), Uyghur
netbsd-srcmastr
pushed a commit
that referenced
this pull request
Mar 30, 2025
## Changes in version 0.14.1 **Released on March 29th, 2025.** * Issue #263: fix release tarball by relying on `make dist`. * Document ATF to Kyua mappings for metadata properties. * Support `require.diskspace` ATF metadata property. * Support backwards compatible `unprivileged_user` metadata property for ease of use dealing with ATF vs Kyua. * Fix building from source by tracking `utils/process/Kyuafile.in` and `engine/execenv/execenv_fwd.hpp` with automake. ## Changes in version 0.14 **Released on December 31st, 2024.** * Replace `--with-atf` with `--enable-atf`. The latter must be specified to enable ATF support and the Kyua tests by proxy. * Require newer versions of ATF (0.21) and Lutok (0.5). This is being done as part of a multi-phase deprecation of pre-C++11 environments. * Vendor the ATF m4 files from the freebsd/atf repo. * Translate `is_exclusive` metadata to its ATF counterpart. * Issue #236: fix accidental test forkbomb in specific user environments with `integration` tests by avoiding infinite recursion calling kyua. * Fix the build on Ubuntu 24.04. - execenv support added. This FreeBSD-specific feature allows tests to be executed in jails. * Issue #169: Remove deprecated `readdir_r` use. * Fix build issue on more recent versions of MacOS. * Fix build issue on IllumOS. * Fix issues with PID reuse in testcases. * Escape characters captured from stderr and stdout in HTML output. * `integration/cmd_report_test:verbose`: fix regular expression used in tests which would break in certain user environments. * Add Cirrus CI support for testing Kyua on FreeBSD. * Remove `UTILS_UNUSED_PARAM` macro. * Fix document rendering with newer versions of doxygen. * Issue #152: explicitly require C++11 language features when compiling Kyua. Remove `std::shared_ptr` compatibility header, `utils/shared_ptr.hpp`. * Fix `igor` and `mandoc -Tlint` reported issues with generated manpages. * Issue #167: fix typos in kyua(1) manpage. ## Changes in version 0.13 **Released on August 26th, 2016.** * Fixed execution of test cases as an unprivileged user, at least under NetBSD 7.0. Kyua-level failures were probably a regression introduced in Kyua 0.12, but the underlying may have existed for much longer: test cases might have previously failed for mysterious reasons when running under an unprivileged user. * Issue #134: Fixed metadata test broken on 32-bit platforms. * Issue #139: Added per-test case start/end timestamps to all reports. * Issue #156: Fixed crashes due to the invalid handling of cleanup routine data and triggered by the reuse of PIDs in long-running Kyua instances. * Issue #159: Fixed TAP parser to ignore case while matching `TODO` and `SKIP` directives, and to also recognize `Skipped`. * Fixed potential crash due to a race condition in the unprogramming of timers to control test deadlines. ## Changes in version 0.12 **Released on November 22nd, 2015.** This is a huge release and marks a major milestone for Kyua as it finally implements a long-standing feature request: the ability to execute test cases in parallel. This is a big deal because test cases are rarely CPU-bound: running them in parallel yields much faster execution times for large test suites, allowing faster iteration of changes during development. As an example: the FreeBSD test suite as of this date contains 3285 test cases. With sequential execution, a full test suite run takes around 12 minutes to complete, whereas on a 4-core machine with a high level of parallelism it takes a little over 1 minute. Implementing parallel execution required rewriting most of Kyua's core and partly explains explains why there has not been a new release for over a year. The current implementation is purely subprocess-based, which works but has some limitations and has resulted in a core that is really complex and difficult to understand. Future versions will investigate the use of threads instead for a simplified programming model and additional parallelization possibilities. * Issue #2: Implemented support to execute test cases in parallel when invoking `kyua test`. Parallel execution is *only* enabled when the new `parallelism` configuration variable is set to a value greater than `1`. The default behavior is still to run tests sequentially because some test suites contain test cases with side-effects that might fail when run in parallel. To resolve this, the new metadata property `is_exclusive` can be set to `true` on a test basis to indicate that the test must be run on its own. * Known regression: Running `kyua debug` on a TAP-based test program does not currently report the output in real time. The output will only be displayed once the test program completes. This is a shortcoming of the new parallel execution engine and will be resolved. * Removed the external C-based testers code in favor of the new built-in implementations. The new approach feels significantly faster than the previous one. * Fixed the handling of relative paths in the `fs.*` functions available in `Kyuafile`s. All paths are now resolved relative to the location of the caller `Kyuafile`. `Kyuafile.top` has been updated with these changes and you should update custom copies of this file with the new version. * Changed temporary directory creation to always grant search permissions on temporary directories. This is to prevent potential problems when running Kyua as root and executing test cases that require dropping privileges (as they may later be unable to use absolute paths that point inside their work directory). * The cleanup of work directories does not longer attempt to deal with mount points. If a test case mounts a file system and forgets to unmount it, the mount point will be left behind. It is now the responsibility of the test case to clean after itself. The reasons for this change are simplicity and clarity: there are many more things that a test case can do that have side-effects on the system and Kyua cannot protect against them all, so it is better to just have the test undo anything it might have done. * Improved `kyua report --verbose` to properly handle environment variables with continuation lines in them, and fixed the integration tests for this command to avoid false negatives. * Changed the configuration file format to accept the definition of unknown variables without declaring them local. The syntax version number remains at 2. This is to allow configuration files for newer Kyua versions to work on older Kyua versions, as there is no reason to forbid this. * Fixed stacktrace gathering with FreeBSD's ancient version of GDB. GDB 6.1.1 (circa 2004) does not have the `-ex` flag so we need to generate a temporary GDB script and feed it to GDB with `-x` instead. * Issue #136: Fixed the XML escaping in the JUnit output so that non-printable characters are properly handled when they appear in the process's stdout or stderr. * Issue #141: Improved reporting of errors triggered by sqlite3. In particular, all error messages are now tagged with their corresponding database filename and, if they are API-level errors, the name of the sqlite3 function that caused them. * Issue #144: Improved documentation on the support for custom properties in the test metadata. * Converted the `INSTALL`, `NEWS`, and `README` distribution documents to Markdown for better formatting online. ## Changes in version 0.11 **Released on October 23rd, 2014.** * Added support to print the details of all test cases (metadata and their output) to `report`. This is via a new `--verbose` flag which replaces the previous `--show-context`. * Added support to specify the amount of physical disk space required by a test case. This is in the form of a new `required_disk_space` metadata property, which can also be provided by ATF test cases as `require.diskspace`. * Assimilated the contents of all the `kyua-*-tester(1)` and `kyua-*-interface(7)` manual pages into more relevant places. In particular, added more details on test program registration and their metadata to `kyuafile(5)`, and added `kyua-test-isolation(7)` describing the isolation features of the test execution. * Assimilated the contents of all auxiliary manual pages, including `kyua-build-root(7)`, `kyua-results-files(7)`, `kyua-test-filters(7)` and `kyua-test-isolation(7)`, into the relevant command-specific manual pages. This is for easier discoverability of relevant information when reading how specific Kyua commands work. * Issue #30: Plumbed through support to query configuration variables from ATF's test case heads. This resolves the confusing situation where test cases could only do this from their body and cleanup routines. * Issue #49: Extended `report` to support test case filters as command-line arguments. Combined with `--verbose`, this allows inspecting the details of a test case failure after execution. * Issue #55: Deprecated support for specifying `test_suite` overrides on a test program basis. This idiom should not be used but support for it remains in place. * Issue #72: Added caching support to the `getcwd(3)` test in configure so that the result can be overriden for cross-compilation purposes. * Issue #83: Changed manual page headings to include a `kyua` prefix in their name. This prevents some possible confusion when displaying, for example, the `kyua-test` manual page with a plain name of `test`. * Issue #84: Started passing test-suite configuration variables to plain and TAP test programs via the environment. The name of the environment variables set this way is prefixed by `TEST_ENV_`, so a configuration variable of the form `test_suites.some_name.allow_unsafe_ops=yes` in `kyua.conf` becomes `TEST_ENV_allow_unsafe_ops=YES` in the environment. * Issues #97 and #116: Fixed the build on Illumos. * Issue #102: Set `TMPDIR` to the test case's work directory when running the test case. If the test case happens to use the `mktemp(3)` family of functions (due to misunderstandings on how Kyua works or due to the reuse of legacy test code), we don't want it to easily escape the automanaged work directory. * Issue #103: Started being more liberal in the parsing of TAP test results by treating the number in `ok` and `not ok` lines as optional. * Issue #105: Started using tmpfs instead of md as a temporary file system for tests in FreeBSD so that we do not leak `md(4)` devices. * Issue #109: Changed the privilege dropping code to start properly dropping group privileges when `unprivileged_user` is set. Also fixes `testers/run_test:fork_wait__unprivileged_group`. * Issue #110: Changed `help` to display version information and clarified the purpose of the `about` command in its documentation. * Issue #111: Fixed crash when defining a test program in a `Kyuafile` that has not yet specified the test suite name. * Issue #114: Improved the `kyuafile(5)` manual page by clarifying the restrictions of the `include()` directive and by adding abundant examples. ## Changes in version 0.10 **Experimental version released on August 14th, 2014.** * Merged `kyua-cli` and `kyua-testers` into a single `kyua` package. * Dropped the `kyua-atf-compat` package. * Issue #100: Do not try to drop privileges to `unprivileged_user` when we are already running as an unprivileged user. Doing so is not possible and thus causes spurious test failures when the current user is not root and the current user and `unprivileged_user` do not match. * Issue #79: Mention `kyua.conf(5)` in the *See also* section of `kyua(1)`. * Issue #75: Change the `rewrite__expected_signal__bad_arg` test in `testers/atf_result_test` to use a different signal value. This is to prevent triggering a core dump that made the test fail in some platforms. ## Changes in kyua-cli version 0.9 **Experimental version released on August 8th, 2014.** Major changes: The internal architecture of Kyua to record the results of test suite runs has completely changed in this release. Kyua no longer stores all the different test suite run results as different "actions" within the single `store.db` database. Instead, Kyua now generates a separate results file inside `~/.kyua/store/` for every test suite run. Due to the complexity involved in the migration process and the little need for it, this is probably going to be the only release where the `db-migrate` command is able to convert an old `store.db` file to the new scheme. Changes in more detail: * Added the `report-junit` command to generate JUnit XML result files. The output has been verified to work within Jenkins. * Switched to results files specific to their corresponding test suite run. The unified `store.db` file is now gone: `kyua test` creates a new results file for every invocation under `~/.kyua/store/` and the `kyua report*` commands are able to locate the latest file for a corresponding test suite automatically. * The `db-migrate` command takes an old `store.db` file and generates one results file for every previously-recorded action, later deleting the `store.db` file. * The `--action` flag has been removed from all commands that accepted it. This has been superseded by the tests results files. * The `--store` flag that many commands took has been renamed to `--results-file` in line with the semantical changes. * The `db-exec` command no longer creates an empty database when none is found. This command is now intended to run only over existing files. ## Changes in kyua-testers version 0.3 **Experimental version released on August 8th, 2014.** * Made the testers set a "sanitized" value for the `HOME` environment variable where, for example, consecutive and trailing slashes have been cleared. Mac OS X has a tendency to append a trailing slash to the value of `TMPDIR`, which can cause third-party tests to fail if they compare `${HOME}` with `$(pwd)`. * Issues #85, #86, #90 and #92: Made the TAP parser more complete: mark test cases reported as `TODO` or `SKIP` as passed; handle skip plans; ignore lines that look like `ok` and `not ok` but aren't results; and handle test programs that report a pass but exit with a non-zero code. ## Changes in kyua-cli version 0.8 **Experimental version released on December 7th, 2013.** * Added support for Lutok 0.4. * Issue #24: Plug the bootstrap tests back into the test suite. Fixes in `kyua-testers` 0.2 to isolate test cases into their own sessions should allow these to run fine. * Issue #74: Changed the `kyuafile(5)` parser to automatically discover existing tester interfaces. The various `*_test_program()` functions will now exist (or not) based on tester availability, which simplifies the addition of new testers or the selective installation of them. ## Changes in kyua-testers version 0.2 **Experimental version released on December 7th, 2013.** * Issue #74: Added the `kyua-tap-tester`, a new backend to interact with test programs that comply with the Test Anything Protocol. * Issue #69: Cope with the lack of `AM_PROG_AR` in `configure.ac`, which first appeared in Automake 1.11.2. Fixes a problem in Ubuntu 10.04 LTS, which appears stuck in 1.11.1. * Issue #24: Improve test case isolation by confining the tests to their own session instead of just to their own process group. ## Changes in kyua-cli version 0.7 **Experimental version released on October 18th, 2013.** * Made failures from testers more resilent. If a tester fails, the corresponding test case will be marked as broken instead of causing kyua to exit. * Added the `--results-filter` option to the `report-html` command and set its default value to skip passed results from HTML reports. This is to keep these reports more succint and to avoid generating tons of detail files that will be, in general, useless. * Switched to use Lutok 0.3 to gain compatibility with Lua 5.2. * Issue #69: Cope with the lack of `AM_PROG_AR` in `configure.ac`, which first appeared in Automake 1.11.2. Fixes a problem in Ubuntu 10.04 LTS, which appears stuck in 1.11.1. ## Changes in kyua-cli version 0.6 **Experimental version released on February 22nd, 2013.** * Issue #36: Changed `kyua help` to not fail when the configuration file is bogus. Help should always work. * Issue #37: Simplified the `syntax()` calls in configuration and `Kyuafile` files to only specify the requested version instead of also the format name. The format name is implied by the file being loaded, so there is no use in the caller having to specify it. The version number of these file formats has been bumped to 2. * Issue #39: Added per-test-case metadata values to the HTML reports. * Issue #40: Rewrote the documentation as manual pages and removed the previous GNU Info document. * Issue #47: Started using the independent testers in the `kyua-testers` package to run the test cases. Kyua does not implement the logic to invoke test cases any more, which provides for better modularity, extensibility and robustness. * Issue #57: Added support to specify arbitrary metadata properties for test programs right from the `Kyuafile`. This is to make plain test programs more versatile, by allowing them to specify any of the requirements (allowed architectures, required files, etc.) supported by Kyua. * Reduced automatic screen line wrapping of messages to the `help` command and the output of tables by `db-exec`. Wrapping any other messages (specially anything going to stderr) was very annoying because it prevented natural copy/pasting of text. * Increased the granularity of the error codes returned by `kyua(1)` to denote different error conditions. This avoids the overload of `1` to indicate both "expected" errors from specific subcommands and unexpected errors caused by the internals of the code. The manual now correctly explain how the exit codes behave on a command basis. * Optimized the database schema to make report generation almost instantaneous. * Bumped the database schema to 2. The database now records the metadata of both test programs and test cases generically, without knowledge of their interface. * Added the `db-migrate` command to provide a mechanism to upgrade a database with an old schema to the current schema. * Removed the GDB build-time configuration variable. This is now part of the `kyua-testers` package. * Issue #31: Rewrote the `Kyuafile` parsing code in C++, which results in a much simpler implementation. As a side-effect, this gets rid of the external Lua files required by `kyua`, which in turn make the tool self-contained. * Added caching of various configure test results (particularly in those tests that need to execute a test program) so that cross-compilers can predefine the results of the tests without having to run the executables. ## Changes in kyua-testers version 0.1 **Experimental version released on February 19th, 2013.** This is the first public release of the `kyua-testers` package. The goal of this first release is to adopt all the test case execution code of `kyua-cli` 0.5 and ship it as a collection of independent tester binaries. The `kyua-cli` package will rely on these binaries to run the tests, which provides better modularity and simplicity to the architecture of Kyua. The code in this package is all C as opposed to the current C++ codebase of `kyua-cli`, which means that the overall build times of Kyua are now reduced. ## Changes in kyua-cli version 0.5 **Experimental version released on July 10th, 2012.** * Issue #15: Added automatic stacktrace gathering of crashing test cases. This relies on GDB and is a best-effort operation. * Issue #32: Added the `--build-root` option to the debug, list and test commands. This allows executing test programs from a different directory than where the `Kyuafile` scripts live. See the *Build roots* section in the manual for more details. * Issue #33: Removed the `kyuaify.sh` script. This has been renamed to atf2kyua and moved to the `kyua-atf-compat` module, where it ships as a first-class utility (with a manual page and tests). * Issue #34: Changed the HTML reports to include the stdout and stderr of every test case. * Fixed the build when using a "build directory" and a clean source tree from the repository. ## Changes in kyua-cli version 0.4 **Experimental version released on June 6th, 2012.** * Added the `report-html` command to generate HTML reports of the execution of any recorded action. * Changed the `--output` flag of the `report` command to only take a path to the target file, not its format. Different formats are better supported by implementing different subcommands, as the options they may receive will vary from format to format. * Added a `--with-atf` flag to the configure script to control whether the ATF tests get built or not. May be useful for packaging systems that do not have ATF in them yet. Disabling ATF also cuts down the build time of Kyua significantly, but with the obvious drawbacks. * Grouped `kyua` subcommands by topic both in the output of `help` and in the documentation. In general, the user needs to be aware of commands that rely on a current project and those commands that rely purely on the database to generate reports. * Made `help` print the descriptions of options and commands properly tabulated. * Changed most informational messages to automatically wrap on screen boundaries. * Rewrote the configuration file parsing module for extensibility. This will allow future versions of Kyua to provide additional user-facing options in the configuration file. No syntax changes have been made, so existing configuration files (version 1) will continue to be parsed without problems. There is one little exception though: all variables under the top-level `test_suites` tree must be declared as strings. Similarly, the `-v` and `--variable` flags to the command line must now carry a `test_suites.` prefix when referencing any variables under such tree. ## Changes in kyua-cli version 0.3 **Experimental version released on February 24th, 2012.** * Made the `test` command record the results of the executed test cases into a SQLite database. As a side effect, `test` now supports a `--store` option to indicate where the database lives. * Added the `report` command to generate plain-text reports of the test results stored in the database. The interface of this command is certainly subject to change at this point. * Added the `db-exec` command to directly interact with the store database. * Issue #28: Added support for the `require.memory` test case property introduced in ATF 0.15. * Renamed the user-specific configuration file from `~/.kyuarc` to `~/.kyua/kyua.conf` for consistency with other files stored in the `~/.kyua/` subdirectory. * Switched to use Lutok instead of our own wrappers over the Lua C library. Lutok is just what used to be our own utils::lua module, but is now distributed separately. * Removed the `Atffile`s from the source tree. Kyua is stable enough to generate trustworthy reports, and we do not want to give the impression that atf-run / atf-report are still supported. * Enabled logging to stderr for our own test programs. This makes it slightly easier to debug problems in our own code when we get a failing test. ## Changes in kyua-cli version 0.2 **Experimental version released on August 24th, 2011.** The biggest change in this release is the ability for Kyua to run test programs implemented using different frameworks. What this means is that, now, a Kyua test suite can include not only ATF-based test programs, but also "legacy" (aka plain) test programs that do not use any framework. I.e. if you have tests that are simple programs that exit with 0 on success and 1 on failure, you can plug them in into a Kyua test suite. Other than this, there have been several user-visible changes. The most important are the addition of the new `config` and `debug` subcommands to the `kyua` binary. The former can be used to inspect the runtime configuration of Kyua after parsing, and the latter is useful to interact with failing tests cases in order to get more data about the failure itself. Without further ado, here comes the itemized list of changes: * Generalized the run-time engine to support executing test programs that implement different interfaces. Test programs that use the ATF libraries are just a special case of this. (Issue #18.) * Added support to the engine to run `plain` test programs: i.e. test programs that do not use any framework and report their pass/fail status as an exit code. This is to simplify the integration of legacy test programs into a test suite, and also to demonstrate that the run-time engine is generic enough to support different test interfaces. (Issue #18.) * Added the `debug` subcommand. This command allows end users to tweak the execution of a specific test case and to poke into the behavior of its execution. At the moment, all this command allows is to view the stdout and stderr of the command in real time (which the `test` command currently completely hides). * Added the `config` subcommand. This command allows the end user to inspect the current configuration variables after evaluation, without having to read through configuration files. (Issue #11.) * Removed the `test_suites_var` function from configuration files. This was used to set the value of test-suite-sepecific variables, but it was ugly-looking. It is now possible to use the more natural syntax `test_suites.<test-suite-name>.<variable> = <value>`. (Issue #11.) * Added a mechanism to disable the loading of configuration files altogether. Needed for testing purposes and for scriptability. Available by passing the `--config=none` flag. * Enabled detection of unused parameters and variables in the code and fixed all warnings. (Issue #23.) * Changed the behavior of "developer mode". Compiler warnings are now enabled unconditionally regardless of whether we are in developer mode or not; developer mode is now only used to perform strict warning checks and to enable assertions. Additionally, developer mode is now only automatically enabled when building from the repository, not for formal releases. (Issue #22.) * Fixed many build and portability problems to Debian sid with GCC 4.6.3 and Ubuntu 10.04.1 LTS. (Issues #20, #21, #26.) ## Changes in kyua-cli version 0.1 **Experimental version released on June 23rd, 2011.** This is the first public release of the `kyua-cli` package. The scope of this release is to provide functional replacement for the `atf-run` utility included in the atf package. At this point, `kyua` can reliably run the NetBSD 5.99.53 test suite delivering the same results as `atf-run`. The reporting facilities of this release are quite limited. There is no replacement for `atf-report` yet, and there is no easy way of debugging failing test programs other than running them by hand. These features will mark future milestones and therefore be part of other releases. Be aware that this release has suffered very limited field testing. The test suite for `kyua-cli` is quite comprehensive, but some bugs may be left in any place.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Patricia Trie perl module for fast IP address lookups