October 2012 - openSUSE Build Service - openSUSE Mailing Lists

Re: [opensuse-buildservice] Stalled submit requests
by Matwey V. Kornilov 18 Feb '15

18 Feb '15

Hm... You have inspired me to try this on the coming weekend. :) With obs rest/xml api, I need a tiny python script to manage all the things out. It is easy, you're right. 2012/10/18 Jos Poortvliet <jos(a)opensuse.org>: > On Sunday, October 07, 2012 12:09:43 Matwey V. Kornilov wrote: > >> Hi, > >> > >> Is there a page to see full list of submit requests, ordered by date? This > >> statistics is of quite interest. > >> > >> For instance, there is no reaction for two month: (It is not ok for devel: > >> project, I think) > >> > >> >> https://build.opensuse.org/project/requests?project=network%3Amessaging%3Aam > >> qp > >> > >> I think, having such a page, such statistics, one would be able to > >> redistribute his power. > > > > Not a bad idea at all - it'd nice to show which projects need some help, > which are doing very well etcetera. Maybe a top-ten of fastest SR/MR > solvers, too ;-) > > > > Crazy idea: Adrian responded to you that it is possible to request this info > from the API. If you got the skillzz to do that, it'd be nice to publish > those statistics somewhere - and that part I could help with. Something like > a weekly overview of the health of the OBS projects and stuff like that. > > > > Up for it? > > > > /Jos -- With best regards, Matwey V. Kornilov http://0x2207.blogspot.com xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 9

[opensuse-buildservice] Open Build Service(OBS) 2.3.4 released
by Adrian Schröter 17 Feb '15

17 Feb '15

Open Build Service(OBS) 2.3.4 just got released =============================================== This is a bugfix release in first place. But also the distribuition default target list has been updated. This release is most important for cross build support. Building against openSUSE 12.2 and Factory for ARM architecture works now out-of-the-box. OBS 2.3.4 is published in "openSUSE:Tools" project: http://download.opensuse.org/repositories/openSUSE:Tools/ Appliances can be used as usual: http://en.opensuse.org/openSUSE:Build_Service_Appliance Release Notes: ============== Feature backports: ================== * Added "Hostarch" in _buildinfo for osc local builds of cross builds Changes: ======== * package meta creation of package copy command is not copying relationships and devel definitions anymore. * Added openSUSE 12.2 to default target list * Removed openSUSE 11.4 from default target list (EOL soon) * Fedora 15 is EOL, removed from default list Bugfixes: ========= * backend: allow access to access protected project repositories when users are in both projects. * backend: increase vrev on package source copy * webui: fixed underscores in code listings * webui: Do not expose user email address in anonymous mode * obsworker: do not fail when no /etc/sysconfig/proxy exists * build: fixed cross architecture initilisation for chroot builds -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] Expired OBS Keys?
by King Thorin 02 Jul '13

02 Jul '13

It seems the OBS Security key (keyid 79EAFD54) on keys.gnupg.net has expired (2011-Apr-2). Would it be possible for someone to update it? I know an updated key has been generated (which expires 2013) as it can be found here: http://download.opensuse.org/repositories/security:/OpenVAS:/STABLE:/v4/xUb… Further details can be found via: http://lists.wald.intevation.org/pipermail/openvas-distro/2011-April/thread… Basically the issue came to light when following instructions: http://www.openvas.org/install-packages.html#openvas4_ubuntu_obs -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 7

[opensuse-buildservice] New project openSUSE:Current?
by Cristian Morales Vega 18 Mar '13

18 Mar '13

Sometimes you have appA in your repo building for both old and new openSUSE versions. appA depends on libA > X, but only the latest openSUSE version provides it. openSUSE <latest-1> came with libA <X-1>. The solution is to package libA > X for the old distributions and usually you do that linking to the devel project. I would like an openSUSE:Current project that would always contains the latest supported version of the packages. Right now the packages from openSUSE:12.1:Update, but once 12.2 is released it should be changed to openSUSE:12.2:Update. This way I could link to those packages instead of linking to the devel project. It would let me compile appA in old distros while giving to the users a libA package that is not soooooo unsupported (this would be officially unsupported anyway, but...). I would like this since it's a single place to change when a new openSUSE version is released (If needed I can do it). Looking at the openSUSE:12.1:Update project metadata I guess it would just need be something like <project name="openSUSE:Current"> <title>Current version of openSUSE</title> <description></description> <link project="openSUSE:12.1:Update"/> <debuginfo> <enable/> </debuginfo> </project> But I'm not sure since I never really saw a doc explaining the meaning of <link> in the *project metadata*, only in _link files. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 8

