June 2010 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Place for RPM Macros
by Sascha 'saigkill' Manns 27 Jun '10

27 Jun '10

Hello Mates, sadly i've forgotten the right place where i can see what Macros (like %__make %{?jobs:-j %jobs}) are doing. Anyone knows the right place? -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English)

3 3

[opensuse-packaging] perl pkg and "auto directory is included in the perl package"
by Christian 25 Jun '10

25 Jun '10

Hi, hi recognized that perl-Config-Simple is failing for < 1130 cause of |auto directory is included in the perl package| should the "auto" dir be removed on < 1130 ? this "auto" dir is created by MakeMaker + autosplit. what is the purpose of having the module functions splitted to several files ? Thanks Chris -- Christian --------------------------------------------------- Der ultimative shop für Sportbekleidung und Zubehör http://www.sc24.de --------------------------------------------------- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] Need to submit blender to factory for bnc#615679
by Dave Plater 24 Jun '10

24 Jun '10

Hi, is there a special procedure for submitting a fixed blender to factory :- http://bugzilla.novell.com/show_bug.cgi?id=615679 I just need the reporter to test and will be ready to submit tomorrow. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 2

[opensuse-packaging] A question about python naming.
by Dave Plater 24 Jun '10

24 Jun '10

Hi, after reading replies to my "need help with rpmlint" email to this list, I found the packaging/python wiki and used python macros in the spec file. I'm still confused about the rpmlint warning :- ffado.x86_64: W: python-naming-policy-not-applied /usr/lib64/python2.6/site-packages/ffado/mixer/quatafire.ui This package doesn't respect the naming policy for python packages. Its name should match the regular expression ^python(-|$). Prior locating and using the scons option for python file location "PYPKGDIR=%{python_sitearch}" when the x86_64 build python files were under %python_sitelib and still with the i586 build, the rpmlint warning read :- ffado.x86_64: W: python-naming-policy-not-applied /usr/lib/python2.6/site-packages/ffado/mixer/globalmixer.py This package doesn't respect the naming policy for python packages. Its name should match the regular expression ^python(-|$). quatafire.ui isn't a python file, quatafire.py is and none of the other .py files have a python prefix though some of them are ffado prefixed. This needs an upstream fix but I can't seem to find what the openSUSE Naming policy is based on, if this isn't a major distro policy my chances of having it fixed are slim. Can somebody please explain, the package home:plater ffado - multimedia:libs ffado enables musical instrument firewire support for jack and will be pushed to factory after 11.3 release. Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

8 14

[opensuse-packaging] Question about qmake an pathes
by Sascha 'saigkill' Manns 24 Jun '10

24 Jun '10

Hello Mates, atm i'm working on freediams, an medical Software. I'm using in the Spec: %build qmake -r -config release %{name}.pro "CONFIG+=LINUX_INTEGRATED" "INSTALL_ROOT_PATH=%{_prefix}" "LIBRARY_BASENAME=%{_lib}" %__make %{?jobs:-j %jobs} lrelease freediams.pro %install %makeinstall INSTALL_ROOT="%{buildroot}" The Package Building runs good. But if i try to run freediams i'm getting: sascha@linux-hob0:~/osc/home:saigkill:medical/freediams> freediams "Main" "Command line : freediams" "Main" "looking for plugins in path : /usr/bin/plugins" "Database" "Available drivers : QSQLITE ; QMYSQL3 ; QMYSQL" "Main" "Running release version" "Couldn't find 'Core.pluginspec' in /usr/bin/plugins" So i tried to make an ln -s from /usr/lib64/freediams/Core.pluginspec to /usr/bin/plugins, That runs. But now i'm getting: sascha@linux-hob0:/usr/lib64/freediams> freediams "Main" "Command line : freediams" "Main" "looking for plugins in path : /usr/bin/plugins" "Database" "Available drivers : QSQLITE ; QMYSQL3 ; QMYSQL" "Main" "Running release version" "The shared library was not found. Library base name: /usr/bin/plugins/libCore.so" main "The shared library was not found. Library base name: /usr/bin/plugins/libCore.so" Now i think to make an new ln -s from /usr/lib64/freediams/libCore.so to /usr/bin/plugins is not an good idea. The config_paths.pri says: # define some paths related to application sources BUILD_BINARY_PATH = $${SOURCES_ROOT_PATH}/bin BUILD_LIB_PATH = $${SOURCES_ROOT_PATH}/bin/plugins BUILD_PLUGIN_PATH = $${BUILD_LIB_PATH} Is that the right place who i can modify the Target? So i thought, that i can change the BUILD_LIB_PATH to $$(SOURCES_ROOT_PATH/usr/lib. But how can i modify this, that he checks if lib64 is available, and if not that he just use /usr/lib? Is my work right? Or not? Have a nice day.. -- Sincerely Yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Maifeldstrasse 10 D-56 727 Mayen Phone: +49 2651 4014045 Email: Sascha.Manns(a)directbox.com Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English) -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English)

