August 2010 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] obs Application error when accessing https://build.opensuse.org/
by doiggl＠velocitynet.com.au 18 Aug '10

18 Aug '10

Hello, I get this error [1]when accessing this page [2] [1] Application error Change this error message for exceptions thrown outside of an action (like in Dispatcher setups or broken Ruby code) in public/500.html [2] Glenn -- 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] OBS: set release number of package?
by Jon Nelson 18 Aug '10

18 Aug '10

Is there a way to tell the OBS to set the release number of a package to some arbitrary number (or to increase it by some number)? For example, let's say foo version 1.0 and has been checked in 3 times and rebuilt twice. I think the package would then be foo-1.0-3.2.$arch.rpm. Let's say I'd like to set the check in count to 5 (and reset the build count). Is there an easy way to do this without /actually/ checking in a number of dummy commits? -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 8

[opensuse-buildservice] GIT OBS release tags
by Maultuz 18 Aug '10

18 Aug '10

The next time a release, could it be made an annotated object(git tag -a 2.0.6) I'm asking because it would me much easier to understand what changes a snapshot archive is made from. When I look in openSUSE:Tools:Unstable => obs- server I'll find obs-server-2.0.89.tar.bz2 and that tells me nothing. If the tags where an annotated object `git describe` could be used for the version tag i.e. “2.0.5-143-gb9f73fc” then I could use `git log/diff 2.0.5..b9f73fc` or `git log/diff b9f73fc..HEAD` etc. -- 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] Safe way to remove /srv/obs/source folders
by Davis_Phillips＠Dell.com 18 Aug '10

18 Aug '10

Greetings, I posed this questions a week back or so and I wanted to check again. Concerning OBS 1.6: Is considered a best practice for deleting the folders under /src/obs/source? The uploaded tarballs & spec files are being to consume a large amount of space on our front end servers. We would like to archive what we can in an effort to clean up the environment. Thanks in advance! Thanks! Davis Phillips Release Engineer Dell | PG Release Engineering office + 1 512 723 5910 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] Linking two (private) OBS servers at different sites.
by Troy Telford 16 Aug '10

16 Aug '10

Is there a guide anywhere that talks about how to link two different OBS servers, so that when a project/package that is on one server can be linked to on another server (separated by distance and low-bandwidth; so it makes sense to send source code instead of keeping the package mirror constantly updating). I've seen the example where (openSUSE 11.3's obs packages) have /srv/obs/packages has openSUSE.org.xml. I've tried modifying that example, and set it to point between the two servers, and had some success; I've linked some packages and when the package on one system is updated, the changes transfer to the other. I can copypac, linkpac, aggregate pac, for the most part. However, if I look in /srv/obs/log/scheduler_arch.log, I see the following repeated endlessly: 2010-08-09 19:02:13: waiting for an event... retrying watcher for http://obsapi.foo.bar.com/public setting up watcher for http://obsapi.foo.bar.com/public 2010-08-09 19:03:16: waiting for an event... response from watcher for http://obsapi.foo.bar.com/public 400 remote error: Bad Request retrying in 60 seconds Any ideas on what I might be missing? Thanks. Thanks. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 6

[opensuse-buildservice] unresolvable status preventing package build, when same provide is available from two packages
by Frederic Crozat 16 Aug '10

16 Aug '10

Hi, I'm having an issue when trying to build jpilot for SLE10, which can be seen on https://build.opensuse.org/package/show?package=jpilot&project=mobile% 3Asynchronization%3ASTABLE jpilot is trying to use pilot-link / pilot-link-devel (which is now provides by libpisock-devel, which obsoletes/provides pilot-link-devel) as a build requirement but it looks like OBS is trying to use pilot-link-devel / pilot-link packages from SLE10 (which is older) rather than the one from the project. Is it a bug ? For now, I'm changing buildrequirement to libpisock-devel as a workaround. -- Frederic Crozat <fcrozat(a)novell.com> Novell -- 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] Running OBS Rails app in sub directories.
by Leaf John 16 Aug '10

16 Aug '10

