openSUSE Build Service November 2008

buildservice@lists.opensuse.org

66 participants
89 discussions

[opensuse-buildservice] How to bump release numbers?

by Andrew Jorgensen

We need to be able to force our release numbers to be higher than they are now. We don't need any control over them after they are bumped, just a one-time thing. Let me explain: Suppose we have been building software in one repository and we need to move to a new repository. Normally this would cause our release numbers to be reset to start at 0. We want our users to see upgrades though moving forward. Actually we rsync our repos off of the BS to another location, so for the users the location won't change but the release numbers will suddenly jump down. Now it's okay with us if to do this we have to tweak something in the backend in some database or something as what we're doing is moving from OBS to an internal service, but we need some way to do it. Also, are our users going to have a problem if the signing key changes for the repo? If they will have a problem is there a way to migrate the key over? Thanks, Andrew Jorgensen -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

[opensuse-buildservice] using a macro in the BuildRequires tag of a spec file leads to expansion error

by Christopher Lang

Hi, I am just experimenting with a spec file (for Fedora) that includes this line: BuildRequires: %kernel_module_package_buildreqs The macro "%kernel_module_package_buildreqs" is defined in the file "/usr/lib/rpm/redhat/macros" from package redhat-rpm-config, which is installed (I checked that). The Build server says: expansion error. Nothing provides %kernel_module_package_buildreqs It seems that the spec file walkthrough done by the build server before running "rpmbuild" does not resolve this macro properly. The consecutive "rpmbuild" call that the build server does in fact does resolve the macro (I verified that manually). Q: Is this the way it is supposed to be or should the build server actually resolve the macro in the spec file? There is a bug which is similar but in my case the macro is defined outside of the .spec file while in the bug the macro is defined inside of the spec file: https://bugzilla.novell.com/show_bug.cgi?id=305425 Some hint is much appreciated. I have to admit, that I am not runnig the latest version of the build server (NTARS): obs-server-0.5-3.1 obs-worker-0.5-3.1 obs-api-0.5-3.1 many thanks Chris http://www.acurana.de/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

[opensuse-buildservice] Build team meeting 2008-11-11

by Andreas Bauer

present: abauer, tpatzig, poeml, froh, jcborn, cwh Topics: * Status Status ====== abauer: * implemented binarydownload flag and downloader role tpatzig: * work on trainee project poeml: * aquired several new mirrors for distribution and buildservice repositories * mirrors can now set a maximum file size for redirections, requests for files over the limit won't be redirected to them * work on repopush and dvd release process * accelerated osc building for Factory froh: * packaged new obs package, build package is WIP jcborn: * work on new kiwi package * wrote kiwi-instsource plugin for enabling SLP in mini-isos -- Andreas Bauer SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

[opensuse-buildservice] Projects

by Joop Boonen

All, I was looking via: http://software.opensuse.org/search trough different packages in OBS. I saw that there quite a few duplicate projects. Some with identical new versions and some with old versions. I saw there are also quite a few overlaps with the fwbuilder package that I also have in OBS. So I'm wondering if there is a way to consolidate packages in groups so that more people can put effort in building packages and bundle their knowledge to get the best out of it. Currently a lot of people put a lot of time in "duplicate" packages. I'm wondering wouldn't it be better to start for for instance fwbuilder a security project that can be maintained by joined effort of people? In that way more package can be maintained in OBS I think? If this option if feaseble what is the best way to accomplish this? The project ofcourse needs to be created. Shall the individual OBS builder contact the other OBS builder? Regards, Joop Boonen. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

[opensuse-buildservice] Updated openSUSE Build Service

by Adrian Schröter

Hello, we have an updated Build Service Roadmap on the wiki now. It describes the features, we are working atm and what we will be able to release end of this year :) http://en.opensuse.org/Build_Service/Roadmap#Milestone_.27.27Aster.27.27_.2… The headline is to provide really everything, what we use to build our openSUSE 11.1 distro, which is build in build.opensuse.org since Beta 1. I think this makes us to the first Linux Distro who open source their automated distribution building system. We will provide beta package builds ASAP, with the goal to create an RC1 end of this month. have fun adrian PS: If some of us are not that responsive these days as usual (like me), this is caused by the usage of openSUSE Build Service also for our internal SLE products. We had to spend quite some time there, but it shows that the OBS is really good enough also for enterprise products ! :) -- 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

12 years, 2 months

[opensuse-buildservice] Fedora 8/RHEL kernel module packages - arch i386 problem

by Christopher Lang

Hi, I am just experimenting with the build server and Fedora kmod's. The problem is that all the Fedora rpmrc stuff for the build server "arch i586" comes with "i386" inside, which leads to a dependency problem with the Fedora package "kernel-devel" when rpmbuild is called by the build server: builder:/home/chris # chroot /tmp/root_2 su -c 'rpmbuild -ba --eval "%define _srcdefattr (-,root,root)" /usr/src/redhat/SOURCES/hso-kmod.spec' - abuild error: Failed build dependencies: kernel-devel-i386 = 2.6.23.1-42.fc8 is needed by hso-1.6.0-30.1.i386 The problem is that the Fedora package kernel-devel only provides "kernel-devel-i586". As a temporary solution I manually patched the "build" script (/usr/lib/obs/server/build/build) of the build server to include "--target i586". Well, it works, but this is not good. So my question is: Is there a possibility either by including something in the .spec file or by including something into the .conf file of the project to produce a similar effect? There is the variable ABUILD_TARGET_ARCH in the "build" script, but how do I set it using the .spec file or the .conf file? many thanks! cheers Chris http://www.acurana.de/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

