libQuotient-0.8.1.2-bp156.1.3

- Update to 0.8.1.2
  * It turned out that version 0.8.1 is not entirely ABI compatible
    with 0.8.0 as it should. This release is made solely to fix it;
    there are no other changes.

- Add Qt5DBus as build requirement
  * fixes Leap 15.5 build

- Update to 0.8.1.1
  * Got rid of deprecated RoomPinnedEvent name
    (gh#quotient-im/libQuotient#680)
  * Fixed session verification (gh#quotient-im/libQuotient#682)
  * Constified Room::userIdsAtEvent()
    (gh#quotient-im/libQuotient#686)
  * Enhanced logging around key verification
    (gh#quotient-im/libQuotient#690)
  * Made it possible to use the key backup client-server API
    in the backend (gh#quotient-im/libQuotient#693)
  * Constrained the e-mail logic in linkifyUrl() so that it
    doesn't trigger in the middle of another URL
    (gh#quotient-im/libQuotient#698)

- Update to 0.8.0. Check
  https://github.com/quotient-im/libQuotient/releases for older
  changes list.
  * Fixed AccountRegistry::invokeLogin() to still add Connection
    objects after successfully connecting them to the homeserver
    (gh#quotient-im/libQuotient#675)
  * pinned events actually follow the specification (and
    therefore, interoperable) (gh#quotient-im/libQuotient#677)
- Add a Qt6 flavor. Needed by the KDE CI
- Enable E2EE by default. This will be required by neochat soon.

- Update to version 0.7.0:
  * E2EE is the biggest part of this release,
    + The following parts of E2EE are known to work:
  - foundations additional contributions and refactoring.
  - Olm/Megolm signalling with our parties/devices.
  - managing device and one-time keys.
  - sending and receiving (monstrous new encrypted messages.
  - encrypting/decrypting attachment.
  - retrieval and decryption of historical messages keys
    for which are already in the database.
  - device verification.
    + What is not there yet:
  - historical Megolm sessions are not requested from other
    devices/parties, so you will see quite a few undecryptable
    messages in rooms with past communication - this might be
    fixed (if possible without breaking the API) in further
    0.7.x releases.
  - secure server-side storage (SSSS) is not supported at
    all for now, and will likely require API breakage so
    will come in 0.8.
  - soft logout is not supported; this is also a subject of 0.8.
    + Because there's no soft logout the database for a given account
    is completely reset upon a successful login attempt. This may
    come as a very unpleasant surprise if you don't keep your
    login session between client restarts; but this is a necessary
    trade-off for the current feature set (see #546 for the
    discussion). Together with the rest of the above not-there-yet
    list, this means that you MUST NOT use E2EE with
    libQuotient-backed clients as your only device(s) on
    the account - there's quite a risk of losing encrypted
    conversations if anything happens to the database libQuotient
    keeps key material in, or if you lose your session and have
    to log in again. Did I mention the whole E2EE functionality
    is still in beta? Client authors are strongly recommended
    to show big scary warnings against E2EE for now.
  * Read markers -> read receipts + fully read markers.

- Update to version 0.6.11:
  * Just after 0.6.10 was out another nasty bug has been discovered,
    preventing from proper usage of URLs with an unescaped double-hash (##),
    which may come when a matrix.to URL is generated for a bridged IRC channel
    (and it even got a very nice number #512). Aside from this fix,
    quotest will not return with success code 0 any more if it failed to
    even start testing for some reason (#496).

- Update to versiosn 0.6.10:
  * Yet another maintenance release of the stable branch, fixing an
    issue (#510) with invites not showing up in some cases
    (especially on less active/smaller accounts).

- Update to version 0.6.9:
  * Here's one more stable branch release of libQuotient,
    fixing a rare assertion failure due to uninitialised
    read marker when new events arrive and all history
    is already loaded.

- Update to version 0.6.8:
  * Retain the current room member avatar when renaming the user
    for the room.
  * When displaying the room, notification/highlight counters are
    no more reset. This never really worked, with the notification
    and highlight counts jumping to zero and then back to the
    original value if the timeline hasn't been completely read;
    now that read receipts are correctly sent, the counters
    can be left to the homeserver to update
    (while E2EE is not around).
  * Fix the missing percent encoding in User::fetchProfile(),
    leading to problems around historical userids that still
    have slashes.
  * CS API files have been regenerated from the new matrix-doc
    after revamping the layout and tooling; the library API didn't
    change, but doc-comments are now in Markdown rather than
    ReStructured Text.
  * Update GTAD configuration to version 0.8 of the tool.
  * Fix potential linking errors around quotient_common.h.

- Updae to version 0.6.7:
  * One more maintenance release at the stable branch, fixing
    gh#quotient-im/libQuotient#471 that affects NeoChat - thanks
    to @ognarb for pinpointing and suggesting a fix to it.
- Mention soversion in %files
- Simplify %files
- Use full tarball name
- Don't install quotest and ndk-modules/Android.mk

- Update to version 0.6.6:
  * Another update on the stable branch, to address #456
    (possible crash on some malformed user ids).

- Update to version 0.6.5:
  * Fix rich replies handling.
  * Support abbreviated aka Reddit-style type specifiers in
    Matrix URIs (e.g., matrix:r/quotient:matrix.org)

- Actually disable e2ee

- Update to version 0.6.4:
  * Several fixes around homeserver resolution.

- Add a build conditional for E2EE and disable it by default, as
  applications using libQuotient with E2EE enabled have
  stability issues and memory leaks
- Run spec-cleaner

- Update to version 0.6.3:
  * (#412 with an additional fix in e7c9ca9) Take profile data from
    the previous user state for users who already left
  * (693241d) Fix defunct network requests stalling the request queue
  * (e81117f, 6e8be18) Minor performance improvements on loading
    rooms and accounts involving many users (0.7 will have more work
    on handling that)
  * (2340f3d) Power level events are properly redacted now locally
  * (ff2cb9f) Work around lack of native Qt support for request
    bodies in DELETE requests
  * (97b0bec) Fix a few cases of insufficient escaping in
    Quotient::Uri (thanks to nephele for reporting)
  * (#421) Fix incorrect processing when a network request
    (especially for .well-known) returns 404 with non-empty body
    that is not JSON (which is quite usual when a .well-known
    record is missing)
  * (66972c8) Room tags that start with . (fullstop) are no more
    considered correct and will get u. in front of them.
  * Many thanks for all the help in testing and contributing!

- Update to version 0.6.2:
  * More stringent serverpart checks in user ids.
  * Uri::toUrl() now returns an actually working matrix.to link.
  * The biggest change in this release is a rewrite of the code
    maintaining user profiles (generic and per-room).
    The new code is simpler, faster and occupies less memory -
    a hat-trick of optimisation. The improvement is most noticeable
    when opening bigger rooms with many users (such as Matrix HQ).
  * Trying to set displayname or avatar URL to an empty value with
    Synapse homeservers led to an obscure error;
    now it works as it should.
  * Another noticeable change is that the library should be more
    robust against gateway/CDN/proxy errors that sometimes bring
    unexpected responses (e.g. an HTML payload when JSON is expected).
  * Quotest: added a test for changing the user display name
  * User::bridged() and User::rawName() has long been useless,
    as Matrix stopped using bridge postfixes - they are deprecated now.
  * Smaller optimisations, cleanup and documentation updates, as usual.

- Update to 0.6.0 stable

- Update to 0.6-beta1
  * actually build against the packaged libQtOml instead of the
    intree version

- Update to version 0.6.0:
  * Fix build on big-endian systems
  * Use parsed RoomPowerLevelsEvent in room upgrading
  * Add powerLevelForState()
  * Mark methods as const.

- Update to 0.5.2
  - (#323) Direct chats are no more unmarked when logging in or
    after clearing the cache.
  - 0.5.x releases keep the previous library name, libQMatrixClient
- Upstream renamed library to libQuotient, so this package
  libqmatrixclient also renamed to libQuotient.

- Update to 0.5.1.2
  - (#316) Expired tokens no more bring IncorrectRequestError
    instead of ContentAccessError; consequently,
    Connection::logout() ignores ContentAccessErrors so expired
    tokens don't leave the library in a "can't go-in, can't go out"
    state.
  - Jobs abandoned due to Connection being deleted no more cause
    crashes.

- Update to 0.5.1.1
  This release fixes a bug that makes 0.5.1 not being "new enough"
  for Quaternion 0.0.9.4, and another bug that made user showing up
  multiple times in the user list of Quaternion after renaming.
  Otherwise it's the same as version 0.5.1.

- Update to 0.5.1
  - Fix (#303): linkification doesn't break on peculiar links.
  - Fix (#310 and 27c2989): quirks in rendering room display names
    have been ironed out.
  - Fix: Tighter validations of URLs coming with file events
    (too relaxed validations were causing the library to
    assert-crash on, e.g., encrypted attachments).
  - Enhancement (#305): rooms created as direct chats are now
    automatically marked as m.direct for invited as well as
    inviting users.
  - Enhancement (#306): Room::canSwitchVersions() returns false on
    rooms already upgraded (you still can disregard and call
    Room::switchVersion() but you better think twice
  - see matrix-org/matrix-doc#1937).
  - Enhancement: Room::postFile() now first starts file upload and
    then places a pending event (neatly packed with file transfer
    information), rather than the other way around. Unless you do
    weird things with the library's API, you shouldn't notice.
  - Enhancement: LRO/RLO Unicode markers are now stripped from
    display names, to curtail abuse of those.
  - Feature: Connection::domain() to save client authors from
    taking the domain from user MXID.

- Update to 0.5.0.2
  * Another bugfix release in 0.5.x branch, fixing issues with
    sending read receipts and redactions in v3 rooms (#300).
- Changes from 0.5.0.1
  * This version fixes too stringent checks in debug builds that
    led to assertion crashes upon encounter with upgraded rooms.
- Changes from 0.5
  As usual for 0.x versions, 0.5 breaks API compatibility with
  previous versions; 0.4-compatible clients may or may not need
  changes in order to compile with version 0.5. As usual, see diffs
  in header files to track the changes and update the client code
  accordingly; these release notes highlight most prominent API
  changes.
  Micro-versions in 0.5.y will maintain the API and ABI.
  Version 0.6 will break either API or ABI or both.
  Over 200 commits. So see for changelog
  https://github.com/QMatrixClient/libqmatrixclient/commits/0.5.0