openSUSE Build Service September 2010

buildservice@lists.opensuse.org

57 participants
82 discussions

[opensuse-buildservice] build: improve local debian builds

by Marcus Hüwe

Hi, currently the build script doesn't maintain a "clean" chroot for local debian builds because it never removes unused packages from old builds. So I wrote a small patch which should fix it. The code is similar to the existing rpm implementation except that it is a bit more difficult to get a "unique" id from a package (for rpm the buildtime is used but debian doesn't provide something like that (or at least I didn't find anything:) )). In order to get the id from a *.deb package we do the following: * untar the control.tar.gz * calculate md5 from the sorted control file (using perl's default sort()) * sort all filenames from the control.tar.gz (except the control file) and calculate the md5 for each file * id == md5 of all concatenated md5 sums To get the id from an installed package we do the same (all relevant data is stored in /var/lib/dpkg/status and /var/lib/dpkg/info/*). Feedback, objections etc. are always welcome:) Marcus

10 years, 6 months

[opensuse-buildservice] repmod.xml not found

by Sascha 'saigkill' Manns

Hello Mates, from time to time i'm getting zypper ref issues like the following: Datei '/repodata/repomd.xml' nicht auf dem Medium 'http://download.opensuse.org/repositories/home:/saigkill/openSUSE_11.3/' gefunden. Datei '/repodata/repomd.xml' nicht auf dem Medium 'http://download.opensuse.org/repositories/home:/thomas- schraitle/openSUSE_11.3' gefunden. Datei '/repodata/repomd.xml' nicht auf dem Medium 'http://download.opensuse.org/repositories/home:/thomas- schraitle:/calibre/openSUSE_11.3' gefunden. Does anyone know, why the repmod.xml is missed? AFAIK OBS produces that File automaticly... Or not? -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.saschamanns.de Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English) Open-SLX : Linux convenient, simple, secure and complete

10 years, 6 months

[opensuse-buildservice] plymouth packages

by Nelson Marques

Hi, I've seen several plymouth packages on the build service from several people. I've been also toying around with plymouth 0.8.4 on openSUSE 11.3 (the version for Fedora 15, currently in rawhide). I'm just wondering if there are some guidelines or if someone already has some work done with the init scripts and mkinitrd to integrate it in opensuse, or if I can freely start hammering here and there? This is just something personal (getting plymouth on my opensuse machines). Nelson. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 6 months

[opensuse-buildservice] How can I configure OBS to use crossbuild?

by Francisco Javier Cuadrado

Hi, all! I'm trying to configure an OBS instance to use sh4 cross compilation, so I configured an OBS instance like it's said into README.SETUP file and I can compile for x86 architecture. Here I got my first problems, I can't compile for x86-64 architecture and I don't know why. But I don't want to compile for x86-64 architecture, so it doesn't matter, so I read some wiki articles[1, 2] to configure a project so it can compile for sh4 architecture and all seems to work well, I have an scheduler for sh4 but it doesn't compile anything, and I don't know if I haven't configured well my OBS or it's another kind of problem. Reading crossbuild wiki articles, I understand that once I have added my architecture to scheduler configuration and I have created my project with that architecture in its build target, OBS will create the chroot to build that project into a qemu, because OBS hasn't got any cross compiler for sh4 architecture. Is it right? Also, I read that OBS crossbuild can use cross compilers, for sh4 architecture there is a debian port that I will like to use as base for my project, how could I use it? Like you see, I'm fully lost and I will like to know more deeply how OBS crossbuild works. Regards. [1] http://en.opensuse.org/openSUSE:Build_Service_Concept_CrossDevelopment [2] http://en.opensuse.org/openSUSE:Build_Service_adding_build_targets -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 6 months

[opensuse-buildservice] php5 on sles11

by Peter Bowen

A recent update to php5 on SLES11 moved from 5.2.6 to 5.2.14. However builds are still against 5.2.6, meaning all the independent php5-* packages are still picking up a requirement on php5 = 5.2.6, rendering them uninstallable. How can we build against 5.2.14 so we get packages compatible with the updated version? Thanks, Peter -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 6 months

[opensuse-buildservice] I can't configure OBS to use SH4 cross compilation

by Francisco Javier Cuadrado

Hi, all! I have an OBS instance configured properly, I can compile packages to pre-configured build targets. Now, I want to configure my OBS to cross compile to SH4 architectures, I see a check button at the bottom of repositories configuration, so I think it's possible. So I read related wiki articles[1, 2], but always I get the same error: ** error saving project: unknown architecture: 'sh4' ** My idea is: 1. Create a new build target for SH4 architectures, like it's written in [2]. 2. Use debian SH4 port[3] as distribution packages. 3. SH4 Cross compilation into my own OBS What I'm doing is: 1. Adding sh4 architecture to OBS_SCHEDULER_ARCHITECTURES variable at /etc/sysconfig/obs-server file. 2. Executing: # osc -A http://localhost:81 meta -e prj debian-sh4 Adding the following repository section to XML file: <repository name="standard"> <arch>sh4</arch> </repository> But always I get the error that I mentioned before. Can anyone point me out to the right direction in this issue? [1] http://en.opensuse.org/openSUSE:Build_Service_Concept_CrossDevelopment [2] http://en.opensuse.org/openSUSE:Build_Service_adding_build_targets [3] http://ftp.debian-ports.org/debian/pool-sh4/ --- Regards, Francisco Javier Cuadrado -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 6 months

[opensuse-buildservice] Docs : Build Service Operations Guide .... help needed

by David Greaves

I thought it would be worth collecting information on managing an OBS: http://en.opensuse.org/openSUSE:Build_Service_Operations_Guide (No, there is nothing useful there yet but it was about to be deleted) Since this is generic documentation I thought it would be good to put it in the openSuse wiki rather than a more installation specific space. I thought it would be a good place to put some diagnostic approaches too... Comments welcome. Since I'm mentioning docs; I put together some of my notes on how I installed a distributed MeeGo community OBS with Xen workers: http://wiki.meego.com/Build_Infrastructure/Community_Builder/Installation David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 6 months

[opensuse-buildservice] On RHEL4 and SLES9 only Source packages are generated

by Johannes Weberhofer

Hello! In the below project I have the problem that it's build nicely in all systems except RHEL4 and SLES9 where after configuring it packs the sources and finishes the build successful. Unfortunately no RPMs are built. Any ideas? https://build.opensuse.org/package/show?package=maildrop&project=home%3Aweb… Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 7 months

[opensuse-buildservice] OBS 2.1 Beta 1 released

by Adrian Schröter

OBS 2.1 Beta 1 is available =========================== As usual packages can be found inside of the openSUSE:Tools:Unstable project of OBS and its repositories. The correct version tag for the packages and inside git is 2.0.103 for this release: http://download.opensuse.org/repositories/openSUSE:/Tools:/Unstable/ Appliances can be accessed via this wiki page as usual: http://en.opensuse.org/Build_Service/OBS-Appliance Appliance users can just update the appliance image or the packages and reboot for ugrading their instance. Others need to read the "README.UPDATERS" file with information about manual updating the server. There is also a new media, called obs-server-install inside of http://download.opensuse.org/repositories/openSUSE:/Tools:/Unstable/images/… which can be used to install an entire OBS server from scratch to hard disc. Special thanks go to LinuxFoundation, Intel and Nokia for their contributions to this release. We plan to release 2.1 Final in about 2 weeks. The following is an extract of the release notes with informations about the new features: Features: ========= * web interface improvements: - Linked projects and packages are shown if existing. - Source Service Editor can be used to add or remove source services. Also to edit each service parameters and to trigger a run. - Merged sources of linked packages can be shown and the merged files can be edited. - New submit requests can be created. - Existing repository configuration can be edited. Add or remove pathes or architectures. - Additional reviews by users or groups can be added to requests. The reviews can be processed as well in web interface. - Displayed load diagrams can be configured to any architecture now. - Source history and commit view has been added. * api - Support Clone and supersed of existing requests. "osc rq clone" can be used to clone packages from an existing request. When submitting these cloned packages the original request gets superseded. - api: Improved LDAP support updating user information from LDAP server (This functionality has been provided by Intel) - Read access control for package sources. New created projects or packages can get the "<sourceaccess>" flag to hide any access to the sources of a package. This includes access to the source files, source and debug packages and build log. (This functionality has been provided by the LinuxFoundation) * backend: - Source services to checkout from external SCM repositories have been added. This includes also necessary source services to compress tar balls, use spec/dsc files out of them or to update the version in spec/dsc files. - Accepted submit request store the exact merged versions to allow later tracking of the requests. osc and the web interface can show now the diffs of accepted requests as result. - aggregate allows to skip source packages now. (Functionality has been provided by Nokia). - File provides can be mapped to packages now in prjconf - GPG sign key can get modifed with increased expiration date - scheduler kills building jobs when switching to blocked/excluded/disabled state - Cross Build support for MIPS architecture (Functionality has been provided by LinuxFoundation) Changes: ======== * It is recommended to switch to MySQL database for the webui. Please see README.UPDATERS for details. -- 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

10 years, 7 months

[opensuse-buildservice] webui: add file to package

by Petr Vaněk

hi all, is it correct that I cannot add files into newly created package package? The form looks like this: ____ Source Services Add a service for source processing. Source Files ____ there is no "Add file" link/icon as it used to be. This link is available in already existing packages. thanks, petr P.S.: snippet from the source code of the webpage:  <h3>Source Files <img alt="Ajax-loader" class="hidden" id="spinner_files" src="https://static.opensuse.org/hosts/build2.o.o/images/ajax-loader.gif? 1274082977" /> </h3> </div> </div>

10 years, 7 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service September 2010