October 2008 - openSUSE Build Service - openSUSE Mailing Lists

Re: [opensuse-buildservice] Kiwi-inside-obs - bug-squashing the loop
by Ulf 31 Oct '08

31 Oct '08

Hi, installed 5480S. I still get excluded (file name sles10.kiwi). # osc results SLES10_SP2 i586 excluded Do I have to integrate any patch? Ulf -- GMX Download-Spiele: Preizsturz! Alle Puzzle-Spiele Deluxe über 60% billiger. http://games.entertainment.gmx.net/de/entertainment/games/download/puzzle/i… -- 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: Cross-build and Download on Demand - Major Milestone reached
by Martin Mohring 30 Oct '08

30 Oct '08

Hi, due to missing news about the OBS development Marcus, Jan-Simon and me are stepping in. Cross-build and Download on Demand, now integrated in one single patch, have reached a major milestone of "testing and usability". You can now use these new features by installing the following openSUSE:Tools:Devel packages: - qemu-svn+gcc3 - obs-all-cross The rest is the same as running a normal OBS in fact. We have successfully tested it for the following processor targets: - openSUSE:10.3 @ i586,ppc,x86_64 - Fedora:9 @ i586,ppc,x86_64 - Fedora:8 @ arm,i586,ppc,x86_64 - Debian:Etch @ arm,i586,ppc,x86_64 - Debian:Lenny @ arm,i586,ppc,x86_64 - Debian:Sid @ arm,i586,ppc,x86_64 You can then activate builds for the new targets. You must install the QEMU in the workers, then OBS Workers can automatically run ARM processor jobs. Emulated targets can be used like x86 targets on a x86 machine in local builds as well as OBS Worker builds. Also other distributions than this list should work, we have chosen for testing the widely used Distros from openSUSE, Fedora and Debian type. You do not need a remote OBS and no complete local copy to build for these targets from now on. A complete copy of a distro for Debian:Etch would need 50 GB local diskspace for processor architectures arm,i586,ppc,x86_64. But with Download on Demand, only those Packets needed are loaded on the local disk. Typical minimum loaded packages for a chroot with a compiler are no more than 200 MB per processor architecture versus 15 GB or more for a complete copy. Mega collections like "Fedora Everthing" spin are even bigger per architecture. After configuring the cross-build and download on demand feature, you can build and run for the listed targets. The qemu emulator is sufficently fixed to run on even oldest and newest ARM Processor Distributions with glibc 2.7, gcc 4.3 and kernel headers 2.6.26 (like Debian:Sid on ARM - Sid is the Factory equivalent for Debian). For more info about all this, read the wiki here: http://en.opensuse.org/Build_Service/Concepts/CrossDevelopment. In the next step we will test the quality of emulators for the other processor targets. Also, Jan Simon has already some news on OBS KIWI Imaging and zypper usage on the issue. He will soon report. Martin PS: Adrian, Andreas, I wish you Novell guys will soon step in and provide us also with a "real good" embedded targets distribution, e.g. an openSUSE Version for arm or sh4 Architecture. I want to run my Nokia N810 with an openSUSE distro and nothing else. -- 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] Question about Buildservice
by Sascha Manns 30 Oct '08

30 Oct '08

Hello, my Name is Sascha Manns, and i make my first Steps in compiling RPM's. For Testing i maked an Buildservice-Account (build.opensuse.org) with my Novell-Account. No i maked i Subproject in home:/saigkill:/boinc/ . I maked the Project-Description and have uploaded an ready compiled RPM through the Webinterface. Then i'm going to the right Side, Point "Repositories". I had installed the openSUSE 11.0 Repository and disabled x86_64-Build and Publish. Then i disabled Build-i586, but i left the Publish-i586 Button. Now i would like to access my Repository with: http://download.opensuse.org/repositories/home:/saigkill:/ but i become an Answer: "Object not found". Must i enable the Folder in my WebAPI? -- 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

2 1

Re: [opensuse-buildservice] Howto create a KIWI image with OBS
by Ulf 29 Oct '08

29 Oct '08

Hi, I tried to apply the patch to the current svn release obs-server-1.1.0.5466S, but the patches doesn' t work anymore (unable to find the lines to patch). Maybe kiwi will be working soon. Currently uploading a kiwi file results in the state exluded. Ulf -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

Re: [opensuse-buildservice] Howto create a KIWI image with OBS
by Ulf 28 Oct '08

28 Oct '08

No, I was unable to store the image. Unfortunatly I' ve no idea, how to fix it. The whole OBS is too complex for me. Ulf -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

Re: [opensuse-buildservice] Howto create a KIWI image with OBS
by Ulf 28 Oct '08

