Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package python-py-vapid for openSUSE:Factory
checked in at 2022-12-15 19:24:52
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-py-vapid (Old)
and /work/SRC/openSUSE:Factory/.python-py-vapid.new.1835 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-py-vapid"
Thu Dec 15 19:24:52 2022 rev:4 rq:1042872 version:1.9.0
Changes:
--------
--- /work/SRC/openSUSE:Factory/python-py-vapid/python-py-vapid.changes
2022-04-13 21:05:46.716604764 +0200
+++
/work/SRC/openSUSE:Factory/.python-py-vapid.new.1835/python-py-vapid.changes
2022-12-15 19:25:02.864002551 +0100
@@ -1,0 +2,11 @@
+Tue Dec 13 16:23:06 UTC 2022 - Yogalakshmi Arunachalam <yarunacha...@suse.com>
+
+- Update to v1.9.0
+ * chore: Jul 2022 update
+ Now that this is one of the Critical Projects (thanks?) I should
+ update it to be more modern, clean up some of the crap, and
+ run it through flake8 at least.
+ * Add a rst version of the README
+ * update rust version to 0.6.0
+
+-------------------------------------------------------------------
Old:
----
py-vapid-1.8.2.tar.gz
New:
----
py-vapid-1.9.0.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-py-vapid.spec ++++++
--- /var/tmp/diff_new_pack.xKgAg2/_old 2022-12-15 19:25:03.380005487 +0100
+++ /var/tmp/diff_new_pack.xKgAg2/_new 2022-12-15 19:25:03.388005532 +0100
@@ -18,7 +18,7 @@
%{?!python_module:%define python_module() python-%{**} python3-%{**}}
Name: python-py-vapid
-Version: 1.8.2
+Version: 1.9.0
Release: 0
Summary: VAPID header generation library
License: MPL-2.0
++++++ py-vapid-1.8.2.tar.gz -> py-vapid-1.9.0.tar.gz ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/py-vapid-1.8.2/PKG-INFO new/py-vapid-1.9.0/PKG-INFO
--- old/py-vapid-1.8.2/PKG-INFO 2021-04-19 18:35:08.091729600 +0200
+++ new/py-vapid-1.9.0/PKG-INFO 2022-12-06 00:50:11.147311200 +0100
@@ -1,114 +1,125 @@
Metadata-Version: 2.1
Name: py-vapid
-Version: 1.8.2
+Version: 1.9.0
Summary: Simple VAPID header generation library
Home-page: https://github.com/mozilla-services/vapid
Author: JR Conlin
Author-email: src+va...@jrconlin.com
License: MPL2
-Description:
- Easy VAPID generation
- =====================
-
- This minimal library contains the minimal set of functions you need to
- generate a VAPID key set and get the headers youâll need to sign a
- WebPush subscription update.
-
- VAPID is a voluntary standard for WebPush subscription providers (sites
- that send WebPush updates to remote customers) to self-identify to Push
- Servers (the servers that convey the push notifications).
-
- The VAPID âclaimsâ are a set of JSON keys and values. There are two
- required fields, one semi-optional and several optional additional
- fields.
-
- At a minimum a VAPID claim set should look like:
-
- ::
-
-
{"sub":"mailto:yourem...@yoursite.com","aud":"https://PushServer","exp":"ExpirationTimestamp"}
-
- A few notes:
-
- **sub** is the email address you wish to have on record for this
- request, prefixed with â``mailto:``â. If things go wrong, this is
the
- email that will be used to contact you (for instance). This can be a
- general delivery address like
â``mailto:push_operati...@example.com``â
- or a specific address like â``mailto:b...@example.com``â.
-
- **aud** is the audience for the VAPID. This is the scheme and host you
- use to send subscription endpoints and generally coincides with the
- ``endpoint`` specified in the Subscription Info block.
-
- As example, if a WebPush subscription info contains:
- ``{"endpoint": "https://push.example.com:8012/v1/push/...";, ...}``
-
- then the ``aud`` would be â``https://push.example.com:8012``â
-
- While some Push Services consider this an optional field, others may be
- stricter.
-
- **exp** This is the UTC timestamp for when this VAPID request will
- expire. The maximum period is 24 hours. Setting a shorter period can
- prevent âreplayâ attacks. Setting a longer period allows you to
reuse
- headers for multiple sends (e.g. if youâre sending hundreds of
updates
- within an hour or so.) If no ``exp`` is included, one that will expire
- in 24 hours will be auto-generated for you.
-
- Claims should be stored in a JSON compatible file. In the examples
- below, weâve stored the claims into a file named ``claims.json``.
-
- py_vapid can either be installed as a library or used as a stand along
- app, ``bin/vapid``.
-
- App Installation
- ----------------
-
- Youâll need ``python virtualenv`` Run that in the current directory.
-
- Then run
-
- ::
-
- bin/pip install -r requirements.txt
-
- bin/python setup.py install
-
- App Usage
- ---------
-
- Run by itself, ``bin/vapid`` will check and optionally create the
- public_key.pem and private_key.pem files.
-
- ``bin/vapid --gen`` can be used to generate a new set of public and
- private key PEM files. These will overwrite the contents of
- ``private_key.pem`` and ``public_key.pem``.
-
- ``bin/vapid --sign claims.json`` will generate a set of HTTP headers
- from a JSON formatted claims file. A sample ``claims.json`` is included
- with this distribution.
-
- ``bin/vapid --sign claims.json --json`` will output the headers in JSON
- format, which may be useful for other programs.
-
- ``bin/vapid --applicationServerKey`` will return the
- ``applicationServerKey`` value you can use to make a restricted
- endpoint. See
- https://developer.mozilla.org/en-US/docs/Web/API/PushManager/subscribe
- for more details. Be aware that this value is tied to the generated
- public/private key. If you remove or generate a new key, any restricted
- URL youâve previously generated will need to be reallocated. Please
note
- that some User Agents may require you `to decode this string into a
- Uint8Array
<https://github.com/GoogleChrome/push-notifications/blob/master/app/scripts/main.js>`__.
-
- See ``bin/vapid -h`` for all options and commands.
-
- .. |PyPI version py_vapid| image::
https://badge.fury.io/py/py-vapid.svg
- :target: https://pypi.org/project/py-vapid/
-
Keywords: vapid push webpush
Platform: UNKNOWN
Classifier: Topic :: Internet :: WWW/HTTP
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Description-Content-Type: text/x-rst
+License-File: LICENSE
+
+|PyPI version py_vapid|
+
+Easy VAPID generation
+=====================
+
+This minimal library contains the minimal set of functions you need to
+generate a VAPID key set and get the headers youâll need to sign a
+WebPush subscription update.
+
+VAPID is a voluntary standard for WebPush subscription providers (sites
+that send WebPush updates to remote customers) to self-identify to Push
+Servers (the servers that convey the push notifications).
+
+The VAPID âclaimsâ are a set of JSON keys and values. There are two
+required fields, one semi-optional and several optional additional
+fields.
+
+At a minimum a VAPID claim set should look like:
+
+::
+
+
{"sub":"mailto:yourem...@yoursite.com","aud":"https://PushServer","exp":"ExpirationTimestamp"}
+
+A few notes:
+
+**sub** is the email address you wish to have on record for this
+request, prefixed with â``mailto:``â. If things go wrong, this is the
+email that will be used to contact you (for instance). This can be a
+general delivery address like â``mailto:push_operati...@example.com``â
+or a specific address like â``mailto:b...@example.com``â.
+
+**aud** is the audience for the VAPID. This is the scheme and host you
+use to send subscription endpoints and generally coincides with the
+``endpoint`` specified in the Subscription Info block.
+
+As example, if a WebPush subscription info contains:
+``{"endpoint": "https://push.example.com:8012/v1/push/...";, ...}``
+
+then the ``aud`` would be â``https://push.example.com:8012``â
+
+While some Push Services consider this an optional field, others may be
+stricter.
+
+**exp** This is the UTC timestamp for when this VAPID request will
+expire. The maximum period is 24 hours. Setting a shorter period can
+prevent âreplayâ attacks. Setting a longer period allows you to reuse
+headers for multiple sends (e.g. if youâre sending hundreds of updates
+within an hour or so.) If no ``exp`` is included, one that will expire
+in 24 hours will be auto-generated for you.
+
+Claims should be stored in a JSON compatible file. In the examples
+below, weâve stored the claims into a file named ``claims.json``.
+
+py_vapid can either be installed as a library or used as a stand along
+app, ``bin/vapid``.
+
+App Installation
+----------------
+
+Youâll need ``python virtualenv`` Run that in the current directory.
+
+Then run
+
+::
+
+ bin/pip install -r requirements.txt
+
+ bin/python setup.py install
+
+App Usage
+---------
+
+Run by itself, ``bin/vapid`` will check and optionally create the
+public_key.pem and private_key.pem files.
+
+``bin/vapid --gen`` can be used to generate a new set of public and
+private key PEM files. These will overwrite the contents of
+``private_key.pem`` and ``public_key.pem``.
+
+``bin/vapid --sign claims.json`` will generate a set of HTTP headers
+from a JSON formatted claims file. A sample ``claims.json`` is included
+with this distribution.
+
+``bin/vapid --sign claims.json --json`` will output the headers in JSON
+format, which may be useful for other programs.
+
+``bin/vapid --applicationServerKey`` will return the
+``applicationServerKey`` value you can use to make a restricted
+endpoint. See
+https://developer.mozilla.org/en-US/docs/Web/API/PushManager/subscribe
+for more details. Be aware that this value is tied to the generated
+public/private key. If you remove or generate a new key, any restricted
+URL youâve previously generated will need to be reallocated. Please note
+that some User Agents may require you `to decode this string into a
+Uint8Array
<https://github.com/GoogleChrome/push-notifications/blob/master/app/scripts/main.js>`__.
+
+See ``bin/vapid -h`` for all options and commands.
+
+CHANGELOG
+---------
+
+Iâm terrible about updating the Changelog. Please see the
+```git log``
<https://github.com/web-push-libs/vapid/pulls?q=is%3Apr+is%3Aclosed>`__
+history for details.
+
+.. |PyPI version py_vapid| image:: https://badge.fury.io/py/py-vapid.svg
+ :target: https://pypi.org/project/py-vapid/
+
+
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/py-vapid-1.8.2/README.rst
new/py-vapid-1.9.0/README.rst
--- old/py-vapid-1.8.2/README.rst 2020-06-17 15:53:23.000000000 +0200
+++ new/py-vapid-1.9.0/README.rst 2022-12-06 00:49:33.000000000 +0100
@@ -1,3 +1,4 @@
+|PyPI version py_vapid|
Easy VAPID generation
=====================
@@ -95,5 +96,12 @@
See ``bin/vapid -h`` for all options and commands.
+CHANGELOG
+---------
+
+Iâm terrible about updating the Changelog. Please see the
+```git log``
<https://github.com/web-push-libs/vapid/pulls?q=is%3Apr+is%3Aclosed>`__
+history for details.
+
.. |PyPI version py_vapid| image:: https://badge.fury.io/py/py-vapid.svg
:target: https://pypi.org/project/py-vapid/
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/py-vapid-1.8.2/py_vapid/__init__.py
new/py-vapid-1.9.0/py_vapid/__init__.py
--- old/py-vapid-1.8.2/py_vapid/__init__.py 2021-04-19 18:34:15.000000000
+0200
+++ new/py-vapid-1.9.0/py_vapid/__init__.py 2022-09-23 17:56:38.000000000
+0200
@@ -261,7 +261,7 @@
def _base_sign(self, claims):
cclaims = copy.deepcopy(claims)
if not cclaims.get('exp'):
- cclaims['exp'] = str(int(time.time()) + 86400)
+ cclaims['exp'] = int(time.time()) + 86400
if not self.conf.get('no-strict', False):
valid = _check_sub(cclaims.get('sub', ''))
else:
@@ -277,7 +277,6 @@
"Missing 'aud' from claims. "
"'aud' is the scheme, host and optional port for this "
"transaction e.g. https://example.com:8080";)
-
return cclaims
def sign(self, claims, crypto_key=None):
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/py-vapid-1.8.2/py_vapid/main.py
new/py-vapid-1.9.0/py_vapid/main.py
--- old/py-vapid-1.8.2/py_vapid/main.py 2021-04-19 18:34:15.000000000 +0200
+++ new/py-vapid-1.9.0/py_vapid/main.py 2022-09-23 17:56:38.000000000 +0200
@@ -36,15 +36,17 @@
parser.add_argument('--applicationServerKey',
help="show applicationServerKey value",
default=False, action="store_true")
+ parser.add_argument('--private-key', '-k', help='private key pem file',
+ default="private_key.pem")
args = parser.parse_args()
# Added to solve 2.7 => 3.* incompatibility
Vapid = Vapid02
if args.version1:
Vapid = Vapid01
- if args.gen or not os.path.exists('private_key.pem'):
+ if args.gen or not os.path.exists(args.private_key):
if not args.gen:
- print("No private_key.pem file found.")
+ print("No private key file found.")
answer = None
while answer not in ['y', 'n']:
answer = prompt("Do you want me to create one for you? (Y/n)")
@@ -60,7 +62,7 @@
vapid.save_key('private_key.pem')
print("Generating public_key.pem")
vapid.save_public_key('public_key.pem')
- vapid = Vapid.from_file('private_key.pem')
+ vapid = Vapid.from_file(args.private_key)
claim_file = args.sign
result = dict()
if args.applicationServerKey:
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/py-vapid-1.8.2/py_vapid.egg-info/PKG-INFO
new/py-vapid-1.9.0/py_vapid.egg-info/PKG-INFO
--- old/py-vapid-1.8.2/py_vapid.egg-info/PKG-INFO 2021-04-19
18:35:07.000000000 +0200
+++ new/py-vapid-1.9.0/py_vapid.egg-info/PKG-INFO 2022-12-06
00:50:11.000000000 +0100
@@ -1,114 +1,125 @@
Metadata-Version: 2.1
Name: py-vapid
-Version: 1.8.2
+Version: 1.9.0
Summary: Simple VAPID header generation library
Home-page: https://github.com/mozilla-services/vapid
Author: JR Conlin
Author-email: src+va...@jrconlin.com
License: MPL2
-Description:
- Easy VAPID generation
- =====================
-
- This minimal library contains the minimal set of functions you need to
- generate a VAPID key set and get the headers youâll need to sign a
- WebPush subscription update.
-
- VAPID is a voluntary standard for WebPush subscription providers (sites
- that send WebPush updates to remote customers) to self-identify to Push
- Servers (the servers that convey the push notifications).
-
- The VAPID âclaimsâ are a set of JSON keys and values. There are two
- required fields, one semi-optional and several optional additional
- fields.
-
- At a minimum a VAPID claim set should look like:
-
- ::
-
-
{"sub":"mailto:yourem...@yoursite.com","aud":"https://PushServer","exp":"ExpirationTimestamp"}
-
- A few notes:
-
- **sub** is the email address you wish to have on record for this
- request, prefixed with â``mailto:``â. If things go wrong, this is
the
- email that will be used to contact you (for instance). This can be a
- general delivery address like
â``mailto:push_operati...@example.com``â
- or a specific address like â``mailto:b...@example.com``â.
-
- **aud** is the audience for the VAPID. This is the scheme and host you
- use to send subscription endpoints and generally coincides with the
- ``endpoint`` specified in the Subscription Info block.
-
- As example, if a WebPush subscription info contains:
- ``{"endpoint": "https://push.example.com:8012/v1/push/...";, ...}``
-
- then the ``aud`` would be â``https://push.example.com:8012``â
-
- While some Push Services consider this an optional field, others may be
- stricter.
-
- **exp** This is the UTC timestamp for when this VAPID request will
- expire. The maximum period is 24 hours. Setting a shorter period can
- prevent âreplayâ attacks. Setting a longer period allows you to
reuse
- headers for multiple sends (e.g. if youâre sending hundreds of
updates
- within an hour or so.) If no ``exp`` is included, one that will expire
- in 24 hours will be auto-generated for you.
-
- Claims should be stored in a JSON compatible file. In the examples
- below, weâve stored the claims into a file named ``claims.json``.
-
- py_vapid can either be installed as a library or used as a stand along
- app, ``bin/vapid``.
-
- App Installation
- ----------------
-
- Youâll need ``python virtualenv`` Run that in the current directory.
-
- Then run
-
- ::
-
- bin/pip install -r requirements.txt
-
- bin/python setup.py install
-
- App Usage
- ---------
-
- Run by itself, ``bin/vapid`` will check and optionally create the
- public_key.pem and private_key.pem files.
-
- ``bin/vapid --gen`` can be used to generate a new set of public and
- private key PEM files. These will overwrite the contents of
- ``private_key.pem`` and ``public_key.pem``.
-
- ``bin/vapid --sign claims.json`` will generate a set of HTTP headers
- from a JSON formatted claims file. A sample ``claims.json`` is included
- with this distribution.
-
- ``bin/vapid --sign claims.json --json`` will output the headers in JSON
- format, which may be useful for other programs.
-
- ``bin/vapid --applicationServerKey`` will return the
- ``applicationServerKey`` value you can use to make a restricted
- endpoint. See
- https://developer.mozilla.org/en-US/docs/Web/API/PushManager/subscribe
- for more details. Be aware that this value is tied to the generated
- public/private key. If you remove or generate a new key, any restricted
- URL youâve previously generated will need to be reallocated. Please
note
- that some User Agents may require you `to decode this string into a
- Uint8Array
<https://github.com/GoogleChrome/push-notifications/blob/master/app/scripts/main.js>`__.
-
- See ``bin/vapid -h`` for all options and commands.
-
- .. |PyPI version py_vapid| image::
https://badge.fury.io/py/py-vapid.svg
- :target: https://pypi.org/project/py-vapid/
-
Keywords: vapid push webpush
Platform: UNKNOWN
Classifier: Topic :: Internet :: WWW/HTTP
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Description-Content-Type: text/x-rst
+License-File: LICENSE
+
+|PyPI version py_vapid|
+
+Easy VAPID generation
+=====================
+
+This minimal library contains the minimal set of functions you need to
+generate a VAPID key set and get the headers youâll need to sign a
+WebPush subscription update.
+
+VAPID is a voluntary standard for WebPush subscription providers (sites
+that send WebPush updates to remote customers) to self-identify to Push
+Servers (the servers that convey the push notifications).
+
+The VAPID âclaimsâ are a set of JSON keys and values. There are two
+required fields, one semi-optional and several optional additional
+fields.
+
+At a minimum a VAPID claim set should look like:
+
+::
+
+
{"sub":"mailto:yourem...@yoursite.com","aud":"https://PushServer","exp":"ExpirationTimestamp"}
+
+A few notes:
+
+**sub** is the email address you wish to have on record for this
+request, prefixed with â``mailto:``â. If things go wrong, this is the
+email that will be used to contact you (for instance). This can be a
+general delivery address like â``mailto:push_operati...@example.com``â
+or a specific address like â``mailto:b...@example.com``â.
+
+**aud** is the audience for the VAPID. This is the scheme and host you
+use to send subscription endpoints and generally coincides with the
+``endpoint`` specified in the Subscription Info block.
+
+As example, if a WebPush subscription info contains:
+``{"endpoint": "https://push.example.com:8012/v1/push/...";, ...}``
+
+then the ``aud`` would be â``https://push.example.com:8012``â
+
+While some Push Services consider this an optional field, others may be
+stricter.
+
+**exp** This is the UTC timestamp for when this VAPID request will
+expire. The maximum period is 24 hours. Setting a shorter period can
+prevent âreplayâ attacks. Setting a longer period allows you to reuse
+headers for multiple sends (e.g. if youâre sending hundreds of updates
+within an hour or so.) If no ``exp`` is included, one that will expire
+in 24 hours will be auto-generated for you.
+
+Claims should be stored in a JSON compatible file. In the examples
+below, weâve stored the claims into a file named ``claims.json``.
+
+py_vapid can either be installed as a library or used as a stand along
+app, ``bin/vapid``.
+
+App Installation
+----------------
+
+Youâll need ``python virtualenv`` Run that in the current directory.
+
+Then run
+
+::
+
+ bin/pip install -r requirements.txt
+
+ bin/python setup.py install
+
+App Usage
+---------
+
+Run by itself, ``bin/vapid`` will check and optionally create the
+public_key.pem and private_key.pem files.
+
+``bin/vapid --gen`` can be used to generate a new set of public and
+private key PEM files. These will overwrite the contents of
+``private_key.pem`` and ``public_key.pem``.
+
+``bin/vapid --sign claims.json`` will generate a set of HTTP headers
+from a JSON formatted claims file. A sample ``claims.json`` is included
+with this distribution.
+
+``bin/vapid --sign claims.json --json`` will output the headers in JSON
+format, which may be useful for other programs.
+
+``bin/vapid --applicationServerKey`` will return the
+``applicationServerKey`` value you can use to make a restricted
+endpoint. See
+https://developer.mozilla.org/en-US/docs/Web/API/PushManager/subscribe
+for more details. Be aware that this value is tied to the generated
+public/private key. If you remove or generate a new key, any restricted
+URL youâve previously generated will need to be reallocated. Please note
+that some User Agents may require you `to decode this string into a
+Uint8Array
<https://github.com/GoogleChrome/push-notifications/blob/master/app/scripts/main.js>`__.
+
+See ``bin/vapid -h`` for all options and commands.
+
+CHANGELOG
+---------
+
+Iâm terrible about updating the Changelog. Please see the
+```git log``
<https://github.com/web-push-libs/vapid/pulls?q=is%3Apr+is%3Aclosed>`__
+history for details.
+
+.. |PyPI version py_vapid| image:: https://badge.fury.io/py/py-vapid.svg
+ :target: https://pypi.org/project/py-vapid/
+
+
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/py-vapid-1.8.2/setup.py new/py-vapid-1.9.0/setup.py
--- old/py-vapid-1.8.2/setup.py 2021-04-19 18:32:46.000000000 +0200
+++ new/py-vapid-1.9.0/setup.py 2022-09-23 17:58:16.000000000 +0200
@@ -3,7 +3,7 @@
from setuptools import setup, find_packages
-__version__ = "1.8.2"
+__version__ = "1.9.0"
def read_from(file):
