March 2012 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Dependencies in update project
by Josef Reidinger 24 Mar '12

24 Mar '12

Hi, I am not sure if this is related to packaging, maybe more to new setup of build service and maintenance procedure. Problem: now for 12.1 there is update for kernel to version 3.1.9. But kernel modules is not recompiled against this version, which is critical ( e.g. virtual box host segfault ). Is it possible to have such setup automatic? I can create bug report for such issue if you find it appropriate. Josef -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] How to disable debug for a local osc build of a new package not existing on OBS server?
by Marguerite Su 22 Mar '12

22 Mar '12

Hi, all I'm building a package locally, by using the powerful "osc", I can get lots of useful rpmlint information. But due to "Plenty of reasons", the package can't exist on OBS at all. I'm planning to build it and upload it to my personal dropbox for further use. I created the package by osc mkpac, so actually the package isn't on OBS server until I run "osc ci". And the package can't generate useful debug info because it's a commercial and ugly package, so I decided to turn it off. Then here's the problem: the local package seems to inherit my repository settings automatically, which has debug info on. while because the package isn't on server right now, I can't use command like "osc meta pkg -e" to disable debug info, which actually create the package on server. even if it's an authorized package, doing this will return you a "packge existed" error when you run "osc ci" later. OBS controls the generation of debug info, but it also does so to a theoretically non-exist package. I have checked .osc directory, which has no such settings. So how can I turn debuginfo off for such a package? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 4

[opensuse-packaging] My home project has been deleted
by Ilya Chernykh 21 Mar '12

21 Mar '12

Hi! After accepting this request my home project has been deleted: https://build.opensuse.org/request/show/110003 I lost all my packages. How can I restore them? I accepted the request because it said it requests deletion of a blacklisted package, but my home project is not a blacklisted package! -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging] Need gcc / makefile / autotools help with a new python/C package
by Greg Freemyer 20 Mar '12

20 Mar '12

All, As I've blasted across the universe, I'm trying to package a set of computer forensic apps. I'm tracking my progress here. http://en.opensuse.org/Portal:Digital_Forensics_/_Incident_Response The next one on my list is pyflag. I have a package in OBS: home:gregfreemyer:Tools-for-forensic-boot-cd > pyflag But the build is failing in the INSTALL section with: == gcc -shared -I/usr/include/python2.7 -I../../src/include -L -lpython2.7 -o pypacket.so pypacket.c .libs/pypacket.a -lpthread -ldl -lutil In file included from /usr/include/python2.7/Python.h:8:0, from ../../src/include/pypacket.h:4, from pypacket.c:8: /usr/include/python2.7/pyconfig.h:1161:0: warning: "_POSIX_C_SOURCE" redefined [enabled by default] /usr/include/features.h:215:0: note: this is the location of the previous definition pypacket.c:323:5: warning: initialization from incompatible pointer type [enabled by default] pypacket.c:323:5: warning: (near initialization for 'PyPacketType.tp_getattr') [enabled by default] /usr/lib64/gcc/x86_64-suse-linux/4.6/../../../../x86_64-suse-linux/bin/ld: /tmp/ccHOtZu6.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC /tmp/ccHOtZu6.o: could not read symbols: Bad value collect2: ld returned 1 exit status == I have unpacked the tarball and manually done "./configure; make; make install" and I get the same error. If I cd into "pyflag-0.87-pre1/src/lib" and then do a make pypacket.so (which seems to be the goal of the above gcc command), I get the exact same error. So I'm in the right place, but I don't know how to debug this any further. I've attached the Makefile from pyflag-0.87-pre1/src/lib folder. Can anyone help me with that? Thanks Greg

3 9

[opensuse-packaging] Clean up abuse usage of obs
by Bruno Friedmann 19 Mar '12

19 Mar '12

