lead2gold pushed to python-apprise (epel9). "Updated to v0.9.6 (..more)"

Notification time stamped 2022-08-31 23:53:53 UTC

From 482b83485b66f0fd8dab1989138000db6528272e Mon Sep 17 00:00:00 2001
From: Chris Caron 
Date: Dec 02 2021 19:03:21 +0000
Subject: Updated to v0.9.6

Signed-off-by: Chris Caron

---

diff --git a/.gitignore b/.gitignore
index 0ef815e..bea2ab5 100644
--- a/.gitignore
+++ b/.gitignore
@@ -20,3 +20,4 @@
 /apprise-0.9.3.tar.gz
 /apprise-0.9.4.tar.gz
 /apprise-0.9.5.1.tar.gz
+/apprise-0.9.6.tar.gz
diff --git a/apprise.1 b/apprise.1
index 64f3225..0d12675 100644
--- a/apprise.1
+++ b/apprise.1
@@ -1,224 +1,141 @@
-." generated with Ronn/v0.7.3
-." http://github.com/rtomayko/ronn/tree/0.7.3
-.
-.TH "APPRISE" "1" "February 2021" "ff" ""
-.
+." generated with Ronn-NG/v0.9.1
+." http://github.com/apjanke/ronn-ng/tree/0.9.1
+.TH "APPRISE" "1" "November 2021" ""
 .SH "NAME"
 \fBapprise\fR - Push Notifications that work with just about every platform!
-.
 .SH "SYNOPSIS"
-\fBapprise\fR [\fIoptions\fR...] \fIservice-url\fR...
-.
+\fBapprise\fR [\fIoptions\fR|.|.|.] \fIservice-url\fR|.|.|.
 .br
-.
 .SH "DESCRIPTION"
 \fBApprise\fR allows you to send a notification to \fIalmost all\fR of the most popular notification services available to us today such as: Discord, Telegram, Pushbullet, Slack, Twitter, etc.
-.
-.IP "(bu" 4
+.IP "[ci]" 4
 One notification library to rule them all.
-.
-.IP "(bu" 4
+.IP "[ci]" 4
 A common and intuitive notification syntax.
-.
-.IP "(bu" 4
+.IP "[ci]" 4
 Supports the handling of images (to the notification services that will accept them).
-.
 .IP "" 0
-.
 .SH "OPTIONS"
 The Apprise options are as follows:
-.
 .P
 \fB-b\fR, \fB--body=\fR\fITEXT\fR: Specify the message body. If no body is specified then content is read from \fIstdin\fR.
-.
 .P
 \fB-t\fR, \fB--title=\fR\fITEXT\fR: Specify the message title. This field is complete optional.
-.
 .P
 \fB-c\fR, \fB--config=\fR\fICONFIG-URL\fR: Specify one or more configuration locations.
-.
 .P
 \fB-a\fR, \fB--attach=\fR\fIATTACH-URL\fR: Specify one or more file attachment locations.
-.
 .P
 \fB-n\fR, \fB--notification-type=\fR\fITYPE\fR: Specify the message type (default=info). Possible values are "info", "success", "failure", and "warning".
-.
 .P
 \fB-i\fR, \fB--input-format=\fR\fIFORMAT\fR: Specify the input message format (default=text). Possible values are "text", "html", and "markdown".
-.
 .P
 \fB-T\fR, \fB--theme=\fRTHEME: Specify the default theme.
-.
 .P
 \fB-g\fR, \fB--tag=\fRTAG: Specify one or more tags to filter which services to notify. Use multiple \fB--tag\fR (\fB-g\fR) entries to \fBOR\fR the tags together and comma separated to \fBAND\fR them. If no tags are specified then all services are notified.
-.
 .P
 \fB-Da\fR, \fB--disable-async\fR: Send notifications synchronously (one after the other) instead of all at once.
-.
 .P
 \fB-R\fR, \fB--recursion-depth\fR: he number of recursive import entries that can be loaded from within Apprise configuration. By default this is set to 1. If this is set to zero, then import statements found in any configuration is ignored.
-.
 .P
 \fB-e\fR, \fB--interpret-escapes\fR Enable interpretation of backslash escapes. For example, this would convert sequences such as \en and \er to their respected ascii new-line and carriage
-.
 .P
 \fB-d\fR, \fB--dry-run\fR: Perform a trial run but only prints the notification services to-be triggered to \fBstdout\fR. Notifications are never sent using this mode.
-.
 .P
 return characters prior to the delivery of the notification.
-.
+.P
+\fB-l\fR, \fB--details\fR Prints details about the current services supported by Apprise.
 .P
 \fB-v\fR, \fB--verbose\fR: The more of these you specify, the more verbose the output is. e.g: -vvvv
-.
 .P
 \fB-D\fR, \fB--debug\fR: A debug mode; useful for troubleshooting.
-.
 .P
 \fB-V\fR, \fB--version\fR: Display the apprise version and exit.
-.
 .P
 \fB-h\fR, \fB--help\fR: Show this message and exit.
