devel/ruby-minitest: update to 5.15.0

5.15.0 (2021-12-14)

* 1 major enhancement:

  - assert_throws returns the value returned, if any. (volmer)

* 3 minor enhancements:

  - Added -S <CODES> option to skip reporting of certain types of output

  - Enable Ruby deprecation warnings by default. (casperisfine)

  - Use Etc.nprocessors by default in order to maximize cpu
    usage. (tonytonyjan)

* 6 bug fixes:

  - Close then unlink tempfiles on Windows. (nobu)

  - Fixed #skip_until for windows paths. (MSP-Greg)

  - Fixed a bunch of tests for jruby and windows. (MSP-Greg)

  - Fixed marshalling of specs if they error. (tenderlove, jeremyevans, et
    al)

  - Updated deprecation message for block expectations. (blowmage)

  - Use Kernel.warn directly in expectations in case CUT defines their own
    warn. (firien)

(taca)

doc: Updated databases/ruby-arel-helpers to 2.14.0

(taca)

databases/ruby-arel-helpers: update to 2.14.0

2.14.0 (2021-12-16)

* Add support for Rails 7.

(taca)

textproc/ruby-rails-dom-testing: allow more rails version

Accept more rails version.

(taca)

doc: Added www/ruby-rails70 version 7.0.0

(taca)

www/Makefile: add and enable ruby-rails70

(taca)

www/ruby-rails70: add package version 7.0.0

Ruby on Rails

Rails is a web-application framework that includes everything needed to
create database-backed web applications according to the
Model-View-Controller (MVC) pattern.

This is meta gem package for Ruby on Rails 7.0.

(taca)

doc: Added textproc/ruby-actiontext70 version 7.0.0

(taca)

textproc/Makefile: add and enable ruby-actiontext70

(taca)

textproc/ruby-actiontext70: add package version 7.0.0

(taca)

doc: Added devel/ruby-railties70 version 7.0.0

(taca)

devel/Makefile: add and enable ruby-railties70

(taca)

devel/ruby-railties70: add package version 7.0.0

Railties -- Gluing the Engine to the Rails

Railties is responsible for gluing all frameworks together. Overall, it:

* handles the bootstrapping process for a Rails application;

* manages the +rails+ command line interface;

* and provides the Rails generators core.

This is for Ruby on Rails 7.0.

(taca)

doc: Added www/ruby-actioncable70 version 7.0.0

(taca)

www/Makefile: add and enable ruby-actioncable70

(taca)

www/ruby-actioncable70: add package version 7.0.0

Action Cable - Integrated WebSockets for Rails

Action Cable seamlessly integrates WebSockets with the rest of your Rails
application.  It allows for real-time features to be written in Ruby in the
same style and form as the rest of your Rails application, while still being
performant and scalable.  It's a full-stack offering that provides both a
client-side JavaScript framework and a server-side Ruby framework.  You have
access to your full domain model written with Active Record or your ORM of
choice.

This is for Ruby on Rails 7.0.

(taca)

doc: Added mail/ruby-actionmailbox70 version 7.0.0

(taca)

mail/Makefile: add and enable ruby-actionmailbox70

(taca)

mail/ruby-actionmailbox70: add package version 7.0.0

Action Mailbox

Action Mailbox routes incoming emails to controller-like mailboxes for
processing in Rails.  It ships with ingresses for Mailgun, Mandrill,
Postmark, and SendGrid.  You can also handle inbound mails directly via the
built-in Exim, Postfix, and Qmail ingresses.

The inbound emails are turned into `InboundEmail` records using Active
Record and feature lifecycle tracking, storage of the original email on
cloud storage via Active Storage, and responsible data handling with
on-by-default incineration.

These inbound emails are routed asynchronously using Active Job to one or
several dedicated mailboxes, which are capable of interacting directly with
the rest of your domain model.

This is for Ruby on Rails 7.0.

(taca)

doc: Added mail/ruby-actionmailer70 version 7.0.0

(taca)

mail/Makefile: add and enable ruby-actionmailer70

(taca)

mail/ruby-actionmailer70: add package version 7.0.0

Action Mailer -- Easy email delivery and testing

Action Mailer is a framework for designing email service layers.  These
layers are used to consolidate code for sending out forgotten passwords,
welcome wishes on signup, invoices for billing, and any other use case that
requires a written notification to either a person or another system.

Action Mailer is in essence a wrapper around Action Controller and the Mail
gem.  It provides a way to make emails using templates in the same way that
Action Controller renders views using templates.

Additionally, an Action Mailer class can be used to process incoming email,
such as allowing a blog to accept new posts from an email (which could even
have been sent from a phone).

This is for Ruby on Rails 7.0.

(taca)

doc: Added devel/ruby-activestorage70 version 7.0.0

(taca)

devel/Makefile: add and enable ruby-activestorage70

(taca)

devel/ruby-activestorage70: add package version 7.0.0

Active Storage

