September 2007 - openSUSE Build Service

[opensuse-buildservice] Introduction
by Klaas Freitag 05 Sep '07

05 Sep '07

Hi, Adrian talked about me in the status and ask me for a short intro, which is a great idea and here it is. After the last internal restructuring of SUSE R&D I found myself in the position of an architect of the OPS/IPD department which takes care about all infrastructure issues in SUSE R&D. Fortunately, and I am very happy about that, we now have a distinct team that is dedicated to the development of the openSUSE Buildservice which will be the important part also of the next generation of our internal build system. The architects job is to influence and design the technologies used and built in the department together with the internal and external community :) I hope to be able to bring in some ideas about the base technology of the BS, have many discussions about the direction and the details which hopefully ends up in more transparency - for the project and the community, the technology, the direction we're going. Another focus will be the combination of internal and external systems to be be finally able to work on the openSUSE distribution all together internally and externally and still meet the needs of our business products when it comes to strange topics like NDAs, maintenance and stuff like that. About me: I am with SUSE since 1999 and was most of the time working on infrastructure tasks together with a great team. I was working on the BS infrastructure in the very beginning but were unfortunately eaten up by other tasks often. I am really happy that I now can spend more time on the BS again because it is the most exiting project I ever worked in. It already shows so much potential to help people to distribute their software. I think the BS can really change the world of free software distribution - let's see what we can achieve :-) If you allow me to have a wish already, please everybody on the list get into the discussion, give us your feedback about the technology, use and relevance of the BS. Help us to be more open through asking questions and bash us if we do not maintain transparency enough ;-) Thanks for listening, Klaas -- Klaas Freitag Architect OPS/IPD SUSE LINUX Products GmbH - Nuernberg --------------------------------------------------------------------- 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] ANN: Tutorial about extending osc / osc plugins
by Dr. Peter Poeml 04 Sep '07

04 Sep '07

Hi, http://en.opensuse.org/Build_Service/osc_plugins About writing osc plugins, new commands, or using the osc Python module. James: as one of the examples, I took my in-osc implementation of a "mirror_binaries" command. However, it can't do the same as your obs_mirror_project script, because it will probably not be called as root, and I tried to implement just some more generically useful thing. But it may still be interesting. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

1 0

[opensuse-buildservice] Status: Build Service
by Adrian Schröter 04 Sep '07

04 Sep '07

Hi, from now on, we will send each tuesday the current state of the openSUSE build service development to the list. This will include more than what we track on our news page in the wiki like current open issues and current tasks we do work on. Additionaly Klaas Freitag joined the Build Service team as architect. Welcome Klaas, maybe you want to introduce yourself and your goals a bit :) Status updates: * Build Service Development roadmap discussion between Michael, Klaas and Adrian with an agreement for the next 4-6 month. A version to publish is WIP (AI: adrian). * Improve source handling. We want to improve our source handling and also the cooperation possibilities within the OBS. And last but not least allow easy and transparent source changes/additions to openSUSE:Factory. Klaas posted already a concept paper for the server side, to be discussed on opensuse-buildservice(a)opensuse.org * We want to improve the security of the generated repositories of the OBS. It should become possible to destinguish between projects via the used gpg signing key. We will have a local meeting to discuss possible concepts with the SUSE security people. * Andreas Bauer diged into the memory leak problems of ruby/rails/OBS happens on api.opensuse.org . A final fix does not exist, but a workaround should protect us from downtimes in the future. * api.o.o will get deployed to a new version tomorrow as well, it will esp. include the larger updates from Thomas Scholz improving the build flag handlings. General updates: * Server move / down time of the backend of the build service will happen tomorrow as announced. * The Build Service will use the e-mail adresses stored within the Novell Account database. * some discussions about general hardware re-organisation and requirements for next year. please add stuff I missed (or wrote incorrectly), AJ will repost this as general openSUSE status tomorrow on opensuse-project. 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

1 0

[opensuse-buildservice] Extra repository for Qt4 packages
by Nikolay Derkach 04 Sep '07

