Hi all,
my local build server 2.0 seems to be stuck on "source update
running", even though I haven't used any services yet.
Any way to abort/skip this step?
It's been this way for a couple of hours now...
--
later, Robert Xu
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi all,
I know that you can enable anonymous access from
/srv/www/obs/api/config/options.yml.
Is that all you have to do? I can't seem to get it to work.
--
later, Robert Xu
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi all,
I've just blogged about my Hackweek V project: osc bash completion
and I thought you might be interested :)
If you want to have a look, the blogpost is here:
http://lizards.opensuse.org/2010/06/15/hackweek-v-osc-bash-completion/
I won't repeat here what's been already written in the
blogpost, but let me just mention that
The script provides support for completing:
* osc subcommand names (checkout, commit, ...)
* global long osc options (e.g. --quiet, --debug, ...)
* long subcommand options
* project names
* package names (in given project)
* file names (in given project/package)
* repository names (openSUSE_Factory, ...)
* architectures (i586, x86_64, ...)
* ...
Best regards,
Petr
--
Petr Uzel
IRC: ptr_uzl @ freenode
present: aj, tschmidt, coolo, mls, adrian, mrueckert
Topics:
=======
* Upcoming releases
* Server stability problems
Upcoming releases
=================
* 2.0.1 this week
- just bugfixes
* 2.1 currently planned for 8th July
The release is driven by LinuxFoundation features for read access control.
Current open issues are:
- closing open access leaks
- implemented test suite for new access features.
* 2.2 release planned end of year
Big candidates are
- integrated QA system
- maintenance support
Planing and concept work is needed.
Server Instability
==================
We did run in OOM two times this night. The cause was high
memory usage of source server process. We run now with
ulimits, but we need to find out what calls are causing this.
Discussion about how to modify the "first login" page
=====================================================
Do we need to modify the "create your home page" to get
policy approval explicit ?
AI: mls ask legal how to approve account
--
Adrian Schroeter
SUSE Linux Products GmbH
email: adrian(a)suse.de
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
I want to create a project which is private to some group only but no success. Could someone shed some light on me? Thanks.
More particular, I have the following questions.
1) Is the OBS 1.8 RC5 the release version? I download them from http://download.opensuse.org/repositories/openSUSE:/Tools:/MeeGo/openSUSE_1…. If not, where should I get the release version?
2) There are 2 new flags are added for a project. "sourceaccess" and "privacy". What's mean for these 2? I believe I need to set to "enable" for "privacy" for a project. How about "souceaccess"
3) There are 2 new permissions too: "source_access" and "private_view". How do I use them?
4) After the project is created, who has and who does not have the privilege to read/write the project?
Actually, I am wandering, is there a manual for OBS, especially for the
role/permission part. Thanks.
Regards,
Dengyi Wang
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
just tried to update my staging system to obs 2.0 and get the following
conflicts (on SLE11):
#### YaST2 conflicts list - generated 2010-06-14 18:38:18 ####
nothing provides gpg2_signd_support needed by obs-signd-1.9.92-1.1.i586
[ ] do not install obs-signd-1.9.92-1.1.i586
obs-api-2.0.0-5.2.i586 requires rubygem-rails-2_3 = 2.3.5, but this
requirement cannot be provided
[ ] Following actions will be done:
do not install rubygem-rails-2_3-2.3.8-1.6.i586
do not install rubygem-actionmailer-2_3-2.3.8-2.6.i586
do not install rubygem-actionpack-2_3-2.3.8-3.6.i586
do not install rubygem-activerecord-2_3-2.3.8-2.4.i586
do not install rubygem-activeresource-2_3-2.3.8-1.5.i586
do not install rubygem-activesupport-2_3-2.3.8-2.4.i586
[ ] Following actions will be done:
do not install obs-api-2.0.0-5.2.i586
downgrade of obs-api-1.7.2-18.1.i586 to obs-api-1.6.0-0.4.1.i586
install obs-api-1.6.0-0.4.1.i586 (with vendor change)
openSUSE Build Service --> SUSE LINUX Products GmbH, Nuernberg, Germany
[ ] Ignore some dependencies of obs-api
#### YaST2 conflicts list END ###
--
With best regards,
Carsten Hoeger
Hi,
When I link a project, say if I link project B from A and then I try
osc branch B <pkg>
The packages is branched from A rather than from B...
I was expecting the pkg to come from B...
Anas
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi all,
build.opensuse.org has a Create/Manage Account link that lets people
register for iChain accounts, but
for us local OBS users who don't have such a system, is there any way
to allow public signups?
--
later, Robert Xu
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I've noted a slightly old thread where somebody asked about how to use
obssigner or obssignd. However, the problem was that there wasn't any
documentation; and there wasn't any discussion on how to set up the signer.
I'd be more than willing to help document the process on the build service
wikis -- if only I knew how to set it up. I can't find any documentation on
how to configure obssigner.
I've uncommented:
our $sign = '/usr/bin/sign';
from BSConfig.pm
I've tried putting the following into my /etc/sign.conf:
### for build service host
server: <my_real_ip_address>
user: obsbuild(a)foo.com
allowuser: obsrun
#
### for sign server
#allow: <IP of your build service host>
allow: <my_real_ip_address>
#phrases: /root/.phrases
When I start /etc/init.d/obssignd, it starts without throwing an error.
After I start /etc/init.d/obssigner, there is a new logfile created in:
/srv/obs/log/signer.log
This logfile has the following contents:
Name "BSConfig::sign_project" used only once: possible typo at
/usr/lib/obs/server//bs_signer line 96.
starting build service signer
waiting for an event...
When I try to create a key (from a project I've checked out), I get:
~/src/obs/myproject$ osc signkey --create
Server returned an error: HTTP Error 404: Not Found
don't know how to create a key
I'm using the packages in OpenSUSE:Tools, for openSUSE 11.2.
The packages I have are:
obs-service-download_url-0.1-7.1.noarch
obs-utils-1.7.5-1.1.x86_64
obs-common-1.7.0-1.1.x86_64
obs-api-1.7.5-1.1.x86_64
obs-worker-1.7.5-1.1.x86_64
obs-server-1.7.2-18.8.x86_64
obs-signd-1.7.0-5.1.x86_64
obs-source_service-1.7.5-1.1.x86_64
obs-productconverter-1.7.5-1.1.x86_64
Any hints?
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
The openSUSE Project is proud to announce the 1.8 and 2.0 releases of the
openSUSE Build Service (OBS). It is an open package and distribution
development platform that provides a transparent infrastructure that allows
developers to build for various major Linux distributions and hardware
architectures.
The public server http://build.opensuse.org is available for all open
source developers to build packages for the most popular distributions
including Debian, Fedora, Mandriva, openSUSE, Red Hat Enterprise Linux,
SUSE Linux Enterprise and Ubuntu. It is also used to build the openSUSE
and MeeGo distributions.
OBS 2.0's key features are a newly designed Web UI, anonymous access and an
enhanced request system. OBS 1.8 is an update to the 1.7 release driven by
the needs of the MeeGo project. Its major feature is access control
enforcement. The next OBS release 2.1 will also include the access control
enforcement, which is not yet in 2.0.
The completely refreshed Web UI for OBS 2.0 allows developers to work more
efficiently, as data is displayed where it is expected, and the Web service
loads faster and provides better access to projects, packages and meta
data.
Anonymous access in OBS 2.0 to all packages and projects offers great
convenience for users and more effectively promotes packages in the Build
Service to the world at large, enabling search engines to index the Build
Service as well. It also makes it easy to collaborate with other developers
to show them patches or log files.
With OBS 2.0, review handling by a team is supported and roles can get
assigned to groups instead of just to a single person.
The access control enforcement feature of OBS 1.8 allows access for
projects, packages and repositories to be restricted to specified users and
groups. This acknowledges privacy concerns of users.
"openSUSE Build Service has substantial momentum in the mobile and embedded
space, specifically being used now by the MeeGo project," said Amanda
McPherson, vice president marketing and developer services at the Linux
Foundation. "The Linux Foundation is proud to be a strong contributor to
OBS, including making substantial contributions to these new releases and
features. We look forward to working with our members on OBS-related
projects."
“The openSUSE Build Service 2.0 release is a significant improvement for
developers,” said Michael Löffler, chairperson of the openSUSE Board, “It
eases collaboration with the broader open source community due to
supporting anonymous access. Developers can get their job better done with
the new WebUI and the faster and more flexible OBS. ”
Users can use OBS 2.0 on the project's public server
http://build.opensuse.org or run it in their own on-premise infrastructure.
Deployment is possible directly from source code or from our appliance
image (http://en.opensuse.org/Build_Service/OBS-Appliance).
For additional information, please read the release notes for OBS 1.8
(http://www.gitorious.org/opensuse/build-
service/blobs/1.8/ReleaseNotes-1.8) and 2.0
(http://www.gitorious.org/opensuse/build-
service/blobs/2.0/ReleaseNotes-2.0).
--
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