March 2010 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] How to Build and Package Python 3 Packages?
by Thomas Schraitle 16 Mar '10

16 Mar '10

Hi, in my repository I package a lot of Python packages almost exclusively for version 2.x. I use the template described in [1] which works pretty well in most cases. So far, so good. However, I haven't found anything that covers how to build Python 3 packages. As most projects probably will consider either switching to the new version or supporting both versions, I think this will become more and more important. Maybe I missed something, but at the moment it seems to me, the details are not fully described. Maybe some friendly developer can give me some recommendations: 1. Are there any RPM macros definied for Python3? In /usr/lib/rpm/macros there are the usual suspects like py_prefix, py_libdir, etc. However, these macros are definied for Python2.x only. I haven't found macros for Python3 yet. Do I have to define it myself or where can I find them? What is recommended in this case? 2. What is the official naming schema for Python 3 packages? I saw that some packages in the OBS starts with the prefix "python3-" which I think is a good idea. Is this a convention or an official policy? Is it expected that Python2 packages will be renamed to "python2-" and Python3 packages become "python-"? Similar to the KDE3/KDE4 package renaming? (My impression is this will not happen soon.) 3. How to build packages in OBS which are written for Python 2.x and 3.x? I maintain the package python-lxml[2]. The source can be build for both versions which is good. :) I tried some variations but in the end I wrote two spec files: python- lxml.spec and python3-lxml.spec and committed it. However, OBS seems to build only the packages for python-lxml and doesn't look at the python3-lxml.spec. Do I have to create another project? If possible, I would like to keep everything in one project. Any recommendations here? 4. Anything else which is important for building Python 3.x packages? Thanks, Tom -------- [1] http://en.opensuse.org/Packaging/Python [2] https://build.opensuse.org/package/show?package=python- lxml&project=home%3Athomas-schraitle -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX GmbH >o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team http://developer.novell.com/wiki/index.php/Lessons_for_Lizards http://lizards.opensuse.org/author/thomas-schraitle/ --------------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 4

[opensuse-packaging] remove obsolete packages from obs/software download
by Denny Beyer 12 Mar '10

12 Mar '10

Dear all, this question has been asked several times, also in opensuse forums and left unanswered, also the wiki doesn't give any help. So I'm asking here: How do I remove obsolete packages left in obs and with it for download? For an example see home:lumnis/yabs, where the i586 packages should be removed not to waste any space and to confuse users, as updated packages are created on the x86_64 arch thanks for shedding some light on this. Denny -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 4

[opensuse-packaging] has anyone ever asked google for permissions to redistribute google earth in the non-oss repo?
by Richard Bos 12 Mar '10

12 Mar '10

The subject line has it all: has anyone ever asked google for permissions to redistribute google earth in the non-oss repo? The question was asked in a comment on my blog about building a Google Earth rpm: http://lizards.opensuse.org/2010/03/09/build-your-own-google-earth-rpm Is there someone within openSuSE / Novell with contact with Google, who could asked that question to Google? Google used to have their own repository before, see the http://en.opensuse.org/Google_Earth/rpm#External_links, items 'suse102 repository' and 'YAST repository setup for Google Earth' Don't understand why Google does not use their own OBS to deliver software for Linux ;) -- Richard -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 4

[opensuse-packaging] Splitting off a -doc subpackage when using %find_lang
by Guido Berhoerster 11 Mar '10

11 Mar '10

Hello, I'm using the %find_lang macro to create a -lang subpackage but I want to split off a separate -doc subpackage with a number of files which are currently automatically put into the -lang subpackage. What is the cleanest way to do that, should I just edit the list of files created by %find_lang after calling it? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Re: Problem with linking - undefined glTexParameterf
by Michal Vyskocil 11 Mar '10

11 Mar '10

