openSUSE Packaging May 2010

packaging@lists.opensuse.org

53 participants
36 discussions

[opensuse-packaging] Right usage of libexecdir?
by Vincent Untz 25 May '11

25 May '11

Hey, Dominique and I are currently wondering what to do wrt libexecdir for evolution-data-server. Should we leave it unchanged (so files will be in /usr/lib) or should we change it to /usr/lib/evolution-data-server? If the latter, is there any reason this is not done automatically? Also, hrm, would rpmlint have ways to warn about packages that put binaries in libdir instead of libexecdir? (I can find a few of them here with a grep) 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

6 9

[opensuse-packaging] CPU vendor specific packages
by Cristian Rodríguez 31 May '10

31 May '10

Hi: IS there any way to hint the dependency resolver in libzypp to only install resolvable X when the user is running Intel CPU and remove the package from the system when that condition is not met ? Thanks. -- 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] Why won't packages build against openSUSE:Factory texlive-latex
by Dave Plater 27 May '10

27 May '10

Hi, if I set my home project to build against factory standard lilypond and dirac have no problem finding texlive-latex to build against but if it's set to snapshot then no texlive-latex or texlive-devel. Regards 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] Hermes Packaging
by Klaas Freitag 26 May '10

26 May '10

Hi, I know I am a wimp but I like to ask here if somebody is willing to help me packaging Hermes [1]. As Hermes is part of the OBS it kind of becomes urgent to have good packages in place because more people ask for it and want to run it along locally installed build services. I admit I am only a semi skilled packager and thus it would take me _long_ to figure out the packages as Hermes is, well, a bit heterogenous. And maybe my rare Hermes time is better spent if I fix some issues with Hermes instead? So if one wants to contribute that way, it would be great. Please send private mail to me. regards, Klaas [1] http://en.opensuse.org/Hermes -- 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] nautilus extensions
by Malcolm 25 May '10

25 May '10

Hi There is a package on the OBS Contrib nautilus-image-converter the current packages push the libnautilus-image-converter.so into %{_libdir}/nautilus/extensions-1.0 but this doesn't work, if I use %{_libdir}/nautilus/extensions-2.0 in the Makefile it functions as expected. Is this an acceptable method of patching? If so I will submit the patch. -- Cheers Malcolm °¿° (Linux Counter #276890) SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.27.45-0.1-default up 8 days 22:33, 2 users, load average: 0.07, 0.04, 0.00 GPU GeForce 8600 GTS Silent - CUDA Driver Version: 195.36.15 -- 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] How do I fix the dirac naming conflict with packman packages
by Dave Plater 24 May '10

24 May '10

Hi, the openSUSE package dirac consists of the following :- dirac which contains tools and README AUTHORS and the usual text docs libdirac_decoder0 decoder libs libdirac_encoder0 encoder libs dirac-devel which contains devel files and api documentation The Packman package dirac consists of the following :- dirac Contents identical to openSUSE libdirac_decoder0 Contents identical to openSUSE libdirac_encoder0 Contents identical to openSUSE libdirac-devel which contains only devel files. dirac-doc which contains api documentation As you can see packman have split dirac-devel into libdirac-devel and dirac-doc. What is the correct way to handle this conflict? The way it stands atm the installation system allows dirac-devel, libdirac-devel and dirac-doc to exist in the system. When following openSUSE packaging conventions for merging two packages into one I get an rpmlint error about self-obsoletion. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 8

[opensuse-packaging] package cacti (cacti-0.8.7f) in 32 bit build succeeds, and in 64 bit build fails
by doiggl＠velocitynet.com.au 23 May '10

23 May '10

