openSUSE Build Service August 2009

buildservice@lists.opensuse.org

54 participants
73 discussions

[opensuse-buildservice] Building Opensuse 11.0 JeOS liveCD using kiwi 3.66 -- Module is unknown
by Arani Bhattacharya 04 Aug '09

04 Aug '09

I tried to build a Live CD by following the instructions given here: http://en.opensuse.org/Build_Service/KIWI/Cookbook. I followed the steps and managed to successfully create the iso image file. I burned it on my CD, and tried to boot from it. Everything seems to be working properly, until it asks for the login name. I gave root as login name, and linux as password. Instead of logging in, I am getting the message "Module is unknown", and it again asks for the login name. Can anyone please tell me why this problem has occurred and how to solve it? Thanks for reading this. -- 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] Build Team Meeting
by Adrian Schröter 04 Aug '09

04 Aug '09

present: cwh, aj, bg, lrupp, adrian Topics: * Status * openSUSE for HPPA * Server Status New people: =========== - Berthold Gunreben (bg) joined the Build Team. He will take care about product development after learning the stuff. Welcome Berthold ! - Andreas Jaeger joined the meeting, because he took over product manager responsibilities for the openSUSE Build Service. Status: ======= adrian: * very first source service was working and automatically building a package. Working on getting stuff clean enough to deploy it on opensuse.org instance. abauer: * Working on attribute system and on external web site connection interface. HPPA Builds =========== Berthold develops HPPA openSUSE distro as hobby project. He will try build it in an own build service instance to learn the OBS code. We may publish later a HPPA openSUSE snapshot and look how much interesst is there in it. Server Status: ============== The three strong build hosts are still broken unfortunatly. openSUSE:Factory can get build anyway in time due to new dispatcher extensions (good/bad host implementation). -- 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

2 2

[opensuse-buildservice] Help in formatting a .spec file
by Anshul Jain 04 Aug '09

04 Aug '09

Hi, I need some help in formatting a .spec file for the Mozilla xulrunner package. The xulrunner rpm for 11.0 is built without the --enable-system-cairo option. I need to add the following line to the spec file:- ac_add_options --enable-system-cairo I have linked the xulrunner from the mozilla repository, but I do not know how to edit the _link file to add this line. Can someone help me please? :) Regards Anshul -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 5

Re: [opensuse-buildservice] Help in formatting a .spec file
by Michal Marek 04 Aug '09

04 Aug '09

Anshul Jain napsal(a): > On Tue, Aug 4, 2009 at 3:59 PM, Michal Marek<mmarek(a)suse.cz> wrote: >> Anshul Jain napsal(a): >>> I have linked the xulrunner from the mozilla repository, but I do not >>> know how to edit the _link file to add this line. Can someone help me >>> please? :) >> Run 'osc up -e' in the working copy and edit the specfile directly. >> >> Michal >> > I'm using the web interface not the command line option. Can I edit > the _link file directly? AFAIK the web interface has no support for editing linked packages (unless you want to type a patch manually...). Do a $ osc co $project $package $ cd $project/$package ... make changes ... $ osc ci Michal -- 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] Updating the Fedora targets
by Cristian Morales Vega 04 Aug '09

04 Aug '09

Hi, it seems Fedora has an uncommon update policy and the Build Service should build packages against the "update" Fedora repository and not against the base/release distro. See https://www.redhat.com/archives/fedora-packaging/2009-August/msg00000.html Is this possible? It's my understanding that new distros/versions are manually imported, so... -- 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] buildservice query
by doiggl＠velocitynet.com.au 04 Aug '09

04 Aug '09

Hello, Just a query in relation to the build service. In relation to Ram(memory) and Disk, I know things get done quicker in ram than on disk. Question: Could a ram disk be utilized do the compilation of packges/projects/rpms in faster memory instead of slower disk ? The build logs/completed rpms/are then copied off to disk, and the ramdisk is cleared off before the next project starts compiling. Get more packages done in the same amount of time. Extra Ram costs money but there would be a benefit as well. Also see http://www.vanemery.com/Linux/Ramdisk/ramdisk.html http://www.linuxfocus.org/English/November1999/article124.html Just a suggestion, worth a try, comments welcome. Glenn -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 6

[opensuse-buildservice] Conventions for game packages
by Vincent Petry 03 Aug '09

03 Aug '09

Hello, I have been advised to use these conventions when packaging games: http://en.opensuse.org/Packaging/Games and have the following questions about the package splitting between base and game data: 1) Is it necessary to always put the data in a separate package ? Is there a maximum size (ex: < 10MB) for which it is okay to keep it as one single package ? Because if many small games have data packages, it will easily "spam" the package list. This info should be added on that wiki page (I can do that if someone can confirm). 2) How to handle the mentionned "bugfixes" updates ? If the upstream tar archive has changed, OBS will anyway rebuild both the base and data packages, if there is only one spec file. So after this it all depends on how the user chooses to do the update. But for the user it might also not be clear whether the data package needs to be updated as well. I guess this could be enforced using version numbers in the Require tag. What do you think ? 3) How is the Requires dependency applied ? I guess the base package requires the data package. Is it possible to make the data package require the base one at the same time ? (double-dependency) Thanks, Vincent -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 9

[opensuse-buildservice] Source Services 0.0.1, no more writing SPEC files ?
by Adrian Schröter 03 Aug '09

03 Aug '09

Just a heads up ... and a call for help of course ;) http://lizards.opensuse.org/2009/08/03/source-services-001-no-more-writing- spec-files/ I would be really happy if packagers with dedicated areas, like perl moduls, java packages and so on join the attempt to write spec file code generators. As you can read there is some groundwork, like mapping link libraries to package names which can be reused. thanks adrian -- 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

1 0

[opensuse-buildservice] osc up -u checks out expanded if there's no checkout on disk
by Jan-Simon Möller 03 Aug '09

03 Aug '09

Hi ! osc up -u should just checkout the unexpanded version. If a packages is newly linked into a project or more general there's no checkout of this package yet on disk, then even "osc up -u" checks out all sources. This is annoying for big projects, where you could do osc up -u and only expand the needed portions. This also applies to osc co -u . Best, Jan-Simon -- 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] [bugzilla-3.4] - Need assistance with .spec file
by doiggl＠velocitynet.com.au 03 Aug '09

03 Aug '09

Hello I am trying to compile bugzilla-3.4 and it ends up with this error: > bugzilla: An empty RPM is not allowed anymore in SuSE Linux > System halted Can someone have a look at the bugzilla.spec and last log file for me and tell me what needs to be changed/added/deleted to the file to see if this application will built please ? Details: https://build.opensuse.org/package/view_file?file=bugzilla.spec&package=Bug… https://build.opensuse.org/package/show?package=Bugzilla&project=home%3Adoi… Thankyou Glenn -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service August 2009