January 2010 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Making kernel modules for specific kernel versions
by Roger Oberholtzer 07 Jan '10

07 Jan '10

I have been looking through http://www.novell.com/communities/node/9226/using-opensuse-build-service-cr… to see how to make kernel drivers in OBS. I have one question: can I specify the specific kernel version to be used? For example, openSUSE 11.2 came out with some release of the kernel, and there have since been updates. I would like to make the kernel driver for the original kernel that was delivered with openSUSE. How would I specify that? Is there a better way to do this? Is it possible to make a kernel driver that would load into any release of the kernel for an openSUSE release? For example, if I compile the driver for the -desktop kernel, can I do so in such a way that it can be installed on all -desktop kernels for that openSUSE release? -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- 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] building cross distribution packages
by Pedro Lopez-Cabanillas 06 Jan '10

06 Jan '10

Hi, I'm packaging my own programs using openSUSE build service, until now for openSUSE only, but I'm trying also packaging for other distributions. I've created a subproject at 'home:plcl:test', with only one KDE4 package (kmetronome) and repositories for openSUSE, xUbuntu, Fedora and Mandriva. I've started reading some documentation, at: http://en.opensuse.org/Build_Service/cross_distribution_package_how_to And a pointer provided by Will Stephenson: http://www.kdedevelopers.org/node/3994 Looking to the projects packaged by Lubos Lunak, like ksshaskpass and wmiface it seemed to me an easy task, but I was wrong... First, this error in Fedora (10, 11 and 12) packages: CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage The only way to fix it was to add "BuildRequires: gcc-c++". But, this doesn't match the Fedora documentation: http://fedoraproject.org/wiki/Packaging:Guidelines#Exceptions_2 "There is no need to include the following packages or their dependencies as BuildRequires because they would occur too often." And the C++ compiler is among those common packages. Why I need to include it in OBS? Second, for Mandriva there is a failure installing some dependencies. error: Failed build dependencies: kde4-macros is needed by kmetronome-0.9.1-28.1.x86_64 kdelibs4-devel is needed by kmetronome-0.9.1-28.1.x86_64 dbus-devel is needed by kmetronome-0.9.1-28.1.x86_64 alsa-lib-devel is needed by kmetronome-0.9.1-28.1.x86_64 I've tried to follow the directions in this document: http://wiki.mandriva.com/en/Development/Tasks/Packaging/Policies/Kde4 But something is wrong, and I am unable to see what and where. Any clues? Regards, Pedro -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 8

[opensuse-buildservice] RPM_OPT_FLAGS difference between osc build and rpmbuild
by Dave Plater 06 Jan '10

06 Jan '10

Hi, I'm trying to find why home:plater:branches:openSUSE:Factory:Contrib lilypond fails on make docs with osc build or build service but succeeds with rpmbuild. I'm busy comparing logs and noticed that my rpmbuild expands $RPM_OPT_FLAGS to include -g and -m64 whereas with the build service these flags aren't present. Whether this is why docs fail to build with osc or not I don't know but surely the -g flag affects the debug rpms and after looking at the gcc man page, I'm not to sure of what -m 64 means. Any help with this project will also be much appreciated, spec file at :- https://build.opensuse.org/package/view_file?file=lilypond.spec&package=lil… and build log at :- https://build.opensuse.org/package/live_build_log?arch=x86_64&package=lilyp… Thanks Dave P -- 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] tail: cannot open `debian/changelog' for reading: No such file or directory
by Richard Bos 05 Jan '10

05 Jan '10