Hello The package cacti (cacti-0.8.7f) in 32 bit build succeeds, and in 64 bit build fails when it gets to ... checking filelist why is this the case , how can it be fixed if so how ? >From the logs 64 bit - fail ============= Wrote: /usr/src/packages/SRPMS/cacti-0.8.7f-8.1.src.rpm Wrote: /usr/src/packages/RPMS/noarch/cacti-0.8.7f-8.1.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.YN8C2q + umask 022 + cd /usr/src/packages/BUILD + cd cacti-0.8.7f + rm -rf /usr/src/packages/BUILDROOT/cacti-0.8.7f-8.1.x86_64 + exit 0 ... checking for files with abuild user/group ... running 00-check-install-rpms ... installing all built rpms Preparing packages for installation... cacti-0.8.7f-8.1 ... running 01-check-debuginfo ... testing for empty debuginfo packages ... running 02-check-gcc-output ... testing for serious compiler warnings (using /usr/lib/build/checks-data/check_gcc_output) (using //.build.log) ... running 03-check-binary-kernel-log ... running 04-check-filelist ... checking filelist cacti: "/usr/share/cacti/install/index.php.orig" is not allowed anymore in SuSE Linux. cacti: "/usr/share/cacti/lib/functions.php.orig" is not allowed anymore in SuSE Linux. System halted. 32 bit -pass ============ Wrote: /usr/src/packages/SRPMS/cacti-0.8.7f-21.1.src.rpm Wrote: /usr/src/packages/RPMS/noarch/cacti-0.8.7f-21.1.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.thXpLK + umask 022 + cd /usr/src/packages/BUILD + cd cacti-0.8.7f + rm -rf /usr/src/packages/BUILDROOT/cacti-0.8.7f-21.1.i386 + exit 0 ... checking for files with abuild user/group ... running 00-check-install-rpms ... installing all built rpms Preparing packages for installation... cacti-0.8.7f-21.1 ... running 01-check-debuginfo ... testing for empty debuginfo packages ... running 02-check-gcc-output ... testing for serious compiler warnings (using /usr/lib/build/checks-data/check_gcc_output) (using //.build.log) ... running 03-check-binary-kernel-log ... running 04-check-filelist ... checking filelist ... running 05-check-invalid-requires ... running 06-check-installtest ... testing for pre/postinstall scripts that are not idempotent ... running 08-check-permissions ... testing for modified permissions ... running 09-check-packaged-twice ... running 10-check-lanana cacti: Name of cron script "cacti" is not LSB conform ... running 11-check-pkgconfig-deps ... testing devel dependencies required by pkgconfig .pc files ... running 12-check-libtool-deps ... testing devel dependencies required by libtool .la files (can be skipped by "skip-check-libtool-deps" anywhere in spec) ... running 13-check-invalid-provides ... running 14-check-gconf-scriptlets ... testing GConf scriptlet presence ... running 99-check-remove-rpms ... removing all built rpms (order: reverse cacti) - Other info I saw the problem over here too -> https://build.opensuse.org/package/show?package=cacti&project=openSUSE%3AFa… Project -> https://build.opensuse.org/package/show?package=cacti&project=home%3Adoiggl Spec -> https://build.opensuse.org/package/view_file?file=cacti.spec&package=cacti&… Complete Logs ->https://build.opensuse.org/package/live_build_log?arch=i586&package=cacti&p… ->https://build.opensuse.org/package/live_build_log?arch=x86_64&package=cacti… Thanks Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 3

[opensuse-packaging] (Factory) source pre-checkin tests
by Adrian Schröter 21 May '10

21 May '10

Heya, were you ever angry because your Factory submission was declined because of some obvious simple error ? Rudi published these Factory spec file validators now and osc is calling them by default before committing new sources. You can install the validators and new osc from openSUSE:Tools:Unstable project zypper ar http://download.opensuse.org/repositories/openSUSE:Tools:Unstable/$YOUR_DIS… zypper in osc-0.126git This should also install the new "osc-source_validator" package. It would be good to check if this has also un-expected downsides, if you maintain packages not intended to be submitted to Factory for example. Fixes or additional checks are highly welcome :) Just submit them to openSUSE:Tools:Unstable osc-source_validator . have fun adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- 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] Misc Issues in home:saigkill/boinc-client
by Sascha 'saigkill' Manns 20 May '10

20 May '10

Hello Mates, atm i´m working on boinc-client. Now im getting: boinc-client.x86_64: W: shared-lib-calls-exit /usr/lib64/libboinc_graphics2.so.6.10.56 exit(a)GLIBC_2.2.5 boinc-client.x86_64: W: shared-lib-calls-exit /usr/lib64/libboinc_api.so.6.10.56 exit(a)GLIBC_2.2.5 boinc-client.x86_64: W: binary-or-shlib-calls-gethostbyname /usr/lib64/libboinc.so.6.10.56 boinc-client.x86_64: W: binary-or-shlib-calls-gethostbyname /usr/bin/boinc-client Anyone know how to fix it? -- 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 2

[opensuse-packaging] A question about aggregatepac
by Dave Plater 18 May '10

18 May '10

Hi, multimedia:libs enca aggregates to Education enca and the latter builds fine for SLE11 but multimedia:libs enca is broken for SLE11 with the message :- missing repositories: Education/SLE_11 What causes this and shouldn't mmlibs enca rather link to the education package? Mmlibs enca seems to exist for mmlibs libass to build for <= 11.1 and the resulting rpms require enca so IMHO the latest rpm should be available in mmlibs to enable easy installation. Regards 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

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging May 2010