November 2008

[opensuse-buildservice] Build Team Meeting Minutes
by Adrian Schröter 04 Nov '08

04 Nov '08

present: mls, jcborn, tpatzig, mjung, freitag, adrian, poeml, dmueller Topics: * Status round. * OBS Roadmap Status round ============ mls: * reworked classic kiwi processing in OBS jcborn: * created branch in kiwi svn for OBS * bugfixing and patch merging for * kiwi packages for OBS build in home project currently mjung: * Presented trust concept work in university * started implementation of trust value calculation freitag: * working on hermes rewrite due to feedback of Andreas and … [View More]

1 0

[opensuse-buildservice] Kiwi-inside-obs - bug-squashing the loop
by Jan-Simon Möller 04 Nov '08

04 Nov '08

Hi! We improved kiwi now to be able to build also images for arm (and other architectures) on an x86 host. Only remaining is the rebuild-loop when kiwi is used inside obs. Let's hunt that little bug now ;). Summary: The scenario is like this: project "imaging:Admin", package "foo", repository "image". Simple kiwi-config (only bootstrap section!), output is ext2-image. Filename ends in "*0.0.1" (version in the kiwi.xml). So far: build succeeds, things get uploaded here (also show up in /srv/… [View More]obs/build/<foo>), BUT not in /srv/obs/repos and the job is directly rescheduled and thus builds in a loop. here's the scheduler-log: event finished:imaging::image::obs-imaging-8d2731b6e7128e3694ffb623f20177a6 0 left) - imaging/image: obs-imaging built: 3 files looking at med prio imaging/image (0/0/1/0/17) - imaging/image expanding dependencies sorting 1 packages - obs-imaging (kiwi) +autoconf +automake [...] +openvpn +perl-base +python +python-xml +rpm +rpm-python +smart +terminfo-base +xenomai +zlib meta change, start build Use of uninitialized value in substitution (s///) at BSFileDB.pm line 86. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 1. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 1. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 1. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 2. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 2. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 2. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 3. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 3. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 3. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 4. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 4. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 4. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 5. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 5. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 5. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 6. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 6. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 6. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 7. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 7. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 7. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 8. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 8. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 8. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 9. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 9. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 9. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 10. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 10. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 10. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 11. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 11. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 11. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 12. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 12. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 12. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 13. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 13. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 13. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 14. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 14. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 14. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 15. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 15. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 15. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 16. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 16. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 16. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 17. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 17. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 17. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 18. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 18. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 18. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 19. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 19. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 19. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 20. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 20. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 20. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 21. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 21. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 21. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 22. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 22. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 22. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 23. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 23. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 23. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 24. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 24. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 24. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 25. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 25. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 25. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 26. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 26. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 26. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 27. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 27. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 27. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 28. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 28. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 28. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 29. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 29. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 29. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 30. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 30. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 30. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 31. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 31. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 31. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 32. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 32. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 32. scheduled: 1 building: 1, notready: 1 took 0 seconds to check the packages looking at low prio imaging/image (0/0/0/0/17) - imaging/image expanding dependencies sorting 1 packages scheduled: 1 building: 1, notready: 1 took 0 seconds to check the packages waiting for an event... Looks like BSFileDB doesn't find variables in this case. My worker sends these files: $VAR1 = [ { 'filename' => '/tmp//root_1/.build.packages/KIWI/limbo-auto-config.i686-0.0.1', 'name' => 'limbo-auto-config.i686-0.0.1' }, { 'filename' => '/tmp//root_1/.build.meta', 'name' => 'meta' }, { 'filename' => '/tmp//root_1/.build.log', 'name' => 'logfile' } ]; We need to find a way to accept kiwi's output filenames (other than .iso). I looked at bs_sched, but I'm (a bit) lost finding the right spot. best regards, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org [View Less]

3 12

[opensuse-buildservice] Finding dependent builds
by Luke Imhoff 04 Nov '08

04 Nov '08

Is there a way through the API to find out which packages depend on a given package? This has come up a couple times when I've been showing OBS to developers at my company. Here's a use-case: I have a patch to the kernel, so kernel-source, kernel-syms, and kernel-<flavor> are all directly affected by a change to their source (since they all share kernel-source's tarball). Being a careful developer, I want to make sure the change to the kernel doesn't break any kernel module packages … [View More]

1 0

[opensuse-buildservice] Building packages in projects against the previous build of Factory
by Vincent Untz 03 Nov '08

03 Nov '08

Hi, Beware, this is a naive question :-) When oS:F gets rebuilt, all packages in GNOME:Factory, eg, get blocked for quite some time, which makes it a bit more difficult to work (at least, for me). I was wondering if there was a way to build G:F against the last complete build of oS:F, so that G:F is not blocked for so long. Maybe people already considered this and it can't work? But, well, it'd make my life so much easier... Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To … [View More]

1 1

[opensuse-buildservice] Download counter
by Michael Behrisch 03 Nov '08

03 Nov '08

Hello, I played a little with the statistics and it is mentioning download counters for some packages and for others not. Even after having a (very short) look at the api and searching the list archive and the forums I could not find out for which packages / files the counters are enabled or how to enable them. Maybe someone here can shed a little light ...? Regards, Michael -- 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] install_info_prereq on CentOS
by Michael Behrisch 03 Nov '08