[opensuse-buildservice] Problem building Perl packages for SLES11SP2 with certain build requirements
by Joschi Brauchle 21 Nov '12

21 Nov '12

Hello everyone, I have a question/problem with Perl packages and BuildRequires when building for SLES(SP2). The problem comes up with multiple packages when trying to build them for SLES, let's look at perl-HTTP-BrowserDetect from devel:languages:perl for example. The spec files includes: --- BuildRequires: perl(Module::Build) >= 0.3601 --- and the build log clearly states (see https://build.opensuse.org/package/rawlog?arch=x86_64&package=perl-HTTP-Bro…) that it is being installed: --- installing perl-Module-Build-0.36.07-4.1 --- but still, the build fails with: --- Module::Build version 0.3601 required--this is only version 0.280801 at Build.PL line 5. --- As far as I understand, "Module::Build" v0.280801 is already installed by default under SLES11SP2 and the newer required version 0.3607 is not found OR the older version is found first by the script "Build.pl". A second example would be "perl-POE-Test-Loops" which requires a version of Test::More/Test::Simple >=0.94, but this is not found although installed (i.e. only an older version is found), see log here: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=perl-… How do I circumvent this problem? Thanks for your help!

4 7

[opensuse-buildservice] JFYI: we are using ext4 now
by Adrian Schröter 05 Nov '12

05 Nov '12

JFYI, by default all build instances are using ext4 instead of ext3 file system now. We did this switch for all distros to support SSD disks better. There is a little chance that this might influence build results, so it should not. However, please report if you spot a problem. We may do the switch only for selected distributions in that case. thanks adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 11

[opensuse-buildservice] [PATCH0/0] raw_input checks if stdin is tty
by Michal Vyskocil 05 Nov '12

05 Nov '12

Hi community, The biggest problem during usage and testing of a remote build feature is the fact osc asks user several times for the input. In this case, remote process simply hangs and waits for the response, which is not even displayed, because of stdout buffering. The samy apply for non-interactive usage - if osc is called from a script, then it hangs waiting on something on stdin, which will never come. Therefor I've added a simple check os.isatty(sys.stdin.fileno()) to the osc.core.raw_input() - in case it's not terminal, the new RawInputError is raised. It will show-up the question on stderr and program will be terminated. I'd say there is some non-interactive osc feature requested by L3 team, which can be partially solved by this patch @milan, can you follow up? BTW: I've added the osc.core.raw_input to oscssl.py and build.py as well, to enforce the new behavior. The cmdln.py remains untouched, because I was not sure if this code is even used by osc. Michal Vyskocil (1): raw_input checks if stdin is tty osc/build.py | 1 + osc/core.py | 2 ++ osc/oscerr.py | 8 ++++++++ osc/oscssl.py | 2 ++ 4 files changed, 13 insertions(+) -- 1.7.10.4

2 4

[opensuse-buildservice] Ubuntu 12.10
by Srivats P 01 Nov '12

01 Nov '12

When can we expect Ubuntu 12.10 to be available on OBS? Srivats -- http://ostinato.org/ @ostinato -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 5

[opensuse-buildservice] Fedora:17 - have choice for libatlas
by Matwey V. Kornilov 01 Nov '12

01 Nov '12

Hi, I got "have choice for libatlas.so.3 needed by gsl: atlas-sse2 atlas-sse3 atlas-sse atlas-3dnow atlas". It seems slightly different packaging style. So "Prefer:" field is required here in project conf. As far as I understand, there are different versions for different optimizations. That is, it doesn't play a role for building, because ABI is compatible. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] prjconf Order does not work?
by Jiri Slaby 01 Nov '12

