Hi, Just noticed that only project maintainers can branch from a linked project. When trying to branch a package from a linked project I am not a maintainer of, I get:
Server returned an error: HTTP Error 403: Forbidden. no permission to execute command 'branch' for not existing package
Since we use linked projects as a Testing facility where developers can submit changes for staging, this will not work since otherwise we would need to make everyone admin of that project...
Any ideas how to fix this? Anas-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Donnerstag, 30. September 2010, 10:13:20 schrieb Anas Nashif:
Hi, Just noticed that only project maintainers can branch from a linked project. When trying to branch a package from a linked project I am not a maintainer of, I get:
Server returned an error: HTTP Error 403: Forbidden. no permission to execute command 'branch' for not existing package
which code base is this exactly ?
The 2.1 beta 1 ?
I had to change quite a lot in current 2.1 branch afterwards and right now this seems to work according to my test cases.
I hope to be able to ship a Beta 2 tomorrow ...
bye adrian
Am Donnerstag, 30. September 2010, 10:22:54 schrieb Adrian Schröter:
Am Donnerstag, 30. September 2010, 10:13:20 schrieb Anas Nashif:
Hi, Just noticed that only project maintainers can branch from a linked project. When trying to branch a package from a linked project I am not a maintainer of, I get:
Server returned an error: HTTP Error 403: Forbidden. no permission to execute command 'branch' for not existing package
which code base is this exactly ?
Sorry, I just see 2.0.6 ...
Can you do a "osc -H branch ..." and tell me what the error code is ?
Something like create_project_no_permission, create_package_no_permission or create_package_no_permission
Am Donnerstag, 30. September 2010, 10:27:42 schrieb Adrian Schröter:
Am Donnerstag, 30. September 2010, 10:22:54 schrieb Adrian Schröter:
Am Donnerstag, 30. September 2010, 10:13:20 schrieb Anas Nashif:
Hi, Just noticed that only project maintainers can branch from a linked project. When trying to branch a package from a linked project I am not a maintainer of, I get:
Server returned an error: HTTP Error 403: Forbidden. no permission to execute command 'branch' for not existing package
which code base is this exactly ?
Sorry, I just see 2.0.6 ...
Can you do a "osc -H branch ..." and tell me what the error code is ?
Something like create_project_no_permission, create_package_no_permission or create_package_no_permission
I see the bug ...
However, I would like to avoid to apply the fix in 2.0 branch, because it is large and I would also need to backport quite some test cases to avoid regressions.
It definitive works in 2.1 already, is it an option to wait for that for you ?
bye adrian
On 2010-09-30, at 9:31 AM, Adrian Schröter wrote:
Am Donnerstag, 30. September 2010, 10:27:42 schrieb Adrian Schröter:
Am Donnerstag, 30. September 2010, 10:22:54 schrieb Adrian Schröter:
Am Donnerstag, 30. September 2010, 10:13:20 schrieb Anas Nashif:
Hi, Just noticed that only project maintainers can branch from a linked project. When trying to branch a package from a linked project I am not a maintainer of, I get:
Server returned an error: HTTP Error 403: Forbidden. no permission to execute command 'branch' for not existing package
which code base is this exactly ?
Sorry, I just see 2.0.6 ...
Can you do a "osc -H branch ..." and tell me what the error code is ?
Something like create_project_no_permission, create_package_no_permission or create_package_no_permission
header: X-Opensuse-Errorcode: cmd_execution_no_permission
I see the bug ...
However, I would like to avoid to apply the fix in 2.0 branch, because it is large and I would also need to backport quite some test cases to avoid regressions.
It definitive works in 2.1 already, is it an option to wait for that for you ?
I already applied a local hack, but would prefer to backport a real solution until we move to 2.1 since this is required for us now.
Anas
bye adrian
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Donnerstag, 30. September 2010, 10:36:02 schrieb Anas Nashif:
On 2010-09-30, at 9:31 AM, Adrian Schröter wrote:
...
I see the bug ...
However, I would like to avoid to apply the fix in 2.0 branch, because it is large and I would also need to backport quite some test cases to avoid regressions.
It definitive works in 2.1 already, is it an option to wait for that for you ?
I already applied a local hack, but would prefer to backport a real solution until we move to 2.1 since this is required for us now.
Hm, please test the applied patch (I have not tested it at all).
It would be a minimal invasive (but also not cover all cases, for example when target package exists already), but should work in most cases.
bye adrian
On 2010-09-30, at 9:46 AM, Adrian Schröter wrote:
Am Donnerstag, 30. September 2010, 10:36:02 schrieb Anas Nashif:
On 2010-09-30, at 9:31 AM, Adrian Schröter wrote:
...
I see the bug ...
However, I would like to avoid to apply the fix in 2.0 branch, because it is large and I would also need to backport quite some test cases to avoid regressions.
It definitive works in 2.1 already, is it an option to wait for that for you ?
I already applied a local hack, but would prefer to backport a real solution until we move to 2.1 since this is required for us now.
Hm, please test the applied patch (I have not tested it at all).
It would be a minimal invasive (but also not cover all cases, for example when target package exists already), but should work in most cases.
Does not work :(
reply: 'HTTP/1.1 400 Bad Request\r\n' header: Connection: close header: X-Opensuse-APIVersion: 2.0 header: Content-Type: application/xml; charset=utf-8 header: X-Opensuse-Errorcode: unknown header: Content-Length: 183 header: Cache-Control: no-cache header: Date: Thu, 30 Sep 2010 13:39:55 GMT header: Server: lighttpd/1.4.20 Server returned an error: HTTP Error 400: Bad Request uncaught exception: private method `split' called for nil:NilClass
and in the log:
NoMethodError (private method `split' called for nil:NilClass): app/models/db_project.rb:512:in `find_parent_for' app/models/user.rb:215:in `can_create_project?' app/controllers/source_controller.rb:260:in `index_package' public/dispatch.fcgi:24
[E|#15305] rescue_action: caught NoMethodError: private method `split' called for nil:NilClass [I|#15305] Rendering status [I|#15305] errorcode 'unknown' - uncaught exception: private method `split' called for nil:NilClass [I|#15305] Rendering status (400)
bye adrian
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de <2.0_branch_fix.diff>
Am Donnerstag, 30. September 2010, 15:43:37 schrieb Anas Nashif:
On 2010-09-30, at 9:46 AM, Adrian Schröter wrote:
Am Donnerstag, 30. September 2010, 10:36:02 schrieb Anas Nashif:
On 2010-09-30, at 9:31 AM, Adrian Schröter wrote:
...
I see the bug ...
However, I would like to avoid to apply the fix in 2.0 branch, because it is large and I would also need to backport quite some test cases to avoid regressions.
It definitive works in 2.1 already, is it an option to wait for that for you ?
I already applied a local hack, but would prefer to backport a real solution until we move to 2.1 since this is required for us now.
Hm, please test the applied patch (I have not tested it at all).
It would be a minimal invasive (but also not cover all cases, for example when target package exists already), but should work in most cases.
Does not work :(
okay, take two ... much simpler ...
buildservice@lists.opensuse.org
-
Adrian Schröter -
Anas Nashif