Hi, JFI resent from opensuse-java, but problem is in gcc/ld, not in java On Monday 08 March 2010 11:00:05 am Kirill Kirillov wrote: > Hi, all! > > We [1] are trying to move [2] Java-based Scilab [3] to Factory OSS > repository. > > We have problem with linking jogl JNI to Scilab [4], if we remove the > following line in scilab.spec: > "BuildRequires: -post-build-checks" > then build fails on configure stage with the following error: > > checking jogl... /usr/lib64/java//jogl.jar > checking for glTexParameterf in -ljogl... no > configure: WARNING: Could not link against -ljogl. Will try against -ljogl > -lGL checking for glTexParameterf in -ljogl ... no > configure: error: "libjogl: Library missing (Cannot find symbol > glTexParameterf). Check if libjogl - C/Java (JNI) interface for JOGL - or > libGL are installed and if the version is correct. Note that you might > have to update etc/librarypath.xml to provide the actual path the the JNI > libraries." error: Bad exit status from /var/tmp/rpm-tmp.CYklG7 (%build) The configure script fails on a linking during gcc -o conftest conftest.c - L/usr/lib64/jni -ljogl. But the manual run in chroot works well and I got this error only when using build script. I did not find any problem during ld - there's the output with CFLAGS=-Wl,--trace,--trace-symbol=glTexParameterf This is the output from config.log from a first run with -ljogl only configure:11894: checking for glTexParameterf in -ljogl configure:11919: gcc -o conftest -fmessage-length=0 -O2 -Wall - D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind- tables -fno-strict-aliasing -Wl,--trace,--trace-symbol=glTexParameterf - DNDEBUG -fno-stack-protector -DNARROWPROTO -m64 - I$(top_srcdir)/modules/core/includes/ -I$(top_srcdir)/libs/MALLOC/includes/ - I$(top_srcdir)/modules/localization/includes/ -L/usr/lib/jni - L/usr/lib64/jni/ -L./thirdparty/ -L./bin/ conftest.c -ljogl >&5 /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../x86_64-suse-linux/bin/ld: mode elf_x86_64 /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/crt1.o /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/crti.o /usr/lib64/gcc/x86_64-suse-linux/4.4/crtbegin.o /tmp/ccKtTcdn.o -ljogl (/usr/lib64/jni//libjogl.so) -lgcc_s (/usr/lib64/gcc/x86_64-suse-linux/4.4/libgcc_s.so) /lib64/libc.so.6 (/usr/lib64/libc_nonshared.a)elf-init.oS /lib64/ld-linux-x86-64.so.2 -lgcc_s (/usr/lib64/gcc/x86_64-suse-linux/4.4/libgcc_s.so) /usr/lib64/gcc/x86_64-suse-linux/4.4/crtend.o /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/crtn.o /tmp/ccKtTcdn.o: reference to glTexParameterf /usr/lib64/jni//libjogl.so: reference to glTexParameterf /tmp/ccKtTcdn.o: In function `main': conftest.c:(.text+0x7): undefined reference to `glTexParameterf' /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../x86_64-suse-linux/bin/ld: link errors found, deleting executable `conftest' collect2: ld returned 1 exit status configure:11919: $? = 1 The second run with -lGL gcc -o conftest -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack- protector -funwind-tables -fasynchronous-unwind-tables -fno-strict-aliasing - Wl,--trace,--trace-symbol=glTexParameterf -DNDEBUG -fno-stack-protector - DNARROWPROTO -m64 -I$(top_srcdir)/modules/core/includes/ - I$(top_srcdir)/libs/MALLOC/includes/ - I$(top_srcdir)/modules/localization/includes/ -L/usr/lib/jni - L/usr/lib64/jni/ -L./thirdparty/ -L./bin/ -lGL conftest.c -ljogl >&5 /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../x86_64-suse-linux/bin/ld: mode elf_x86_64 /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/crt1.o /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/crti.o /usr/lib64/gcc/x86_64-suse-linux/4.4/crtbegin.o -lGL (/usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/libGL.so) /tmp/cckG39mv.o -ljogl (/usr/lib64/jni//libjogl.so) -lgcc_s (/usr/lib64/gcc/x86_64-suse-linux/4.4/libgcc_s.so) /lib64/libc.so.6 (/usr/lib64/libc_nonshared.a)elf-init.oS /lib64/ld-linux-x86-64.so.2 -lgcc_s (/usr/lib64/gcc/x86_64-suse-linux/4.4/libgcc_s.so) /usr/lib64/gcc/x86_64-suse-linux/4.4/crtend.o /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/crtn.o /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/libGL.so: definition of glTexParameterf /tmp/cckG39mv.o: reference to glTexParameterf /usr/lib64/jni//libjogl.so: reference to glTexParameterf /tmp/cckG39mv.o: In function `main': conftest.c:(.text+0x7): undefined reference to `glTexParameterf' /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../x86_64-suse-linux/bin/ld: link errors found, deleting executable `conftest' collect2: ld returned 1 exit status On the other side the build of conftest.c in chroot works well - be aware that I use the shortest form, but there's no difference when I use the same set of arguments as configure does, it is built well. gcc -L/usr/lib64/jni -o conftest conftest.c -ljogl -Wl,--trace,--trace- symbol=glTexParameterf /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../x86_64-suse-linux/bin/ld: mode elf_x86_64 /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/crt1.o /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/crti.o /usr/lib64/gcc/x86_64-suse-linux/4.4/crtbegin.o /tmp/ccUZe3IC.o -ljogl (/usr/lib64/jni/libjogl.so) -lgcc_s (/usr/lib64/gcc/x86_64-suse-linux/4.4/libgcc_s.so) /lib64/libc.so.6 (/usr/lib64/libc_nonshared.a)elf-init.oS /lib64/ld-linux-x86-64.so.2 -lgcc_s (/usr/lib64/gcc/x86_64-suse-linux/4.4/libgcc_s.so) /usr/lib64/gcc/x86_64-suse-linux/4.4/crtend.o /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/crtn.o /tmp/ccUZe3IC.o: reference to glTexParameterf /usr/lib64/jni/libjogl.so: reference to glTexParameterf /usr/lib64/libGL.so.1: definition of glTexParameterf gcc -L/usr/lib64/jni -o conftest conftest.c -lGL -ljogl -Wl,--trace,--trace- symbol=glTexParameterf /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../x86_64-suse-linux/bin/ld: mode elf_x86_64 /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/crt1.o /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/crti.o /usr/lib64/gcc/x86_64-suse-linux/4.4/crtbegin.o /tmp/cc4FryQF.o -lGL (/usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/libGL.so) -ljogl (/usr/lib64/jni/libjogl.so) -lgcc_s (/usr/lib64/gcc/x86_64-suse-linux/4.4/libgcc_s.so) /lib64/libc.so.6 (/usr/lib64/libc_nonshared.a)elf-init.oS /lib64/ld-linux-x86-64.so.2 -lgcc_s (/usr/lib64/gcc/x86_64-suse-linux/4.4/libgcc_s.so) /usr/lib64/gcc/x86_64-suse-linux/4.4/crtend.o /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/crtn.o /tmp/cc4FryQF.o: reference to glTexParameterf /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/libGL.so: definition of glTexParameterf /usr/lib64/jni/libjogl.so: reference to glTexParameterf conftest.c is attached and you need libGL.so and ligjogl.so from Education project to build. Does anyone have an idea what's wrong? Regards Michal Vyskocil > > I've fixed jogl package [5] to place jar's and so's according to [6]: > /usr/lib/java and /usr/lib/jni for 32 bits and > /usr/lib64/java and /usr/lib64/jni for 64 bits. > But unfortunately it didn't help. > > Could you tell please how to fix it? Thanks. > > [1] http://lists.opensuse.org/opensuse-edu/2010-03/msg00000.html > [2] http://en.opensuse.org/Scilab/Moving > [3] http://www.scilab.org/ > [4] > https://build.opensuse.org/package/show?package=scilab&project=Education > [5] > https://build.opensuse.org/package/show?package=jogl&project=Education > [6] > http://en.opensuse.org/Packaging/Java#Packaging_JAR_files_that_use_JNI