To maintain our infrastructure in good shape, and enforce our policies I would like to find a way to at least find a way to ask packager to respect those policies The first and big concern is getting blob proprietary software published First target (as the most simple to track) nvidia drivers It's easy to find who as linkpac/branch the nvidia package and forget or modify the build/publish status osc bse x11-video-nvidia Now what could be the next step is to build a really simple script that can extract emails from incriminated project/package osc maintainer -e do that well. Coolo should already have a nice part of his reminder script to send the mail. Is it shareable ? List of projects to warn home:opensuse_zh home:hillwood home:Lord_LT:drivers home:Bumblebee-Project not that much, and put in cc here Any thought about it ? Oh before someone ask me to simply ask a sr delete The package could reside on obs (doesn't contain any proprio blob), but build & publish has to stay off like it is in the base package Then it could be build locally Thanks to get our obs clean! -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging] How do I get a link into factory after splitting a package into two packages?
by Dave Plater 18 Mar '12

18 Mar '12

I'm (attempting to) splitting lilypond into a program with info package and a linked lilypond-doc package due to the fact that the doc package has an extremely long build time and very often has build failures. How do I go about submitting the link package to factory? Dave -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 5

[opensuse-packaging]
by Nelson Marques 17 Mar '12

17 Mar '12

A few users from KDE are having issues with cinnamon (mainly lack of packages). Is there a way to pass as requires the GNOME pattern? -- Nelson Marques // I've stopped trying to understand sandwiches with a third piece of bread in the middle... -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

7 14

[opensuse-packaging] skrooge build: kde version specific directories
by Sascha Manns 16 Mar '12

16 Mar '12

Hello mates, i'm trying to update skrooge atm. But i have a curious problem and don't know how to package this. Skrooge builds a module for grantlee. The output is: %{_libdir}/grantlee/0.1/grantlee_skroogefilters.so (For 11.4, 12.1) %{_libdir}/grantlee/0.2/grantlee_skroogefilters.so (For 12.1 Uns., Fac) I'm guessing that i have to define which one matches with a special KDE Version. Anything like: %if 0%{?_kde4_version} => 4.8.0 %{_libdir}/grantlee/0.2/grantlee_skroogefilters.so %else %{_libdir}/grantlee/0.1/grantlee_skroogefilters.so %endif But do we have that macro? Or how can i do this job? cu Sascha -- Sincerly yours Sascha Manns - open-slx GmbH Community Agent / Documentation Specialist Web (business): http://www.open-slx.com Web (private): http://saigkill.homelinux.net -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 3

[opensuse-packaging] How to fix python-bytecode-inconsistent-mtime rpmlint warning?
by Marguerite Su 15 Mar '12

15 Mar '12

Hi, all, I'm packaging a twitter client, whose GTK version uses Python. And I got python-bytecode-inconsistent-mtime rpmlint warning. Actually I got that msg a few times before when I was packaging other python applications. At first I try to fix it by running "python -m compileall *.pyc", but recently OBS import a new rule which will check if you have buildroot in your *.pyc file. I then "fix" a warning to an 10000 error. That's too bad. I googled the web to find a answer, only one item related: https://bugzilla.redhat.com/show_bug.cgi?id=591730 In that bug report, the packager said he fixed it, but leaved no method for me. So now it seems I'm the only one who frequently get this warning. I'm thinking two methods to fix it: 1. find . -name "*.pyc" | sed to replace buildroot in pyc to null. 2. delete all *.pyc Any better idea for me ? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 5

[opensuse-packaging] Has anyone managed to build CodeAnalyst version 3_2_14
by doiggl＠velocitynet.com.au 15 Mar '12

15 Mar '12

Hello, Has anyone managed to build CodeAnalyst version 3_2_14 [1] If so have you a link to the built rpm package ? source code dated 01/19/2012 Thanks Glenn [1] http://developer.amd.com/tools/CodeAnalyst/codeanalystlinux/Pages/default.a… http://developer.amd.com/Downloads/CodeAnalyst-3_2_14_0311-Public.tar.gz -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0