2 1

[opensuse-packaging] cmake injecting rules for installation DebugFull / RelWithDebInfo
by Dominique Leuenberger 23 Jun '10

23 Jun '10

Hi Listmates! I'm fighting with cmake for a few hours already and it seems it doesbehave differently on different platforms. I'm building the project home:dimstar:libproxy (in the role of upstream developer) and I'm targeting most of the RPM based distributions for now. For most of the things this works just fine, some of course have dependency issues due to package naming differences, nothing to worry about. Also the windows_mingw repository is nothing to worry about, this is 'future development - WIP'. What strikes me though is that on SLE_11, the libproxy-plugins fails to build. After tracking down and debugging a bit with local 'osc build', I found that the plugins have a rule added in cmale_install.cmake, that skips installing them if BUILD_TYPE != DebugFull... OF course I could just go ahead and specify this buildtype, but the Fedora builds fail, because those check on RelWithDebInfo. How can I stop cmake from adding those weird install rules to the makefiles? Especially as they are not defined in the upstream CMakeList.txt at all. In the hopes somebody knows cmake very well, Dominique -- 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] Maintenance for our build service 2010-06-23
by Marcus Rueckert 22 Jun '10

22 Jun '10

Hi openSUSE Users There is some maintenance to be done in the following areas of our openSUSE infrastructure: * build.opensuse.org (Buildservice) * api.opensuse.org * users.opensuse.org * software.opensuse.org As result, there will be a brief outage of all services provided by this machine. Wednesday, 2010-06-23, 12:00 German time (CET) (10:00 UTC) The downtime is expected to be 120 minutes. Apologies for inconveniencies this may cause. Please contact admin(a)opensuse.org with any queries. Your openSUSE Admins http://en.opensuse.org/Downtime/2010-06-23 -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- 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] beagle, tracker & obsoletion fun for 11.3
by Vincent Untz 22 Jun '10

22 Jun '10

Hi friends, For openSUSE 11.3, the GNOME team switched to tracker by default instead of beagle for the indexer. Beagle is still available for those who want it (we'll drop it in the next cycle). However, one thing I just realized is that for people upgrading from previous versions of openSUSE, they will likely get both beagle and tracker installed. And possibly indexing stuff. Which sounds wrong. So I'm wondering: should tracker obsolete beagle (as in Obsoletes tag)? Even though beagle is still available? Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 6

[opensuse-packaging] fixing a error in %prep section
by doiggl＠velocitynet.com.au 16 Jun '10

16 Jun '10

Hello How can I fix this error. Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.4Pw2s6 + umask 022 + cd /usr/src/packages/BUILD + cd /usr/src/packages/BUILD + rm -rf cacti-PA-0.8.7g-beta2 + /usr/bin/gzip -dc /usr/src/packages/SOURCES/cacti-plugin-0.8.7g-beta2-PA-v2.8.tar.gz + /bin/tar -xvvf - drwxr-xr-x roman/users 0 2010-06-14 02:28 cacti-plugin-arch/ drwxr-xr-x roman/users 0 2010-06-14 02:18 cacti-plugin-arch/files-0.8.7g/ -rw-r--r-- roman/users 17909 2010-06-05 14:45 cacti-plugin-arch/files-0.8.7g/poller.php . . -rw-r--r-- roman/users 124840 2010-06-14 02:50 cacti-plugin-arch/cacti-plugin-0.8.7g-PA-v2.8.diff + STATUS=0 + '[' 0 -ne 0 ']' + cd cacti-PA-0.8.7g-beta2 /var/tmp/rpm-tmp.4Pw2s6: line 29: cd: cacti-PA-0.8.7g-beta2: No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.4Pw2s6 (%prep) Question: What lines do I need to change in the %prep section in the .spec file to resolve the error ? What should the revised lines look like ? Thanks Glenn Full Spec file -> https://build.opensuse.org/package/view_file?file=cacti-PA.spec&package=cac… Last log -> https://build.opensuse.org/package/live_build_log?arch=x86_64&package=cacti… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] Need help with rpmlint warnings.
by Dave Plater 16 Jun '10

16 Jun '10

Hi, in home:plater ffado (on it's way to mmlibs ffado) I've a couple of python rpmlint errors that I don't quite understand, the first looks like an upstream bug :- ffado.x86_64: W: python-naming-policy-not-applied /usr/lib/python2.6/site-packages/ffado/mixer/globalmixer.py This package doesn't respect the naming policy for python packages. Its name should match the regular expression ^python(-|$). ffado.x86_64: W: no-dependency-on python-base 2.6 This last one I can't understand because the ffado package that contains the python files has an automatic dependency on python-base listed. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 10