Hi,
as a few of you already noticed we work on a new OBS Webclient design.
New design means roughly improved...
... workflow.
... usability.
... look &feel.
We collect the results of our work at http://en.opensuse.org/Build_Service/WebClientIdeas
.
It's work in progress so there is still missing content.
I would appreciate a good discussion during the design-process and
many suggestions ;-)
If you have functionality which is now missing in the Webclient please
let me know.
Some possible functionality is already listed unter http://en.opensuse.org/Build_Service/WebClientIdeas#Functionality
.
Also interesting would be some input about the things you mainly do
with the Webclient or you would like to do.
Best,
Robert
---
Robert Lihm, Webdesigner - Build Service Team
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
Tel: +49-911-74053-0 - rlihm(a)suse.de
____________________________________________________________
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
____________________________________________________________
SUSE - a Novell business
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Since the network:telephony project doesn't build for SLES-9, I'm
trying to build a package (zaptel) for SLES-9 myself.
First attempt: run 'osc build SLES-9 i586' on an openSUSE 10.3
machine. This didn't work:
-> + exec rpmbuild -ba --eval '%define _srcdefattr (-,root,root)'
/usr/src/packages/SOURCES/zaptel.spec
-> error: line 27: Unknown tag: %suse_kernel_module_package -p
/usr/src/packages/SOURCES/preamble kdump um iseries64 ppc64 debug xen
Hmm, OK maybe you must build on the same machine that you're
targeting? (is that true?)
Second try: run 'osc build' on a SLES-9 machine.
-> There is no 'osc' in openSUSE:Tools for SLES-9.
-> For some reason 'osc' is disabled in openSUSE:Tools project for
SLES-9 (only).
Third try: use SLES-9 version of 'osc' from maw's home project. Nope:
-> $ osc co network:telephony
-> Traceback (most recent call last):
-> File "/usr/bin/osc", line 7, in ?
-> from osc import commandline
-> File "/usr/lib64/python2.3/site-packages/osc/commandline.py", line 78
-> @cmdln.alias('ls')
-> ^
-> SyntaxError: invalid syntax
I've run out of ideas, other than building remotely on the OBS
servers. Is there a way to build packages for SLES-9 locally... ?
Thanks,
-Archie
--
Archie L. Cobbs
---------------------------------------------------------------------
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 will be down on wednesday. (in two days).
We will be back with a new storage system and current build service server
code from svn. There was quite some code changes after 1.0 already in svn :)
bye
adrian
--
Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
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've just installed openSUSE:11.0 with obs
Works fine and obs is running :)
In the docs of obs-spi README.SETUP, there is a Test mentioned:
...
6.1. Test build
===============
You can do a test build like this:
(in a svn co of the current openSUSE build server, in the
buildservice/dist subdir)
What does this mean? I did not get it. Sorry, need some advice
....
Now prepare for a check-in. This will do a checkout and locally build
using the packages from your local buildserver:
OBSOPT="-A http://127.0.42.2" ./distribute
So where comes distribute from. It's not part of the obs-packages nor
workers-package
...
Any help welcome
--
_
Stefan Werden
-----------------------------------------------------------------
-----------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello!
I just generated the package yacy-test for mandriva. I can see the packages in
the webinterface, but the folder for the mandriva repository is not
generated. It should be
http://download.opensuse.org/repositories/home://f1ori/Mandriva_2008
What's wrong there?
Thanks,
Florian
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
I want to build a '_link' package locally. 'osc build' doesn't work
because it expects to find a spec file (none exists).
Is there a way to do this?
Thanks,
-Archie
--
Archie L. Cobbs
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
Martin Mohring, one of our busy contributors and testers of
openSUSE:Tools pointed out that he had created an openSUSE:Tools:Devel
project on his build server because he had noticed that quite a few
people use openSUSE:Tools:UNSTABLE and he doesn't want to break them
while they are using more extensive testing.
As I like three staged integration environments (one for Development,
one for Testing and one for Release), and as openSUSE:Tools:UNSTABLE
actually is that Testing environment for many, I've added a devel
stage:
https://build.opensuse.org/project/show?project=openSUSE%3ATools%3ADevel
So now we have
openSUSE:Tools
the currently recommended, released version
openSUSE:Tools:UNSTABLE
the upcoming release, an ongoing beta version
openSUSE:Tools:Devel
very current packages, svn snapshots, this may break at any
time, only use this if you are actively participating in
development and alpha testing
A proposed release process is to first submit new package versions to
Devel and announce updates on opensuse-buildservice(a)o.o
Then 'good' versions of the packages that seem to work together go to
UNSTABLE for broader beta testing.
Once that has stabilized it is moved over to openSUSE:Tools as new
release.
This also allows to remove the build-svn, osc-svn and obs-server-svn
packages: they now can go to "Devel" under teir 'real' names (without
-svn).
Hey, with repo priorities you could even subscribe to just the Tools
repo to be user, to Tools and UNSTABLE to be a beta tester and to
all three, Tools, UNSTABLE and Devel as developer :)
Not sure how these repo priorites can be set easily, though?
S.
--
Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business
OPS Engineering Maxfeldstraße 5
Processes and Infrastructure Nürnberg
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
present: mjung, rlihm, jcborn, tpatzig, froh, abauer, freitag, adrian, poeml,
mls
Topics
======
* general status
* discussion about submission requests handling
Status:
=======
abauer:
* Worked on hermes/starship. General code cleanup
* Worked for Martin and Zonker on promo dvd order interface. Will go
online today.
* Introduced new request state "revoked" which is an allowed action for
submitter.
freitag:
* Work on architecture change in hermes to allow personalized submissions.
Target is to have personalized messages running until end of week.
* Designed filter system for hermes.
mjung:
* Did talk about trust system.
* Discussing about details.
rlihm:
* Worked on web client UI change wiki page.
jcborn:
* Worked on architecture list modularization. This describes the fallback
architecture for a given one, what is currently in plenty places.
* working on support for script running from meta packages during product
creation.
mls:
* fixed breaking of sources due to submission to openSUSE:Factory.
poeml:
* fixed an issue removing local changes when source link breaks on server.
adrian:
* kiwi build works again using new kiwi version and obs:// url descriptors for
preference files and repositories.
-> working on support in worker for kiwi config inheritence.
* Got multiple good news regarding new hardware for OBS. We will get new stuff
in all areas :)
Discussion about request handling:
==================================
* Should submitters be allowed to change the complete request ?
Yes, to allow to keep the history
Problem is that accept switch should not be allowed and that the request is
changing during review phase.
Decision: Using Review state to disallow changes by submitter.
Change to Accept must not
--
Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
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,
How can I maintain the executable mode of a file when I check it in into
the build service?
Some RPMs have scripts that are called directly from the spec file,
build fails because the files can't be executed due to bad permissions.
Thanks,
Anas
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org