01 Nov '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I'm trying to solve this issue: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=kerne… by adding this line to prjconf of the project: Order: systemd:mkinitrd When I trigger rebuild, the very same error appears in the log. Am I doing something wrong? thanks, - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQa//SAAoJEL0lsQQGtHBJ0DMP/037sZIxENH9XfTuDpunsh1M eb6zTYuOdBlpgWE2B+EaGtR5HL+wfIi9dFjs31SQzui2liQKrH34x+lLyVkto6Xb KvWdde17IyBKY2MTh7mCVqdUuLZElIHSrtuU8owMA09aXi0BfabXmjDDbzVSaqOF 95NuC07KADjgDzpaFEVcZ2k4Tc1Kfg7R4cOQdDBa/n3VieJVKk7oRZ/9FXyBj8qW aVlIXJY2HP2Akweax5ba+2vPwH+n9ukZLa8TfRWCCmodzJ2gSM/W0naQIZg6kEKf TfFh2hYbFIl1f9+NcMgvKpYS0Ckw+0QgzeDBE4N/ztBnaj9tOD46EEs4E2zqsE7f Q5/sc1Oa1HiUKNKBMDZ+pPsVyIHVdvgic7AqADdL1Q1QhRYJG0f5DOfeQX1rHUm7 HVZ3JX/QxsOauOf1Pt/XAHv9pkwVO39f4CrMw3ZjN7QHpSy6at7/0LVv1Zf+sNZK oD9aXtPhVWHWorQFJnH+TgdvuM9wBRlnFxjbu06UID5Mw/s9x97CnQg4CWc45Gj2 JU743wyxAxUJF8DcU4bYK8o1VHe3LKb6P8Kn8EKynVqbKIqmV2nRIRnjgfh1MqoC 69Vgdz/jHnijzekfMycRk2JbO6Cv+KdwXHQs4c5e8u+9po/IFF/ZxgpIhmNt7kMU cgJH/czwrQzX8LyTa8W1 =kUYH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] sles build problem
by Peter Czanik 31 Oct '12

31 Oct '12

