On Tue, Jun 30, 2015 at 12:01:14PM +0200, Stephan Sürken wrote:
On Sa, 2015-06-27 at 21:11 +0200, Marc Haber wrote:
(...)
Currently, mini-buildd merely uses the django user management as-is, as
it comes for free, using the existing user/staff/superuser flags to have
some privilege
Hi Marc,
On Sa, 2015-06-27 at 21:11 +0200, Marc Haber wrote:
(...)
Currently, mini-buildd merely uses the django user management as-is, as
it comes for free, using the existing user/staff/superuser flags to have
some privilege handling for the API calls. Not a lot of extra code
needed.
Hi Marc,
On Sa, 2015-06-27 at 15:28 +0200, Marc Haber wrote:
(..)
when a normal user tries to remove a package from a repository, the
error message is 401 Unauthorized: API: 'remove': Needs superuser
login.
Please consider adding a user permission to do so, so that mini-buildd
can be
Source: mini-buildd
Version: 1.0.7
Severity: wishlist
Hi,
when a normal user tries to remove a package from a repository, the
error message is 401 Unauthorized: API: 'remove': Needs superuser
login.
Please consider adding a user permission to do so, so that mini-buildd
can be configured so that
On Sat, Jun 27, 2015 at 04:31:54PM +0200, Stephan Sürken wrote:
On Sa, 2015-06-27 at 15:28 +0200, Marc Haber wrote:
(..)
when a normal user tries to remove a package from a repository, the
error message is 401 Unauthorized: API: 'remove': Needs superuser
login.
Please consider adding
On Sa, 2015-06-27 at 17:54 +0200, Marc Haber wrote:
(...)
you can already achieve this by giving a normal user the superuser
flag (via the django admin interface).
Yes, but that would give the user many more privileges. I currently
cannot explain why, but my feeling says that this shuld be
retitle #790129 please add more finegrained user privileges
thanks
On Sat, Jun 27, 2015 at 06:48:57PM +0200, Stephan Sürken wrote:
On Sa, 2015-06-27 at 17:54 +0200, Marc Haber wrote:
(...)
you can already achieve this by giving a normal user the superuser
flag (via the django admin
7 matches
Mail list logo