My situation is, I could export obs service through only one port( 80 ), I have only one server, and the server has only one domainname.so I've to run different rails app by different sub dirs. I tried the strip uri feature of lighttpd, and I added this line to rails.inc: "max-procs" => rails_procs, "idle-timeout" => 3600, + "strip-request-uri" => strip_uri, ) ) ) Than I add another obs-80.conf to vhosts.d, add this content: HTTP["url"] =~ "^/webui/" { ...... strip_uri="/webui" include "vhosts.d/rails.inc" } Than I visit my server like, http://myip/webui, and I got the front page all right, but no link works, no style sheet, even no images in the web page. >From the html source I see that all links point to some absolute address like /stylesheet/xxx.css, /images/opensuse.png.. So, My question is, is there any solutions for this case? If not where can I do the modifications to solve the link address issue? Modifications won't be an easy task, cause the absolute path will save some energy in web page generation, but it won't be a task not possible. -- Best Reagres, Leaf Johnson<leafjohn(a)gmail.com> -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] osc collab hardcoded to build.o.o?
by Robert Xu 15 Aug '10

15 Aug '10

Hi all, I decided to play around with osc collab on my home project on build.o.o, then on my local bs, but I noticed that it defaults to build.o.o even if .oscrc says to use my local bs as the apisrv. Is this supposed to happen? -- later, Robert Xu -- 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 SCM with OBS
by brook.hong＠nokia.com 13 Aug '10

13 Aug '10

Hi ALL, I had started a discussion about integrating SCM with OBS in our company. And now when I checked back http://en.opensuse.org/Category:Build_Service, I found there was an interesting wiki page(http://en.opensuse.org/openSUSE:Build_Service_Concept_GitUpstreamSuppo… talking about the similar task, also noticed that some of you have started relevant work. Here I would like share my thoughts. Follows my writing in my earlier emails. ====================================== For example, we would like to have Meego OBS to build a package -- gstreamer, which is located at http://git.gitorious.org/maemo-multimedia/gstreamer.git. With current OBS, we need fetch all the code from gitorious, create a compressed tar file, then upload the tar file, spec/dsc file to OBS source server, these files will go into /srv/obs/sources/gstreamer/. OBS scheduler(bs_sched) will detect the file change, and trigger a rebuild. If source repository URL is included in the meta file of this package as below <package project="devel" name="gstreamer"> <title>gstreamer</title> <description>gstreamer</description> <sources>http://git.gitorious.org/maemo-multimedia/gstreamer.git</sources> </package> Then create a new server in OBS, may be named as bs_scmagent, which focuses on the following tasks -- * maintain a package list for all the packages whose meta data file includes a source repository URL, * connect to SCM server to detect code change, * if changed, fetch code from SCM, tar them, put the new file into /srv/obs/sources/gstreamer/, let bs_sched to trigger a rebuild. bs_scmagent needs to support plugin, which is to give support for different kinds of SCM. For compatibility, a special value is needed to indicate that the files were uploaded manually. <package project="devel" name="gstreamer"> <title>gstreamer</title> <description>gstreamer</description> <sources>native</sources> </package> How to detect code change? For git, Polling seems to be the only solution since it is distributed version control system. Thus, we need tune up the polling way for performance consideration. * polling not that frequently, for example, once n hours(n can be configured from webui or osc, and is limited between a range) * if developer wants his code change being built immediately, an osc action will be involved, he can run "osc remoteupdatesource gstreamer" to tell bs_scmagent to get latest code. ====================================== "osc git refresh" mentioned in http://en.opensuse.org/openSUSE:Build_Service_Concept_GitUpstreamSupport seems much like "osc remoteupdatesource" I proposed. I like the idea of generating a diff from SCM as a patch for spec file, but I don't like "git" as an action of "osc". I prefer the interfaces to be clear, osc is osc, git is git, don't mess them up. Also how about other SCMs except git? What's your progress now? ---------------- Best Regards, Brook Hong -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

6 6

[opensuse-buildservice] Packages appear excluded, although they shouldn't
by Hans-Peter Jansen 13 Aug '10

13 Aug '10

