June 2012 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] "W: non-executable-script" for files which are executable in the sources
by Florian Höch 19 Jun '12

19 Jun '12

I get the above warning for some files in the following package: https://build.opensuse.org/package/show?package=dispcalGUI&project=home%3Af… rpmlint log for Factory i586: dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/wxDisplayAdjustmentFrame.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/ccmx.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/main.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/report.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/wxwindows.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/wxLUTViewer.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/colormath.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/encodedstdio.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/jspacker.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/util_str.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/wxMeasureFrame.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/safe_print.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/xrandr.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/argyll_RGB2XYZ.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/wxTestchartEditor.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/wxProfileInfo.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/colord.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/util_win.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/setup.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/postinstall.py 0644L /usr/bin/env dispcalGUI.i586: W: non-executable-script /usr/lib/python2.7/site-packages/dispcalGUI/dispcalGUI.py 0644L /usr/bin/env When I look into the source archive, the respective files have the executable bit set, so I'm not really understanding where the warning comes from. I've even hacked the spec file to make sure the files have the executable bit set (ie. I call chmod +x on the files in %prep), but it seems almost as if something removes it later? -- Florian Höch -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] Authorative list of allowed RPM groups?
by Florian Höch 18 Jun '12

18 Jun '12

Basically I'd like something which isn't prone to change often, as I originally got the RPM group (Applications/Multimedia) I used for a package that I'm trying to submit to Factory from http://en.opensuse.org/openSUSE:Package_group_guidelines, but it seems the group was since removed. Are there any "safe bets" from the general graphics category which are less likely to change? (rpmlint returns a different list of possible RPM group names, are those more reliable)? -- Florian Höch -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 6

[opensuse-buildservice] Bogus warning "W: python-naming-policy-not-applied /usr/lib/pythonX.X/site-packages/X/lib/Y.py"
by Florian Höch 18 Jun '12

18 Jun '12

If you have a python package named X, which happens to contain a subpackage lib/Y, OBS complains that "This package doesn't respect the naming policy for python packages. Its name should match the regular expression ^python(-|$).", which is nonsensical because you can't import from a package "python-Y" as hyphens are not possible in package names, and a subpackage just named "python" doesn't make sense either. The warning in the subject should thus be removed. -- Florian Höch -- 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] Creating anaconda style respin with OBS
by He Zhenxing 18 Jun '12

18 Jun '12

Hi, OBS has a great feature that it can define release media with production definition and uses kiwi to build the media, but I'm wondering if it also supports creating anaconda (RedHat/Fedora) style installation media or not. and if yes, where can I find the instructions? Thank you in advance! -- 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] Is Git backend for OBS available?
by He Zhenxing 18 Jun '12

18 Jun '12

Hi, What's the status of using git as the backend of OBS? Is this available in OBS 2.3? -- 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] IE8 build.opensuse.org webpage error
by Rick Liu 17 Jun '12

17 Jun '12

When I use IE8 on WinXP SP3 to open https://build.opensuse.org, I received Webpage error: Line: 6 Error: 'window.G_vmlCanvasManager' is null or not an object >From IE8's built-in script debugger it shows: jquery.flot.ming.js line 6 character 11617 aD=window.G_vmlCanvasManager.initElement(aD) Rick -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] priority for KDE:Release:48
by Mathias Homann 16 Jun '12

16 Jun '12

Hi, would it be possible to raise the priority for KDE:Release:48 a bit? By the way it is crawling right now, KDE 5.0 will be out before 4.8.4 is built... bye, MH -- gpg key fingerprint: 5F64 4C92 9B77 DE37 D184 C5F9 B013 44E7 27BD 763C () ascii ribbon campaign against HTML e-mail /\ www.asciiribbon.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

RE: [opensuse-buildservice] OBS 2.3 in VM : No Arm Build out the box...
by Rick Liu 15 Jun '12

15 Jun '12

> > I understand that this section should be added to my prjconf ... But it > means that my repository should contains a qemu-linux-user and qemu- > accel-arm package ... but original MeeGo doesn't contain them ... > Does it make sense to pick them from > /repositories/openSUSE:/Factory:/ARM/standard/x86_64 ? > Or is it preferable to pick up source and rebuild inside my OBS ? > > Regards > > Xavier > [Rick Liu] There's a third way not recommended by Andrian. You can modify "/usr/lib/obs/server/build/build" file on your obs-server to enable USE_SYSTEM_QEMU (set USE_SYSTEM_QEMU="--use-system-qemu"), and install qemu-linux-user package onto your obs-workers. In this way, you don't need to pick up from opensuse.org, or have source package under your obs. This is the way I'm using right now, but my company is working on bringing qemu source to our obs. The downside would be if you have too many workers, it'll be hard to maintain a consistent qemu version across workers. (some of cross build results depends on the qemu version you use.) Rick -- 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] Re: openSUSE Build Service - YaST:Head/yast2-core
by Arvin Schnell 15 Jun '12

15 Jun '12

On Fri, Jun 15, 2012 at 01:50:42PM +0200, Woski, Michael wrote: > On Friday 15 June 2012 12:03:59 you wrote: > > On Fri, Jun 15, 2012 at 09:14:44AM +0200, michael.woski(a)e-concepts.de wrote: > > > Hey Arvin, > > > > > > you submitted a new revision of the yast2-core package. This package I > > > think is causing some issue when I try to run the package manager. > > > > > > I think my yast packages are all consistently from the factory repository. > > > > They are not, see below. > > No update candidate for 'yast2-core-2.23.1-1.1.x86_64'. The highest available > version is already installed. > > No update candidate for 'yast2-xml-2.16.1-68.5.x86_64'. The highest available > version is already installed. Indeed, but yast2-xml-2.16.1-68.5.x86_64 in openSUSE Factory is from April 23rd, very old. The buildservice should have recompiled the package since it build-requires yast2-core-devel. Maybe someone with more knowledge about the buildservice can explain that. Regards, Arvin -- Arvin Schnell, <aschnell(a)suse.de> Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- 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] OBS 2.3 in VM : No Arm Build out the box...
by JAFFREZIC Xavier 15 Jun '12

15 Jun '12

Hi OBS gurus ... I'm trying to migrate for on old OBSLight on a dedicated hardware to a OBS 2.3 in a VirtualBox ... So I've started from obs-server.x86_64-2.3.0-Build1.16-vmx.tar.bz2 ... I've updated it to 2.3.1 with Zypper - I've successfully configured a project from MeeGo 1.2.0 Release : --> Created a Project in the webUI and edit the meta file to add a repository --> Created 2 subdirs in /srv/obs/build/<Project>/<Repository> : One is i586/:full, second is armv8el/:full --> imported to each directory the binary package for each architecture... -I've enabled armv8el arch for OBS_SCHEDULED_ARCHITECTURES in /etc/sysconfig/obs-server >From this point, I've created a package and use the previously defined project as build target ... It works well for i586 : builds and publishs NB : I've also applied correction on /etc/apache2/vhosts.d/obs.conf and remove "/src" in strings for "build results" section as proposed in the git... The problem is that armv8el : the state is scheduled and remains scheduled...in the webUI But the "Status" is build finished ... It acting as if the build process crash in the very early phase (so returns finished) but the package is not treated ... I've tried to use the 32bit version of the appliance but result is exactly the same ... Which command should I issue to monitor what is done when I issue a "trigger rebuild" In the /srv/obs/log/scheduler_armv8el.log file a event occurs on "trigger rebuild" but I've no idea to investigate deeper on the problem ... Please help !!!! Regards Xavier -- Disclaimer ------------------------------------ Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme. *** This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] EPEL as extra repo in OBS?
by Tim Serong 15 Jun '12

15 Jun '12

Hi All, A while ago Nelson Marques was asking about having EPEL added as an extra repo to OBS: http://lists.opensuse.org/opensuse-buildservice/2011-11/msg00140.html - but that discussion kind of petered out. Did anything ever come of this? Is there any way to build CentOS and RHEL packages on OBS that have dependencies in EPEL, short of building those dependencies with OBS too? For reference, I'm asking in the context of this bug/enhancement request: bnc#765456 - network:ha-clustering: build for RH-based distros https://bugzilla.novell.com/show_bug.cgi?id=765456 Thanks, Tim -- Tim Serong Senior Clustering Engineer SUSE tserong(a)suse.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] OBS check causing questionable failure.
by Roger Oberholtzer 15 Jun '12

15 Jun '12

When I build the mingw32 package, OBS makes a debug package. I did not (I think) request this. Part of the build checks the source. In my case, I get this complaint: mingw32-blt-debug-2.5-51.1 ... running 01-check-debuginfo ... testing for empty debuginfo packages ! ! //usr/src/packages/RPMS/noarch/mingw32-blt-debugsource-2.5-51.1.noarch.rpm: empty debuginfo/debugsource package, deleting ! ... running 02-check-gcc-output ... testing for serious compiler warnings (using /usr/lib/build/checks-data/check_gcc_output) (using //.build.log) E: mingw32-blt 64bit-portability-issue bltWindow.c:876 And then the build fails. Even though the RPMs I really wanted are made... Can I disable this check? Oddly, as I am building a 32-bit application, I would not expect a 64-bit complaint. And I see in the code that there is a #define for 32- and 64-bit compiles which the test ignores. The complaint is in code that is for the 32-bit version. Any help would be appreciated. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer(a)ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] feature request: a service to test spec file for distro specific policies
by .. ink .. 14 Jun '12

14 Jun '12

some distro's like opensuse seem to have policies on how a package is to be build and these policy are checked in the spec file in addition to rpm spec file requirements. The build service seem to check the policies after the code is compiled and the package is being build and then bail out if the limit on error points in reached. Trying to modify the spec file to go under the limit if not eliminating them means spinning up the entire thing from the beginning, build the sources and then check to see if a policy is not violated, only to see a new. Doing guess work on my part means wasting unnecessary resources on your part.I dont have suse locally so you guys' resources are my only hope :-) Having a way to process a spec file before building a package would save a few resources on your guys part. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] Re: [opensuse-factory] Calling for a new openSUSE development model
by doiggl＠velocitynet.com.au 14 Jun '12

14 Jun '12

Hello, >From a obs package throughput/turnaround/build time perspective, this thread about the SSD [1] is still valid. You can ask fusionio support, about what other effective ways of speeding up the obs. You could have a trial of a iodrive card. You can even register for a trial of a card, see[2]. Info about the cards, see[3] Card demo,see [4]its worth a look. Just my 2cents worth. The fastest fleet, is only as fast as the slowest ship in the fleet. Cheers Glenn [1] Use solid state disks [ssd] to improve obs build times. http://lists.opensuse.org/opensuse-buildservice/2012-06/msg00090.html http://lists.opensuse.org/opensuse-factory/2012-06/msg00532.html [2] Registration http://www.fusionio.com/platforms/ https://account.fusionio.com/register?authid=10&returnpath=%2Fplatforms%2F [3] Info about the cards. http://www.fusionio.com/platforms/iodrive/ -- 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] Open Build Service 2.3.1 released
by Adrian Schröter 14 Jun '12

14 Jun '12

Open Build Service(OBS) 2.3.1 just got released =============================================== This release brings support for Fedora 17 and for kiwi product building of ftp trees on remote build hosts. And of course a number of bugfixes as usual OBS 2.3.1 is published in "openSUSE:Tools" project: http://download.opensuse.org/repositories/openSUSE:Tools Appliances can be used as usual: http://en.opensuse.org/openSUSE:Build_Service_Appliance The official release notes: Feature backports: ================== * Support remote product build tree building * Make kiwi support packages configurable. Defaults are: Substitute: kiwi-setup:image kiwi createrepo tar Substitute: kiwi-setup:product kiwi Changes: ======== * Support Order: handling also during preinstall (for Fedora 17) * Added Fedora-17 default target * bnc and fate issue tags are also accepted with whitespace: bnc #123 (This requires to run migrations on api). * Increased timeouts for OBS inter connects Bugfixes: ========= * Use right architecture on spec file parsing when project configuration contains a "Target:" line * Fixed warning messages about 'nextstate' in dispatcher * Fixed urls in webui to www.open-build-service.org * Init script fixes for automatic deployment of workers * Fixed debian handling for exporting sources -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[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