Freshly updated to 1.7.5.
'osc my rq' gave a traceback:
Traceback (most recent call last):
File "/usr/bin/osc", line 21, in <module>
r = babysitter.run(osccli)
File "/usr/lib/python2.6/site-packages/osc/babysitter.py", line 47, in run
return prg.main()
File "/usr/lib/python2.6/site-packages/osc/cmdln.py", line 308, in main
return self.cmd(args)
File "/usr/lib/python2.6/site-packages/osc/cmdln.py", line 331, in cmd
retval = self.onecmd(argv)
File "/usr/lib/python2.6/site-packages/osc/cmdln.py", line 447, in onecmd
return self._dispatch_cmd(handler, argv)
File "/usr/lib/python2.6/site-packages/osc/cmdln.py", line 1177, in
_dispatch_cmd
return handler(argv[0], opts, *args)
File "/usr/lib/python2.6/site-packages/osc/commandline.py", line
3958, in do_my
exclude_projects, what.has_key('project'), what.has_key('package'))
File "/usr/lib/python2.6/site-packages/osc/core.py", line 4695, in
get_user_projpkgs
if e.code != 400 or not role_filter:
NameError: global name 'role_filter' is not defined
osc version: 0.126
--
Jon
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
JFYI,
Fedora 13 and Ubuntu 10.04 are available on build.opensuse.org now.
good morning
adrian
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian(a)suse.de
Hi, All
As we using obs/osc in Moblin/MeeGo development, we have maintained
several internal used plugins to support new commands for special
usage. One of the most used one, 'mobsr' (stands for
moblin-send-request), is a wrapper to the built-in 'sr' command and
with extra checking and function to send mail to mailing list.
We consider the sendmail feature can be a generic enhancement to
original 'sr' command, so I am trying to rewrite the code based on
upstream osc git. The following is my personal clone of git tree, with
three new commits on the tip to implement it:
http://gitorious.org/~jfding/opensuse/jfdings-osc/commits/master
More details of these commits:
If user specifying both:
'commit_mailing_list' (the mail address for mailing list)
and:
'smtp_server' (address of smtp server),
'sendrequest' commmand will send declaration mails to this mailing list
for each new request.
And, two new conf key: 'commit_mailing_list' and 'smtp_server'
'smtp_server' is a global [general] key, with default value ""
'commit_mailing_list' can be either a global key, or a apiurl
section key, and global value can be overrided by apiurl
special one if specified.
Any advice please, thanks!
Regards,
JF Ding (Intel, OTC)
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
The openSUSE Build Service (obs) is an open package and distribution
development platform that provides a transparent infrastructure that allows
developers to build for various major Linux distributions and
architectures.
The public server build.opensuse.org is available for all open source
developers to build packages for the most popular distributions incl.
Debian, Fedora, Mandriva, openSUSE, Red Hat, SUSE Linux Enterprise and
Ubuntu. It is also used to build the openSUSE distribution.
This is the first beta release of version 2.0. Version 2.0 is planned to be
released on June 10th. We have updated the public server
http://build.opensuse.org with the current code stream as part of our
testing. We invite others running a build service to test the code and give
feedback via the opensuse-buildservice mailing list and report bugs in
bugzilla.
Beta1 is feature complete, new features will go in the next major release
(release planned for end of 2010), we will concentrate on fixing bugs now.
Beta1 includes the following major changes:
New Web UI Tailor-Made for Packagers
The new Web UI makes your work more efficient as stuff is where it is
expected, it loads faster and gives you a better access to projects,
packages and meta data.
Public Read Access For Convenient Collaboration
Anonymous access gets you to packages and projects without log-in. This is
pretty convenient for the users and promotes all packages in the Build
Service more to the world as now search engines can index the Build Service
as well. It makes it also easy to collaborate with other developers to show
them your patches or log files.
New Features for Cooperation in a Team
With obs 2.0 review handling by a team is possible and roles can get
assigned to groups instead of just to a single person.
Additional Changes
The full list of changes is available as part of the OBS Roadmap and
includes also the following enhancements:
* An easy way to view unsubmitted changes in development projects or
new upstream releases. This is used especially for our openSUSE
distribution development.
* The request system has been enhanced: A new request type to add or
change the user list of packages or projects has been added. Also review
handling is now possible to allow a team to review changes prior to
accepting a request.
* Developers can receive notifications if one of their package gets
branched by others.
* Improved source handling: It’s possible to undelete packages. Meta
data are now under version control.
* The build service has seen many speedups so that packages get build
faster.
You can try the obs 2.0 beta1 either on http://build.opensuse.org or in
your own infrastructure. Deployment is possible directly from source code
or from our combined server and worker virtual appliance image.
Thanks!
This is a release where many different people were involved in development
and even more in testing by using the openSUSE instance. We received also a
number of good feature requests that got implemented. Thanks to everybody
that participated!
I’d like to give special credit for the great WebUI work done by the
Boosters team, mainly Coolo and Tom!
Andreas
--
Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org}
Twitter: jaegerandi | Identica: jaegerandi
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
We, the openSUSE Build Service development team are happy to declare
OBS 2.0 feature complete.
OBS 2.0 Beta 1 can be downloaded as usual from openSUSE:Tools:Unstable
project:
https://build.opensuse.org/project/show?project=openSUSE:Tools:Unstable
2.0 Beta 1 packages are marked as version 1.9.90. The same is true for
the OBS Appliance, which can be used to evaluate OBS or to run it in
a productive enviroment. Please find the OBS appliance here as usual:
http://wiki.opensuse.org/openSUSE:Build_Service_Appliance
The next beta will be release on friday this week, the final release is
estimated on 10th June.
Please find details about this release from the Release Notes.
Updaters should also read the README.UPDATERS file.
Extract from the release notes (consider them also as Beta for now ;)
Reqgressions:
=============
* read access control feature enhancements of MeeGo branch (1.8 in git)
are not included with this release.
Do *NOT* update from 1.8 to this release.
We will merge these branches in a later release.
* API calls which got deprecated with 1.0 release got removed:
/platform (use /build or /search/repository_id instead)
/repository (use /build or /search/repository_id instead)
/project (use /source instead)
/package (use /source instead)
Features:
=========
* Revised webui, new layout with more funcationality.
* Anonymous access mode for webui
=> to be configured in api config/options.yml
* Improved permission system:
- User group support for roles and requests
* Improved request system:
- Review mechanism
- New "reviewer" role to set default reviewers for a package or project.
These can be users or groups.
http://en.opensuse.org/Build_Service/Concepts/Review
- New requests types for
- set bugowner
- add role
* Project link mechanism
http://en.opensuse.org/Build_Service/Concepts/ProjectLinking
* Build job strategies got configurable
http://en.opensuse.org/Build_Service/Concepts/BuildSchedulingStrategies
* New fair build job dispatcher is distribution the jobs based on importance
and former used build times now.
* Build cycle dependencies are accessable via api and webui now.
* History for meta files like _meta and _prjconf
* Project/Package undelete feature
* Source service are stabelized
- default services for downloading files and to verify them are available.
* Lots of smaller improvements and bugfixes
Changes:
========
* xml files are validated by the api
* "expansion error" state got renamed to "unresolved".
* New "signing" state.
* For cross architecture compiling support:
CBpreinstall and CBinstall prjconf directives added.
- CBPreinstall: add to preinstall section if emulator_arch
- CBinstall: add to install section if emulator_arch
- as with VMinstall, there's no dependency resolution.
Add all needed dependencies manually.
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian(a)suse.de
Hello Mates,
i´m just working in my home:saigkill:medical Repository. I´ve deleted
libqt4 there and OBS says that it is successfully deleted. But if i try
to link libqt4 from KDE:Qt to my Repo, OBS says that the Package already
exists.
Maybe i make anything false?
--
Sincerely yours
Sascha Manns
open-slx GmbH
openSUSE Community & Support Agent
openSUSE Marketing Team
Blog: http://saigkill.wordpress.com
Web: http://www.open-slx.de (openSUSE Box Support German)
Web: http://www.open-slx.com (openSUSE Box Support English)
Using 1.7.4
I tried to use the import script to import a newly setup project, but
the script crashed:
/usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/session/cookie_store.rb:163:in
`ensure_session_key': A key is required to write a cookie containing
the session data. Use config.action_controller.session = { :key =>
"_myapp_session", :secret => "some secret phrase" } in
config/environment.rb (ArgumentError)
from /usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/session/cookie_store.rb:74:in
`initialize'
from /usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/middleware_stack.rb:72:in
`new'
from /usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/middleware_stack.rb:72:in
`build'
from /usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/middleware_stack.rb:116:in
`build'
from /usr/lib64/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/inflector.rb:361:in
`inject'
from /usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/middleware_stack.rb:116:in
`each'
from /usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/middleware_stack.rb:116:in
`inject'
from /usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/middleware_stack.rb:116:in
`build'
from /usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:130:in
`build_middleware_stack'
from /usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:81:in
`initialize'
from /usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:51:in
`new'
from /usr/lib64/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/dispatcher.rb:51:in
`run_prepare_callbacks'
from /usr/lib64/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:631:in
`prepare_dispatcher'
from /usr/lib64/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:185:in
`process'
from /usr/lib64/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:113:in
`send'
from /usr/lib64/ruby/gems/1.8/gems/rails-2.3.5/lib/initializer.rb:113:in
`run'
from import:18
--
Jon
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
For the last year or so I have been maintaining the package for the
Falcon programming language [1] in openSUSE:Contrib:Factory [2] as
well as a number of supplementary packages, module and tools for it in
my home project [3] (the ones prefixed with 'falcon-'). I would like
to request the creation of a new project under devel:languages called
falcon (i.e. alongside similar projects for Python, R, Haskell etc.)
to place these supplementary packages.
Also, while I'm here I'm wondering about the status of Contrib. I've
heard that it is no longer really necessary and instead packages
should request inclusion in openSUSE proper. I was wondering about
how/if to do that for the main falcon package.
Regards,
Matt Williams
[1] http://falconpl.org
[2] https://build.opensuse.org/package/show?package=falcon&project=openSUSE%3AF…
[3] https://build.opensuse.org/project/show?project=home%3AMilliams
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
since the /stage area recently moved to the webroot - noticed by the
style change on http://build.opensuse.org/ - there's the first problem.
Clicking on "login" does not do anything. Javascript is turned on, but
I'm not going to bughunt that any further.
Please, don't put javascript into essential places like those.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org