04 Sep '07

Hi, According to my own experience in building Qt4 packages in the BS I think we need an additional repository for packages which depend on libqt4. It should contain Factory and other repositories (say 10.0, 10.1, 10.2) created on top of KDE:Qt project (custom projects) What for is it needed? Well, * to build _all_ the Qt4 packages for SUSE Linux 10.1 and older (aggregate of libqt4 doesn't work here) * to make packages that require the latest libqt4 avaible for distributions different from Factory (some programs require the latest qt to build, svn versions, etc...). Well, aggregate can solve this issue, but it's not smart to add libqt4 packages to every project. Maybe there are other advantages... What do you think? -- Regards, Nikolay Derkach --------------------------------------------------------------------- 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] Problems with libqt4 package
by Philipp Thomas 04 Sep '07

04 Sep '07

In order to build the current vym for SLES?SLED 10, I need Qt 4.3. Therefor I tried pulling in the libqt4 package from KDE:Qt. For this, I get expansion error nothing provides libqt4 Next I tried linking to it and putting Provides: libqt4 into libqt4.spec (shouldn't the package provide this by default?). Now I get --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 4

[opensuse-buildservice] xaw3d and openmotif packages for Mandriva and Fedora repository
by Ladislav Michnovič 04 Sep '07

04 Sep '07

Hello. I wanted to build timidity for Fedora 7 and Mandriva 2007 but I got expansion error : nothing provides openmotif, nothing provides openmotif-devel, nothing provides xaw3d xaw3d is not tranformed to "Xaw3d". I have to rewrite it manually. Can you please automate this replacement for Mandriva and Fedora? Thanks in advance. openmotif exists in Mandriva 2007.1, but I didn't find it for 2007.0 and Fedora7. Is there a way how to push binary RPM to my build? I know that I can build them myself in BS, but it' s really pain. Regards Ladislav. --------------------------------------------------------------------- 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] How to add custom patches on top of factory sources added through _link
by Veerapuram Varadhan 04 Sep '07

04 Sep '07

Hi All, I am working on http://build.opensuse.org/package/show?package=evolution-data-server&projec… and been wondering how to apply the two patches mentioned in the link to have a successful build. evolution-data-server-spec-dbg-cflags.patch has been added with "patch to SPEC file" option checked. (also, %debug_package seems to not generate proper debuginfo rpms - according to some sources - so, I am trying with CFLAGS) TIA, V. Varadhan --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 4

Re: [opensuse-buildservice] Proposal: Add LSB Symbol generation to the openSUSE build system.
by Alexey Khoroshilov 04 Sep '07

04 Sep '07