Active Storage makes it simple to upload and reference files in cloud
services like [Amazon S3](https://aws.amazon.com/s3/), [Google Cloud
Storage](https://cloud.google.com/storage/docs/), or [Microsoft Azure
Storage](https://azure.microsoft.com/en-us/services/storage/), and attach
those files to Active Records. Supports having one main service and mirrors
in other services for redundancy. It also provides a disk service for
testing or local deployments, but the focus is on cloud storage.

Files can be uploaded from the server to the cloud or directly from the
client to the cloud.

Image files can furthermore be transformed using on-demand variants for
quality, aspect ratio, size, or any other
[MiniMagick](https://github.com/minimagick/minimagick) or
[Vips](https://www.rubydoc.info/gems/ruby-vips/Vips/Image) supported
transformation.

This is for Ruby on Rails 7.0.

(taca)

doc: Added databases/ruby-activerecord70 version 7.0.0

(taca)

databases/Makefile: add and enable ruby-activerecord70

(taca)

databases/ruby-activerecord70: add package version 7.0.0

Active Record -- Object-relational mapping in Rails

Active Record connects classes to relational database tables to establish an
almost zero-configuration persistence layer for applications.  The library
provides a base class that, when subclassed, sets up a mapping between the
new class and an existing table in the database.  In the context of an
application, these classes are commonly referred to as *models*.  Models can
also be connected to other models; this is done by defining *associations*.

Active Record relies heavily on naming in that it uses class and association
names to establish mappings between respective database tables and foreign
key columns.  Although these mappings can be defined explicitly, it's
recommended to follow naming conventions, especially when getting started
with the library.

This is for Ruby on Rails 7.0.

(taca)

doc: Added www/ruby-actionpack70 version 7.0.0

(taca)

www/Makefile: add and enable ruby-actionpack70

(taca)

www/ruby-actionpack70: add package version 7.0.0

Action Pack -- From request to response

Action Pack is a framework for handling and responding to web requests.
It provides mechanisms for *routing* (mapping request URLs to actions),
defining *controllers* that implement actions, and generating responses.
In short, Action Pack provides the controller layer in the MVC paradigm.

It consists of several modules:

* Action Dispatch, which parses information about the web request, handles
  routing as defined by the user, and does advanced processing related to
  HTTP such as MIME-type negotiation, decoding parameters in POST, PATCH,
  or PUT bodies, handling HTTP caching logic, cookies and sessions.

* Action Controller, which provides a base controller class that can be
  subclassed to implement filters and actions to handle requests.
  The result of an action is typically content generated from views.

With the Ruby on Rails framework, users only directly interface with the
Action Controller module.  Necessary Action Dispatch functionality is
activated by default and Action View rendering is implicitly triggered by
Action Controller.  However, these modules are designed to function on their
own and can be used outside of Rails.

This is for Ruby on Rails 7.0.

(taca)

doc: Added www/ruby-actionview70 version 7.0.0

(taca)

www/Makefile: add and enable ruby-actionview70

(taca)

www/ruby-actionview70: add package version 7.0.0

Action View

Action View is a framework for handling view template lookup and rendering,
and provides view helpers that assist when building HTML forms, Atom feeds
and more.  Template formats that Action View handles are ERB (embedded Ruby,
typically used to inline short Ruby snippets inside HTML), and XML Builder.

This is for Ruby on Rails 7.0.

(taca)

doc: Added devel/ruby-activejob70 version 7.0.0

(taca)

devel/Makefile: add and enable ruby-activejob70

(taca)

devel/ruby-activejob70: add package version 7.0.0

Active Job - Make work happen later

Active Job is a framework for declaring jobs and making them run on a
variety of queuing backends.  These jobs can be everything from regularly
scheduled clean-ups, to billing charges, to mailings -- anything that can be
chopped up into small units of work and run in parallel.

It also serves as the backend for Action Mailer's #deliver_later
functionality that makes it easy to turn any mailing into a job for running
later.  That's one of the most common jobs in a modern web application:
sending emails outside the request-response cycle, so the user doesn't have
to wait on it.

The main point is to ensure that all Rails apps will have a job
infrastructure in place, even if it's in the form of an "immediate runner".
We can then have framework features and other gems build on top of that,
without having to worry about API differences between Delayed Job and
Resque.  Picking your queuing backend becomes more of an operational
concern, then.  And you'll be able to switch between them without having to
rewrite your jobs.

This is for Ruby on Rails 7.0.

(taca)

doc: Added devel/ruby-activemodel70 version 7.0.0

(taca)

devel/Makefile: add and enable ruby-activemodel70

(taca)

devel/ruby-activemodel70: add package version 7.0.0

Active Model -- model interfaces for Rails

Active Model provides a known set of interfaces for usage in model classes.
They allow for Action Pack helpers to interact with non-Active Record
models, for example.  Active Model also helps with building custom ORMs for
use outside of the Rails framework.

This is for Ruby on Rails 7.0.

(taca)

doc: Added devel/ruby-activesupport70 version 7.0.0

(taca)

devel/Makefile: add and enable ruby-activesupport70

(taca)

devel/ruby-activesupport70: add package version 7.0.0

Active Support -- Utility classes and Ruby extensions from Rails

Active Support is a collection of utility classes and standard library
extensions that were found useful for the Rails framework.  These additions
reside in this package so they can be loaded as needed in Ruby projects
outside of Rails.

This is for Ruby on Rails 7.0.

(taca)

lang/ruby/rails.mk: add support for Ruby no Rails 7.0

(taca)

doc: Note update of Ruby on Rails 6.1 packages to 6.1.4.4

devel/ruby-activesupport61
devel/ruby-activemodel61
devel/ruby-activejob61
www/ruby-actionview61
www/ruby-actionpack61
databases/ruby-activerecord61
devel/ruby-activestorage61
mail/ruby-actionmailer61
mail/ruby-actionmailbox61
www/ruby-actioncable61
devel/ruby-railties61
textproc/ruby-actiontext61
www/ruby-rails61

(taca)

www/ruby-rails61: update to 6.1.4.4

No change except version.

(taca)

textproc/ruby-actiontext61: update to 6.1.4.4

No change except version.

(taca)

devel/ruby-railties61: update to 6.1.4.4

## Rails 6.1.4.4 (December 15, 2021) ##

*  No changes.

## Rails 6.1.4.3 (December 14, 2021) ##

*  Allow localhost with a port by default in development

    [Fixes: #43864]

(taca)

www/ruby-actioncable61: update to 6.1.4.4

No change except version.

(taca)

mail/ruby-actionmailbox61: update to 6.1.4.4

pkgsrc change: update dependency.

No change except version.

(taca)

mail/ruby-actionmailer61: update to 6.1.4.4

No change except version.

(taca)

devel/ruby-activestorage61: update to 6.1.4.4

pkgsrc change: update comment outed dependency.

No change except version.

(taca)

databases/ruby-activerecord61: update to 6.1.4.4

No change except version.

(taca)

www/ruby-actionpack61: update to 6.1.4.4

## Rails 6.1.4.4 (December 15, 2021) ##

*  Fix issue with host protection not allowing host with port in development.

## Rails 6.1.4.3 (December 14, 2021) ##

*    Fix issue with host protection not allowing localhost in development.

(taca)

www/ruby-actionview61: update to 6.1.4.4

No change except version.

(taca)

devel/ruby-activejob61: update to 6.1.4.4

No change except version.

(taca)

devel/ruby-activemodel61: update to 6.1.4.4

No change except version.

(taca)

devel/ruby-activesupport61: update to 6.1.4.4

No change except version.

(taca)

lang/ruby: start update of Ruby on Rails 6.1 to 6.1.4.4

(taca)

doc: note update of Ruby on Rails 6.0 packages to 6.0.4.4

devel/ruby-activesupport60
devel/ruby-activemodel60
devel/ruby-activejob60
www/ruby-actionview60
www/ruby-actionpack60
databases/ruby-activerecord60
mail/ruby-actionmailer60
mail/ruby-actionmailbox60
www/ruby-actioncable60
devel/ruby-railties60
devel/ruby-activestorage60
textproc/ruby-actiontext60
www/ruby-rails60

(taca)

www/ruby-rails60: update to 6.0.4.4

No change except version.

(taca)

textproc/ruby-actiontext60: update to 6.0.4.4

No change except version.

(taca)

devel/ruby-activestorage60: update to 6.0.4.4

No change except version.

(taca)

devel/ruby-railties60: update to 6.0.4.4

## Rails 6.0.4.4 (December 15, 2021) ##

*  No changes.

## Rails 6.0.4.3 (December 14, 2021) ##

*  Allow localhost with a port by default in development

    [Fixes: #43864]

(taca)

www/ruby-actioncable60: update to 6.0.4.4

No change except version.

(taca)

mail/ruby-actionmailbox60: update to 6.0.4.4

pkgsrc change: correct dependency.

No change except version.

(taca)

mail/ruby-actionmailer60: update to 6.0.4.4

No change except version.

(taca)

databases/ruby-activerecord60: update to 6.0.4.4

No change except version.

(taca)

www/ruby-actionpack60:  update to 6.0.4.4

## Rails 6.0.4.4 (December 15, 2021) ##

*  Fix issue with host protection not allowing host with port in development.

## Rails 6.0.4.3 (December 14, 2021) ##

*  Fix issue with host protection not allowing localhost in development.

(taca)

www/ruby-actionview60:  update to 6.0.4.4

No change except version.

(taca)

devel/ruby-activejob60:  update to 6.0.4.4

No change except version.

(taca)

devel/ruby-activemodel60: update to 6.0.4.4

No change except version.

(taca)

devel/ruby-activesupport60: update to 6.0.4.4

No change except version.

(taca)

lang/ruby: start update of Ruby on Rails 6.0 to 6.0.44

(taca)

doc: Updated lang/php81 to 8.1.1

(taca)

lang/php81: update to 8.1.1

16 Dec 2021, PHP 8.1.1

- IMAP:
  . Fixed bug #81649 (imap_(un)delete accept sequences, not single numbers).
    (cmb)

- PCRE:
  . Update bundled PCRE2 to 10.39. (cmb)
  . Fixed bug #74604 (Out of bounds in php_pcre_replace_impl). (cmb, Dmitry)

- Standard:
  . Fixed bug #81659 (stream_get_contents() may unnecessarily overallocate).
    (cmb)

(taca)

doc: Updated lang/php80 to 8.0.14

(taca)

lang/php80: update to 8.0.14

pkgsrc change: fix indentation in options.mk.

16 Dec 2021, PHP 8.0.14

- Core:
  . Fixed bug #81582 (Stringable not implicitly declared if __toString() came
    from a trait). (Nikita)
  . Fixed bug #81591 (Fatal Error not properly logged in particular cases).
    (Nikita)
  . Fixed bug #81626 (Error on use static:: in __��allStatic() wrapped to
    Closure::fromCallable()). (Nikita)
  . Fixed bug #81631 (::class with dynamic class name may yield wrong line
    number). (Nikita)

- FPM:
  . Fixed bug #81513 (Future possibility for heap overflow in FPM zlog).
    (Jakub Zelenka)

- GD:
  . Fixed bug #71316 (libpng warning from imagecreatefromstring). (cmb)

- IMAP:
  . Fixed bug #81649 (imap_(un)delete accept sequences, not single numbers).
    (cmb)

- OpenSSL:
  . Fixed bug #75725 (./configure: detecting RAND_egd). (Dilyan Palauzov)

- PCRE:
  . Fixed bug #74604 (Out of bounds in php_pcre_replace_impl). (cmb, Dmitry)

- SPL:
  . Fixed bug #81587 (MultipleIterator Segmentation fault w/ SimpleXMLElement
    attached). (Nikita)

- Standard:
  . Fixed bug #81618 (dns_get_record fails on FreeBSD for missing type).
    (fsbruva)
  . Fixed bug #81659 (stream_get_contents() may unnecessarily overallocate).
    (cmb)

(taca)

doc: Updated lang/php74 to 7.4.27

(taca)

lang/php74: update to 7.4.27

16 Dec 2021, PHP 7.4.27

- Core:
  . Fixed bug #81626 (Error on use static:: in __callStatic() wrapped to
    Closure::fromCallable()). (Nikita)

