public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Chris Caron <lead2gold@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/python-apprise] epel10: Updated to v1.12.0
Date: Sat, 11 Jul 2026 22:14:48 GMT	[thread overview]
Message-ID: <178380808887.1.1868966255460219165.rpms-python-apprise-e2a5347ff959@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python-apprise
            Branch : epel10
            Commit : e2a5347ff95921e69184f2aa8259192039bf3174
            Author : Chris Caron <lead2gold@gmail.com>
            Date   : 2026-07-11T16:02:40-04:00
            Stats  : +34/-15 in 2 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-apprise/c/e2a5347ff95921e69184f2aa8259192039bf3174?branch=epel10

            Log:
            Updated to v1.12.0

Signed-off-by: Chris Caron <lead2gold@gmail.com>

---
diff --git a/apprise.1 b/apprise.1
index 6ba297b..eb167ba 100644
--- a/apprise.1
+++ b/apprise.1
@@ -1,6 +1,6 @@
 .\" generated with Ronn-NG/v0.10.1
 .\" http://github.com/apjanke/ronn-ng/tree/0.10.1
-.TH "APPRISE" "1" "May 2026" "Chris Caron <lead2gold@gmail.com>"
+.TH "APPRISE" "1" "July 2026" "Chris Caron <lead2gold@gmail.com>"
 .SH "NAME"
 \fBapprise\fR \- Push Notifications that work with just about every platform!
 .SH "SYNOPSIS"
@@ -64,6 +64,10 @@ Tag values may include an optional priority prefix and/or retry suffix:
 .P
 \fB\-Da\fR, \fB\-\-disable\-async\fR: Send notifications synchronously (one after the other) instead of all at once\.
 .P
+\fB\-L\fR, \fB\-\-limit=\fR\fISECONDS\fR: Give up on the whole run if it's taking too long, e\.g\. \fB\-L 10\fR or \fB\-L 2\.5\fR\. By default (\fB0\fR) there's no limit; see \fB\-\-service\-limit\fR below to cap each service on its own instead\. If a service is truly stuck, Apprise gives it a few extra seconds to wrap up, then exits anyway with status \fB5\fR\.
+.P
+\fB\-SL\fR, \fB\-\-service\-limit=\fR\fISECONDS\fR: Give up on any single service if it's taking too long, e\.g\. \fB\-SL 10\fR or \fB\-SL 2\.5\fR, or \fB0\fR to turn this off entirely\. Leave it unset to use Apprise's own default of 60 seconds\.
+.P
 \fB\-R\fR, \fB\-\-recursion\-depth\fR\fIINTEGER\fR: The 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 return characters prior to the delivery of the notification\.
@@ -116,11 +120,15 @@ The \fBstorage\fR action has the following sub actions:
 .IP "\(bu" 4
 \fB0\fR if all of the notifications were sent successfully\.
 .IP "\(bu" 4
-\fB1\fR if one or more notifications could not be sent\.
+\fB1\fR if every notification failed, or the notification could not start\.
+.IP "\(bu" 4
+\fB2\fR if there was an error specified on the command line such as not providing a valid argument\.
+.IP "\(bu" 4
+\fB3\fR if one or more Apprise Service URLs were successfully loaded but none could be notified due to user filtering (via tags)\.
 .IP "\(bu" 4
-\fB2\fR if there was an error specified on the command line such as not providing an valid argument\.
+\fB4\fR if at least one notification was sent successfully and at least one other was not (whether it failed outright or ran out of time)\.
 .IP "\(bu" 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)\.
+\fB5\fR if no notification was sent, and the only problem was that one or more services ran out of time\.
 .IP "" 0
 .SH "SERVICE URLS"
 There are too many service URL and combinations to list here\. It's best to visit the Apprise GitHub page \fIhttps://appriseit\.com/services/\fR and see what's available\. Also try out the Apprise URL Builder \fIhttps://appriseit\.com/tools/url\-builder/\fR to easily construct the URLS this tool supports and works with\.

diff --git a/python-apprise.spec b/python-apprise.spec
index ac9ff81..bf54287 100644
--- a/python-apprise.spec
+++ b/python-apprise.spec
@@ -58,38 +58,44 @@
 Apprise is a Python package that simplifies access to many popular \
 notification services. It supports sending alerts to platforms such as: \
 \
-`46elks`, `AfricasTalking`, `Amazon Chime`, `Apprise API`, `APRS`, \
+`46elks`, `800.com`, `AfricasTalking`, `Amazon Chime`, `Apprise API`, \
+`APRS`, \
 `AWS SES`, `AWS SNS`, `Bark`, `Blink(1)`, `BlueSky`, `Brevo`, \
 `Burst SMS`, `BulkSMS`, `BulkVS`, \
 `Chanify`, `Clickatell`, `ClickSend`, `DAPNET`, `DingTalk`, `Discord`, \
 `Dot. (Quote/0)`, `E-Mail`, `Emby`, `Evolution API`, `Exotel`, \
