February 2007 - openSUSE Build Service

[opensuse-buildservice] x86_64 status unknown
by Donnie S Bhayangkara 04 Feb '07

04 Feb '07

just currious, what happened? i can't build any x86_64 package since this morning (GMT +7) thanks. -- http://donnie.110mb.com PGP Fingerprint: D7BB F0E5 C0DD 534A 11A2 F310 0DDD 05F1 C3DC 26AB --------------------------------------------------------------------- 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] commit notifications
by Wolfgang Rosenauer 04 Feb '07

04 Feb '07

Hi, in case I missed that something like this is already available, sorry. What I really would appreciate would be a mail notification like the commit mails for buildservice packages to (at least) people who are set as maintainers in the specific project or package. The mail addresses are already there so it shouldn't be too hard to implement AFAIK. Wolfgang --------------------------------------------------------------------- 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] buildservice permission problem
by Sami Vento 04 Feb '07

04 Feb '07

Hi! I tried to commit changes to drivers:bluetooth -project, where I didn't have permission granted. Somehow I managed to remove old source package but not to upload new one nor change spec -file. Rebuild was also triggered automatically and builds failed because of missing source files. -- Sami Vento email: sami.vento(a)tr.spt.fi --------------------------------------------------------------------- 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] Please add support for debian virtual packages
by Amilcar do Carmo Lucas 02 Feb '07

02 Feb '07

Hi, I build KDevelop packages here: http://build.opensuse.org/package/show?package=KDevelop3&project=home%3Aami… All build fine except Debian Etch, it gives: expansion error: nothing provides xlibmesa-glu-dev needed by libopenexr-dev But xlibmesa-glu-dev is a virtual package: http://packages.debian.org/unstable/virtual/xlibmesa-glu-dev More info here: http://www.debian.org/doc/debian-policy/ch-binary.html#s-virtual_pkg Please add support for these packages in the dependency machinery of the build system. Thanks, -- Amilcar Lucas Webmaster The KDevelop project --------------------------------------------------------------------- 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] probs with yold in Build-Depends from dsc file (ubuntu, debian)
by Stephan Lauffer 02 Feb '07

02 Feb '07

Hi! Thank you for the buildservice! It's a great project! :) Well, I've a question about the ubuntu/debian builds. After I wrote a dsc file and started the build for ubuntu I got this error report in the build status overview: expansion error nothing provides yodl This is caused by "yodl" in the list of the Build-Depends of the dsc file and yes, we need it. If I removce it from the list the build starts but ends with a: dpkg-checkbuilddeps: Unmet build dependencies: yodl dpkg-buildpackage: Build dependencies/conflicts unsatisfied; aborting. Has anybody a hint for this problem here? btw: I speake about home:nixda/samba-tng, see: http://build.opensuse.org/package/show?package=samba-tng&project=home%3Anix… -- Liebe Gruesse, with best regards Stephan Lauffer [ University of Education Freiburg - Germany ] [ http://www.ph-freiburg.de/zik/ ] [ Fon/ Fax: +49 761 682 -459/ -486 ] --------------------------------------------------------------------- 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] Richclient 0.3.17 release
by Jonh Arson 02 Feb '07

02 Feb '07

Released version 0.3.17 of the Richclient yesterday after Cornelius blitzed around on it a bit, its now (almost) possible to create package and project with it, couple minor bug to fix before this can work correctly. This release got a bit different UI using 2 listviews side by side as Cornelius suggested for project and package listing. It will also now auto connect on app start-up using username stored in your preference. Note that file download should now work too (but they aren't saved anywhere and just dumped on kdebug, still allow you to view patch or spec on the terminal, yes i know how ugly this is). http://software.opensuse.org/download/openSUSE:/Tools/<suse_version>/ -- Jonh Arson <jonharson(a)gmail.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] python naming standard?
by Claes Bäckström 02 Feb '07

02 Feb '07

Hi everyone. I am in the start to try to build some stuff in the buildservice. I wonder if there is a naming standard to name the python libraries. What I'm thinking about packaging is pychm http://gnochm.sourceforge.net/pychm.html but I wonder if I should name the package pychm or python-chm. And is there any good simple python package to look at to get tips about cross distribution packaging or do you think it's better to get it working for suse first and then get it working for other distros? Warm Regards, Claes Backstrom --------------------------------------------------------------------- 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] Build error struct udphdr' missing 'uh_dport' for sipp on BS
by Richard Bos 01 Feb '07

01 Feb '07

Hi, hopefully someone on the list knows the root cause of the underneath problem. The root cause is probably a missing pkg, but I have no idea which one. The build fails when executing 'osc build ....sipp.spec', but the build is succesfull in my local environment. I assume some more pkgs are available there. cc -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -O2 -I. -I/opt/openssl/include -c -o send_packets.o send_packets.c send_packets.c: In function 'send_packets': send_packets.c:177: error: 'struct udphdr' has no member named 'uh_dport' send_packets.c:179: error: 'struct udphdr' has no member named 'uh_sport' send_packets.c:180: error: 'struct udphdr' has no member named 'uh_dport' send_packets.c:183: error: 'struct udphdr' has no member named 'uh_sport' send_packets.c:186: error: 'struct udphdr' has no member named 'uh_sport' send_packets.c:193: error: 'struct udphdr' has no member named 'uh_sum' make[1]: *** [send_packets.o] Error 1 make[1]: Leaving directory `/usr/src/packages/BUILD/sipp-1.1rc8.src' make: *** [pcapplay_ossl] Error 2 It looks to me that the structure is provided by: /usr/include/netinet/udp.h /* UDP header as specified by RFC 768, August 1980. */ struct udphdr { u_int16_t uh_sport; /* source port */ u_int16_t uh_dport; /* destination port */ u_int16_t uh_ulen; /* udp length */ u_int16_t uh_sum; /* udp checksum */ }; This file is part of the osc build, see (the grep for dport): Local osc build output: + cd sipp-1.1rc8.src + make clean rm -f *.o sipp *~ *.log sipp.tgz *.csv *.exe rm -rf cxx_repository + grep uh_dport /usr/include/netinet/udp.h u_int16_t uh_dport; /* destination port */ Is something processes/installed in the wrong order? What's needed to have sipp build succesfull on the BS? -- TIA, Richard Bos We are borroing the world of our chlidren, We don't inherit her from our parents. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 9

Re: [opensuse-buildservice] python naming standard?
by andreas.hanke＠gmx-topmail.de 01 Feb '07

01 Feb '07

Marcus Rueckert wrote: > python-<originalpackagename> > > python-pychm in your case Really? I thought the convention was python-<importablepackagename> which would become python-chm in this case because you write #!/usr/bin/python import chm and not #!/usr/bin/python import pychm Andreas Hanke -- "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail?ac=OM.GX.GX003K11713T4783a --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 4

[opensuse-buildservice] xUbunto repository is broken for applications requiring X11
by Amilcar do Carmo Lucas 01 Feb '07

01 Feb '07

Hi all I keep on getting this error message in the log when I use the xUbuntu repository: installing x11-common /usr/sbin/invoke-rc.d: line 276: /sbin/runlevel: No such file or directory /etc/init.d/x11-common: line 20: /etc/default/rcS: No such file or directory invoke-rc.d: initscript x11-common, action "start" failed. dpkg: error processing x11-common (--install): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: x11-common Any clues ? -- Amilcar Lucas Webmaster The KDevelop project --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3