[opensuse-buildservice] rpmlint error /opt/.... is not allowed anymore in FHS 2.2

by Richard Bos

Hi, I get the following error message: Wrote: /usr/src/packages/SRPMS/openims-1.0-0.src.rpm Wrote: /usr/src/packages/RPMS/noarch/openims-1.0-0.noarch.rpm ... checking for files with abuild user/group ... running 00-check-install-rpms ... installing all built rpms Preparing packages for installation... openims-1.0-0 ... running 01-check-debuginfo ... testing for empty debuginfo packages ... running 02-check-gcc-output ... testing for serious compiler warnings (using /usr/lib/build/checks-data/check_gcc_output) (using /var/tmp/build-root-openSUSE_Factory-i586/.build.log) ... running 03-check-binary-kernel-log ... running 04-check-filelist ... checking filelist openims: "/opt/OpenIMSCore" is not allowed anymore in FHS 2.2. As you can see the rpms is build fine, but rpmlint does not allow the build to finish completely... As those rpms are used to study the concept of the communication platform IMS, I don't see upstream to change the install location from /opt to an approved FHS location. In this case /opt is the correct location. This error is only generated in factory, Is there a way to prevent that rpmlint complains about /opt? I checked the rpmlint rpm for the error message, but I did not see a reference to the error message. Hence I do not see a possibility to use for example a construction with addFilter. Looking forward to an solution for this problem, if there is one! -- Richard Bos We are borrowing the world of our children, It is not inherited from our parents. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

[opensuse-buildservice] Error 'cannot read table of mounted file systems'...

by John Pye

Hi all I have a strange error here while building a Mandriva package, any idea what this is? Looks like suddenly OBS couldn't read its virtual hard drive? Cheers JP |Warning: network-up is needed by netfs in runlevel 5 installing libxrender1-devel-0.9.3-1mdv2008.0 installing libxext6-devel-1.0.3-1mdv2007.1 installing sysklogd-1.4.2-5mdv2008.0 installing libxscrnsaver1-devel-1.1.2-1mdv2008.0 installing libxft-devel-2.1.12-2mdv2008.0 installing basesystem-2008.0-3mdv2008.0 installing libtk-devel-8.5a6-8mdv2008.0 removing nis flags from //etc/nsswitch.conf... now finalizing build dir... texhash: Updating /usr/share/texmf/ls-R... texhash: Updating /usr/share/texmf-var/ls-R... texhash: Updating /var/lib/texmf/ls-R... texhash: Done. df: Warning: cannot read table of mounted file systems chown: missing operand after `/' Try `chown --help' for more information. /.build/build: line 1096: test: : integer expression expected ----------------------------------------------------------------- I have the following modifications for ascend.spec: 7c7 < Release: 0%{?dist} --- > Release: 10.1 115c115 < Requires: tktable < 2.10, tktable >= 2.8 --- > Requires: tktable < 2.10 ----------------------------------------------------------------- ----- building ascend.spec (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

[opensuse-buildservice] Start a Synce OBS repository?

by MasterPatricko

Hello, I would like to suggest starting a SynCE (http://www.synce.org) OBS repository. For those who don't know, SynCE is a framework to sync Windows Mobile PocketPC's and Smartphones with Linux machines. It handles transferring files, syncing PIM data with opensync, installing software on your device, and is getting to be pretty reliable (v0.12 now, started in 2002). For sometime now I have been maintaining the latest versions of SynCE software in my home repository (home:MasterPatricko:synce), mostly for my own use. But I have noticed that many people are finding my packages with the software search and using them, emailing me questions, etc. So the packages are clearly in demand. I have also talked to the upstream developers and they say that they get many questions from openSUSE users and because they do not have one, official, repository (unlike Mandriva [http://wiki.mandriva.com/en/2008.1_Tour#Easy_synchronization_with_Windows_M…] where SynCE is now a integrated part of the distro), people are found to be running old, incompatible, or wrongly-compiled versions of software. There are many other OBS users also maintaining SynCE packages, many of them obsolete, which causes increased confusion for the users. I don't know where we want to keep this SynCE repository. OpenSync has its own repositories and SynCE is in many ways linked to it. Probably just synce: would be sufficient. The SynCE page on the wiki is also woefully out-of-date, I am hoping to get round to updating it. Of course, I volunteer to help maintain this repository but any others are welcome as well. In particular I am a KDE(4) user so I am not very good at testing Gnome packages ... Regards, MasterPatricko -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

[opensuse-buildservice] openSUSE Factory build of home:/saigkill boinc failed

by Sascha Manns

Hello, now i'm try to package home:/saigkill boinc. The OS_11.0 runs perfectly. The OS-Factory BuildLog says: Wrote: /usr/src/packages/SRPMS/boinc-6.3.14-4.1.src.rpm Wrote: /usr/src/packages/RPMS/i586/boinc-6.3.14-4.1.i586.rpm Wrote: /usr/src/packages/RPMS/i586/boinc-devel-6.3.14-4.1.i586.rpm but a little bit later: .... running 03-check-binary-kernel-log .... running 04-check-filelist .... checking filelist boinc: "/etc/sysconfig/boinc-client" is not allowed anymore in SuSE Linux. boinc-6.3.14-4.1.i586.rpm: directories not owned by a package: - /usr/share/locale/ko_KR - /usr/share/locale/sv_SE System halted. Why the System halted? The RPMs was builded, but not released... -- Sincereley yours Sascha Manns Open-News-Network e.V. Web: http://saschamanns.gulli.to -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 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 November 2008