From 07478100393211726a20e1b4dec2385f24a87b98 Mon Sep 17 00:00:00 2001 From: CoprDistGit Date: Tue, 11 Apr 2023 06:32:06 +0000 Subject: automatic import of python-edx-name-affirmation --- python-edx-name-affirmation.spec | 121 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 121 insertions(+) create mode 100644 python-edx-name-affirmation.spec (limited to 'python-edx-name-affirmation.spec') diff --git a/python-edx-name-affirmation.spec b/python-edx-name-affirmation.spec new file mode 100644 index 0000000..8285b96 --- /dev/null +++ b/python-edx-name-affirmation.spec @@ -0,0 +1,121 @@ +%global _empty_manifest_terminate_build 0 +Name: python-edx-name-affirmation +Version: 2.3.5 +Release: 1 +Summary: Name affirmation app for Open edX +License: AGPL 3.0 +URL: https://github.com/edx/edx-name-affirmation +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/c3/9f/ed78ba4ed7aa99c7d8e587709db82db70714129c3ba3ac0f642f7c0a3e51/edx-name-affirmation-2.3.5.tar.gz +BuildArch: noarch + +Requires: python3-djangorestframework +Requires: python3-edx-api-doc-tools +Requires: python3-edx-django-utils +Requires: python3-django-model-utils +Requires: python3-Django +Requires: python3-edx-celeryutils +Requires: python3-edx-toggles +Requires: python3-django-simple-history +Requires: python3-django-config-models +Requires: python3-edx-drf-extensions + +%description +This library mainly stores various stages of a learner's verified identifying information. +The prevalent example is the learner's full name. To verify the full name, the learner +has to first initiate from UI that is part of the platform. +Here are the steps of which the PII information, for example: full name, goes through: +1. learner requests to update the name +2. learner is brought to go through ID verification process +3. learner submit the ID verification after providing supporting evidence +4. the ID Verification reviewer approves or denies the verification +5. the library receives the verdict and updates the name record in the model accordingly +The above process can also be triggered by a Proctored exam attempt, where the exam attempt status +can be the input into this library to create and update the name record's status. In this case, +the learner do not have to go through ID Verification. The proctoring process always collects ID +verification evidence. +For more context of the library, see `context`_. + +%package -n python3-edx-name-affirmation +Summary: Name affirmation app for Open edX +Provides: python-edx-name-affirmation +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-edx-name-affirmation +This library mainly stores various stages of a learner's verified identifying information. +The prevalent example is the learner's full name. To verify the full name, the learner +has to first initiate from UI that is part of the platform. +Here are the steps of which the PII information, for example: full name, goes through: +1. learner requests to update the name +2. learner is brought to go through ID verification process +3. learner submit the ID verification after providing supporting evidence +4. the ID Verification reviewer approves or denies the verification +5. the library receives the verdict and updates the name record in the model accordingly +The above process can also be triggered by a Proctored exam attempt, where the exam attempt status +can be the input into this library to create and update the name record's status. In this case, +the learner do not have to go through ID Verification. The proctoring process always collects ID +verification evidence. +For more context of the library, see `context`_. + +%package help +Summary: Development documents and examples for edx-name-affirmation +Provides: python3-edx-name-affirmation-doc +%description help +This library mainly stores various stages of a learner's verified identifying information. +The prevalent example is the learner's full name. To verify the full name, the learner +has to first initiate from UI that is part of the platform. +Here are the steps of which the PII information, for example: full name, goes through: +1. learner requests to update the name +2. learner is brought to go through ID verification process +3. learner submit the ID verification after providing supporting evidence +4. the ID Verification reviewer approves or denies the verification +5. the library receives the verdict and updates the name record in the model accordingly +The above process can also be triggered by a Proctored exam attempt, where the exam attempt status +can be the input into this library to create and update the name record's status. In this case, +the learner do not have to go through ID Verification. The proctoring process always collects ID +verification evidence. +For more context of the library, see `context`_. + +%prep +%autosetup -n edx-name-affirmation-2.3.5 + +%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-edx-name-affirmation -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Tue Apr 11 2023 Python_Bot - 2.3.5-1 +- Package Spec generated -- cgit v1.2.3