I'm trying again to build packages for xUbuntu and Debian, but I'm encountering the following obstacle: tail: cannot open `debian/changelog' for reading: No such file or directory dpkg-buildpackage: error: tail of debian/changelog gave error exit status 1 Hopefully someone has a solution or a hint how to tackle this obstacle. At the top of the build log there is: processing specfile /home/richard/packages/osc/home:rbos:ib/ib2009/ib2009.dsc ... running changelog2spec --target debian --file /home/richard/packages/osc/home:rbos:ib/ib2009/ib2009.dsc don't know how to convert changelog to format 'debian' init_buildsystem --clean --rpmlist /tmp/rpmlist.jO8i2H /home/richard/packages/osc/home:rbos:ib/ib2 Versions installed are: linux:~ # rpm -q build osc build-2009.09.23-2.3.1.noarch osc-0.120-2.1.i586 This one has in /usr/lib/build/changelog2spec (from the above mentioned build package): 191 192 die("don't know how to convert changelog to format '$target'\n") if $target ne 'rpm'; 193 Will it ever be possible to pass that line if --target != rpm as is the case with building Debian based packages? Is it possible to convert a .changes file into a debian.changelog? -- Richard -- 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 version 1.7 Beta 1 release
by Adrian Schröter 05 Jan '10

05 Jan '10

Just in time as christmas present we release openSUSE Build Service 1.7 Beta 1 For us developers this mean we shall not create large changes anymore until version 1.7 got released. Instead we shall complete the new APIs and fix them because they need to stay stable after 1.7 The current exceptions for new feature or api changes have been noted so far: * Defining attributes will not be done in project meta data in final release, but via own attribute controller. * 1.7 may offer additional informations about the scheduling state of a repository. Please check first with us, if you plan to add another feature or make larger changes. The main features as documented in our road map are: * Fast scheduler using SAT solver now. * Clean Product builds * Attribute system - Allows to define global keys which can be set for projects, source packages and each binary package. - fast lookup and browse interface (Complete except for the attribute definition api) * New request types - delete request - change devel information request - automatic cleanup options on submit request - review mechanism for requests * Lookup for build dependencies - "osc dependson" and "osc whatdependson" are telling the dependency states between the packages according to calculations of the scheduler * SLP lookup support in backend runlevel scripts for automatic setup. New features, which are still declared as experimental and incomplete: * Source services. The core functionality is ready but we lack a number of services and practical experiences still. * patchinfo support is only good enough to submit informations. The server is not creating updates via it yet. Our roadmap is maintained here: http://en.opensuse.org/Build_Service/Roadmap My hope is that we get the 1.7 final release out in January or February next year. Packages can get found in the openSUSE:Tools:Unstable project: http://software.opensuse.org/search?baseproject=openSUSE:Tools:Unstable&q=o… Due to the lack of a final place for tar balls (due to our move away from forge) we do not release a tar ball this time. Please use either the one from our packages or get the source via git: http://en.opensuse.org/Build_Service/Run_from_git The final release will also get released as Add-On product and appliance (Live image). This means OBS products built by OBS ;) -- 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

4 8

[opensuse-buildservice] _workerstatus returning wrong info and other questions
by Jon Nelson 05 Jan '10

05 Jan '10

I have a local OBS instance, and I have _3_ problems/questions I was hoping to get some help with. I am running 1.6.0-7.2 on openSUSE 11.2 1. When I call /build/_workerstatus, I get back XML (as expected) but the contents are wrong. Specifically, I have *4* workers configured for the local host, but I get back *5* <building/> elements. One of the elements is just plain wrong. The workerid is the duplicated from one of the others, it's starttime value doesn't change even after multiple restarts of the worker, and so on. What's going on here? Is this related to the (still unfixed?) bug where one cannot reduce the number of workers? 2. When can we expect the next 'stable'-ish release of the obs server component? Recent versions of osc seem to have their fair share of issues with obs 1.6. 3. Sometimes my builds seem to get stuck in loops. Usually, some core library like libtool or glibc changes, and that kicks off a rebuild of, well, everything. It seems, then, that things get stuck in a loop and some packages get rebuilt multiple times, and yet there are no obvious loops present in the dependencies. What might be going on, and how do I diagnose -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 11

[opensuse-buildservice] expansion error: nothing provides kernel-source
by Todor Prokopov 05 Jan '10

05 Jan '10

Hello buildservice developers, Recently there was a kernel update for the openSUSE 11.2 kernel. Since then I get the following expansion errors when building my KMPs for openSUSE 11.2/x86_64: nothing provides kernel-source = 2.6.31.8-0.1 needed by kernel-syms, nothing provides kernel-source = 2.6.31.8-0.1 needed by kernel-xen-devel, nothing provides kernel-source = 2.6.31.8-0.1 needed by kernel-default-devel, nothing provides kernel-source = 2.6.31.8-0.1 needed by kernel-debug-devel, nothing provides kernel-source = 2.6.31.8-0.1 needed by kernel-desktop-devel The package in question is mvimpact_acquire-1_10_96 in home:koprok repository. The expansion errors happen only for openSUSE 11.2/x86_64. The same package builds without errors for openSUSE 11.2/i586 and also for openSUSE 11.1 and 11.0. Thank you in advance, Todor Prokopov -- 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] How can I remove packages that should not be published
by Richard Bos 05 Jan '10

05 Jan '10

Hi, I don't want to publish the packages in this project: https://build.opensuse.org/project/show?project=server:Kolab:STABLE Hence I do not allow the packages to be published on repository level, but the packages are still published, see e.g.: http://download.opensuse.org/repositories/server:/Kolab:/STABLE/openSUSE_11… How can I remove the packages from the above location? I tried: # osc wipebinaries server:Kolab:STABLE --repo=openSUSE_11.1 the return value is 'ok', but the packages are still there. How can I empty the download location (http://download.opensuse.org/repositories/server:/Kolab:/STABLE/openSUSE_11… -- TIA, Richard -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 6

[opensuse-buildservice] chroot: cannot run command `dpkg': No such file or directory
by Richard Bos 05 Jan '10

05 Jan '10