-.
 .SH "EXIT STATUS"
 \fBapprise\fR exits with a status of:
-.
-.IP "(bu" 4
+.IP "[ci]" 4
 \fB0\fR if all of the notifications were sent successfully.
-.
-.IP "(bu" 4
+.IP "[ci]" 4
 \fB1\fR if one or more notifications could not be sent.
-.
-.IP "(bu" 4
+.IP "[ci]" 4
 \fB2\fR if there was an error specified on the command line such as not providing an valid argument.
-.
-.IP "(bu" 4
+.IP "[ci]" 4
 \fB3\fR if there was one or more Apprise Service URLs successfully loaded but none could be notified due to user filtering (via tags).
-.
 .IP "" 0
-.
 .SH "SERVICE URLS"
 There are to many service URL and combinations to list here. It's best to visit the Apprise GitHub page \fIhttps://github%5C.com/caronc/apprise/wiki#notification%5C-services%5CfR and see what's available.
-.
 .SH "EXAMPLES"
 Send a notification to as many servers as you want to specify as you can easily chain them together:
-.
 .IP "" 4
-.
 .nf
-
 $ apprise -vv -t "my title" -b "my notification body" \e
    "mailto://myemail:[e-mail]" \e
    "pbul://o.gn5kj6nfhv736I7jC3cj3QLRiyhgl98b"
-.
 .fi
-.
 .IP "" 0
-.
 .P
 If you don't specify a \fB--body\fR (\fB-b\fR) then stdin is used allowing you to use the tool as part of your every day administration:
-.
 .IP "" 4
-.
 .nf
-
 $ cat /proc/cpuinfo | apprise -vv -t "cpu info" \e
     "mailto://myemail:[e-mail]"
-.
 .fi
-.
 .IP "" 0
-.
 .P
 Load in a configuration file which identifies all of your notification service URLs and notify them all:
-.
 .IP "" 4
-.
 .nf
-
 $ apprise -vv -t "my title" -b "my notification body" \e
    --config=~/apprise.yml
-.
 .fi
-.
 .IP "" 0
-.
 .P
 Load in a configuration file from a remote server that identifies all of your notification service URLs and only notify the ones tagged as \fIdevops\fR.
-.
 .IP "" 4
-.
 .nf
-
 $ apprise -vv -t "my title" -b "my notification body" \e
    --config=https://localhost/my/apprise/config \e
    -t devops
-.
 .fi
-.
 .IP "" 0
-.
 .P
 Include an attachment:
-.
 .IP "" 4
-.
 .nf
-
 $ apprise -vv -t "School Assignment" -b "See attached" \e
    --attach=Documents/FinalReport.docx
-.
 .fi
-.
 .IP "" 0
-.
 .SH "CONFIGURATION"
 A configuration file can be in the format of either \fBTEXT\fR or \fBYAML\fR where [TEXT][textconfig] is the easiest and most ideal solution for most users. However YAML \fIhttps://github%5C.com/caronc/apprise/wiki/config_yaml%5CfR configuration files grants the user a bit more leverage and access to some of the internal features of Apprise. Reguardless of which format you choose, both provide the users the ability to leverage \fBtagging\fR which adds a more rich and powerful notification environment.
