July 2010 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] BS: Read-only file system failures
by Hans-Peter Jansen 30 Jul '10

30 Jul '10

Hi, today I saw a couple of: /abuild/root_4/.pkgs/python-qt.rpm: Read-only file system failures, this one in: https://build.opensuse.org/package/live_build_log?arch=i586&package=python-… but the same goes for: https://build.opensuse.org/package/live_build_log?arch=i586&package=kdebase… https://build.opensuse.org/package/live_build_log?arch=x86_64&package=kdeba… Something in BS goes haywire ATM. Cheers, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

[opensuse-buildservice] Updated distro packages
by Stephen Shaw 29 Jul '10

29 Jul '10

I've been working on some packages that I need to provide across multiple distributions. In some case I need to patch one of the core packages of each distribution which OBS makes this really nice and easy. This particular package is xulrunner191. I need to patch it (working on upstream the patch) and want to make sure that I'm providing the latest version in hopes to make sure that I include all the latest security patches. The problem I'm running into with this however is that it requires newer versions of other packages which so far has turned in to a big mess with no success. What I'd look to see is maybe every month or so to pull all of the available updates into the repository or create something like Fedora_12:Updates Cheers, Stephen -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] k3b in KDE:Distro:Stable in strange error state
by Hans-Peter Jansen 29 Jul '10

29 Jul '10

Hi, the pkg k3b in KDE:Distro:Stable is hanging out in a strange error state: the Files page says: The link contains errors: conflict in file k3b.spec. The question is: how can a link contain conflicts? Shouldn't simply superseed a local existing file a linked one, e.g. k3b.spec in this case? Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 4

[opensuse-buildservice] signer problems
by Marcel Ritter 29 Jul '10

29 Jul '10

Hi, we recently upgraded our installation to buildserver 2.x, and are now experiencing problems with the signing daemon(s). webui reports "signer" as "dead", however signd and signer are up and running. Packages themselves seem to get signed, but the package repositories are no longer signed. Any ideas where to look for the problem? Some more info about our setup: We're running a split setup on 2 machines: Repo-Server/Signer/Scheduler: obs-utils-2.0.4-3.1 obs-signd-2.1.2-1.1 obs-server-2.0.4-3.1 Frontend/API/Webui: obs-common-2.0.1-1.1 obs-api-2.0.4-3.1 Bye, Marcel -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] Is there any plan to integrate MIC(MeeGo Image Creator) into OBS?
by victor.liu＠Nokia.com 28 Jul '10

28 Jul '10

Hi, Since MeeGo is using OBS as official build service and MIC2 is their image creation tool. It seems to be reasonable to integrate MIC2 into OBS, just like KIWI in OBS. Is there any plan on that? Thanks Victor Liu-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] how to use local repository to build packages for fedora ?
by Coly Li 28 Jul '10

28 Jul '10

Hi, Now I am installing a local instant of openSuSE build service on openSUSE 11.3. My purpose is to build fedora rpm packages which is said supported currently. >From the document, I know the distribution repository is needed during the package build, and I download a fedora 13 repo into my local hard disk. Unfortunately, I don't find from the document how to use this local fedora 13 repo into OBS. I know I must miss some lines from the documents, aftere re-read the docs, I still have very clear idea. Can any body give me some hints ? Thanks in advance. -- Coly Li -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Integrating OBS with Subversion - Cray's solution
by Luke Imhoff 28 Jul '10

28 Jul '10

I've recently uploaded the tools developed at Cray to work with OBS and Subversion to gitorious at http://www.gitorious.org/cray-obs. If there's interest in any of the features in this code I'll try to merge it to the official OBS. Cray's tools includes svndownstream, which we use to package up Subversion workareas into a format digestible by OBS, among other things. Some cool features added to obs-server and osc with svndownstream: svndownstream ls - Shows all packages in OBS that use the source from this workarea. Follows links backwards and forwards. Example: You're in the kernel Subversion workarea. It supplies the source for kernel-source directly. kernel-source is then linked in OBS to all the kernel-<flavor> packages as the flavors use the same source, just different specs. There also is a kernel:trunk:debug project where, we do some additional debug option, so this is an indirect link of kernel:trunk:debug/kernel-cray_gem_c -> kernel:trunk:debug/kernel-source -> kernel:trunk/kernel-source. So, all the links are followed. kernel/linux/trunk> svndownstream ls kernel:trunk kernel-source kernel:trunk kernel-cray_gem_c kernel:trunk kernel-cray_ss_c kernel:trunk kernel-cray_gem_s kernel:trunk kernel-syms kernel:trunk kernel-cray_ss_s kernel:trunk:debug kernel-source kernel:trunk:debug kernel-cray_gem_c kernel:trunk:debug kernel-cray_ss_c kernel:trunk:debug kernel-cray_gem_s kernel:trunk:debug kernel-syms kernel:trunk:debug kernel-cray_ss_s Well, that's great, now the develop can tell what they can build using just the source in kernel/linux/trunk, but what if they want to check what's going to be rebuilt if they check in that code. This could be important if they are doing a change that could impact all the kernel module packages (kmps) that depend on the kernel. In that case there's svndownstream dependents svndownstream dependents - Perform actions on dependents. Dependents are anything that (in)directly BuildRequires a package or (in)directly Requires a package, so that the dependent package would be rebuilt if you changed the source in Subversion. There are numerous subcommands (it works a lot like osc meta in that way), but as an intro: svndownstream dependents list - This command will display a dependency tree (and optionally write it to a file) Example: This is just an excerpt, but the real dependency tree is huge for the kernel svndownstream dependents list --collapse repository \ --collapse architecture ... kernel:trunk/kernel-source virtual-cluster:danube/cray-virtual-cluster XT:trunk:ss/cray-job XT:trunk:ss/cray-account ... The --collapse flags tell the server to ignore repository and architecture differences so it only looks for dependencies between project/package pairs. One cool bit about the output is svndownstream dependents list supports the graph format used by graphviz, so you can make visualizations of dependencies. Good for figuring out where to sever dependencies by breaking up packages to make builds faster or happen less often. The dependency calculations use a MySQL database in the server backend to cache the dependencies calculated in bs_sched. You can see the majority of those changes in http://www.gitorious.org/cray-obs/obs-server/commit/00705dba7a409d766ac28d5… . -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] [PATCH OSC] fix links that point to the wiki
by Henne Vogelsang 27 Jul '10

