diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-tracprivatetickets.spec | 142 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 144 insertions, 0 deletions
@@ -0,0 +1 @@ +/TracPrivateTickets-2.3.0.tar.gz diff --git a/python-tracprivatetickets.spec b/python-tracprivatetickets.spec new file mode 100644 index 0000000..fa334a5 --- /dev/null +++ b/python-tracprivatetickets.spec @@ -0,0 +1,142 @@ +%global _empty_manifest_terminate_build 0 +Name: python-TracPrivateTickets +Version: 2.3.0 +Release: 1 +Summary: Modified ticket security for Trac. +License: BSD 3-Clause +URL: https://trac-hacks.org/wiki/PrivateTicketsPlugin +Source0: https://mirrors.aliyun.com/pypi/web/packages/bf/da/aa5552e0869e3b93d09d85fd2f6f3600ebc74563a5fc74a3d9ca3547dbb3/TracPrivateTickets-2.3.0.tar.gz +BuildArch: noarch + +Requires: python3-Trac + +%description +Allow users to only see tickets they are associated with. +There are three main permissions for this plugin: ``TICKET_VIEW_REPORTER``, +``TICKET_VIEW_CC``, and ``TICKET_VIEW_OWNER``. ``TICKET_VIEW_SELF`` is an +alias for all three of these. +With each permission, users will only be able to see tickets where they are +the person mentioned in the permission. So if a user has +``TICKET_VIEW_REPORTER``, they can only see tickets they reported. For +``TICKET_VIEW_CC``, they just have to be included in the CC list. +There are also group-based permissions: ``TICKET_VIEW_REPORTER_GROUP``, +``TICKET_VIEW_CC_GROUP``, and ``TICKET_VIEW_OWNER_GROUP``. These work in a +similar way to their non-group counterparts, except that you are granted +access if you share a group with the target user. For example, if ticket 1 was +reported by Allan, and Allan and Bob are both in the group company_foo, and +Bob has ``TICKET_VIEW_REPORTER_GROUP``, then Bob will be able to see ticket 1 +since he shares a group with the reporter. Each group-based permission is also +an alias for the normal one, so you do not have to grant both. +``TICKET_VIEW_GROUP`` is an alias for all the group-based permissions (and +therefore all the normal ones as well). +These extra permissions can only deny access, not allow it. This means the +user must still have ``TICKET_VIEW`` granted as normal. +Finally, users with ``TRAC_ADMIN`` will not be restricted by this plugin. +The meta-user "anonymous" also cannot be restricted by this plugin, as their +identity isn't known to be checked. Be sure to not grant ``TICKET_VIEW`` to +anonymous, or unauthenticated users will be able to see all tickets. + +%package -n python3-TracPrivateTickets +Summary: Modified ticket security for Trac. +Provides: python-TracPrivateTickets +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-TracPrivateTickets +Allow users to only see tickets they are associated with. +There are three main permissions for this plugin: ``TICKET_VIEW_REPORTER``, +``TICKET_VIEW_CC``, and ``TICKET_VIEW_OWNER``. ``TICKET_VIEW_SELF`` is an +alias for all three of these. +With each permission, users will only be able to see tickets where they are +the person mentioned in the permission. So if a user has +``TICKET_VIEW_REPORTER``, they can only see tickets they reported. For +``TICKET_VIEW_CC``, they just have to be included in the CC list. +There are also group-based permissions: ``TICKET_VIEW_REPORTER_GROUP``, +``TICKET_VIEW_CC_GROUP``, and ``TICKET_VIEW_OWNER_GROUP``. These work in a +similar way to their non-group counterparts, except that you are granted +access if you share a group with the target user. For example, if ticket 1 was +reported by Allan, and Allan and Bob are both in the group company_foo, and +Bob has ``TICKET_VIEW_REPORTER_GROUP``, then Bob will be able to see ticket 1 +since he shares a group with the reporter. Each group-based permission is also +an alias for the normal one, so you do not have to grant both. +``TICKET_VIEW_GROUP`` is an alias for all the group-based permissions (and +therefore all the normal ones as well). +These extra permissions can only deny access, not allow it. This means the +user must still have ``TICKET_VIEW`` granted as normal. +Finally, users with ``TRAC_ADMIN`` will not be restricted by this plugin. +The meta-user "anonymous" also cannot be restricted by this plugin, as their +identity isn't known to be checked. Be sure to not grant ``TICKET_VIEW`` to +anonymous, or unauthenticated users will be able to see all tickets. + +%package help +Summary: Development documents and examples for TracPrivateTickets +Provides: python3-TracPrivateTickets-doc +%description help +Allow users to only see tickets they are associated with. +There are three main permissions for this plugin: ``TICKET_VIEW_REPORTER``, +``TICKET_VIEW_CC``, and ``TICKET_VIEW_OWNER``. ``TICKET_VIEW_SELF`` is an +alias for all three of these. +With each permission, users will only be able to see tickets where they are +the person mentioned in the permission. So if a user has +``TICKET_VIEW_REPORTER``, they can only see tickets they reported. For +``TICKET_VIEW_CC``, they just have to be included in the CC list. +There are also group-based permissions: ``TICKET_VIEW_REPORTER_GROUP``, +``TICKET_VIEW_CC_GROUP``, and ``TICKET_VIEW_OWNER_GROUP``. These work in a +similar way to their non-group counterparts, except that you are granted +access if you share a group with the target user. For example, if ticket 1 was +reported by Allan, and Allan and Bob are both in the group company_foo, and +Bob has ``TICKET_VIEW_REPORTER_GROUP``, then Bob will be able to see ticket 1 +since he shares a group with the reporter. Each group-based permission is also +an alias for the normal one, so you do not have to grant both. +``TICKET_VIEW_GROUP`` is an alias for all the group-based permissions (and +therefore all the normal ones as well). +These extra permissions can only deny access, not allow it. This means the +user must still have ``TICKET_VIEW`` granted as normal. +Finally, users with ``TRAC_ADMIN`` will not be restricted by this plugin. +The meta-user "anonymous" also cannot be restricted by this plugin, as their +identity isn't known to be checked. Be sure to not grant ``TICKET_VIEW`` to +anonymous, or unauthenticated users will be able to see all tickets. + +%prep +%autosetup -n TracPrivateTickets-2.3.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-TracPrivateTickets -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Tue Jun 20 2023 Python_Bot <Python_Bot@openeuler.org> - 2.3.0-1 +- Package Spec generated @@ -0,0 +1 @@ +22627578607b9ab6630e39960e63cf5e TracPrivateTickets-2.3.0.tar.gz |