-.
 .P
 Configuration files can be directly referenced via \fBapprise\fR when referencing the \fB--config=\fR (\fB-c\fR) CLI directive. You can identify as many as you like on the command line and all of them will be loaded. You can also point your configuration to a cloud location (by referencing \fBhttp://%5CfR or \fBhttps://%5CfR%5C. By default \fBapprise\fR looks in the following local locations for configuration files and loads them:
-.
 .IP "" 4
-.
 .nf
-
 $ ~/.apprise
 $ ~/.apprise.yml
 $ ~/.config/apprise
 $ ~/.config/apprise.yml
-.
 .fi
-.
 .IP "" 0
-.
 .P
 If a default configuration file is referenced in any way by the \fBapprise\fR tool, you no longer need to provide it a Service URL. Usage of the \fBapprise\fR tool simplifies to:
-.
 .IP "" 4
-.
 .nf
-
 $ apprise -vv -t "my title" -b "my notification body"
-.
 .fi
-.
 .IP "" 0
-.
 .P
 If you leveraged tagging \fIhttps://github%5C.com/caronc/apprise/wiki/CLI_Usage#label%5C-leverage%5C-tag..., you can define all of Apprise Service URLs in your configuration that you want and only specifically notify a subset of them:
-.
 .IP "" 4
-.
 .nf
-
 $ apprise -vv -t "Will Be Late" -b "Go ahead and make dinner without me" \e
           --tag=family
-.
 .fi
-.
 .IP "" 0
-.
 .SH "BUGS"
 If you find any bugs, please make them known at: \fIhttps://github%5C.com/caronc/apprise/issues%5CfR
-.
 .SH "COPYRIGHT"
 Apprise is Copyright (C) 2021 Chris Caron \[e-mail]\fR
diff --git a/python-apprise.spec b/python-apprise.spec
index 257fd6d..51c162a 100644
--- a/python-apprise.spec
+++ b/python-apprise.spec
@@ -47,18 +47,18 @@ Apprise is a Python package for simplifying access to all of the different
 notification services that are out there. Apprise opens the door and makes
 it easy to access:

-Boxcar, ClickSend, DingTalk, Discord, E-Mail, Emby, Faast, FCM, Flock, Gitter,
-Google Chat, Gotify, Growl, Home Assistant, IFTTT, Join, Kavenegar, KODI,
-Kumulos, LaMetric, MacOSX, Mailgun, Mattermost, Matrix, Microsoft Windows,
-Microsoft Teams, MessageBird, MQTT, MSG91, MyAndroid, Nexmo, Nextcloud, Notica,
-Notifico, Office365, OneSignal, Opsgenie, ParsePlatform, PopcornNotify, Prowl,
-Pushalot, PushBullet, Pushjet, Pushover, PushSafer, Reddit, Rocket.Chat,
-SendGrid, SimplePush, Sinch, Slack, SMTP2Go, Spontit, SparkPost, Super Toasty,
-Streamlabs, Stride, Syslog, Techulus Push, Telegram, Twilio, Twitter, Twist, XBMC,
-XMPP, Webex Teams}
+Apprise API, Boxcar, ClickSend, DingTalk, Discord, E-Mail, Emby, Faast, FCM,
+Flock, Gitter, Google Chat, Gotify, Growl, Home Assistant, IFTTT, Join,
+Kavenegar, KODI, Kumulos, LaMetric, MacOSX, Mailgun, Mattermost, Matrix,
+Microsoft Windows, Microsoft Teams, MessageBird, MQTT, MSG91, MyAndroid, Nexmo,
+Nextcloud, Notica, Notifico, Office365, OneSignal, Opsgenie, ParsePlatform,
+PopcornNotify, Prowl, Pushalot, PushBullet, Pushjet, Pushover, PushSafer,
+Reddit, Rocket.Chat, SendGrid, SimplePush, Sinch, Slack, SMTP2Go, Spontit,
+SparkPost, Super Toasty, Streamlabs, Stride, Syslog, Techulus Push, Telegram,
+Twilio, Twitter, Twist, XBMC, XMPP, Webex Teams}

Name:           python-%{pypi_name}
-Version:        0.9.5.1
+Version:        0.9.6
 Release:        1%{?dist}
 Summary:        A simple wrapper to many popular notification services used today
 License:        MIT
@@ -145,12 +145,6 @@ BuildRequires: python%{python3_pkgversion}-requests-oauthlib
 BuildRequires: python%{python3_pkgversion}-six
 BuildRequires: python%{python3_pkgversion}-click >= 5.0
 BuildRequires: python%{python3_pkgversion}-markdown
-%if (0%{?rhel} && 0%{?rhel} >= 8) || (0%{?fedora} && 0%{?fedora} >= 35)
-# gntp isn't available from EPEL for RHEL/CentOS 8 or Fedora 35+
-%else
-# For all other distributions, include gntp
-BuildRequires: python%{python3_pkgversion}-gntp
-%endif
 BuildRequires: python%{python3_pkgversion}-yaml
 BuildRequires: python%{python3_pkgversion}-babel
 BuildRequires: python%{python3_pkgversion}-cryptography
@@ -159,12 +153,6 @@ Requires: python%{python3_pkgversion}-requests-oauthlib
 Requires: python%{python3_pkgversion}-six
 Requires: python%{python3_pkgversion}-markdown
 Requires: python%{python3_pkgversion}-cryptography
-%if (0%{?rhel} && 0%{?rhel} >= 8) || (0%{?fedora} && 0%{?fedora} >= 35)
-# gntp isn't available from EPEL for RHEL/CentOS 8 or Fedora 35+
-%else
-# For all other distributions, include gntp
-Requires: python%{python3_pkgversion}-gntp
-%endif
 Requires: python%{python3_pkgversion}-yaml

%if %{with tests}
@@ -248,6 +236,9 @@ LANG=C.UTF-8 PYTHONPATH=%{buildroot}%{python3_sitelib} py.test-%{python3_version
 %endif

%changelog
+* Wed Dec  1 2021 Chris Caron  - 0.9.6-1
+- Updated to v0.9.6
+
 * Sat Sep 18 2021 Chris Caron  - 0.9.5.1-2
 - Updated to v0.9.5.1

diff --git a/sources b/sources
index b055737..f34242b 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (apprise-0.9.5.1.tar.gz) = 2b6e68545069ebf17824fc130e2f47d62b22794b722d090fcf7993858dc8fa92b82ecc307fa42a2592640d245e83730258780c85abab12324d0c0e04a0194a63
+SHA512 (apprise-0.9.6.tar.gz) = c694cec6e31c15ddee5be10cc96cc5c72c97a0b061fdd4ba470edfa0a03e9303c5be00a4310733f9ef2a01e3a5c3d737ea5ef830b2dacdd7e57e9c35cea9cbb6

https://src.fedoraproject.org/rpms/python-apprise/c/482b83485b66f0fd8dab1989...