-`FCM`, `Feishu`, `Flock`, `Fluxer`, `Free Mobile`, `Google Chat`, \
+`FCM`, `Feishu`, `Flock`, `Flowtriq`, `Fluxer`, `Free Mobile`, `Google Chat`, \
 `Gotify`, `GroupMe`, `Growl`, `Guilded`, `Home Assistant`, `httpSMS`, \
 `HumHub`, \
-`IFTTT`, `IRC`, `Jellyfin`, `Jira`, `Join`, `Kavenegar`, `KODI`, \
-`Kumulos`, `LaMetric`, `Lark`, `Line`, `MacOSX`, `Mailgun`, `Mastodon`, \
+`IFTTT`, `IRC`, `Jellyfin`, `Jira`, `Join`, `Kavenegar`, `KODI`, `Kook`, \
+`Kumulos`, `LaMetric`, `Lark`, `Line`, `MacOSX`, `Mailgun`, `MailerSend`, \
+`Mastodon`, \
 `Mattermost`, `Matrix`, `MessageBird`, `Microsoft Windows`, \
 `Microsoft Teams`, `Misskey`, \
 `MQTT`, `MSG91`, `MyAndroid`, `Nexmo`, `Nextcloud`, \
 `NextcloudTalk`, `Notica`, `NotificationAPI`, `Notifiarr`, `Notifico`, \
+`Notifyre`, \
 `ntfy`, `Octopush`, `Office365`, `OneSignal`, `Opsgenie`, `PagerDuty`, \
-`PagerTree`, `ParsePlatform`, `Plivo`, `PopcornNotify`, `Prowl`, \
+`PagerTree`, `ParsePlatform`, `Plivo`, `Prowl`, \
 `Postmark`, `Pushalot`, `PushBullet`, \
-`Pushjet`, `PushMe`, `Pushover`, `Pushplus`, `PushSafer`, `Pushy`, `PushDeer`, \
+`Pushjet`, `PushMe`, `Pushover`, `Pushplus`, `PushSafer`, `PushWard`, \
+`Pushy`, `PushDeer`, \
 `QQ Push`, `Revolt`, `Reddit`, `Resend`, `RingCentral`, `Rocket.Chat`, \
 `RSyslog`, `SendGrid`, \
-`SendPulse`, `ServerChan`, `Session Open Group Server`, `Seven`, `SFR`, \
+`SendPulse`, `ServerChan`, `SerwerSMS`, `Session Open Group Server`, \
+`Seven`, `SFR`, \
 `Signal`, `SIGNL4`, `SimplePush`, \
-`Sinch`, `Slack`, `SMPP`, `SMSEagle`, `SMS Manager`, `SMTP2Go`, `SparkPost`, \
-`Splunk`, `Spike`, `Spug Push`, `Super Toasty`, `Streamlabs`, `Stride`, \
+`Sinch`, `Slack`, `SMPP`, `SMSC`, `SMSEagle`, `SMS Manager`, `SMTP2Go`, \
+`SparkPost`, `Splunk`, `Spike`, `Spug Push`, `Stackfield`, `Super Toasty`, \
+`Streamlabs`, `Stride`, \
 `Synology Chat`, `Syslog`, `Techulus Push`, `Telegram`, `Threema Gateway`, \
 `Twilio`, `Twitter`, `Twist`, `Vapid`, `Viber`, `VictorOps`, `Voipms`, \
 `Vonage`, `WebPush`, `WeChat (WeCom)`, `WeCom Bot`, `WhatsApp`, \
 `Webex Teams`, `Workflows`, `WxPusher`, `XBMC`, `XMPP`, `Zoom`, and `Zulip`.}
 
 Name:           python-%{pypi_name}
-Version:        1.11.0
-Release:        2%{?dist}
+Version:        1.12.0
+Release:        1%{?dist}
 Summary:        A simple wrapper to many popular notification services used today
 License:        BSD-2-Clause
 URL:            https://github.com/caronc/%{pypi_name}
@@ -123,6 +129,8 @@ BuildRequires: python%{python3_pkgversion}-devel
 
 %if %{legacy_python_build}
 BuildRequires: python3dist(setuptools)
+%else
+BuildRequires: python3dist(setuptools) >= 69
 %endif
 
 BuildRequires: python3dist(wheel)
@@ -241,6 +249,9 @@ LANG=C.UTF-8 PYTHONPATH=%{buildroot}%{python3_sitelib}:%{_builddir}/%{name}-%{ve
 %{python3_sitelib}/%{pypi_name}/__pycache__/cli*.py?
 
 %changelog
+* Sat Jul  4 2026 Chris Caron <lead2gold@gmail.com> - 1.12.0-1
+- Updated to v1.12.0
+
 * Thu Jun 04 2026 Python Maint <python-maint@redhat.com> - 1.11.0-2
 - Rebuilt for Python 3.15
 

             reply	other threads:[~2026-07-11 22:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11 22:14 Chris Caron [this message]
2026-07-11 22:14 [rpms/python-apprise] epel10: Updated to v1.12.0 Chris Caron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178380808887.1.1868966255460219165.rpms-python-apprise-e2a5347ff959@fedoraproject.org \
    --to=lead2gold@gmail.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox