June 2012 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] RHEL-4, full filesystem?
by Ruediger Meier 12 Jun '12

12 Jun '12

Hi, since a few days I have this problem on RedHat_RHEL-4: ------------ Using BUILD_ROOT=/var/cache/obs/worker/root_10/.mount Using BUILD_ARCH=x86_64:i686:i586:i486:i386 Doing kvm build in /var/cache/obs/worker/root_10/root build09 started "build truffle.spec" at Tue Jun 12 14:56:38 UTC 2012. Building truffle for project 'home:rudi_m' repository 'RedHat_RHEL-4' arch 'x86_64' srcmd5 '13817094099cc0eac89c8601718f82fb' [...] now finalizing build dir... Filesystem Size Used Avail Use% Mounted on rootfs 49G 535M 48G 2% / build does not work on a completely full filesystem [ 77.131556] Power down. ------------------ It happens on different build hosts. Building locally works. For me it looks like a script on OBS which is incorrectly parsing the output of df. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] How to setup OBS to support multilib builing
by He Zhenxing 12 Jun '12

12 Jun '12

Hi, I have setup a local OBS (2.3.0), and I'm working on some packages that requires both 32 and 64 bit packages for building, I don't find a way to make this work. It seems OBS does not support building packages this way. I have put both 32 and 64 bit packages in the repository, but when I use package.i386 or package.x86_64 in the requires of the package to be built, the whole string include the arch name will be treated as a package name and OBS will complain that the package is unresolvable. Any help on this will be appreciated! Thank you! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] Deleting .svn directories
by Ciro Iriarte 11 Jun '12

11 Jun '12

Hi, I'm stuck with something that should be pretty simple, I'm trying to delete .svn directories as part of the build process for a package, "find" appears to find the directories but while trying to delete them it gets "No such file or directory". As this is reaaaaaally basic and is not working, is there any OBS particularity that would cause this?. Ref: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=kanne… Regards, -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 9

Fwd: [opensuse-buildservice] Re: Deleting .svn directories
by Ciro Iriarte 11 Jun '12

11 Jun '12

Oops, didn't CC the list.. ---------- Forwarded message ---------- From: Ciro Iriarte <cyruspy(a)gmail.com> Date: 2012/6/11 Subject: Re: [opensuse-buildservice] Re: Deleting .svn directories To: Malcolm <malcolm_lewis(a)bellsouth.net> 2012/6/11 Malcolm <malcolm_lewis(a)bellsouth.net>: > On Mon, 11 Jun 2012 07:54:21 -0400 > Ciro Iriarte <cyruspy(a)gmail.com> wrote: > >> Hi, I'm stuck with something that should be pretty simple, I'm trying >> to delete .svn directories as part of the build process for a package, >> "find" appears to find the directories but while trying to delete them >> it gets "No such file or directory". >> >> As this is reaaaaaally basic and is not working, is there any OBS >> particularity that would cause this?. >> >> Ref: >> https://build.opensuse.org/package/live_build_log?arch=x86_64&package=kanne… >> >> Regards, >> > Hi > Grab the source with the export command eg; > svn export -r175 http://gimp-dds.googlecode.com/svn/trunk/ gimp-dds > > Else something like; > # Remove cvs files > find source/ -name .svn* -exec rm {} \; > find examples/ -name .svn* -exec rm {} \; > > -- > Cheers Malcolm °¿° (Linux Counter #276890) > openSUSE 12.1 (x86_64) Kernel 3.1.10-1.9-desktop > up 7:37, 4 users, load average: 0.13, 0.06, 0.05 > CPU Intel i5 CPU M520(a)2.40GHz | Intel Arrandale GPU I could delete the .svn directories and repack de tarball, the idea was to modify the least possible the tarball provided by upstream. Regards, -- Ciro Iriarte http://cyruspy.wordpress.com -- -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Build fails because of wrong timezone on OBS buildhost?
by Fritz Elfert 11 Jun '12