> Hello Build Team, > > I have a proposal. I am working with the LSB (and ISP RAS) on a > project to improve their symbol data in their database for ISV > applications. If you look at their project ( > http://ispras.linux-foundation.org/index.php/Main_Page ), you will see > they have an LSB Application Test Kit (ATK). An application writer > can have symbol data from their application submitted to the LSB > Infrastructure Project DB. Currently, they have PERL scripts that use > utilities like 'readelf' to extract the symbol information. They also > have a web front end to make it easy to submit the data. The goal is > that with symbol data from a broad set of applications, that better > decisions can be made about what APIs are being used (and can be > standardized) by the LSB. > > The LSB (and Markus Rex) would like us to run these scripts to get the > symbol data to add to the LSB database. It seems to me that it would > be easier (and quicker) to add the scripts to the openSUSE build > system. I would envision a check box that could be selected from the > openSUSE build interface that would say "Generate LSB Symbol data > files", to make it optional if people would like. Then, as part of > the build, the symbol files would be generated and available for the > LSB (ISP RAS) engineers to grab and put into the database. > > Thoughts? Why is adding of symbol data to the LSB database interesting to ISVs? Upload information about application binary dependencies to the LSB database is a "vote" for libraries and interfaces required by this particular application. More votes for an interface are more chances to be included into the next version of the LSB. The positive impact of the inclusion is as follows: - The Linux Foundation makes sure that all LSB certified distros provides the interface; - The LSB testing program checks that interfaces behaves as specified in its documentation on all distros (new tests are developed if required); - The Linux Foundation makes sure that the interface will be available in future LSB certified distros at least during 6 years [1]. Thus the LSB reduces ISV's expenses for support the Linux platform as a whole. There can be also additional benefits of integration of the LSB tools with the openSUSE Build Service. 1. The LSB tools detect some general and LSB-specific issues in application binaries. General purpose warnings includes: - superfluous library dependencies in application executables (when a library is in the NEEDED ELF section, but actually it is not required to the application) [2]; - usage of the interfaces, which are not the best practice or which are considered as obsolete; - known problems in the required interfaces according to the LSB problem knowledge base. LSB-specific warnings list usage of non-LSB interfaces and include recommendations how to make application LSB-compliant. 2. LSB Repository can be added to the standard list of the openSUSE Build Service repositories to automate creation of LSB-compliant packages. Creation of the LSB build target will require some improvements in LSB tools. [1] https://www.linux-foundation.org/en/Application_Compatibility [2] http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html -- Alexey Khoroshilov, Linux Verification Center, ISPRAS web: http://www.linuxtesting.org e-mail: khoroshilov(a)ispras.ru --------------------------------------------------------------------- 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] Request for new project Application:Geo
by Dirk Stoecker 04 Sep '07

04 Sep '07

Hello, I would like to request a new top-level project called Application:Geo - Used for all the geo-related programs like GIS/GPS/Mapping software, which currently is in science, Education:Desktop and other places, where it does not fit at all. examples: GMT, grass, qgis, libgdal, libproj, mapnik, gpsdrive and lots more - Also introduction the "Application" level, which should be used to reduce the top-level space a bit I think. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5

[opensuse-buildservice] frontend and sqlite3
by AgBr 03 Sep '07

03 Sep '07

Hello, I use obs-api-0.1.1-37.1. Is it possible to use frontend with sqlite3 database engine? my /srv/www/obs/frontend/config/database.yml: development: adapter: sqlite3 database: db/frontend_development.sqlite3 rake migrate returns an error: (in /srv/www/obs/frontend) >>>>>>>>>>>>>>>>>>>>>>> /srv/www/obs/common/lib <<<<<<<<<<<<<<<<<<<<<<<<<< Using global environment /srv/www/obs/frontend/config/../config/environments/development_base.rb Using global environment /srv/www/obs/frontend/config/../config/environments/development_base.rb == InitialDatabase: migrating ================================================= -- create_table("groups", {:force=>true}) -> 0.5798s -- add_index("groups", ["parent_id"], {:name=>"groups_parent_id_index"}) -> 0.2343s -- create_table("groups_roles", {:force=>true, :id=>false}) -> 0.4251s -- add_index("groups_roles", ["group_id", "role_id"], {:name=>"groups_roles_all_index", :unique=>true}) -> 0.0716s -- add_index("groups_roles", ["role_id"], {:name=>"role_id"}) -> 0.2138s -- create_table("groups_users", {:force=>true, :id=>false}) -> 0.2460s -- add_index("groups_users", ["group_id", "user_id"], {:name=>"groups_users_all_index", :unique=>true}) -> 0.0992s -- add_index("groups_users", ["user_id"], {:name=>"user_id"}) -> 0.1558s -- create_table("roles", {:force=>true}) -> 0.4221s -- add_index("roles", ["parent_id"], {:name=>"roles_parent_id_index"}) -> 0.1087s -- create_table("roles_static_permissions", {:force=>true, :id=>false}) -> 0.2324s -- add_index("roles_static_permissions", ["static_permission_id", "role_id"], {:name=>"roles_static_permissions_all_index", :unique=>true}) -> 0.1104s -- add_index("roles_static_permissions", ["role_id"], {:name=>"role_id"}) rake aborted! SQLite3::SQLException: index role_id already exists: CREATE INDEX "role_id" ON roles_static_permissions ("role_id") (See full trace by running task with --trace) What's wrong? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3