Hello, I ran into an "interesting" problem while trying to build for SLES 11 SP2: the build of libeventlog, necessary for building syslog-ng, fails in the build service. I checked it out to my laptop to debug locally, but it compiles fine here. The error in the BS is: |[ 773s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define 'disturl obs://build.opensuse.org/home:czanik:syslog-ng33/SLE_11_SP2/5403e843a913043…' /usr/src/packages/SOURCES/libevtlog.spec [ 774s] error: Group field must be present in package: libevtlog0| For details, see https://build.opensuse.org/package/live_build_log?arch=x86_64&package=libev… Bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] Re: [Kiwi-devel] kiwi in OBS request
by Joop Boonen 31 Oct '12

31 Oct '12

On 2012-10-29 13:51, Adrian Schröter wrote: > Am Montag, 29. Oktober 2012, 12:50:03 schrieb Joop Boonen: >> Hi all, >> >> I see one Kiwi improvement in OBS. >> >> Currently source path="obs:// needs to be put in the .kiwi file. >> This >> is a problem if you want build an image with the same kiwi file for >> more >> then one repo. >> Would it be an option use the repositories in the meta file (like >> obs >> build, for rpm) does? >> >> Currently I cant for example build a JeOS.kiwi for >> openSUSE:Factory:ARM >> and openSUSE:12.2:ARM In the same project. Even tough I've created >> two >> image build repositories for them. One Factory and on 12.2. > > Yes, I see this also as an important feature. > > However, I guess this need to be solved in OBS. > > We should have just a generic obsproject:// url or alike in the kiwi > file > and obs_worker and osc needs to replace it by the right set of > repositories. > > So, this mailing list is maybe the wrong place, except for asking for > feedback > on that approach :) I've sent it to the openSUSE buildservice mailing list too. > > bye > adrian Regards, Joop. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] obs private instance and Fedora repos
by Robert Story 31 Oct '12

31 Oct '12

Hi, I've got the obs server appliance running here locally, and I've successfully built my test rpm for Fedora. Now I'm looking to branch out, and have some questions. I'm still trying to wrap my head around obs, so forgive me if I get the terminology mixed up... * When I build against the Fedora 17 repository, that downloads dependencies from the openSUSE build server to my local machine and builds my rpm locally, right? That is, it's not using Fedora's mirrors to get rpms, nor is it using openSUSE machines to build.. * Is it possible to configure obs to pull rpms from a local repo? I have mirrors of the fedora repositories, and I'd rather pull from there instead of across the net to the openSUSE servers. I've seen threads on importing rpms from other repos to an obs server to make a new repository, but I don't have enough space to copy all of Fedora over to my obs appliance. * Do the openSUSE Fedora repositories have Fedora updates merged in? I've seen some messages that gave me the impression that they just contained the rpms from the original release date. Thanks, Robert -- Senior Software Engineer SPARTA, Inc., a Parsons Company

2 1

[opensuse-buildservice] [PATCH0/1] raw_input checks if stdin is tty
by Michal Vyskocil 31 Oct '12

31 Oct '12

Python's raw_input does not check if stdin is conntected to the terminal, which makes it pretty hard to call such script from an another one or from ssh. This patch changes the raw_input from osc.core - in case sys.stdin is not connected to the terminal, it raises RawInputError. The from osc.core import raw_input lines were added to oscssl.py and build.py to enforce this behavior as much as possible. --- osc/build.py | 1 + osc/core.py | 2 ++ osc/oscerr.py | 8 ++++++++ osc/oscssl.py | 2 ++ 4 files changed, 13 insertions(+) diff --git a/osc/build.py b/osc/build.py index add7631..211b046 100644 --- a/osc/build.py +++ b/osc/build.py @@ -14,6 +14,7 @@ from tempfile import NamedTemporaryFile, mkdtemp from osc.fetch import * from osc.core import get_buildinfo, store_read_apiurl, store_read_project, store_read_package, meta_exists, quote_plus, get_buildconfig, is_package_dir from osc.core import get_binarylist, get_binary_file +from osc.core import raw_input from osc.util import rpmquery, debquery, archquery import osc.conf import oscerr diff --git a/osc/core.py b/osc/core.py index 1ac189b..70d064e 100644 --- a/osc/core.py +++ b/osc/core.py @@ -6381,6 +6381,8 @@ def get_user_projpkgs(apiurl, user, role=None, exclude_projects=[], proj=True, p return res def raw_input(*args): + if getattr(os, "isatty") and not os.isatty(sys.stdin.fileno()): + raise oscerr.RawInputError(*args) import __builtin__ try: return __builtin__.raw_input(*args) diff --git a/osc/oscerr.py b/osc/oscerr.py index 5429ddf..cd6ba62 100644 --- a/osc/oscerr.py +++ b/osc/oscerr.py @@ -150,4 +150,12 @@ class PackageInternalError(PackageError): def __init__(self, prj, pac, msg): PackageError.__init__(self, prj, pac) self.msg = msg + +class RawInputError(OscBaseError): + def __init__(self, *args): + OscBaseError.__init__(self, *args) + + def __str__(self): + return "Following question cannot be answered, because tandard input is not connected to the terminal\n\n\n%s" % self.args + # vim: sw=4 et diff --git a/osc/oscssl.py b/osc/oscssl.py index 127c0cd..f6c2dea 100644 --- a/osc/oscssl.py +++ b/osc/oscssl.py @@ -13,6 +13,8 @@ import urllib import httplib import sys +from osc.core import raw_input + class TrustedCertStore: _tmptrusted = {} -- 1.7.10.4

1 0

[opensuse-buildservice] questions about debian builds
by Marcin Wojdyr 31 Oct '12

31 Oct '12

When I add debian files to OBS and try to build locally, I get: $ osc build Debian_6.0 x86_64 Multiple build description files found: fityk.spec, fityk.dsc It builds fine on the OBS server, so as a workaround I'm temporarily renaming spec file when doing local deb build. Is there another way? And a small inconvenience. When I was building only RPMs I used to keep one older tarballs, just in case I need to rollback. But two tarballs make debian transform failing: [ 39s] running debian transformer... [ 39s] package contains more than one tar file: fityk-1.2.0.tar.bz2 fityk-0.9.8.tar.bz2 [ 39s] debian transforming failed. not a big issue, I can remove one, I'm just writing to let you know. Thanks for this great service Marcin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] ***:Update repositories for other distributions?
by Nico Kruber 29 Oct '12

29 Oct '12

is it possible to integrate the update channels of the non-SUSE distributions as well and integrate them into build.opensuse.org? e.g. for kernel modules or newer libraries/fixes? Regards Nico Kruber -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] No baselibs for glibc
by Jan Engelhardt 28 Oct '12