11 Jun '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I experienced this problem several times in the past and always assumed, that my local clock is not perfectly in sync as usually, a rebuild trigger solves it. However, since it just happened again, I checked my local clock (perfectly in sync to the second due to NTP) and therefore investigated the logs more closely: Result: At least some build hosts on OBS apparently have the wrong timezone. Here are some log snippets: The build was started around 14:59 *MESZ*, (not UTC!), but - according to the build log - it started at 14:59 *UTC* which is clearly in the past. Note: The uploaded tarball is auto-generated on my Jenkins-CI and auto-committed to OBS following a successful local build. Therefore, the timestamps in the tarball are quite current. === Start of build on build02 Using BUILD_ROOT=/var/cache/obs/worker/root_6/.mount Using BUILD_ARCH=i586:i486:i386 Doing xen build in /var/cache/obs/worker/root_6/root build02 started "build wsgate.spec" at Mon Jun 11 14:59:50 UTC 2012. Building wsgate for project 'home:felfert' repository 'SLE_11_SP1' arch 'i586' srcmd5 '0aeba73255941d3fef6bcfde89bd42f9' processing specfile /var/cache/obs/worker/root_6/.build-srcdir/wsgate.spec ... [...] === Later in that build: + /usr/bin/gzip -dc /usr/src/packages/SOURCES/wsgate-1.0.0.tar.gz + tar -xf - tar: wsgate-1.0.0/webroot/js: time stamp 2012-06-11 14:58:28 is 316.234112878 s in the future tar: wsgate-1.0.0/webroot/css: time stamp 2012-06-11 14:58:28 is 316.232706758 s in the future [...] === Finally autoconf's sanity check fails: checking whether build environment is sane... configure: error: newly created file is older than distributed files! Check your system clock error: Bad exit status from /var/tmp/rpm-tmp.29510 (%build) So: Is it possible to fix the TZ of the build hosts or otherwise improve accuracy by using NTP? Thanks -Fritz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/WE1IACgkQboM4mAMyprDIqwCfb3UVjH1NW1UY0SESOZDA8R55 V9AAn0I5CvHDWd76BpFKbOF4W+Z+msNk =g//q -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] %goprep macro not found by rpm-build
by Michał Papis 11 Jun '12

11 Jun '12

I have created build script home:mpapis/sm-json and it fails, here is log of it's build https://build.opensuse.org/package/live_build_log?arch=x86_64&package=sm-js… I tried to google for this/similar error, and it looks like there is no %goprep macro, but I have no clue why it would be missing, I have searched for similar packages spec and I think I did everything properly - but still the error happens in both building via service and locally. after commenting the %goprep line it fails on %gobuild line. Thanks, Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 5

[opensuse-buildservice] cloning deleted package
by Ruediger Meier 11 Jun '12

11 Jun '12

Hi, I know about "osc undelete" but I don't have permissions in that particular project. Is there a way to copypac a deleted package? BTW how can I find out who has deleted the package? cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 4

[opensuse-buildservice] Problems with build26
by Fritz Elfert 11 Jun '12