I'm trying to build .deb packages. I have created the different files that are needed for .deb packages, such as debian.control, debian.rules and the .dsc file. The tarbals and changes file exists as file, and as a side note the package builds find for many rpm based distributions. When I execute an 'osc build Ubuntu_9.10 i586 ib2009.dsc' , or another one like: osc build Debian_5.0 i586 ib2009.dsc, the build fails with: ...... ...... cycle: libpam0g -> libpam-runtime -> libpam-modules breaking dependency libpam-modules -> libpam0g cycle: g++-4.4 -> libstdc++6-4.4-dev breaking dependency g++-4.4 -> libstdc++6-4.4-dev done installing autotools-dev-20090427.1-None.all chroot: cannot run command `dpkg': No such file or directory The buildroot was: /var/tmp/build-root-Ubuntu_9.10-i586 Did I forget something, like a dependency? I have attached the related .deb files, as they are not present on the build server. Hopefully, can shine some light on this error. -- TIA, Richard

1 3

[opensuse-buildservice] RPM Macro %cmake_kde4
by Pedro Lopez-Cabanillas 04 Jan '10

04 Jan '10

Hi, The "%cmake_kde4" RPM macro doesn't accept arbitrary arguments? I need in "kmidimon" (OBS project "home:plcl:kde4") a boolean option "STATIC_ASEQMM" controlling if the libaseqmm library is built and statically linked to kmidimon, or the shared library is used instead. So my first guess was to do something like this in kmidimon.spec: %build %cmake_kde4 -DSTATIC_ASEQMM=NO But the above syntax fails. Looks like the macro doesn't accept arguments other than "-d builddir". By the way, I don't understand why is needed the option "-d" for out of source builds in RPM specs. Out of source is convenient for a developer, or to hand building a program, but RPM already provides a disposable building environment, so building out of source is redundant, IMO. BTW2. Is there an upstream repository for the macros.kde4 file? Regards, Pedro -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] kbackup expansion error for Mandriva-2010
by Martin Koller 04 Jan '10

04 Jan '10

Hi, in my project https://build.opensuse.org/package/show?package=kbackup-kde4&project=home:m… I get the following expansion error for Mandriva 2010: "nothing provides libkde4-devel" The spec file works fine with openSuse though. How can I know what the name of the corresponding package is in other distributions ? -- Best regards/Schöne Grüße Martin () ascii ribbon campaign - against html mail /\ - against microsoft attachments Geschenkideen, Accessoires, Seifen, Kulinarisches: www.bibibest.at

3 2

[opensuse-buildservice] Can't cd into tmpdir for Mandriva 2008
by Richard Bos 04 Jan '10

04 Jan '10

Hi, I get the following build error: + /usr/share/spec-helper/clean_files Can't cd to /var/tmp/inkomstenbelasting-2008-11.1-buildroot: No such file or directory at /usr/share/spec-helper/clean_files line 17. error: Bad exit status from /var/tmp/rpm-tmp.5225 (%install) This is for Mandriva-2008 For a lot of other rpm based distributions the same build goes fine, from CentOS_5, Fedora 10, 11 and 12 and of course all current openSUSE releases. See http://download.opensuse.org/repositories/home:/rbos:/ib What could be wrong with this (Mandriva 2008) distribution? Could it be that the "clean_files" is faulty? My tmppath definition is: BuildRoot: %{_tmppath}/%{name}_%{version}_root The build project is: https://build.opensuse.org/package/show?package=inkomstenbelasting&project=… -- Richard -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

Re: [opensuse-buildservice] osc 0.124 and obs 1.6 Compatibility
by Stephan Kulow 04 Jan '10

04 Jan '10

On Sunday 03 January 2010 18:55:24 Nashif, Anas wrote: > I guess I found it: > > RAILS_ENV="production" rake jobs:workerstatus Correct. we run this every minute. > > I had to disable the status graphs, they have been generating lots of > exceptions.. Also, "My Projects" does not work: The status graphs rely on the api cron job running as they retrieve the history from the api database. They should not generate exceptions but render "No data" though. > > Errorcode: uncaught_exception > Message: undefined method `name' for nil:NilClass > > <?xml version="1.0" encoding="UTF-8"?> > <status code="uncaught_exception"> > <summary>undefined method `name' for nil:NilClass</summary> > <details></details> > <exception> > <type>NoMethodError</type> > <message>undefined method `name' for nil:NilClass</message> > <backtrace> > <line>/srv/www/obs/api/app/models/db_package.rb:513:in > `to_axml_id'</line> > <line>/srv/www/obs/api/app/controllers/search_controller.rb:50:in > `search'</line> Hmm, that means it's a package without project. I'm afraid debugging that without your data will be near to impossible. My first guess is that your tables are out of sync for some reason ;( > .... > > I am now getting emails with the expections, the subject is too long, it > basically has the complete exception :) > I fixed that already, it only says "uncaught exception" now - and you can configure to get exception mails from api independently. Greetings, Stephan -- 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] osc 0.124 and obs 1.6 Compatibility
by Anas Nashif 03 Jan '10

03 Jan '10

Hi, While many operation using osc 0.124 work as expected with obs 1.6.0, I just noticed that submitrequest does not work and fails with: constructor needs either REXML::Element, String or Hash Is the 1.6 API compatible with osc 0.124? Anas-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 13