28 Oct '12

Why would openSUSE:Factory/glibc not build any baselibs? The configuration is there, but the build log is silent on that: ../openSUSE/Factory/glibc$ osc bl standard i586 (lots of text) [ 2344s] ... creating baselibs [ 2345s] ... comparing built packages with the former built [ 2345s] /usr/lib/build/rpm-check.sh [ 2345s] compare /.build.oldpackages/glibc-2.16-4.1.src.rpm /home/abuild/rpmbuild/SRPMS/glibc-2.16-5.1.src.rpm -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] Motif has been released under LGPL
by Matwey V. Kornilov 27 Oct '12

27 Oct '12

Motif has been released under LGPL. I think, it is worth to put openmotif back from NonFree to main repo. http://sourceforge.net/projects/motif http://motif.ics.com/motif-234-release-notes Moreover, it seems that package should also be renamed from openmotif to motif. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 8

[opensuse-buildservice] out of memory trying to build VirtualBox
by Nico Kruber 26 Oct '12

26 Oct '12

Hi, I was trying to build VirtualBox 4.2.2 for openSUSE 11.3 but got the following: [ 3719s] [ 3659.820789] Out of memory: Kill process 17687 (cc1plus) score 478 or sacrifice child [ 3719s] [ 3659.821665] Killed process 17687 (cc1plus) total-vm:1510764kB, anon-rss:487176kB, file-rss:224kB https://build.opensuse.org/package/rawlog?arch=x86_64&package=virtualbox&pr… afaik it is already building with one thread only is there anything else I can do to get it to work? (32bit builds seem to be fine) Nico -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] Ubuntu 12.10
by Nico Kruber 26 Oct '12

26 Oct '12

I know, there is no official support for Ubuntu 12.10 yet, but I tried it in OBS and got the following error: [ 80s] [195/321] installing x11-common [ 80s] Selecting previously unselected package x11-common. [ 81s] Can't exec "insserv": No such file or directory at /usr/sbin/update- rc.d line 417. [ 81s] update-rc.d: error: insserv rejected the script header [ 81s] dpkg: error processing x11-common (--install): [ 81s] subprocess installed post-installation script returned error exit status 255 [ 81s] Errors were encountered while processing: [ 81s] x11-common [ 81s] exit ... https://build.opensuse.org/package/live_build_log?arch=i586&package=scalari… svn-bindings&project=home%3Ascalaris%3Asvn&repository=xUbuntu_12.10 since another package of mine works, I figured I should send this hint... tell me if you need anything more info to fix it Thanks Nico -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] OBSLight 1.0 and FakeOBS 1.0.1 with support for mic and gbs on OpenSUSE, Fedora and Unbuntu
by Dominig ar Foll (Intel OTC) 25 Oct '12

25 Oct '12

