automatic import of python-falocalrepo-databaseopeneuler20.03

3 files changed, 437 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..43a4ace 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/falocalrepo_database-5.4.4.tar.gz
diff --git a/python-falocalrepo-database.spec b/python-falocalrepo-database.spec
new file mode 100644
index 0000000..8158c44
--- /dev/null
+++ b/python-falocalrepo-database.spec
@@ -0,0 +1,435 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-falocalrepo-database
+Version:	5.4.4
+Release:	1
+Summary:	Database functionality for falocalrepo.
+License:	EUPL-1.2
+URL:		https://github.com/FurryCoders/falocalrepo-database
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/08/6b/d11f509878dd32843c37a8c20498cbd8728df18d64d42fd68826fbc5bde5/falocalrepo_database-5.4.4.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-filetype
+Requires:	python3-chardet
+Requires:	python3-psutil
+
+%description
+<div align="center">
+
+<img alt="logo" width="400" src="https://raw.githubusercontent.com/FurryCoders/Logos/main/logos/falocalrepo-database-transparent.png">
+
+# FALocalRepo-Database
+
+Database functionality for [falocalrepo](https://pypi.org/project/falocalrepo).
+
+[![](https://img.shields.io/github/v/tag/FurryCoders/falocalrepo-database?label=github&sort=date&logo=github&color=blue)](https://github.com/FurryCoders/falocalrepo-database)
+[![](https://img.shields.io/pypi/v/falocalrepo-database?logo=pypi)](https://pypi.org/project/falocalrepo-database/)
+[![](https://img.shields.io/pypi/pyversions/falocalrepo-database?logo=Python)](https://www.python.org)
+
+</div>
+
+## Tables
+
+To store its information, the database uses separate tables: `USERS`, `SUBMISSIONS`, `JOURNALS`, `SETTINGS`,
+and `HISTORY`.
+
+**Note**: bar-separated lists are formatted as `|item1||item2|` to properly isolate all elements
+
+### Users
+
+The users' table contains a list of all the users that have been download with the program, the folders that have been
+downloaded, and the submissions found in each of those.
+
+Each entry contains the following fields:
+
+* `USERNAME` the URL username of the user (no underscores or spaces)
+* `FOLDERS` the folders downloaded for that specific user, sorted and bar-separated
+* `ACTIVE` `1` if the user is active, `0` if not
+* `USERPAGE` the user's profile in HTML or BBCode format
+
+### Submissions
+
+The submissions' table contains the metadata of the submissions downloaded by the program and information on their files
+
+* `ID` the id of the submission
+* `AUTHOR` the username of the author (uploader) in full format
+* `TITLE`
+* `DATE` upload date in ISO format _YYYY-MM-DDTHH:MM_
+* `DESCRIPTION` description in HTML or BBCode format
+* `FOOTER` footer in HTML or BBCode format
+* `TAGS` bar-separated tags
+* `CATEGORY`
+* `SPECIES`
+* `GENDER`
+* `RATING`
+* `TYPE` image, text, music, or flash
+* `FILEURL` a bar-separated list of the remote URLs for the submission files
+* `FILEEXT` a bar-separated list of extensions of the downloaded files. Can be empty if the file contained errors and
+  could not be recognised upon download
+* `FILESAVED` file and thumbnail download status as a 3bit flag:`xx1` if thumbnail was downloaded, `xx0` if not; `x1x`
+  if at least one file was valid `x0x` if not; `1xx` if all given files where valid, `0xx` if not. Possible values
+  are `0` through `7` (3 bit).
+* `FAVORITE` a bar-separated list of users that have "faved" the submission
+* `MENTIONS` a bar-separated list of users that are mentioned in the submission description as links
+* `FOLDER` the folder of the submission (`gallery` or `scraps`)
+* `USERUPDATE` `1` if the submission was added as a user update otherwise `0`
+
+### Journals
+
+The journals' table contains the metadata of the journals downloaded by the program.
+
+* `ID` the id of the journal
+* `AUTHOR` the username of the author (uploader) in full format
+* `TITLE`
+* `DATE` upload date in ISO format _YYYY-MM-DDTHH:MM_
+* `CONTENT` content in HTML or BBCode format
+* `HEADER` header in HTML or BBCode format
+* `FOOTER` footer in HTML or BBCode format
+* `MENTIONS` a bar-separated list of users that are mentioned in the journal content as links
+* `USERUPDATE` `1` if the journal was added as a user update otherwise `0`
+
+### Comments
+
+The comments' table contains the metadata of the journals and submissions stored in the database.
+
+* `ID` the id of the comment
+* `PARENT_TABLE` `SUBMISSIONS` if the comment relates to a submission, `JOURNAL` if the comment relates to a journal
+* `PARENT_ID` the id of the parent object (submission or journal)
+* `REPLY_TO` the id of the parent comment, if the comment is a reply
+* `AUTHOR` the username of the author in full format
+* `DATE` post date in ISO format _YYYY-MM-DDTHH:MM:SS_
+* `TEXT` the text of the comment
+
+### Settings
+
+The settings table contains settings for the program and variable used by the database handler and main program.
+
+* `COOKIES` cookies for the download program, stored in JSON format
+* `FILESFOLDER` location of downloaded submission files
+* `VERSION` database version
+
+### History
+
+The history table holds events related to the database.
+
+* `TIME` event time in ISO format _YYYY-MM-DDTHH:MM:SS.ssssss_
+* `EVENT` the event description
+
+## Submission Files
+
+The `save_submission` functions saves the submission metadata in the database and stores the files.
+
+Submission files are saved in a tiered tree structure based on their submission ID. IDs are zero-padded to 10 digits and
+then broken up in 5 segments of 2 digits; each of these segments represents a folder tha will be created in the tree.
+
+For example, a submission `1457893` will be padded to `0001457893` and divided into `00`, `01`, `45`, `78`, `93`. The
+submission file will then be saved as `00/01/45/78/93/submission.file` with the correct extension extracted from the
+file itself (FurAffinity links do not always contain the right extension and sometimes confuse JPEG and PNG).
+
+## Upgrading Database
+
+_Note:_ versions prior to 4.19.0 are not supported by falocalrepo-database version 5.0.0 and above. To update from
+those, use [falocalrepo v3.25.0](https://pypi.org/project/falocalrepo/v3.25.0) to upgrade the database to version
+4.19.0.<br/>
+_Note:_ Versions prior to 2.7.0 are not supported by falocalrepo-database version 3.0.0 and above. To update from those
+to the new version use [falocalrepo v2.11.2](https://github.com/FurryCoders/FALocalRepo/releases/tag/v2.11.2) to upgrade
+the database to version 2.7.0
+
+
+%package -n python3-falocalrepo-database
+Summary:	Database functionality for falocalrepo.
+Provides:	python-falocalrepo-database
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-falocalrepo-database
+<div align="center">
+
+<img alt="logo" width="400" src="https://raw.githubusercontent.com/FurryCoders/Logos/main/logos/falocalrepo-database-transparent.png">
+
+# FALocalRepo-Database
+
+Database functionality for [falocalrepo](https://pypi.org/project/falocalrepo).
+
+[![](https://img.shields.io/github/v/tag/FurryCoders/falocalrepo-database?label=github&sort=date&logo=github&color=blue)](https://github.com/FurryCoders/falocalrepo-database)
+[![](https://img.shields.io/pypi/v/falocalrepo-database?logo=pypi)](https://pypi.org/project/falocalrepo-database/)
+[![](https://img.shields.io/pypi/pyversions/falocalrepo-database?logo=Python)](https://www.python.org)
+
+</div>
+
+## Tables
+
+To store its information, the database uses separate tables: `USERS`, `SUBMISSIONS`, `JOURNALS`, `SETTINGS`,
+and `HISTORY`.
+
+**Note**: bar-separated lists are formatted as `|item1||item2|` to properly isolate all elements
+
+### Users
+
+The users' table contains a list of all the users that have been download with the program, the folders that have been
+downloaded, and the submissions found in each of those.
+
+Each entry contains the following fields:
+
+* `USERNAME` the URL username of the user (no underscores or spaces)
+* `FOLDERS` the folders downloaded for that specific user, sorted and bar-separated
+* `ACTIVE` `1` if the user is active, `0` if not
+* `USERPAGE` the user's profile in HTML or BBCode format
+
+### Submissions
+
+The submissions' table contains the metadata of the submissions downloaded by the program and information on their files
+
+* `ID` the id of the submission
+* `AUTHOR` the username of the author (uploader) in full format
+* `TITLE`
+* `DATE` upload date in ISO format _YYYY-MM-DDTHH:MM_
+* `DESCRIPTION` description in HTML or BBCode format
+* `FOOTER` footer in HTML or BBCode format
+* `TAGS` bar-separated tags
+* `CATEGORY`
+* `SPECIES`
+* `GENDER`
+* `RATING`
+* `TYPE` image, text, music, or flash
+* `FILEURL` a bar-separated list of the remote URLs for the submission files
+* `FILEEXT` a bar-separated list of extensions of the downloaded files. Can be empty if the file contained errors and
+  could not be recognised upon download
+* `FILESAVED` file and thumbnail download status as a 3bit flag:`xx1` if thumbnail was downloaded, `xx0` if not; `x1x`
+  if at least one file was valid `x0x` if not; `1xx` if all given files where valid, `0xx` if not. Possible values
+  are `0` through `7` (3 bit).
+* `FAVORITE` a bar-separated list of users that have "faved" the submission
+* `MENTIONS` a bar-separated list of users that are mentioned in the submission description as links
+* `FOLDER` the folder of the submission (`gallery` or `scraps`)
+* `USERUPDATE` `1` if the submission was added as a user update otherwise `0`
+
+### Journals
+
+The journals' table contains the metadata of the journals downloaded by the program.
+
+* `ID` the id of the journal
+* `AUTHOR` the username of the author (uploader) in full format
+* `TITLE`
+* `DATE` upload date in ISO format _YYYY-MM-DDTHH:MM_
+* `CONTENT` content in HTML or BBCode format
+* `HEADER` header in HTML or BBCode format
+* `FOOTER` footer in HTML or BBCode format
+* `MENTIONS` a bar-separated list of users that are mentioned in the journal content as links
+* `USERUPDATE` `1` if the journal was added as a user update otherwise `0`
+
+### Comments
+
+The comments' table contains the metadata of the journals and submissions stored in the database.
+
+* `ID` the id of the comment
+* `PARENT_TABLE` `SUBMISSIONS` if the comment relates to a submission, `JOURNAL` if the comment relates to a journal
+* `PARENT_ID` the id of the parent object (submission or journal)
+* `REPLY_TO` the id of the parent comment, if the comment is a reply
+* `AUTHOR` the username of the author in full format
+* `DATE` post date in ISO format _YYYY-MM-DDTHH:MM:SS_
+* `TEXT` the text of the comment
+
+### Settings
+
+The settings table contains settings for the program and variable used by the database handler and main program.
+
+* `COOKIES` cookies for the download program, stored in JSON format
+* `FILESFOLDER` location of downloaded submission files
+* `VERSION` database version
+
+### History
+
+The history table holds events related to the database.
+
+* `TIME` event time in ISO format _YYYY-MM-DDTHH:MM:SS.ssssss_
+* `EVENT` the event description
+
+## Submission Files
+
+The `save_submission` functions saves the submission metadata in the database and stores the files.
+
+Submission files are saved in a tiered tree structure based on their submission ID. IDs are zero-padded to 10 digits and
+then broken up in 5 segments of 2 digits; each of these segments represents a folder tha will be created in the tree.
+
+For example, a submission `1457893` will be padded to `0001457893` and divided into `00`, `01`, `45`, `78`, `93`. The
+submission file will then be saved as `00/01/45/78/93/submission.file` with the correct extension extracted from the
+file itself (FurAffinity links do not always contain the right extension and sometimes confuse JPEG and PNG).
+
+## Upgrading Database
+
+_Note:_ versions prior to 4.19.0 are not supported by falocalrepo-database version 5.0.0 and above. To update from
+those, use [falocalrepo v3.25.0](https://pypi.org/project/falocalrepo/v3.25.0) to upgrade the database to version
+4.19.0.<br/>
+_Note:_ Versions prior to 2.7.0 are not supported by falocalrepo-database version 3.0.0 and above. To update from those
+to the new version use [falocalrepo v2.11.2](https://github.com/FurryCoders/FALocalRepo/releases/tag/v2.11.2) to upgrade
+the database to version 2.7.0
+
+
+%package help
+Summary:	Development documents and examples for falocalrepo-database
+Provides:	python3-falocalrepo-database-doc
+%description help
+<div align="center">
+
+<img alt="logo" width="400" src="https://raw.githubusercontent.com/FurryCoders/Logos/main/logos/falocalrepo-database-transparent.png">
+
+# FALocalRepo-Database
+
+Database functionality for [falocalrepo](https://pypi.org/project/falocalrepo).
+
+[![](https://img.shields.io/github/v/tag/FurryCoders/falocalrepo-database?label=github&sort=date&logo=github&color=blue)](https://github.com/FurryCoders/falocalrepo-database)
+[![](https://img.shields.io/pypi/v/falocalrepo-database?logo=pypi)](https://pypi.org/project/falocalrepo-database/)
+[![](https://img.shields.io/pypi/pyversions/falocalrepo-database?logo=Python)](https://www.python.org)
+
+</div>
+
+## Tables
+
+To store its information, the database uses separate tables: `USERS`, `SUBMISSIONS`, `JOURNALS`, `SETTINGS`,
+and `HISTORY`.
+
+**Note**: bar-separated lists are formatted as `|item1||item2|` to properly isolate all elements
+
+### Users
+
+The users' table contains a list of all the users that have been download with the program, the folders that have been
+downloaded, and the submissions found in each of those.
+
+Each entry contains the following fields:
+
+* `USERNAME` the URL username of the user (no underscores or spaces)
+* `FOLDERS` the folders downloaded for that specific user, sorted and bar-separated
+* `ACTIVE` `1` if the user is active, `0` if not
+* `USERPAGE` the user's profile in HTML or BBCode format
+
+### Submissions
+
+The submissions' table contains the metadata of the submissions downloaded by the program and information on their files
+
+* `ID` the id of the submission
+* `AUTHOR` the username of the author (uploader) in full format
+* `TITLE`
+* `DATE` upload date in ISO format _YYYY-MM-DDTHH:MM_
+* `DESCRIPTION` description in HTML or BBCode format
+* `FOOTER` footer in HTML or BBCode format
+* `TAGS` bar-separated tags
+* `CATEGORY`
+* `SPECIES`
+* `GENDER`
+* `RATING`
+* `TYPE` image, text, music, or flash
+* `FILEURL` a bar-separated list of the remote URLs for the submission files
+* `FILEEXT` a bar-separated list of extensions of the downloaded files. Can be empty if the file contained errors and
+  could not be recognised upon download
+* `FILESAVED` file and thumbnail download status as a 3bit flag:`xx1` if thumbnail was downloaded, `xx0` if not; `x1x`
+  if at least one file was valid `x0x` if not; `1xx` if all given files where valid, `0xx` if not. Possible values
+  are `0` through `7` (3 bit).
+* `FAVORITE` a bar-separated list of users that have "faved" the submission
+* `MENTIONS` a bar-separated list of users that are mentioned in the submission description as links
+* `FOLDER` the folder of the submission (`gallery` or `scraps`)
+* `USERUPDATE` `1` if the submission was added as a user update otherwise `0`
+
+### Journals
+
+The journals' table contains the metadata of the journals downloaded by the program.
+
+* `ID` the id of the journal
+* `AUTHOR` the username of the author (uploader) in full format
+* `TITLE`
+* `DATE` upload date in ISO format _YYYY-MM-DDTHH:MM_
+* `CONTENT` content in HTML or BBCode format
+* `HEADER` header in HTML or BBCode format
+* `FOOTER` footer in HTML or BBCode format
+* `MENTIONS` a bar-separated list of users that are mentioned in the journal content as links
+* `USERUPDATE` `1` if the journal was added as a user update otherwise `0`
+
+### Comments
+
+The comments' table contains the metadata of the journals and submissions stored in the database.
+
+* `ID` the id of the comment
+* `PARENT_TABLE` `SUBMISSIONS` if the comment relates to a submission, `JOURNAL` if the comment relates to a journal
+* `PARENT_ID` the id of the parent object (submission or journal)
+* `REPLY_TO` the id of the parent comment, if the comment is a reply
+* `AUTHOR` the username of the author in full format
+* `DATE` post date in ISO format _YYYY-MM-DDTHH:MM:SS_
+* `TEXT` the text of the comment
+
+### Settings
+
+The settings table contains settings for the program and variable used by the database handler and main program.
+
+* `COOKIES` cookies for the download program, stored in JSON format
+* `FILESFOLDER` location of downloaded submission files
+* `VERSION` database version
+
+### History
+
+The history table holds events related to the database.
+
+* `TIME` event time in ISO format _YYYY-MM-DDTHH:MM:SS.ssssss_
+* `EVENT` the event description
+
+## Submission Files
+
+The `save_submission` functions saves the submission metadata in the database and stores the files.
+
+Submission files are saved in a tiered tree structure based on their submission ID. IDs are zero-padded to 10 digits and
+then broken up in 5 segments of 2 digits; each of these segments represents a folder tha will be created in the tree.
+
+For example, a submission `1457893` will be padded to `0001457893` and divided into `00`, `01`, `45`, `78`, `93`. The
+submission file will then be saved as `00/01/45/78/93/submission.file` with the correct extension extracted from the
+file itself (FurAffinity links do not always contain the right extension and sometimes confuse JPEG and PNG).
+
+## Upgrading Database
+
+_Note:_ versions prior to 4.19.0 are not supported by falocalrepo-database version 5.0.0 and above. To update from
+those, use [falocalrepo v3.25.0](https://pypi.org/project/falocalrepo/v3.25.0) to upgrade the database to version
+4.19.0.<br/>
+_Note:_ Versions prior to 2.7.0 are not supported by falocalrepo-database version 3.0.0 and above. To update from those
+to the new version use [falocalrepo v2.11.2](https://github.com/FurryCoders/FALocalRepo/releases/tag/v2.11.2) to upgrade
+the database to version 2.7.0
+
+
+%prep
+%autosetup -n falocalrepo-database-5.4.4
+
+%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-falocalrepo-database -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Wed May 10 2023 Python_Bot <Python_Bot@openeuler.org> - 5.4.4-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..92805c6
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+6afbc64f7315f9c9688a53aa80c583de  falocalrepo_database-5.4.4.tar.gz