Hi, Repo: https://build.opensuse.org/project/repositories?project=home%3Afrispete%3AK… Build explicitely disabled for CentOS_CentOS-5 and Fedora_13 Now I wanted to split the python-kde package, depending on the build target in python-kde4-44 and python-kde4-45. osc meta pkg home:frispete:KDE python-kde4-44: <build> <disable repository="KDE_Distro_Factory_openSUSE_11.1"/> <disable repository="KDE_Distro_Factory_openSUSE_11.2"/> <disable repository="KDE_Distro_Factory_openSUSE_11.3"/> <enable repository="KDE_Distro_Stable_openSUSE_11.1"/> <enable repository="KDE_Distro_Stable_openSUSE_11.2"/> <enable repository="KDE_Distro_Stable_openSUSE_11.3"/> <disable repository="openSUSE_11.1"/> <disable repository="openSUSE_11.2"/> <enable repository="openSUSE_11.3"/> </build> osc meta pkg home:frispete:KDE python-kde4-45: <build> <disable repository="KDE_Distro_Stable_openSUSE_11.1"/> <disable repository="KDE_Distro_Stable_openSUSE_11.2"/> <disable repository="KDE_Distro_Stable_openSUSE_11.3"/> <disable repository="openSUSE_11.1"/> <disable repository="openSUSE_11.2"/> <disable repository="openSUSE_11.3"/> <enable repository="KDE_Distro_Factory_openSUSE_11.1"/> <enable repository="KDE_Distro_Factory_openSUSE_11.2"/> <enable repository="KDE_Distro_Factory_openSUSE_11.3"/> </build> If I understand this correctly, BS should build python-kde4-44 for KDE_Distro_Stable* and openSUSE_11.3, while python-kde4-45 should build for KDE_Distro_Factory*. But: eric | python-enchant | | python-kde3 | | | python-kde4 | | | | python-kde4-44 | | | | | python-kde4-45 | | | | | | python-logilab-astng | | | | | | | python-logilab-common | | | | | | | | python-pylint | | | | | | | | | python-pysvn | | | | | | | | | | python-qscintilla | | | | | | | | | | | python-qt | | | | | | | | | | | | python-qt4 | | | | | | | | | | | | | python-rope | | | | | | | | | | | | | | python-sip | | | | | | | | | | | | | | | qgit | | | | | | | | | | | | | | | | qscintilla CentOS_CentOS-5 i586 (published) CentOS_CentOS-5 x86_64 (published) Fedora_13 i586 (published) Fedora_13 x86_64 (published) . . . x . . . . . . . . . . . KDE_Distro_Factory_openSUSE_11.1 i586 (published) . . . x . . . . . . . . . . . KDE_Distro_Factory_openSUSE_11.1 x86_64 (published) . . . x . . . . . . . . . . . KDE_Distro_Factory_openSUSE_11.2 i586 (published) . . . x . . . . . . . . . . . KDE_Distro_Factory_openSUSE_11.2 x86_64 (published) . . . x . . . . . . . . . . . KDE_Distro_Factory_openSUSE_11.3 i586 (published) . . . x . . . . . . . . . . . KDE_Distro_Factory_openSUSE_11.3 x86_64 (published) . . . . x . . . . . . . . . . . KDE_Distro_Stable_openSUSE_11.1 i586 (published) . . . . x . . . . . . . . . . . KDE_Distro_Stable_openSUSE_11.1 x86_64 (published) . . . . x . . . . . . . . . . . KDE_Distro_Stable_openSUSE_11.2 i586 (published) . . . . x . . . . . . . . . . . KDE_Distro_Stable_openSUSE_11.2 x86_64 (published) . . . . x . . . . . . . . . . . KDE_Distro_Stable_openSUSE_11.3 i586 (published) . . . . x . . . . . . . . . . . KDE_Distro_Stable_openSUSE_11.3 x86_64 (published) . . . . . . . . . . . . . openSUSE_11.1 i586 (published) . . . . . . . . . . . . . openSUSE_11.1 x86_64 (published) . . . . . . . . . . . . . openSUSE_11.2 i586 (published) . . . . . . . . . . . . . openSUSE_11.2 x86_64 (published) . . . . x . . . . . . . . . . . openSUSE_11.3 i586 (published) . . . . x . . . . . . . . . . . openSUSE_11.3 x86_64 (published) something excludes them which I don't understand. <OT> BTW, it would be cool to have a python-kde4 package (e.g package with a single name), that builds either from KDE 4.4.4, or KDE 4.5.0, without the need to obfuscate the spec with %if..%endif. Is that possible? </OT> Thanks, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0