Hello, we are pleased to announce the new releases of OBSLight (1.0.0) and FakeOBS (1.0.1). This new version allows to create local project and is supported by the latest OpenSUSE, Fedora and Unbuntu. You can now create a project with OBSlight from an OBS server, a gsb manifest or from a local Template. >From an OBS project, you can as previously locally build OBS packages, but you can now also import packages from a git repos (Tizen format) or local files. OBSLight provides all the required tools for all the supported distros. this includes mic and gbs depanneur. OBSLight and FakeOBS have now moved to OpenSUSE OBS and are published at https://build.opensuse.org: - standard users will use the project stable (devel:OBS:Light:Stable): https://build.opensuse.org/project/show?project=devel%3AOBS%3ALight%3AStable - Beta testers can access to the project head () (devel:OBS:Light:Head)(devel version ): https://build.opensuse.org/project/show?project=devel%3AOBS%3ALight%3AHead Use of the stable.version should be preferred by most of you. Never use the both in the same time. The head version is linked to our git branch head, the stable version is linked to our git branch master. https://meego.gitorious.org/meego-developer-tools/obs-light We support OBSLight and FakeOBS for: -Fedora 16 -Fedora 17 -OpenSUSE 12.1 -OpenSUSE 12.2 -Ubuntu 11.10 -Ubuntu 12.04 As OBSLight required mic, gbs and depanneur, we also distribute Mic for: -Fedora 16 -Fedora 17 -OpenSUSE 12.2 and gbs, depanneur,... for: -Fedora 16 -OpenSUSE 12.2 These complementary packages are added automatically when required from OBSLight repo. Features details =========== * OBS Light: - New wizard to create project (now you can choose OBS or local project). - Use GIt package in OBS project. - Use Git package in Local project. - Generate and store manifest.xml from https://review.tizen.org/git/?a=project_index. - Import Tizen Git package from UI. - New appliance is now on Opensuse 12.2. - A New appliance base on the head version (devel branch.). * Fake obs: - improved packaging. - added 'version' option to commandline. - now searching for RPMs which are in :full but not in repositories when doing a grab. - changed data organisation. - rewrote most parts in python. - added 'shrink' command to link duplicated RPMs. - fixed _buildinfo request for ARM builds. - not using manifest anymore to remove a project. - restart daemon after grab or import. - converter for FakeOBS image based on release 0.6x Links ===== Training video (30mn) * http://www.dailymotion.com/video/xu46ij_building-tizen-2-from-the-source-wi… To install or update OBS Light: * http://en.opensuse.org/openSUSE:OBS_Light_Installation * http://en.opensuse.org/openSUSE:OBS_Light_Fakeobs#Installation You can find an appliance including OBS Light here: Stable: * http://susestudio.com/a/e0uuBG/obs-light-obs-client-stable Head: * http://susestudio.com/a/e0uuBG/obs-light-obs-client-head Do not hesitate to submit bugs or suggestions for improvements on our bug tracker: https://bugs.meego.com/buglist.cgi?product=Development%20Tools&componen… Your feedback is welcome. With thanks, the OBS Light Team. -- Dominig ar Foll Senior Software Architect Open Source Technology Centre Intel SSG -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Can I please be add as maintainer to drivers:nic
by Joop Boonen 25 Oct '12

25 Oct '12

Hi all, Can I please be add as maintainer to drivers:nic, as bitshuffler is currently the only maintainer, my request hasn't been accepted yet, after 5 weeks. Regards, Joop. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

Re: [opensuse-buildservice] Profile picture is not shown properly with http proxy
by UkJung Kim 25 Oct '12

25 Oct '12

Thanks for your new path. It works with small modification. -+ proxy_user, proxy_pass = proxy.userinfo.split(/:/) if proxyuri.userinfo ++ proxy_user, proxy_pass = proxy.userinfo.split(/:/) if proxy.userinfo And I think HTTP_PROXY would be http_proxy. We usually use http_proxy in non-capical for environment variable. And also all config options in config/option.yml are non-capital. Many thanks. 2012/10/24 Adrian Schröter <adrian(a)suse.de>: > Am Mittwoch, 24. Oktober 2012, 20:41:17 schrieb UkJung Kim: >> Thanks for you patch. >> But it doesn't seems to work. >> apache server doesn't have any HTTP_PROXY environment variable since >> my shell has. >> >> It works if I change your patch directly to use proxy. > > Hm, I have no better idea right now then to allow als HTTP_PROXY as > config option in config/options.yml . > > The attached (updated patch) should work then. Again, untested. > >> 2012/10/24 Adrian Schröter <adrian(a)suse.de>: >> > Am Mittwoch, 24. Oktober 2012, 09:42:02 schrieb UkJung Kim: >> >> Hi, >> >> >> >> Profile picture is not shown properly with OBS 2.3.6. >> >> >> >> Our OBS server is behind firewall and we have to use http proxy for >> >> web connection. >> >> It seems it has problem with getting profile picture from Gravatar. >> >> And I guess it doesn't use http proxy to connect to Gravatar. >> > >> > I have not tested it, but theoretically the attached patch is fixing >> > this. >> > >> > Patch is against git master though. >> > >> > Would be great if you could test it. >> > >> > thanks >> > adrian >> > >> > -- >> > Adrian Schroeter >> > SUSE Linux Products GmbH >> > email: adrian(a)suse.de > -- > Adrian Schroeter > SUSE Linux Products GmbH > email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] Feature: Show 'unresolvable' packages on status page
by Dominique Leuenberger a.k.a DimStar 24 Oct '12

24 Oct '12