- FPM:
  . Fixed bug #81513 (Future possibility for heap overflow in FPM zlog).
    (Jakub Zelenka)

- GD:
  . Fixed bug #71316 (libpng warning from imagecreatefromstring). (cmb)

- OpenSSL:
  . Fixed bug #75725 (./configure: detecting RAND_egd). (Dilyan Palauzov)

- PCRE:
  . Fixed bug #74604 (Out of bounds in php_pcre_replace_impl). (cmb, Dmitry)

- Standard:
  . Fixed bug #81618 (dns_get_record fails on FreeBSD for missing type).
    (fsbruva)
  . Fixed bug #81659 (stream_get_contents() may unnecessarily overallocate).
    (cmb)

(taca)

Fix libmilter build on older systems that don't have gethostbyname2.

Since this is a build fix for systems where it didn't build before,
no revbump is required.

(jnemeth)

chat/centerim: patch out bogus code

>From momomo@lavabit.com in PR 41423 (years ago)

(dholland)

doc: Updated comms/asterisk19 to 19.1.0

(jnemeth)

Update to Asterisk 19.1.0.

The Asterisk Development Team would like to announce the release
of Asterisk 19.1.0.

The release of Asterisk 19.1.0 resolves several issues reported by
the community and would have not been possible without your
participation.

Thank you!

The following issues are resolved in this release:

New Features made in this release:
-----------------------------------
* ASTERISK-29720 - res_tonedetect: Add call progress tone detection
      (Reported by N A)
* ASTERISK-18069 - [patch] app_queue Add Login Time and Last
      Paused Times to Queue Members
      (Reported by Jamuel Starkey)