3 3

[opensuse-packaging] netcdf package, glibc's debuginfo + valgrind issue
by Filipe Fernandes 08 Mar '10

08 Mar '10

Hello, I have a package (netcdf4.1) that compiles OK for 32 bits but returns the following error for 64 bits: valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. valgrind: valgrind: Cannot continue -- exiting now. Sorry. I could turn valgrind test off. However I would like to know if there is a way to add glibc's debuginfo as a Build requirement. Thank you, Filipe ps: package: https://build.opensuse.org/package/show?package=netcdf&project=home%3Aocefp… full log: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=netcd…

1 0

[opensuse-packaging] codelite build breaks for openSUSE <=11.1
by Mariusz Fik 08 Mar '10

08 Mar '10

Hi, I just tried to update codelite package in my home repository. But build fails for openSUSE <= 11.1 but for 11.2 and build is successful. http://tinyurl.com/ycpdr5a Any hint how to fix build for oS <= 11.1? -- Pozdrawiam / Best regards, Mariusz Fik, openSUSE Community Member

3 3

[opensuse-packaging] Maintenance reboot for our infrastructure 2010-03-09
by Lars Vogdt 08 Mar '10

08 Mar '10

Hi openSUSE Users There is some maintenance to be done in the following areas of our openSUSE infrastructure: * build.opensuse.org (Buildservice) * download.opensuse.org (Download infrastructure) * svn/git.opensuse.org As result, there will be a brief outage of all services provided by this machines Tuesday, 2010-03-09, 09:00 German time (CET) The downtime is expected to be 15-30 minutes for all hosts. Apologies for inconveniencies this may cause. Please contact admin(a)opensuse.org with any queries. Your openSUSE Admins -- http://en.opensuse.org/Downtime/2010-03-09 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] renaming for nagios-nrpe
by Christian 06 Mar '10

06 Mar '10

Hi, I am not very happy with naming of nrpe and its sub-pkg. we have nagios-nrpe-client, nagios-nrpe-server While seeing the client pkg I'll be misled to install this pkg on the remote box and vice versa. But the "client" pkg has to be installed on the nagios box. That's why I am thinking of: - nagios-nrpe it is the package to be installed on the remote box. - nagios-nrpe-plugin or nagios-plugins-nrpe just the name will let you associate to install this pkg on the nagios box. What do you think ? Any recommendations are welcome Kind Regards Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 3

[opensuse-packaging] FYI: kde-obs-generator
by Lubos Lunak 05 Mar '10

05 Mar '10

Hello, for those who could find this interesting, I've created a tool that automatically creates .spec and .dsc files from a source tarball that make the package build on several (also non-openSUSE) distributions supported by the OBS. It is currently still an experimental work in progress, but it works quite well already. It currently requires a specially set up repository (because of mappings between different distributions). It can now handle CMake-based projects (I've only tried with KDE and Qt) and few various KDE theme formats. See http://en.opensuse.org/KDE/Build_Service/Cross-distro , http://www.kdedevelopers.org/node/4177 and http://gitorious.org/kde-obs-generator for further details. -- Lubos Lunak openSUSE Boosters team, KDE developer l.lunak(a)suse.cz , l.lunak(a)kde.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0