openSUSE Build Service December 2010

buildservice@lists.opensuse.org

62 participants
61 discussions

[opensuse-buildservice] overriding project conf

by Christian Daudt

Hi, I've run into a couple of issues for which I can find no resolution, looking for some help. I'm running a private OBS to do Meego builds for arm, and in two case I seem to have gotten stuck due to the same problem, that my project inherits the prjconf from the repository. Here are the 2 cases: 1 - in one project (call it project A), I'm trying to rebuild a subset of packages from another project (call it project B), except that I'm replacing a few (bash, coreutils, etc) with busybox. The problem here is that projectA then has busybox but when anything gets rebuild in project A it loads bash and coreutils still because project B (which is the repository) has these rpms in its prjconf file (Preinstall). 2 - I'm trying to create 1 rpm which is just an aggregation of various rpms. So I have 1 project which creates this rpm, and then I with to use that rpm in the prjconf of projects that use this project as repository, but it still pulls in this project's repository's prjconf, which then pulls in all the original rpms which causes conflicts. I would really want to have an option to say "don't inherit the project conf" but there doesn't seem to be such an option. Any suggestions? thanks, Christian. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 1 month

[opensuse-buildservice] OBS @ FOSDEM?

by Uwe Geuder

Hi! We at Nomovok Ltd. have a couple of OBS installations running here, mainly for building natively on ARM workers. We have recently started to develop an extension we call worker pool. The idea is that several OBS instances can share workers from a common pool in a controlled way. The extension will be open source. We intend to publish our work at FOSDEM 2011 in form of a lightning talk. Does anybody else from the OBS community plan to attend FOSDEM in any way? Regards, Uwe Geuder Nomovok Ltd. Tampere, Finland uwe.gxuder(a)nomovok.com (bot test: correct 1 obvious spelling error) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 1 month

[opensuse-buildservice] couchdb

by Matwey V. Kornilov

Hi, There is `couchdb` package in server:database project and it is in unresolved state for all distros except 11.2 due to lack of erlang in server:database. I think it would be better to handle `couchdb` like `ejabberd` package which locates in devel:language:erlang and is aggregated by server:messaging. The second possibility is to add properly lines to the server:database project config. Anyway I hope that maintainers of devel:language:erlang and `couchdb` will read this. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 1 month

[opensuse-buildservice] Locked packages on SLES10 break update

by Lars Volker

Hi everyone, we operate an own installation of OBS 2.0.4 and use it to build several php-related packages for various platforms including SLES 10 + 11. It happens only for SLES10, that automatic updates of our packages will fail. All packages coming from our repository are flagged as "locked" and zypper will not upgrade them. I also cannot find the lockfile in /etc/zypp/locks as suggested by http://en.opensuse.org/openSUSE:Libzypp_locksfile. When running "zypper install locked-package-name" it will complain about the locks. If one proceeds and selects "unlock" from the list of choices, then all packages will be installed, but each one will throw a dependency error during installation. I've read (German: http://www.linux-club.de/viewtopic.php?f=3&t=81259&sid=d48a82d276afac5e2c0e…), that any external package will be locked automatically in SLES10. Does this include external repositories as well? The zypper version is very old on SLES10 and does not seem to support the lock-managing commands. sles10:~ # rpm -qa | grep zypp zypper-0.6.200-0.4.49 libzypp-2.100.3-0.4.23 libzypp-zmd-backend-7.1.1.0_2.16-0.4.46 Now the question is: Is there a way to flag or sign our repository, so that the packages will not get locked by SLES10? We rely on automatic upgrades of packages distributed from those repositories, so manual install is not a feasible solution. With kind regards, Lars Volker -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 1 month

[opensuse-buildservice] OBS cleanup -> removal of outdated repositories

by Adrian Schröter

Hi, Please excuse the cross post. You may have noticed that we have higher and higher build load on build.o.o. While the new dispatcher algorithms are still good to prefer the "right" jobs, it is still a sign that we may should cleanup. My current plan is to remove all repositories in home projects, which have not been touched this year. Not touched means, no source submission and no meta data has been altered at all. Additionally also all non-home projects, which have not been touch in last two years. This will affect 5668 out of 15668 projects. Why remove repos and not just disable the build ? This will free disk space on our servers and also on all mirrors. As result we can be mirrored more easily. Will any source get lost ? No. How to enable it again ? Just add the wanted repos again. Which projects will get affected exactly ? Find a full list here: http://www.suse.de/~adrian/OBS-remove-list-candidates There is a project which has not been touched, but the repos are still anyway important ! Just drop me a mail .... Why not drop the entire project now that we have an undelete function ? I thought about that, but currently the webui just says that the project does not exist. It does not offer to undelete it, so that might be too agressive for now. Why not drop people a mail and ask them to remove it ? Way to many accounts have no valid email adress and past experience showed that people are often not react when they lost interesst in their project. May plan is to do the removal end of this week, except more discussion about this is needed. Just tell me your opinion, also when you support this ;) 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

10 years, 1 month

[opensuse-buildservice] project hasn't starting building for 20 hours and counting...

by Douglas Hubler