Bugs fixed in this release:
-----------------------------------
* ASTERISK-29779 - progdocs: Hidden code sections with syntax errors.
      (Reported by Alexander Traud)
* ASTERISK-29732 - progdocs: Fix grouping for latest Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29771 - Crash occurs when 2 realtime sippeers mysql
      connections are configured and we have a schema warning
      (Reported by Mario Ban)
* ASTERISK-29776 - stir/shaken: Requires GNU designator
      (Reported by Alexander Traud)
* ASTERISK-29773 - progdocs: doxyref.h outdated
      (Reported by Alexander Traud)
* ASTERISK-29765 - xmldoc: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29762 - channels: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29730 - Segfault in __ao2_ref if refdebug = yes
      (Reported by Alexei Gradinari)
* ASTERISK-29748 - bridging: Infinite loop when both Local
      channel halves in same bridge
      (Reported by Joshua C. Colp)
* ASTERISK-29754 - odbc: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29753 - parking: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29756 - res_ari: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29755 - frame: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29751 - channel: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29752 - app: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29750 - stasis: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29749 - res_xmpp: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29742 - addons: Fix for Doxygen.
      (Reported by Alexander Traud)
* ASTERISK-29747 - res_pjsip: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29737 - chan_iax2: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29743 - bridges: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29740 - apps: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29741 - tests: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29736 - bridge_channel: Fix for Doxygen
      (Reported by Alexander Traud)
* ASTERISK-29734 - progdocs: Use Doxygen \example correctly
      (Reported by Alexander Traud)
* ASTERISK-29735 - progdocs: Avoid multiple use of section labels
      (Reported by Alexander Traud)
* ASTERISK-29733 - progdocs: Avoid name with Doxygen \file
      (Reported by Alexander Traud)
* ASTERISK-29744 - app_morsecode: Fix deadlock
      (Reported by N A)
* ASTERISK-29705 - app_read: Fix custom terminator
      functionality regression
      (Reported by N A)
* ASTERISK-29703 - res_pjsip_callerid: Fix OLI parsing
      (Reported by N A)
* ASTERISK-29724 - BuildSystem: In POSIX sh, == in place of = is undefined.
      (Reported by Alexander Traud)
* ASTERISK-29702 - sig_analog: Fix truncated buffer copy
      (Reported by N A)
* ASTERISK-28040 - pbx: "dialplan reload" is removing minus
      symbol from dynamic hints
      (Reported by Daniel Zanutti)
* ASTERISK-29391 - VoiceMail does not cancel recording on
      rerecord hangup
      (Reported by N A)
* ASTERISK-29709 - res_snmp: Not build on recent Debian distributions.
      (Reported by Alexander Traud)
* ASTERISK-29717 - res_config_sqlite: not removed in makeopts.in
      (Reported by Alexander Traud)
* ASTERISK-29710 - stasis: Clang 13 warns about the unused but
      set variable dispatched.
      (Reported by Alexander Traud)
* ASTERISK-29711 - aelparse: GCC 11.2 found two maybe uninitialized
      (Reported by Alexander Traud)
* ASTERISK-29713 - GCC 11.2: two stringop-overread
      (Reported by Alexander Traud)
* ASTERISK-29682 - Squash compiler issues generated by gcc 11
      (Reported by George Joseph)
* ASTERISK-29693 - Using --with-crypto and --with-ssl fails on a recompile
      (Reported by George Joseph)
* ASTERISK-27816 - func_talkdetect's logic is completely broken
      (Reported by Moritz Fain)
* ASTERISK-26497 - make install downloads x86_32 variants of
      external modules on non Intel architectures
      (Reported by Corey Farrell)
* ASTERISK-29691 - stun: Not all users provide a dst to ast_stun_request
      (Reported by Dennis Haney)

Improvements made in this release:
-----------------------------------
* ASTERISK-29777 - documentation: Standardize example syntax
      (Reported by N A)
* ASTERISK-29715 - app_voicemail: Refactor email generation functions
      (Reported by N A)
* ASTERISK-29727 - Add type for JSON stasis message RTCP Report Received/Sent
      (Reported by Boris P. Korzun)
* ASTERISK-29714 - Spelling errors
      (Reported by Josh Soref)
* ASTERISK-29707 - chan_iax2: Allow both key and secret to be
      specified at dial time
      (Reported by N A)
* ASTERISK-29662 - Add mix option to Playback application for
      say and filename
      (Reported by Shloime Rosenblum)

For a full list of changes in this release, please see the ChangeLog:
https://downloads.asterisk.org/pub/telephony/asterisk/ChangeLog-19.1.0

(jnemeth)

doc: Updated x11/xfce4-dashboard to 0.9.2

(gutteridge)

xfce4-dashboard: update to 0.9.2

(No reasonably condensed upstream change log available.)

(gutteridge)

doc: Updated x11/xfce4-clipman-plugin to 1.6.2

(gutteridge)

xfce4-clipman-plugin: update to 1.6.2

Change log:

1.6.2
======
- Add G_GNUC_FALLTHROUGH definition if GLib < 2.60
- Remove obsolete GTK_CHECK_VERSION checks
- Fix function prototypes
- Remove GSourceFunc casts
- Fix compilation warnings
- automake: Enable subdir-objects
- autoconf: Some updates
- Check for `locale.h` required in release mode
- Update `.gitignore`
- Require gtk 3.22.29
- Fix GCC warnings
- Fix return type of grab_keyboard
- Add README.md
- Avoid deprecated warnings with Gdk >= 3.22
- Add basic GitLab pipeline
- Bug #16717: Move from exo-csource to xdt-csource
- Make settings window title translateable (Bug #16625)
- history: Re-enable singleton
- menu: Indicate primary and clipboard content
- menu: Indicate the primary clipboard item
- Speed up shutdown and paste
- Correct location of appstream info
- Fix a couple of grammatical errors
- Translation Updates:
  Albanian, Armenian (Armenia), Basque, Belarusian, Bulgarian, Catalan,
  Chinese (China), Chinese (Taiwan), Croatian, Czech, Danish, Dutch,
  Eastern Armenian, English (Australia), Estonian, Finnish, French,
  Galician, German, Greek, Hebrew, Hungarian, Icelandic, Indonesian,
  Interlingue, Italian, Japanese, Kazakh, Korean, Lithuanian, Malay,
  Norwegian Bokm奪l, Occitan (post 1500), Polish, Portuguese,
  Portuguese (Brazil), Russian, Serbian, Slovak, Slovenian, Spanish,
  Swedish, Thai, Turkish, Ukrainian

(gutteridge)

revbump for libffi

(pho)

doc: Updated sysutils/podman to 3.4.4

(leot)

podman: Update to 3.4.4

Changes:
[Bugfixes, misc and API changes were omitted due taking too much space and
probably not so interesting]

3.4.4
=====
3.4.4 is a bugfixes release.

3.4.3
=====
Security
  * This release addresses CVE-2021-4024, where the podman machine command
    opened the gvproxy API (used to forward ports to podman machine VMs) to the
    public internet on port 7777.
  * This release addresses CVE-2021-41190, where incomplete specification of
    behavior regarding image manifests could lead to inconsistent decoding on
    different clients.

Features
--------
  * The --secret type=mount option to podman create and podman run supports a
    new option, target=, which specifies where in the container the secret will
    be mounted (#12287).

Several misc, bugfixes and API changes.

3.4.2
=====
3.4.2 is a bugfixes release.

3.4.1
=====
3.4.1 is a misc and bugfixes release.

3.4.0
=====
Features
--------
  * Pods now support init containers! Init containers are containers which run
    before the rest of the pod starts. There are two types of init containers:
    "always", which always run before the pod is started, and "once", which
    only run the first time the pod starts and are subsequently removed. They
    can be added using the podman create command's --init-ctr option.
  * Support for init containers has also been added to podman play kube and
    podman generate kube - init containers contained in Kubernetes YAML will be
    created as Podman init containers, and YAML generated by Podman will
    include any init containers created.
  * The podman play kube command now supports building images. If the --build
    option is given and a directory with the name of the specified image exists
    in the current working directory and contains a valid Containerfile or
    Dockerfile, the image will be built and used for the container.
  * The podman play kube command now supports a new option, --down, which
    removes any pods and containers created by the given Kubernetes YAML.
  * The podman generate kube command now generates annotations for SELinux
    mount options on volume (:z and :Z) that are respected by the podman play
    kube command.
  * A new command has been added, podman pod logs, to return logs for all
    containers in a pod at the same time.
  * Two new commands have been added, podman volume export (to export a volume
    to a tar file) and podman volume import) (to populate a volume from a given
    tar file).
  * The podman auto-update command now supports simple rollbacks. If a
    container fails to start after an automatic update, it will be rolled back
    to the previous image and restarted again.
  * Pods now share their user namespace by default, and the podman pod create
    command now supports the --userns option. This allows rootless pods to be
    created with the --userns=keep-id option.
  * The podman pod ps command now supports a new filter with its --filter
    option, until, which returns pods created before a given timestamp.
  * The podman image scp command has been added. This command allows images to
    be transferred between different hosts.
  * The podman stats command supports a new option, --interval, to specify the
    amount of time before the information is refreshed.
  * The podman inspect command now includes ports exposed (but not published)
    by containers (e.g. ports from --expose when --publish-all is not
    specified).
  * The podman inspect command now has a new boolean value, Checkpointed, which
    indicates that a container was stopped as a result of a podman container
    checkpoint operation.
  * Volumes created by podman volume create now support setting quotas when run
    atop XFS. The size and inode options allow the maximum size and maximum
    number of inodes consumed by a volume to be limited.
  * The podman info command now outputs information on what log drivers,
    network drivers, and volume plugins are available for use (#11265).
  * The podman info command now outputs the current log driver in use, and the
    variant and codename of the distribution in use.
  * The parameters of the VM created by podman machine init (amount of disk
    space, memory, CPUs) can now be set in containers.conf.
  * The podman machine ls command now shows additional information (CPUs,
    memory, disk size) about VMs managed by podman machine.
  * The podman ps command now includes healthcheck status in container state
    for containers that have healthchecks (#11527).

Changes
-------
  * The podman build command has a new alias, podman buildx, to improve
    compatibility with Docker. We have already added support for many docker
    buildx flags to podman build and aim to continue to do so.
  * Cases where Podman is run without a user session or a writable temporary
    files directory will now produce better error messages.
  * The default log driver has been changed from file to journald. The file
    driver did not properly support log rotation, so this should lead to a
    better experience. If journald is not available on the system, Podman will
    automatically revert to the file.
  * Podman no longer depends on ip for removing networks (#11403).
  * The deprecated --macvlan flag to podman network create now warns when it is
    used. It will be removed entirely in the Podman 4.0 release.
  * The podman machine start command now prints a message when the VM is
    successfully started.
  * The podman stats command can now be used on containers that are paused.
  * The podman unshare command will now return the exit code of the command
    that was run in the user namespace (assuming the command was successfully
    run).
  * Successful healthchecks will no longer add a healthy line to the system log
    to reduce log spam.
  * As a temporary workaround for a lack of shortname prompts in the Podman
    remote client, VMs created by podman machine now default to only using the
    docker.io registry.

Several misc, bugfixes and API changes.

(leot)

doc: Updated net/unifi to 6.5.55

(gdt)

net/unifi: Update to 6.5.55

Update log4j version to 2.16.0 (CVE-2021-45046).

(gdt)

doc: Updated net/unison2.51 to 2.51.5

(gdt)

net/unison2.51: Update to 2.51.5

Upstream NEWS:

  * Restore OCaml compat to before 4.02
  * dune/opam improvements/fixes
  * Improve GTK UI by using GtkTreeView
  * Add support for syncing symlinks on Windows (NTFS)
  * Improve ssh support on Windows (hide Windows console in GUI mode)
  * Many bugfixes and minor improvements

(gdt)

doc: Updated devel/ruby-redmine42 to 4.2.3nb1

(taca)

devel/ruby-redmine42: improve dependency

Remove dependency to ruby-mini_mime since ruby-mail already has lax
dependency to it.

Bump PKGREVISION.

(taca)

doc: Updated devel/ruby-redmine41 to 4.1.5nb1

(taca)

devel/ruby-redmine41: improve dependency

Remove dependency to ruby-mini_mime since ruby-mail already has lax
dependency to it.

Bump PKGREVISION.

(taca)

Update apache-solr to 8.11.1.

Most notably: contains the log4j 2.16.0 fix.

(jym)

Upgrade apache-solr to 8.11.1.

Please consult the Solr Upgrade notes for details and links specified below:

    https://github.com/apache/solr/blob/main/solr/solr-ref-guide/src/solr-upgrade-notes.adoc

====================================================================

Changelog:

Solr 8.11

See the 8.11 Release Notes for an overview of the main new features of Solr 8.11.

When upgrading to 8.11.x users should be aware of the following major changes from 8.10.

Support for Multiple Authentication Schemes

Two new authentication and authorization plugins provide support for configuring multiple authentication schemes.

The MultiAuthPlugin allows combining two or more authentication approaches, such as JWT and Basic authentication.

The MultiAuthRuleBasedAuthorizationPlugin is used when the MultiAuthPlugin is also in use, and combines the various roles defined for all plugins to determine the proper role assignment for the user account.

For information on configuring these plugins, see the following sections:

    Combining Basic Authentication with Other Schemes

    Multiple Authorization Plugins

ZooKeeper chroot

It窶冱 now possible to create the ZooKeeper chroot at startup if it does not already exist. See the section Using the -z Parameter with bin/solr for an example.

Other Changes

A few other minor changes are worth noting:

    The config-read pre-defined permission now correctly governs access for various configuration-related APIs. See also Predefined Permissions.

    The S3BackupRepository supports configuring the AWS Profile, if necessary. See also S3BackupRepository.

    Additionally, backups will now properly succeed after SPLITSHARD operations, and will correctly handle incremental backup purges.

    SolrJ now supports uploading configsets.

Solr 8.10

See the 8.10 Release Notes for an overview of the main new features of Solr 8.10.

When upgrading to 8.10.x users should be aware of the following major changes from 8.9.

Schema Designer UI

A new screen has been added to the Admin UI that allows you to interactively design a Solr schema using your documents.

The designer screen provides a safe environment for you to:

    Upload or paste sample documents to identify fields.

    Get a "first" guess at what Solr thinks the field types in the fields should be.

    Edit fields, field types, dynamic fields, and supporting files.

    See how a field窶冱 analysis will impact your text.

    Test how schema changes will impact query-time behavior.

    Save your changes to a configset to use with a new collection.

See the section Schema Designer for full details.

Backups in S3

Following the redesign of backups in Solr 8.8 that allowed storage of incremental backups in Google Cloud environments, Solr 8.10 provides support for storing backups in Amazon S3 buckets.

See the section S3BackupRepository for how to configure.

Security Admin UI

Solr窶冱 Admin UI also got a new screen to support management of users, roles, and permissions.

The new UI works when authentication and/or authorization has been enabled with bin/solr auth or by manually installing a security.json file. Before this, it provides a warning that your Solr instance is unsecured.

See the section Security UI for details.

Solr SQL Improvements

A number of improvements have been made in Solr窶冱 SQL functionality:

    Support added for LIKE, IS NOT NULL, IS NULL, and wildcards (for simplistic LIKE functionality).

    Two new aggregation functions, COUNT(DISTINCT field) and APPROX_COUNT_DISTINCT(field), have been added.

    Queries using an ORDER BY clause can support OFFSET and FETCH operations.

    Multi-valued fields can now be returned.

    User permissions have been simplified so access to query endpoints /sql, /select, and /export is sufficient for full access for all SQL queries.

shards.preference

A new option for the shards.preference parameter allows selection of nodes based on whether or not the replica is a leader. Now adding shards.preference=replica.leader:false will limit queries only to replicas which are not currently their shard窶冱 leader.

See the section shards.preference Parameter for details and examples.

Metrics & Prometheus Exporter

A new expr option in the Metrics API allows for more advanced filtering of metrics based on regular expressions. See the section Metrics API for examples.

The Prometheus Exporter窶冱 default solr-exporter.config has been improved to use the new expr option in the Metrics API to get a smaller set of metrics. The default metrics exported still include most metrics, but the configuration will be easier to trim as needed. This should help provide performance improvements in busy clusters being monitored by Prometheus.

ZooKeeper Credentials

ZooKeeper credentials can now be stored in a file whose location is defined with a system property instead of being passed in plain-text. See Out of the Box Credential Implementations for how to set this up.
Solr 8.9

See the 8.9 Release Notes for an overview of the main new features of Solr 8.9.

When upgrading to 8.9.x users should be aware of the following major changes from 8.8.

Backup and Restore

Solr 8.9 introduces extensive changes to Solr窶冱 backup and restore support.

A new backup format has been introduced in Solr 8.9 which replaces the previous snapshot-based backup. This new format enables 窶亙ncremental窶� backups. Repeated backups to a given location will take advantage of the data stored by their predecessors and will only operate on files that have changed since the previous backup. This is supported by default, simply by storing each backup file in the same location.

The old and new formats are not compatible, although backups in the old format, a full snapshot of all files, can still be used to restore to Solr for the time-being. The old format is officially deprecated, and support for it is likely to be removed in Solr 9.0.

For the time-being the old format can be created by defining a parameter incremental=false. Again, though, this support is likely to be removed in Solr 9.0.

More documentation on backups is available at Backup and Restore.

New Collections API commands for backups:

    LISTBACKUP: Lists information about each backup stored at the specified repository location. See List Backups for more details.

    DELETEBACKUP: Deletes specified backups from the repository. See Delete Backups for more details.

A new option for backup repository is also available in 8.9, which is to use Google Cloud Storage (GCS). This is a contrib (located in contrib/gcs-repository). See GCSBackupRepository for configuration details. The Solr community is working to add support for S3 buckets in the near future.

Nested Docs

Child Doc Transformer窶冱 childFilter parameter no longer applies query syntax escaping because it窶冱 inconsistent with the rest of Solr and was limiting. This refers to [child childFilter='field:value']. There was no escaping here prior to 8.0 either.

Collapse and Expand

    BlockCollapse: If documents have been (or could be) indexed in a way where documents with the same collapse key have been indexed contiguously in the index, a new "block collapse" provides a significant speed improvement over traditional collapse.

    See Block Collapsing for details.

    Expand Null Groups: A new parameter expand.nullGroup allows an expanded group to be returned containing document with no value in the expanded field. See Expand Component for details.

In-Place Updates

A new request parameter update.partial.requireInPlace=true allows telling Solr to "fail fast" if all of the necessary conditions are not satisfied to allow an in-place update to succeed. See also In-Place Updates.

Metrics History

The Metrics History feature, which allowed long-term storage and aggregation of Solr窶冱 metrics, has been deprecated and will be removed in 9.0.

Embedded Solr Server

When using EmbeddedSolrServer, it will no longer close CoreContainer instances that were passed to it.
Solr 8.8

When upgrading to 8.8.x users should be aware of the following major changes from 8.7.

Nested Documents

    When doing atomic/partial updates to a child document:

        Supply the _root_ field (the ID of the root document) so that Solr understands you are manipulating a child document and not a root document. In its absence, Solr looks at the _route_ parameter but this may change in the future because it窶冱 not an ideal substitute. If neither are present, Solr assumes you are updating a root document. If this assumption is false, Solr will do a cheap check that usually detects the problem and will throw an exception to alert you of the need to specify the Root ID. This backwards incompatible change was done to increase performance and robustness.

        This feature no longer requires stored=true or docValues=true on the _root_ field. You might have it for other purposes though (e.g., for uniqueBlock(窶ｦ窶�)).

        This feature no longer requires the _nest_path_ field, although you probably ought to continue to define it as it窶冱 useful for other things.

Removed Contribs

    The search results clustering contrib (Carrot2) has been removed from 8.x Solr due to lack of Java 1.8 compatibility in the dependency that provides online clustering of search results. The contrib will be re-introduced in Solr 9.0.

Learning to Rank

    Interleaving support has been added to Learning to Rank (LTR). Currently only the Team Draft Interleaving algorithm is supported. For examples using this feature, see the section Running a Rerank Query Interleaving Two Models.

Metrics

    Two metrics have been added for SolrCloud窶冱 Overseer:

        solr_metrics_overseer_stateUpdateQueueSize

        solr_metrics_overseer_collectionWorkQueueSize

Prometheus Exporter

    The ./bin scripts included with the Prometheus Exporter contrib now allow use of custom java options with environment variables. See the section Environment Variable Options for more details.

    The default Grafana dashboards now include panels for query performance monitoring. The default Prometheus Exporter configuration includes metrics like queries-per-second (QPS) and 95th percentiles (P95) to populate the new panels.

    The default Prometheus Exporter configuration also includes the two new metrics mentioned in the Metrics above.

Solr Home

    The internal logic for identifying 'Solr Home' (solr.solr.home) has been refactored to make testing less error prone. Plugin developers using SolrPaths.locateSolrHome() or 'new `SolrResourceLoader窶� should check deprecation warnings as existing some existing functionality will be removed in 9.0. SOLR-14934 has more technical details about this change for those concerned.

base_url removed from stored state

As of Solr 8.8.0, the base_url property was removed from the stored state for replicas (SOLR-12182). If you窶决e able to upgrade SolrJ to 8.8.x for all of your client applications, then you can set -Dsolr.storeBaseUrl=false (introduced in Solr 8.8.1) to better align the stored state in ZooKeeper with future versions of Solr. However, if you are not able to upgrade SolrJ to 8.8.x for all client applications, then leave the default -Dsolr.storeBaseUrl=true so that Solr will continue to store the base_url in ZooKeeper.

You may also see some NPE in collection state updates during a rolling upgrade to 8.8.0 from a previous version of Solr. After upgrading all nodes in your cluster to 8.8.0, collections should fully recover. Trigger another rolling restart if there are any replicas that do not recover after the upgrade to re-elect leaders.
Solr 8.7

See the 8.7 Release Notes for an overview of the main new features of Solr 8.7.

When upgrading to 8.7.x users should be aware of the following major changes from 8.6.

Autoscaling

    If upgrading from 8.6.0, please see the 8.6.1 Upgrade notes below for information on performance degradations introduced in 8.6.0 that require some intervention to resolve. If you are already on 8.6.1 or higher, you can ignore these instructions.

Deprecations

    The autoscaling framework is now formally deprecated and will be removed in Solr 9.0. The Solr community is working on pluggable API to replace this functionality, with the goal for it to be ready by the time 9.0 is released. Deprecations include: autoscaling policy, triggers, withCollection support, simulation framework, autoscaling suggestions tab in the UI, autoAddReplicas and UTILIZENODE command.

    Similarly, rule-based replica placement strategy has been deprecated and will be replaced in Solr 9.0 by APIs for replica placement and cluster events, with plugin-based implementations.

    Support for detecting spinning disks has been removed in LUCENE-9576. Corresponding spins metrics in Solr still exist but now they always return false and will be removed in Solr 9.0.

User-Managed Cluster Terminology Updated

    Solr has replaced the terms "master" and "slave" in the codebase and all documentation with "leader" and "follower".

    This functionality has only changed in terms of parameter names changed, and we do not expect any back-compatibility issues on upgrade to 8.7 or even 9.0 later.

    However, users should update their solrconfig.xml files after completing the upgrade on all nodes of a cluster. Comparing your configuration to the updated configuration examples in Index Replication will show examples of what needs to change, but here are the main changes:

        On the replication leader, in the definition of the /replication request handler:

            Replace "master" with "leader".

            Replace "slave" with "follower" if the former term is used in the name of any follower solrconfig.xml file definitions. This file can be named anything, so you can change it to whatever you窶囘 like to call it if you窶囘 like.

            Replace "slave" with "follower" if the former term is used in a replication repeater configuration.

        On the replication follower, in the definition of the /replication request handler:

            Replace "masterUrl" with "leaderUrl".

            Replace "slave" with "follower" if the former term is used in a repeater configuration.

JSON Facets

    Performance enhancements for the relatedness() statistics function are included with 8.7. These yield the highest benefits with high-cardinality fields and can be disabled if working with lower cardinality fields with a new sweep_collection parameter. See the section relatedness() Options for details.

solr.in.sh / solr.in.cmd

    Solr has relied on the SOLR_STOP_WAIT parameter defined in solr.in.sh or solr.in.cmd to determine how long to wait on startup. A new parameter SOLR_START_WAIT allows defining how long Solr should wait for start up to complete.

    If the time set by this parameter is exceeded, Solr will exit the startup process and return the last few lines of the solr.log file to the terminal.

    By default, this parameter is set to the same value as SOLR_STOP_WAIT.

    The default ZooKeeper client timeout (ZK_CLIENT_TIMEOUT) is now 30 seconds (30000 milliseconds) instead of 15.

Configsets

    It窶冱 now possible to overwrite an existing configset when uploading changes by supplying the overwrite=true parameter to the Configset API.

    A related parameter is cleanup=true, which allows deleting any files from the old configset that are left behind after the overwrite.

    The default for both of these parameters is false.

    When deleting a collection that has an automatically created configset (i.e., the configset was copied from the _default collection when the collection was created), the configset will also be deleted if it is not in use by any other collection.

Logging

    A request ID (rid) is now logged for all distributed search requests (in SolrCloud) which can be used to correlate query events across the system. A parameter disableRequestId=true can be added to disable this if desired.

Solr 8.6.1

See the 8.6.1 Release Notes for an overview of the fixes included in Solr 8.6.1.

When upgrading to 8.6.1 users should be aware of the following major changes from 8.6.0.

Autoscaling

    As mentioned in the 8.6 upgrade notes, a default autoscaling policy was provided starting in 8.6.0. This default autoscaling policy resulted in increasingly slow collection creation calls in large clusters (50+ collections).

    In 8.6.1 the default autoscaling policy has been removed, and clusters will not use autoscaling unless a policy has explicitly been created. If your cluster is running 8.6.0 and not using an explicit autoscaling policy, upgrade to 8.6.1 and remove the default cluster policy and preferences via the following command.

    Replace localhost:8983 with your Solr endpoint.

    curl -X POST -H 'Content-type:application/json'  -d '{set-cluster-policy : [], set-cluster-preferences : []}' http://localhost:8983/api/cluster/autoscaling

    This information is only relevant for users upgrading from 8.6.0. If upgrading from an earlier version to 8.6.1+, this warning can be ignored.

Solr 8.6

See the 8.6 Release Notes for an overview of the main new features of Solr 8.6.

When upgrading to 8.6.x users should be aware of the following major changes from 8.5.

Support for Block-Max WAND

Lucene added support for Block-Max WAND in 8.0, and 8.6 makes this available for Solr also.

This can provide significant performance enhancements by not calculating the score for results which are not likely to appear in the top set of results.

It is enabled when using a new query parameter minExactCount. This parameter tells Solr to accurately count the number of hits accurately until at least this value. Once this value is reached, Solr can skip over documents that don窶冲 have a score high enough to be in the top set of documents, which has the potential for greatly speeding up searches.

It窶冱 important to note that when using this parameter, the hit count of searches may not be accurate. It is guaranteed that the hit count is accurate up to the value of minExactCount, but any returned hit count higher than that may be an approximation.

A new boolean attribute numFoundExact is included in all responses to indicate if the hit count in the response is expected to be exact or not.

More information about this new feature is available in the section minExactCount Parameter.

Autoscaling

    NOTE: The default autoscaling policy has been removed as of 8.6.1

    Solr now includes a default autoscaling policy. This policy can be overridden with your custom rules or by specifying an empty policy to replace the default.

    The ComputePlan action now supports a collection selector to identify collections based on collection properties to determine which collections should be operated on.

Security

    Prior to Solr 8.6 Solr APIs which take a file system location, such as core creation, backup, restore, and others, did not validate the path and Solr would allow any absolute or relative path. Starting in 8.6 only paths that are relative to SOLR_HOME, SOLR_DATA_HOME and coreRootDir are allowed by default.

    If you need to create a core or store a backup outside the default paths, you will need to tell Solr which paths to allow. A new element in solr.xml called allowPaths takes a comma-separated list of allowed paths.

    When using the solr.xml file that ships with 8.6, you can configure the list of paths to allow through the system property solr.allowPaths. Please see bin/solr.in.sh or bin\solr.in.cmd for example usage. Using the value * will allow any path as in earlier versions.

    For more on this, see the section Solr.xml Parameters.

    Windows SMB shares on the UNC format, such as \\myhost\myshare\mypath are now always disallowed. Please use drive letter mounts instead, i.e., S:\mypath.

    A new authorization plugin ExternalRoleRuleBasedAuthorizationPlugin is now available. This plugin allows an authentication plugin (such as JWT) to supply a user窶冱 roles instead of maintaining a user-to-role mapping inside Solr.

    When authentication is enabled, the Admin UI Dashboard (main screen) now includes a panel that shows the authentication and authorization plugins in use, the logged in username, and the roles assigned to this user. A new link will also appear in the left-hand navigation to allow a user to log out.

Streaming Expressions

    The /export handler now supports streaming expressions to allow limiting the output of the export to only matching documents.

    For more information about how to use this, see the section Specifying the Local Streaming Expression.

    The stats, facet, and timeseries expressions now support percentiles and standard deviation aggregations.

Highlighting

For the Unified Highlighter: The setting hl.fragsizeIsMinimum now defaults to false because true was found to be a significant performance regression when highlighting lots of text. This will yield longer highlights on average compared to Solr 8.5 but relatively unchanged compared to previous releases. Furthermore, if your application highlights lots of text, you may want to experiment with lowering hl.fragAlignRatio to trade ideal fragment alignment for better performance.

Deprecations

A primary focus of the community is improving Solr窶冱 stability and supportability. With the addition of the package manager system in 8.4, we now have the ability to move some features into plugins maintained by third-parties with the expertise to properly develop and support them. Our goal is to make running Solr easier and less prone to outages and other headaches. In this spirit, the following features have been deprecated and are slated to be removed in Solr 9.0.

    Cross Data Center Replication (CDCR), in its current form, is deprecated and is scheduled to be removed in 9.0. This feature is unlikely to be replaced by an identical plugin. However, the community is working on figuring out a replacement feature for disaster recovery and failover.

    The Data Import Handler (DIH) is deprecated and is scheduled to be removed in 9.0. Work to replace DIH with a community-supported plugin is underway and may be available soon.

    Support to store indexes and backups in HDFS is deprecated and is scheduled to be removed in 9.0. A community-supported version of this may be available as a plugin in the future. For more details, please see SOLR-14021.

Users interested in maintaining a feature as a plugin are encouraged to join the developer mailing list to find out more about how to help.

(jym)