11 Jun '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 To any admin: Apparently build26 currently has some problems. My build of wsgate already lasts for 2h (normally builds much faster) and the buildlog reveals some kernel panics: [ 159.304069] INFO: rcu_sched_state detected stalls on CPUs/tasks: { 2} (detected by 3, t=23371 jiffies) [ 159.305378] Stack: [ 159.305625] Call Trace: [ 159.306032] Code: 66 90 48 8b 05 36 63 b0 00 41 c1 e4 18 8b 68 34 ff 90 48 01 00 00 44 89 24 25 10 a3 5f ff 81 cd 00 04 00 00 89 2c 25 00 a3 5f ff [ 159.308052] 89 df 57 9d 66 66 90 66 90 5b 5d 41 5c c3 66 66 66 66 2e 0f [ 159.305676] Stack: [ 159.305676] Call Trace: [ 159.305676] Code: 2e 0f 1f 84 00 00 00 00 00 fa c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 fb c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 fb f4 <c3> 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 f4 c3 66 66 66 66 66 [ 125.458978] Stack: [ 125.458978] Call Trace: [ 125.458978] Code: 2e 0f 1f 84 00 00 00 00 00 fa c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 fb c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 fb f4 <c3> 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 f4 c3 66 66 66 66 66 [ 349.704093] INFO: rcu_sched_state detected stalls on CPUs/tasks: { 2} (detected by 0, t=70971 jiffies) [ 349.705412] Stack: [ 349.705684] Call Trace: [ 349.706122] Code: 66 90 48 8b 05 36 63 b0 00 41 c1 e4 18 8b 68 34 ff 90 48 01 00 00 44 89 24 25 10 a3 5f ff 81 cd 00 04 00 00 89 2c 25 00 a3 5f ff [ 349.708076] 89 df 57 9d 66 66 90 66 90 5b 5d 41 5c c3 66 66 66 66 2e 0f [ 349.707640] Stack: [ 349.707640] Call Trace: [ 349.707640] Code: 2e 0f 1f 84 00 00 00 00 00 fa c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 fb c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 fb f4 <c3> 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 f4 c3 66 66 66 66 66 [ 349.708097] Stack: [ 349.708097] Call Trace: [ 349.708097] Code: 2e 0f 1f 84 00 00 00 00 00 fa c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 fb c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 fb f4 <c3> 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 f4 c3 66 66 66 66 66 [ 555.168017] INFO: rcu_sched_state detected stalls on CPUs/tasks: { 2} (detected by 3, t=122337 jiffies) [ 555.169349] Stack: [ 555.169613] Call Trace: [ 555.170027] Code: 66 90 48 8b 05 36 63 b0 00 41 c1 e4 18 8b 68 34 ff 90 48 01 00 00 44 89 24 25 10 a3 5f ff 81 cd 00 04 00 00 89 2c 25 00 a3 5f ff [ 555.171990] 89 df 57 9d 66 66 90 66 90 5b 5d 41 5c c3 66 66 66 66 2e 0f [ 555.172034] Stack: [ 555.172034] Call Trace: [ 555.172034] Code: 2e 0f 1f 84 00 00 00 00 00 fa c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 fb c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 fb f4 <c3> 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 f4 c3 66 66 66 66 66 [ 555.171160] Stack: [ 555.171160] Call Trace: [ 555.171160] Code: 2e 0f 1f 84 00 00 00 00 00 fa c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 fb c3 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 fb f4 <c3> 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 f4 c3 66 66 66 66 66 [ 314.996342] Stack: [ 314.996342] Call Trace: [ 314.996342] Code: 74 30 83 fa 08 72 27 89 f9 83 e1 07 74 15 83 e9 08 f7 d9 29 ca 8a 06 88 07 48 ff c6 48 ff c7 ff c9 75 f2 89 d1 c1 e9 03 83 e2 07 <f3> 48 a5 89 d1 f3 a4 31 c0 c3 66 0f 1f 84 00 00 00 00 00 21 d2 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/TcHwACgkQboM4mAMyprDcjgCdFitTTvIwZf9SSyWTPTs2YN5z oTAAn3cCP0A//xVPy7TGLM/hqyW0JNke =K12B -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] led display Suppliers shared photos with you
by led display Suppliers 10 Jun '12

10 Jun '12

Dear Mr/Miss, Still be puzzling about looking for best led display supplier? Now it will be miles easier working with KEROSA! Here you can find competitive price and excellent quality with a best mix. We"ve been in led display career for many years. We know your market and your country well. Our business is flexible which something is more likely to be a friend chat. We never waste your time. Our conversation will be very efficient base on our good communication. Please reply as soon as possible .if you are working on some led display project. We are ready to make you a satisfied offer! Samuel Shezhen Krosa Techology Co.,Ltd. Address: Building 3,Park,Guanguang road,Bao"an District,Shenzhen,China. post 518000

1 0

[opensuse-buildservice] source services and debian packages
by Martin Koegler 08 Jun '12

08 Jun '12

I noticed two bugs/problems: * The OBS Webpage compresses files an additional time: https://build.opensuse.org/package/binary?arch=i586&filename=grandorgue_0.3… The page offers to download the files: https://api.opensuse.org/build/home:e9925248:grandorgue/Debian_6.0/i586/gra… The downloaded file is not the orginal file (content of http://download.opensuse.org/repositories/home:/e9925248:/grandorgue/Debian…), but the file gziped a second time. * debtransform produces incorrect diffs for empty files The version installed on the OBS builders produces an incorrect patch for empty files: ========================================================== --- grandorgue-0.3.0.6.1023.orig/debian/dummy +++ grandorgue-0.3.0.6.1023/debian/dummy ========================================================== dpkg-source reports a syntax error (https://build.opensuse.org/package/live_build_log?arch=i586&package=grandor…) ========================================================== dpkg-source: error: expected ^@@ at line 2 of diff `/usr/src/packages/SOURCES.DEB/grandorgue_0.3.0.6.1023.diff.gz' ========================================================== I'm exploring the possibilties of OBS. The source services provide a simple way to build RPM packages out of a SCM. I'm trying to do the same for DEB packages and managed to get at least something built. Using set_version and debtransform allowed me to build a source package, but the version number is strange for a Debian package, because set_version only insert the version without a release number. I didn't find any way to automatically adapt the version number of built binary packages. The debian build process takes the binary version number from the changelog. I didn't find any source service (similar to set_version) to adapt/generate a debian changelog. Therefore it is only possible to use a fixed version number (either in debian.changelog or in a changelog file in one of the tars). Regards, Martin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0