https://build.opensuse.org/project/monitor?project=home:sipfoundry:4.4 It's gotten progressively slower over last month. Questions 1.) Was there was a change to the queueing algorithm? 2.) Anyone else see slower than normal build scheduling? 3.) Is queue algorithm published somewhere? 4.) I think home projects don't show up in global monitor? If so, is there a way home project can see where they are in the total queue? 5.) Is there anyway someone can bump my build up, there is a nasty bug i'd like to get out to folks. Yes, i know, it's a free service, but just thought I'd ask. Thanks -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 1 month

[opensuse-buildservice] [PATCH] Notifications do not support multiple action requests

by Islam Amer

Hello, I was trying out multiple actions in one request and noticed that the notifications contain only the last action. I looked at the code and found this in /usr/lib/obs/server/BSNotify.pm line 82 : # FIXME: how to handle multiple actions in one request here ? # right now the last one just wins .... So here's a proposed fix : add an actions key in the reqinfo hash, that contains an ordered list of hashes that contain the details of the actions. The Data::Dumper of reqinfo produced by the attached patch looks like this : $VAR1 = { 'when' => '2010-09-30T00:12:13', 'actions' => [ { 'sourcerevision' => '1', 'sourceproject' => 'Foo:Devel:Personal', 'deletepackage' => undef, 'targetproject' => 'Foo:Trunk', 'sourcepackage' => 'libfoo', 'type' => 'submit', 'targetpackage' => 'libfoo', 'deleteproject' => undef }, { 'sourcerevision' => '1', 'sourceproject' => 'Foo:Devel:Personal', 'deletepackage' => undef, 'targetproject' => 'Foo:Trunk', 'sourcepackage' => 'bar', 'type' => 'submit', 'targetpackage' => 'bar', 'deleteproject' => undef } ], 'author' => 'bob', 'description' => 'Test', 'state' => 'new', 'comment' => undef, 'who' => 'bob', 'sender' => 'bob', 'id' => 32, 'type' => '' }; Is this change acceptable ? If so, I guess the notification plugins will have to be changed to accommodate this. Thanks, Islam Amer

10 years, 1 month

[opensuse-buildservice] Problem building a library package for OpenSUSE_11.2

by Angelos Tzotsos

Hello everyone, I am a new user of Build Service but an old user of OpenSUSE. I am trying to provide a repository for a project I am involved in, called OrfeoToolbox. https://build.opensuse.org/package/show?package=OrfeoToolbox&project=home%3… With the help from people over the #opensuse-buildservice Freenode channel, I managed to fix some errors in the spec file I created, and my package now builds correctly (with no errors, only few warnings) for Factory and OpenSUSE_11.3 The spec file is here: https://build.opensuse.org/package/view_file?file=OrfeoToolbox.spec&package… When I try to build for OpenSUSE_11.2 I get the following error: |... running 03-check-binary-kernel-log ... running 04-check-filelist ... checking filelist OrfeoToolbox-3.6.0-74.1.i586.rpm: directories not owned by a package: - /usr/lib/otb OrfeoToolbox-devel-3.6.0-74.1.i586.rpm: directories not owned by a package: - /usr/lib/otb System halted. https://build.opensuse.org/package/live_build_log?arch=i586&package=OrfeoTo… |I got suggestions to list every file of my package in the %files section, but they are way too many to do this. Also, I tried other ways of declaring my file list, like /usr/lib/otb/* with same results (errors only for OpenSUSE_11.2) Can someone please propose a solution to this? Regards, Angelos -- Angelos Tzotsos Remote Sensing Laboratory National Technical University of Athens http://users.ntua.gr/tzotsos -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 1 month

[opensuse-buildservice] Re: [PATCH] allow 'osc results PROJECT', as an alternative to 'osc prjresults PROJECT'. Flagged 'ls' without arguments as deprecated. This should really list relative to the working directory rather than all projects. It's now consistent with running 'osc r' in PRJ/PKG working directory.

by Marcus Hüwe

Hi, On 2010-12-02 23:43:44 +0100, OBS osc wrote: > From: Juergen Weigert <jw(a)suse.de> > > --- > osc/commandline.py | 14 ++++++-------- > 1 files changed, 6 insertions(+), 8 deletions(-) > > diff --git a/osc/commandline.py b/osc/commandline.py > index 62ed8c5..722ab02 100644 > --- a/osc/commandline.py > +++ b/osc/commandline.py > @@ -222,7 +222,7 @@ class Osc(cmdln.Cmdln): > """${cmd_name}: List sources or binaries on the server > > Examples for listing sources: > - ls # list all projects > + ls # list all projects (deprecated) Hmm I really don't like this change. IMHO we shouldn't start deprecating some UI commands unless we have a complete proposal for a reworked (consistent) UI. Introducing such a "transitional" syntax like "osc ls /" doesn't improve the situation (IMHO). Any opinions? If not I would like to revert some parts of your last commits. Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 1 month

[opensuse-buildservice] libgomp for ppc/ppc64

by Florian Leparoux

Hi, Someone know how i can get the libgomp for ppc/ppc64 ? I can't build for powerpc since the obs When i tried to build gcc43 for my power7 i get this required package : glibc-32bit glibc-32bit-devel... Thanks for your help Florian -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 1 month

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service December 2010