%global _empty_manifest_terminate_build 0 Name: python-py-vapid Version: 1.9.0 Release: 1 Summary: Simple VAPID header generation library License: MPL2 URL: https://github.com/mozilla-services/vapid Source0: https://mirrors.nju.edu.cn/pypi/web/packages/a7/a8/2983cdf5f1c25274b941efd7ab0001067686c50640fba7f84fe490c1ce4b/py-vapid-1.9.0.tar.gz BuildArch: noarch %description 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:YourEmail@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_operations@example.com``” or a specific address like “``mailto:bob@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``. %package -n python3-py-vapid Summary: Simple VAPID header generation library Provides: python-py-vapid BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-py-vapid 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:YourEmail@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_operations@example.com``” or a specific address like “``mailto:bob@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``. %package help Summary: Development documents and examples for py-vapid Provides: python3-py-vapid-doc %description help 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:YourEmail@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_operations@example.com``” or a specific address like “``mailto:bob@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``. %prep %autosetup -n py-vapid-1.9.0 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-py-vapid -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Mon Apr 10 2023 Python_Bot - 1.9.0-1 - Package Spec generated