August 2009 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] --ignorearch
by Peter Czanik 25 Aug '09

25 Aug '09

Hello, Yesterday I tried to install a few packages on ARM and it failed with: "package mingetty-1.0.7s-94.5.arm7l is intended for a armv7l architecture" Of course the machine is armv7l arthitecture and the package works fine when installed with rpm's --ignorearch option. Where rpm looks for architecture information? dl9pf wrote last evening, that: (17.59.58) |dl9pf|: what's the output of uname -a and cat /proc/cpuinfo on the board ? (18.00.19) |dl9pf|: rpm checks some of these and complains - buildservice uses rpm --ignorearch I'd try to fix it for my board in the kernel sources, if I knew what to change. Here is the current output: (21.23.15) CzP: czanik@bigone111:~> cat uname.txt (21.23.15) CzP: Linux bigone111 2.6.26-394-gf56b72e #1 PREEMPT Wed Jun 24 17:19:45 CEST 2009 armv7l armv7l armv7l GNU/Linux (21.23.48) CzP: czanik@bigone111:~> cat cpuinfo.txt (21.23.48) CzP: Processor : ARMv7 Processor rev 1 (v7l) (21.23.48) CzP: BogoMIPS : 799.53 (21.23.48) CzP: Features : swp half thumb fastmult vfp edsp (21.23.48) CzP: CPU implementer : 0x41 (21.23.48) CzP: CPU architecture: 7 (21.23.48) CzP: CPU variant : 0x2 (21.23.48) CzP: CPU part : 0xc08 (21.23.48) CzP: CPU revision : 1 (21.24.06) CzP: Cache type : write-back (21.24.06) CzP: Cache clean : read-block (21.24.06) CzP: Cache lockdown : not supported (21.24.06) CzP: Cache format : Unified (21.24.06) CzP: Cache size : 768 (21.24.06) CzP: Cache assoc : 1 (21.24.06) CzP: Cache line length : 8 (21.24.06) CzP: Cache sets : 64 (21.24.06) CzP: Hardware : Freescale MX51 Babbage Board (21.24.06) CzP: Revision : 51020 (21.24.06) CzP: Serial : 0000000000000000 Bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] Weekly News: Announcing Meetings via news.o.o
by Sascha 'saigkill' Manns 24 Aug '09

24 Aug '09

Hello Mates, i would just remind you, to announce meetings in news.o.o too. The thing behind them is, that we use an script for fetching news.o.o events automaticly. It would be great if we all have the events on an central place. Thank you very much :-) -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- 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] different control files for different debian platforms?
by Paul Elliott 24 Aug '09

24 Aug '09

Is it possible to have different control files for different debian platforms? I have a package that has a Build-requires dependancy of libboost-dev for most debian platforms, however, xUbuntu 9.04 wants this to be libboost1.35-dev. Is it possible to have a control-xUbuntu_9.04 file the same way you can have a foo-Fedora_Extras_6.spec for rpm based distributions? What is the best way to handle this? I don't think you can ifdef a debian control file the way you can a rpm spec file. Thank You. -- Paul Elliott 1(512)837-1096 pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117

4 11

[opensuse-buildservice] mandriva_version broken on 2009.1
by Stephan Kleine 24 Aug '09

24 Aug '09

Hi folks. I just noticed that one is neither able to specifically target Mandriva 2009.1 with %if tags in .specs nor do packages containing %{?mandriva_version} build for 2009.1 because the %if comparison always results in a parse error cause of the ".". The way I see it that can be fixed in two ways: 1. The %if %else %endif comparison gets fixed 2. The mandriva_version numbering scheme is changed for all supported Mandriva versions so it is similar to the openSUSE one - 2008 -> 200800, 2009 -> 200900, 2009.1 -> 200910, ... IMHO the second way is probably easier cause only the prjconf has to be changed. Disadvantage is that it probably would break some of the current builds but since there aren't that many Mandriva packages anyways on OBS and it's easy to fix that shouldn't be much of a problem. Last but not least the suggested numbering would be future proof so it were an unique issue. I also filed a bug regarding this: https://bugzilla.novell.com/show_bug.cgi?id=533587 Soo, what do you think, can we get that please fixed asap? Cheers, Stephan -- 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] No ARM builds running on Build Service
by David Greaves 24 Aug '09

24 Aug '09

It appears that the arm scheduler(?) is down. There are no arm builds, the queue is at 0/0 and the architecture isn't appearing in the monitor for new projects. Triggering a rebuild on an existing project is a no-op :( David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." -- 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] Setting Optflags in remote builds?
by Scott Cantor 24 Aug '09

24 Aug '09

Related to my question about getting -fPIC to work on Red Hat 5, I'm not having any success using osc meta prjconf to create a custom set of Optflag settings to use for non-local builds. I guess I interpreted the documentation as implying that that was the whole point of creating a custom build config. http://en.opensuse.org/Build_Service/prjconf Is there some kind of delay involved? An additional step to enable them? No way to do it at all? What I specifically did was check out my project, then run osc meta prjconf <project> -e and put just a set of Optflag lines into the file copied from the settings in the osc default config I found. If the build service was using these settings to begin with, I'd be ok, but it's using stale values. Anyway, then I triggered a rebuild of an affected package, but it's still using the same Optflags as before. -- Scott -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] buildservice breaks a package
by Mathias Homann 24 Aug '09

24 Aug '09

Hi, i have this package which builds just fine locally, even when i check it with rpmlint, but on buildservice it breaks with this: WARNING: '/usr/lib/rpm/brp-desktop.data/suse-screensavers.menu' does not exist WARNING: '/usr/lib/rpm/brp-desktop.data/preferences-gnome.menu' does not exist WARNING: '/usr/lib/rpm/brp-desktop.data/applications-kmenuedit.menu' does not exist + /usr/lib/rpm/brp-rpath ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/doc" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/3rdParty-2.0.0/lib/i686-linux" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/GUI" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/LLChatLib" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/doc" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/3rdParty-2.0.0/lib/i686-linux" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/GUI" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/LLChatLib" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed where did that come from? bye, MH -- Die unaufgeforderte Zusendung einer Werbemail an Privatleute verstößt gegen §1 UWG und §823 I BGB (Beschluß des LG Berlin vom 2.8.1998 Az: 16 O 201/98). Jede kommerzielle Nutzung der übermittelten persönlichen Daten sowie deren Weitergabe an Dritte ist ausdrücklich untersagt! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

[opensuse-buildservice] MonoOSC Help written :-)
by Petit Eric 23 Aug '09

23 Aug '09

Hi The MonoOSC starter guide is written, fill free to complete it : http://en.opensuse.org/MonoOSC/Guide The help is available from MonoOSC Main form (F1 key) and in setting form :-) -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- 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] build21 dead :(
by Christian 22 Aug '09

22 Aug '09

Hi, build21 is dead for 1 day now. Is there anybody who is taking care about it ? Kind Regards Chris -- 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] How does one share source file between packages?
by Paul Elliott 21 Aug '09

21 Aug '09

How does one share source files between packages? I am sorry if this is a dumb question, but I have read references to linking but nothing that would tell me how to do it. Thank You. -- Paul Elliott 1(512)837-1096 pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117

2 1