27 Jul '10

Hey, please apply attached patch to osc to fix the links that point to the wiki. Henne -- Henne Vogelsang, openSUSE. Everybody has a plan, until they get hit. - Mike Tyson

2 1

[opensuse-buildservice] [PATCH BUILD] fix links that point to the wiki
by Henne Vogelsang 27 Jul '10

27 Jul '10

Hey, please apply attached patch to build to fix the links that point to the wiki. Henne -- Henne Vogelsang, openSUSE. Everybody has a plan, until they get hit. - Mike Tyson

2 1

[opensuse-buildservice] issue with BS from scratch
by Hans-Peter Jansen 27 Jul '10

27 Jul '10

Hi, while installing BS from scratch on a 11.1 server, I ran in a couple of issues. I'm using this repo: http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.1 as documented in: http://wiki.opensuse.org/openSUSE:Build_Service_Installation_SUSE zypper in obs-server obs-worker obs-api obs-utils Then I followed: /usr/share/doc/packages/obs-api/README.SETUP, putting optional steps aside, which was pretty straight forward: # rcobsrepserver start Initializing obsrepserver done # rcobssrcserver start Initializing obssrcserver done # rcobsscheduler start Initializing obsscheduler done # rcobsdispatcher start Initializing obsdispatcher done # rcobspublisher start Initializing obspublisher done up until point 2.1: # rcobsworker start Run 8 obsworker using /var/cache/obs/worker cpio: premature end of archive chmod: cannot access `bs_worker': No such file or directory What's up, here: # bash -x /etc/init.d/obsworker start [...] + echo 'Run 8 obsworker using /var/cache/obs/worker' Run 8 obsworker using /var/cache/obs/worker + '[' yes == yes ']' ++ slptool findsrvs service:obs.repo_server ++ sed -n 's/service:obs.repo_server:$[^,]*$,.*/\1/p' + '[' -d /var/run/obs/worker/boot ']' + pushd /var/run/obs/worker/boot + curl -s http://localhost:5252/getworkercode + cpio --quiet --extract cpio: premature end of archive + ln -s . XML + chmod 755 bs_worker chmod: cannot access `bs_worker': No such file or directory + popd Hmm, there's no such thing like http://localhost:5252: # netstat -anp | grep ':5252' # Digging deeper: cat /srv/obs/log/rep_server.log 2010-07-22 15:08:43: AJAX: bs_repserver started 2010-07-22 15:08:43: bs_repserver started on port 6262 Ahh, it's listening on 6262 now. Fixing /etc/sysconfig/obs-worker... Now proceeding up until 3.2, setting up lighttpd. You say, that http://127.0.42.1 resp. http://127.0.42.2 are preconfigured. Looking into /etc/lighttpd/vhosts.d/obs.conf, there is only the PORT defined, doesn't that mean, that it binds to any local address? Sorry for asking these silly questions, but I need to modify this setting in order to get my apache going again, and you're documenting these changes quite extensively, but the references to 127.0.42.* are misleading then, aren't they? Now proceeding up until 4.1, creating a reference project. Running the command: # curl -0 --user "Admin:opensuse" -X PUT -T /usr/share/doc/packages/obs-api/openSUSE.org.xml http://127.0.42.2/source/openSUSE.org/_meta results in some html page printed to the console here. In the middle one can read:  <div id="content" class="container_16 content-wrapper"> <div class="grid_16 box box-shadow alpha omega"> <h1>openSUSE Webclient Error:</h1> <h2>Target not found</h2> <p>A non existing page was requested.</p> <h3>Error Details:</h3> <p> <strong>Errorcode: </strong>404<br/> <strong>Message: </strong>no such route<br/> </p> </div> </div>  Hmm, another issue, I guess. Looking at the destination path, it wants to write to http://127.0.42.2/source/openSUSE.org/_meta, but http://127.0.42.2 is going to match $SERVER["socket"] == ":80" in /etc/lighttpd/vhosts.d/obs.conf, which points to /srv/www/obs/webui, and yes, there is no such directory named source (and it's rather questionable, if that's really the intended destination, since this kind of data would much better fit the /srv/obs hierarchy, but there's no such dir either.. What am I missing here? Thanks for any enlightenment in advance, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 8