Hi all, It would be highly appreciated if the openSUSE Status monitor [0] could also list 'unresolvable' packages as 'failing' packages. I myself make extensive use of this screen to identify priorities of packages maintained by me (or the GNOME Team in general) and putting efforts on those packages. But, as I just had to learn, 'unresolvable' packages do not figure on the list and as such easily slip the attention of packagers. Bringing this kind of build failure on the same status page would enhance its value greatly, as packagers would have a one-stop status overview for Factory. Looking forward! Dominique [0] https://build.opensuse.org/project/status?project=openSUSE%3AFactory -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] OBS Trip Report: oSC12
by Henne Vogelsang 24 Oct '12

24 Oct '12

Hey Guys, over the weekend I went to the openSUSE conference/Linuxdays in Prague/Czech Republic, here is my trip-report for the OBS community. ##General Comments The program of the first two days was more focused on things that are only loosely connected to OBS like FOSS/commons/freedom in general, user workshops and applications. It also featured a gentoo track but they don't have much use for a build service... Monday and Tuesday on the other hand where focused solely on openSUSE and here the OBS, naturally, played a bigger role. All in all it was nice to meet so many OBS users and hear how, what we produce together, makes their FOSS-life a little bit easier. Also nobody screamed at Coolo or me, no one tried to beat us up. So I guess we can't do everything wrong ;-) ##Program related to OBS I've blogged about it before going there. Check out http://openbuildservice.org/2012/10/17/obs-%40-osc/ ###OBS Packager Workshop The room was packed. Somewhere around 30 people participated in our packager workshop and successfully built packages and tried the collaboration features of the OBS. BTW this workshop (and others) is also online¹ and whenever you can, you should hold it at FOSS events! The Libreoffice file includes notes and everything. Check it out. ¹ http://openbuildservice.org/help/materials/ It's modeled after the two screencasts we have, which you also find there. ###OBS for embedded projects Karsten Keil talked about the transparent cross compiling feature B1 is developing for the OBS and the motivation behind it. It was recorded so watch out for it on http://blip.tv/opensuse (it's not released yet). The code is in their fork here: https://github.com/b1-systems/open-build-service ###Packaging tools Daniel Lovasko presented some scripts that make it easier to automate some tasks packagers do repeatedly. It's currently done _around_ osc/rpm, but as far as I could gather some of it is already in python and it could be made a nice OSC plugin. The recording of the talk is here: http://blip.tv/opensuse/osc12-packaging-tools-6410647 And the code here: https://gitorious.org/opensuse/pack-tools ###Future of OBS BoF We talked a little bit about the general features on the roadmap, we showed how the webui looks in master, talked about where osc2 is heading and so on. We also dived a bit into wishes for the near future. >From the ~10 participants I heard 1. Mobile client to do package reviews. People would like to do that task on the train or something very much. 2. Native build hosts for ARM 3. Take another look as the webui/osc from the user experience perspective. Introduce some other personas than the casual packager the current UI's are optimized for. 4. Somehow get going on Hermes fixes and features again but that is currently not really possible for us with the man-power we have. ##Ideas/Features Here are the ideas for features I heard floating around @ osc12 on the hallway, in personal conversations and in talks not really related to OBS. ###osc related * osc plugin to search and install packages from all OBS projects. Basically software.o.o for the command line. Should probably rather be a zypper plugin but is seen as missing feature of the OBS. * Using some VCS _only_ for checkouts. Like an osc plugin that makes it easy to store intermediate steps between checkout & checkin to the OBS ###backend related * Put a "build at my machine" button on home: projects that somehow builds packages (exclusively from this projct) on a local worker instance. So people can use their own hardware as worker. ###webui related * Merge the monitor and the status pages in the webui because they are confusing the casual submitter * Clean up the users tab to not show project maintainers by default, only maintainers/bugowners so people know whom to contact. * If there is a problem with a package in a project, the devel_project should shown it in it's status page as well. Related talk: * Introduce some gamification into the webui. Like badges for the Nth built package or the Nth submitrequest. Top packager lists and stuff like that. Related talk: http://blip.tv/opensuse/osc12-gamefiction-6410559 That's it, I hope you enjoyed this report. The next trip on our radar are the Erlangener Linuxtage the weekend after next where Adrian and me will do the Facts, Features, Future talk (also available on http://openbuildservice.org/help/materials/ as you guessed ;-) Henne -- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2