Update documenation (generated man file) to express that plasma notification system will ignore timeout value when level is in critical mode

when pushing a new commit, I noticed the CI build gets stuck on:

Configuring tzdata
------------------
Please select the geographic area in which you live. Subsequent configuration
questions will narrow this down by presenting a list of cities, representing
the time zones in which they are located.
  1. Africa   3. Antarctica  5. Arctic  7. Atlantic  9. Indian    11. US
  2. America  4. Australia   6. Asia    8. Europe    10. Pacific  12. Etc
Geographic area:

fix CI build stuck on TZ data config

See merge request GNOME/libnotify!16

Do not cut off an icon filename (passed to -i) at the first comma
character. The original motivation probably was to support a list of
icon names in -i separated by comma. However, this has never been
implemented and the help text for -i also only mentions "an icon".

Hence, no functionality is lost by this change. In contrast, -i now
supports commas in icon filepaths.

https://gitlab.gnome.org/GNOME/libnotify/-/issues/16

notify-send: Support commas in icon filenames

See merge request GNOME/libnotify!15

Update documenation (generated man file) to express that plasma notification...

See merge request GNOME/libnotify!14

Right now notify-send will quietly return a successful exit status
even if showing the notification fails.

This commit changes the behavior to instead fail on failure.

https://gitlab.gnome.org/GNOME/libnotify/-/merge_requests/13

See discussions at https://gitlab.gnome.org/GNOME/libnotify/-/issues/20.

Based off https://gitlab.gnome.org/GNOME/libnotify/-/merge_requests/19

Add README clarifying status of libnotify

See merge request GNOME/libnotify!21

This reverts merge request !21

David King authored Dec 13, 2021 and Marco Trevisan committed Apr 21, 2022

This avoids differences between IDs for separate builds of the
specification.

This reverts commit 1ad46301.

As per: https://gitlab.gnome.org/GNOME/libnotify/-/commit/1ad46301#note_1434358

In future meson will check the run_command result by default, while it's
fine for us, it would cause our nicer error message not to work.

It's not really an issue here, as we use a properly typed len, but
better not to use a deprecated and potentially dangerous API.

We used to just add it again, to eventually figure out that the file
did not exists, but may not work properly in some scenarios.

Also always fill the path_filename when using a file-name only, as that
may be refer to something under the SNAP path, and in such case we want
to try check if that exists before giving up.

We may need to use them in various places, so there's no point to repeat
the same in multiple places, this way we can also use some shortcuts for
non-snap setups.

Snaps use desktop IDs based on the snap name and the application name
inside the snap, so if we're in a such container, we need to compute the
desktop-entry using those values. We can figure them out from the snap
cgroup they're in.

In such case, don't even try to use the GApplication ID as that is
likely wrong in a snapped environment.

Paul Collins authored May 22, 2012 and Marco Trevisan committed Apr 25, 2022

Support printing and overriding notification ID, so that it's possible
to replace a notification that is currently showing with an updated
content.

Based on patch as provided by Paul Collins in the following bug
report:
  https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/257135/comments/8



Co-authored-by: Marco Trevisan (Treviño) <mail@3v1n0.net>

Fixes #19

Ben Blain authored Mar 02, 2021 and Marco Trevisan committed Apr 25, 2022

If an expiration timeout is set, the notification is not waited longer
than such time.

Ben Blain authored Mar 11, 2021 and Marco Trevisan committed Apr 25, 2022

The activated action name is written to stdout and the notification is closed
when a valid action has been selected.

We're using error variable multiple times, and this may lead to problems
when trying to set it again. So let's just clear once it's used.

Notification actions can now be activated with an activation token
containing platform data. So update the notification-spec to include
latest version of the specification, and expose the activation token
during an action activation.

Not to change the API, by modifying the type of NotifyActionCallback
it's just better to provide a function to fetch the activation token
during activation only, so that this can be retro-compatible.

Reference: https://gitlab.freedesktop.org/xdg/xdg-specs/-/commit/b9a4700

Update NEWS.

Update to upstream version '0.7.10'
with Debian dir e2d40a445894827877a66b8123af2592550c146e

It's not supported by GLib 2.26.0, the minimum version we required

Boolean hints are used for some common parameters such as "transient".

Original bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636343

Update NEWS.

Update to upstream version '0.7.11'
with Debian dir 43a8674952cc03a9a6961e5ac7fc5254f9627edb

libnotify Debian release 0.7.11-1