03 Nov '08

Hello, I tried to build netcdf on CentOS and it stumbled over the following line PreReq: %install_info_prereq As far as I understand it, this line is needed to prepare the installation of info files but the (CentOS) build went through without it as well. Is this feature unneeded (unsupported) on CentOS? Should I try to forward my changes to the package maintainer and which is the preferred way to do so? (I tried it once with a different package by mailing him directly and got no answer.)… [View More]

3 6

[opensuse-buildservice] Automatic test for correct installation
by Michael Behrisch 03 Nov '08

03 Nov '08

Hello, as far as I understand it, there is currently no test whether a package build by the build service can also be installed (if it is not used by other packages). Maybe there already is such a test and I just did not find the correct settings? If not, one solution would be to create a dummy package which has a BuildRequires line mentioning just the package to test. In the build part it could try to execute an exectuable of the package and report failures. Is it possible to create a … [View More]

2 2

[opensuse-buildservice] New Release in home:saigkill
by Sascha Manns 03 Nov '08

03 Nov '08

New Release: BOINC 6.3.14 necpp 1.4.1 -- 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

1 0

[opensuse-buildservice] Mandriva 2009 doesn't work
by Joop Boonen 03 Nov '08

03 Nov '08

It seems that the new buildservice distro isn't functional yet. <log> ----------------------------------------------------------------- ----- building coppermine.spec (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- su: incorrect password System halted. </log> Regards, Joop. -- 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] OBS i586 scheduler dead
by Guillermo Ballester Valor 03 Nov '08

03 Nov '08

Hello, I've seen in OBS status page that i586 scheduler is dead. I was wondering why some packages I updated were not rebuilding for i586. Is it a serious OBS failure? Thanks to all OBS developer team. Guillermo -- Guillermo Ballester Valor gbv(a)oxixares.com http://www.oxixares.com/~gbv Ogijares, Granada - SPAIN -- 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] Packaging failed
by Sascha Manns 02 Nov '08

02 Nov '08

Hello, no i'm making an Package with the OBS-API. I've written an *.spec File and the Buildsevice begins to build. But now i've an Error: --snip-- make[1]: Entering directory `/usr/src/packages/BUILD/boinc-6.3.14' make[2]: Entering directory `/usr/src/packages/BUILD/boinc-6.3.14' make[2]: Nothing to be done for `install-exec-am'. test -z "/usr/include/boinc" || /bin/mkdir -p "/var/tmp/boinc-6.3.14- build/usr/include/boinc" /usr/bin/install -c -m 644 'config.h' '/var/tmp/boinc-6.3.14- build/… [View More]

3 5

Re: [opensuse-buildservice] Build question for packing precompiled binairies of a different platform
by Ulf 02 Nov '08

02 Nov '08

I was able to create a RPM package for AIX 5.3 with precompiled binaries. First add these lines to your %description secion of your spec file. Target: %_target Target_cpu: %_target_cpu Target_OS: %_target_os Now create the package The best way would be to do a : rpmbuild -ba <spec file> on the target platform Or you can try a: # rpmbuild -ba --target ppc-ibm-aix <spec file> Check the description of your create package, you will get the values for _target, _target_cpu and … [View More]

1 0

[opensuse-buildservice] request release macro
by Joop Boonen 02 Nov '08

02 Nov '08

All, As Mandriva (mdv200*) , Centos (el*) and Fedora (fc*) also have their release in the package name I would like to request a release macro that still handles the package name in more or less the same way (the sub version get one higher every build. But more compliant to the releases. Currently the whole release number is not taken in account it's always replaced by a x.y release. Is it possible to create a macro or to handle it in a different way? Regards, Joop Boonen. -- To … [View More]

1 0

[opensuse-buildservice] Cross distro building question / request
by Joop Boonen 01 Nov '08

01 Nov '08

All, I'm building cross distro packages. But i yhave the following problem. I want to build packages is the following format for for example mandriva: *-|22mdv2008.0.rpm but OBS replaces options like: %define release %mkrel 1 Release: %{release}| |----------------------------------------------------------------- I have the following modifications for coppermine.spec: 27c27 < Release: %{release} --- > Release: 60.1 29c29 < Release: 1 --- > Release: 60.1 ---------------------------… [View More]

1 0

Main

Development

Information

Community

Social Media

Other

openSUSE Build Service