28 Oct '08

I removed some package in my sles10.kiwi and finally OBS started to create the image. But I can' t find the image :-(. Searched the whole disk for a file. But I' ve the same error as you, the building goes in an endless loop. It seems like the KIWI build process will not set the finish flag, unfortunatly I' ve no idea how to set it. But I' ll take look at the source code. Thanks for your work. Ulf -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/wasistshortview.php?mc=sv_ext_mf@gmx -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] perl packages fail in factory, why?
by Richard Bos 28 Oct '08

28 Oct '08

Hi, why do perl packages fail in factory? The packages build fine, and rpms are build but still the build status is failed. The end of the log shows that the rpms are build; Wrote: /usr/src/packages/SRPMS/perl-Mail-IMAPClient-2.2.9-2.12.src.rpm Wrote: /usr/src/packages/RPMS/i586/perl-Mail-IMAPClient-2.2.9-2.12.i586.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.89853 + umask 022 + cd /usr/src/packages/BUILD + cd Mail-IMAPClient-2.2.9 + /bin/rm -rf '%{BuildRoot}' + exit 0 ... checking for files with abuild user/group ... running 00-check-install-rpms ... installing all built rpms Preparing packages for installation... perl-Mail-IMAPClient-2.2.9-2.12 ... 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 //.build.log) ... running 03-check-binary-kernel-log ... running 04-check-filelist ... checking filelist perl-Mail-IMAPClient-2.2.9-2.12.i586.rpm: directories not owned by a package: - /usr/lib/perl5/vendor_perl/5.10.0/Mail - /usr/lib/perl5/vendor_perl/5.10.0/Mail/IMAPClient - /usr/lib/perl5/vendor_perl/5.10.0/Mail/IMAPClient/BodyStructure - /usr/lib/perl5/vendor_perl/5.10.0/i586-linux-thread-multi/auto/Mail - +/usr/lib/perl5/vendor_perl/5.10.0/i586-linux-thread-multi/auto/Mail/IMAPClient System halted. This is for the package perl-Mail-IMAPClient, that I linked from the devel:languages:perl What should be added to the spec file to make this build again? Or is it a build server (BS) problem? Would it be sufficient to add e.g. %dir /usr/lib/perl5/vendor_perl/5.10.0/Mail/IMAPClient %dir /usr/lib/perl5/vendor_perl/5.10.0/i586-linux-thread-multi/auto/Mail or would this not work (of course the perl directories are to be replaced, with perlish directory values). -- 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

2 1

[opensuse-buildservice] MDV 2009.0 and su problem
by Petit Eric 27 Oct '08

27 Oct '08

Hi i just see you've added a MDV2009 repo, nice, but just after the spec inspection the system halt , because "su : incorect password" :-) -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. --------------------------------------------------------------------------- Few people are done for independence, it is the privilege of the powerful ones. --------------------------------------------------------------------------- No key was wounded during the drafting of this message. -- 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] MonoOSC
by Petit Eric 26 Oct '08

26 Oct '08

Hi all, I would like to anouce a new release of MonoOSC with lot of bug fixed and some new feature. I also review some design part, you can see overview with this screenshot : http://picpaste.com/pics/MonoOSCAllIn1.1225048699.jpg I'm searching someone who wanted to help me in buildind package for .deb plateform. MonoOSC is aviable in RPM : http://download.opensuse.org/repositories/home:/surfzoid/ Or from source/project : https://sourceforge.net/users/surfzoid/ The MonoOBSFramework is a part of MonoOSC , but it can be easly used separatly if you want to write your GUI or plugin or anythingh else, this project is a wrapper of OBS API, in this case you should need developer documentation, aviable here : HTML : http://surfzoid.free.fr/freevbsoft/MonoOSC/Docs/html/ CHM : http://surfzoid.free.fr/freevbsoft/MonoOSC/Docs/chm/Documentation.chm I which you a good experiance with MonoOSC -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. --------------------------------------------------------------------------- Few people are done for independence, it is the privilege of the powerful ones. --------------------------------------------------------------------------- No key was wounded during the drafting of this message. -- 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] Packages.gz file exclusive to amd64?
by Jasem Mutlaq 25 Oct '08

25 Oct '08

Hello, I'm building packages for multiple distributions, including xUbuntu 8.04. To test the xUbuntu repo, I wanted to add it to my sources.list, but when I checked the Packages (and Packages.gz) file, it turns out that only amd64 packages are listed in the file. This is an example: http://download.opensuse.org/repositories/home:/mutlaqja/xUbuntu_8.04/Packag es Why aren't the i386 files listed as well in the Packages file? Cheers, Jasem -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1