March 2010 - openSUSE Packaging - openSUSE Mailing Lists

[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] query - compiling package wflogs.
by doiggl＠velocitynet.com.au 07 Apr '10

07 Apr '10

Hello I am trying to compile project called wflogs. Project -> https://build.opensuse.org/package/show?package=wflogs&project=home%3Adoiggl Last log -> https://build.opensuse.org/package/live_build_log?arch=x86_64&package=wflog… spec file -> https://build.opensuse.org/package/view_file?file=wflogs.spec&package=wflog… I have a link to another project called wfnetobjs too (no wfnetobjs rpm installed yet) Last set of wflog errors: configure: error: wfnetobjs-incdir: no directory found, use configure option error: Bad exit status from /var/tmp/rpm-tmp.w8AYXU (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.w8AYXU (%build) System halted. Can someone assist me to compile this package please. 1. I think Ive got to install wfnetobjs rpm but dont know to set that in the spec file. 2. Also I got to do the configure bit with a call like (but unsure how to set in the spec file) # ./configure --with-wfnetobjs-libdir=/usr/include/wallfire/ help appreciated. Cheers Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 13

[opensuse-packaging] Easter and Milestone 5
by Stephan Kulow 07 Apr '10

07 Apr '10

Hi, Milestone 4 is out and Milestone 5 is going to be released next week. But there is a catch: Germany (and a lot of the western world) has holidays either friday or monday (or both in the case of Germany). So while I moved the release data of Milestone 5 to friday next week, this only means we will still take a couple of packages on april, 6th - but the big majority of packages needs to be submitted by tomorrow. With 274 diffs in devel projects, that is a lot to submit. So please take care not to miss the deadline. Note that M5 will bring a new Xorg and a new kernel - and a lot of people have vacation around the holidays, so if you don't make it, there won't be time for extra hand holding. And for those that keep wondering about milestones: Milestone 5 is the last release before we head into feature freeze. After it I only allow leaf packages to be updated - including a text freeze for all of it. Milestone 6 is then the first "Beta" - i.e. a milestone after feature freeze, so Milestone 5 will traditionally be the worst, please don't make it even worse. For details of your forgotten devel project: http://tinyurl.com/factory-status Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

7 10

[opensuse-packaging] applying a patch
by doiggl＠velocitynet.com.au 06 Apr '10

06 Apr '10

Hello I am trying to get a kernel that will be patched, then obs to to compile it to generate a .rpm and I need some assistance. - Its based on kernel 2.6.33.x , so Ive set up a link to the sources of the package kernel-source of project Base:Kernel. Details are: <link project='Base:Kernel' package='kernel-source' cicount='copy'/> Questions: - What does the BuildRequires line need so kernel-source-2.6.33.x gets installed (e.g kernel-source-2.6.33-6.2.src.rpm) ? - How can the patch be applied ? , its in patch.bz2 format Project -> https://build.opensuse.org/package/show?package=r4testdot33&project=home%3A… Assistance appreciated. Thanks Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 8

[opensuse-packaging] future libpng packaging (was: package name of libpng14)
by Petr Gajdos 31 Mar '10

31 Mar '10

Hi list, todays situation is as follows: libpng12-0 package has two subpackages, namely libpng3 and libpng-devel. The first one contains compatibility stuff and seems to be deprecated, as Christian Rodrígez pointed out yet, so only libpng-devel is relevant nowdays. libpng3 will be removed from libpng12-0 package. libpng-devel contains versioned and unversioned stuff, for example /usr/bin/libpng-config -> libpng12-config /usr/bin/libpng12-config /usr/include/libpng12 /usr/include/libpng12/png.h /usr/include/libpng12/pngconf.h /usr/include/png.h -> libpng12/png.h etc. While we are going to have libpng14-14 with 1.4 branch in addition to libpng12-0 I am forced to rework this package a bit. We propose (together with sbrabec) the following: The pair of main packages containing shared libraries will be libpng12-0 and libpng14-14 installable in parallel and independently from other four packages of course. There will be another pair of packages, libpng12-devel and libpng14-devel with versioned files (thanks to Jan Engelhardt to pointing this out). These packages will require libpng12-0 or libpng14-14 respectively. The last pair of packages form libpng12-compat-devel and libpng14-compat-devel containing the common files, like /usr/bin/libpng-config, /usr/include/png.h, etc. symlinks and man-pages (maybe we should have -doc package here?). These packages will require libpng12-devel and libpng14-devel respectively. BOTH will obsolete and provide libpng-devel symbol and BOTH will conflict with otherproviders(libpng-devel). Prefer: libpng14-compat-devel implies: 1. applications using 1.2 version only (-lpng12, etc.) should require libpng12-devel, 2. applications not checking for libpng version and failing with 1.4 branch should require libpng12-compat-devel, 3. applications building against 1.4 can depend on libpng-devel the same way as they do till now. With Prefer: libpng12-compat-devel in prjconf situation would be dual. One of questions is, if we should Prefer: libpng14-compat-devel or Prefer: libpng12-compat-devel in openSUSE 11.3. You can see packages in home:pgajdos:libpng14-14, I am using the latter Prefer: there. You can notice that spec files for both branches are the same except for -%define minor 2 -%define micro 43 +%define minor 4 +%define micro 1 %define branch %{major}%{minor} -Name: libpng%{branch}-0 +Name: libpng%{branch}-%{branch} What do you think? Any comments, suggestions, ...? Petr

5 4

[opensuse-packaging] Moving lilypond to multimedia:apps with the intention to submit it to factory.
by Dave Plater 29 Mar '10

29 Mar '10

Hi, I'm planning to move lilypond from openSUSE:Factory:Contrib to multimedia:apps and to submit it to factory, to enable multimedia:apps and factory rosegarden4 to require it. I'm making this announcement because I've maintainer rights in multimedia:apps and don't want to unwittingly abuse my privilege. I will wait until Wednesday before doing this and when it's accepted into factory will disable the factory build in contrib and delete the binaries leaving only 11.2 and 11.1 available. Any comments welcome. Regards Dave P -- 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] Request to move lilypond from contrib to factory?
by Dave Plater 28 Mar '10

28 Mar '10

Hi, I asked how to go about moving lilypond to factory on the packaging list and it was suggested that I ask on this list as well as a submit request. I've made submit request id 35916 already and here are my reasons :- I maintain contrib lilypond and multimedia:apps rosegarden4,rosegarden4 should "Require: lilypond" but because lilypond resides in contrib I can only recommend it in rosegarden because a new user might not have the contrib repo enabled. Lilypond used to be part of the main distribution and I belive it was moved to contrib due to lack of maintainer. I'm also not sure which devel project it should go to, it's a musical notation printing program, so I have submitted it from contrib. See also http://bugzilla.novell.com/show_bug.cgi?id=546120#c6 Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 1

[opensuse-packaging] How can I move a package from contrib to factory?
by Dave Plater 28 Mar '10

28 Mar '10

Hi, I maintain contrib lilypond and multimedia:apps rosegarden, rosegarden should Require: lilypond but because lilypond resides in contrib I can only Recommend it in rosegarden because a new user might not have the contrib repo enabled. Lilypond used to be part of the main distribution and I belive it was moved to contrib due to lack of maintainer. How do I go about moving lilypond back to factory? I'm also not sure which devel project it should go to, it's a musical notation printing program. See also http://bugzilla.novell.com/show_bug.cgi?id=546120#c6 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 4

[opensuse-packaging] Newly prepared virtualbox-ose in Virtualization repo
by Michal Seben 26 Mar '10

26 Mar '10

Hi all ! Because of bnc#567435 (duplicated symbols in vbox kernel modules) we have to split kernel packages for virtualbox-ose. Well and this is already done (in Virtualization repo https://build.opensuse.org/package/show?package=virtualbox- ose&project=Virtualization), but we also decide to clean up a spec file a little. This is also already done, but package needs testing. We also decide to move virtualbox-ose to Virtualization repo where it belongs. Just a notice : backported will be only last stable product (11.2 today) I will switch devel directory from Virtualization:VirtualBox to Virtualization next week + and I will try to push all changes to Factory. (I want to hit Milestone 5) Suggestions how to improve virtualbox-ose.spec in Virtualization repo are welcome. Preferred way is through the submitrequest :) bye! -- 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] Proposal for a shell scripting policy
by Guido Berhoerster 26 Mar '10

26 Mar '10

Hello, following up the discussion on upstart and init scripts I'd like to propose a new policy on shell scripting. Shell scripting policy ---------------------- /bin/sh can be only expected to support the SUSv3 Shell Command Language, this allows dash, ksh, and bash to become /bin/sh. Init scripts should use /bin/sh, but may use /bin/bash with proper justification, e.g. not just for using ==, [[ ]], or echo -e which are easily replaced by SUSv3 compliant constructs. New packages containing scripts using /bin/sh must be tested with dash as /bin/sh (dash -n/checkbashisms.pl may aid debugging but are not sufficient by themselves). Any errors should be fixed and reported upstream. The rpm specfiles and scriptlets use bash and a GNU userland by default (I think everything else would be a pain to fix because of the many bashisms and GNUisms in specfiles). Rationale --------- * Choice and diversity are good: the ulimate goal would be to allow any SUSv3 compatible shell in openSUSE (currently ksh93, bash, and dash) to be used as /bin/sh * Quality and Correctness: /bin/sh is not /bin/bash, using other shells may expose bugs, corner cases etc. * Speed: bash is slow, allowing scripts to run on other shells such as dash or ksh93 may lead to speedups in certain situations * Portability: allow the re-use of scripts written for openSUSE on other OS What other distros are doing ---------------------------- Fedora does not seem to have a policy on shell scripts, according to the Debian policy handbook (which also applies to Ubuntu) /bin/sh can only be assumed to support the SUSv3 Command Language whith three exceptions, those are support of echo -n, test -a/-o and local. Note that this is not entirely correct, echo -n, test -a/-o are as XSI extensions part of the SUSv3 just not POSIX. Implementation -------------- The implementation of this policy could happen gradually over time assisted by a new rpmlint check which uses dash -n and checkbashisms.pl. In my opinion %_buildshell should point to /bin/bash, simply because fixing all the bashisms and gnuisms (pushd, popd, == etc.) in specfiles would be too much work. Building packages with dash as /bin/sh may expose bugs in build systems which will need to be fixed upstream. However, since Debian and Ubuntu have been doing this for some time, many issues are likely to be resolved already and there is pressure on upstream maintainers to fix their scripts. In the long term /bin/sh could default to dash, choosing ksh93 and bash should remain a possibility through the use of update-alternatives. Finally, here is a rough estimate on the scale of the issue: * on February 22nd the Factory OSS Repository (i586/i686/noarch) contained 8002 binary packages * there are 4065 /bin/sh scripts (267 of which are init scripts) in 1092 packages, furthermore there are 3481 /bin/sh rpm scriptlets in 1488 packages * checkbashisms.pl shows warnings for 794 scripts (100 of which are init scripts) in 372 packets (note that checkbashisms.pl is not very reliable) * dash -n leads shows syntax errors in 356 scripts (16 of which are init scripts) in 111 packages (haowever this does not detect all errors) Comments, Suggestions? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 26

[opensuse-packaging] Directories for message catalogs
by Philipp Thomas 25 Mar '10

25 Mar '10

for a package of mine I get filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/bg_BG/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/ca_ES(a)valencia/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/cs_CZ/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/da_DK/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/et_EE/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/eu_ES/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/fi_FI/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/fr_CA/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/gl_ES/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/he_IL/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/hu_HU/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/id_ID/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/ja_JP/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/km_KH/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/ko_KR/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/lt_LT/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/lv_LV/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/mk_MK/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/nb_NO/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/nn_NO/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/pl_PL/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/pt_PT/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/ro_RO/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/sk_SK/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/sl_SI/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/th_TH/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/uk_UA/LC_MESSAGES/filezilla.mo filezilla.x86_64: W: invalid-lc-messages-dir /usr/share/locale/vi_VN/LC_MESSAGES/filezilla.mo from rpmlint. Could somebody please tell me where a list of the correct directories exists? Philipp -- 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] Push iPhone/iPod Touch Support Library into Factory for openSUSE 11.3
by Martin S. 24 Mar '10

24 Mar '10

Hi, I was approached by Vincent Untz as I am the maintainer of libimobiledevice to push the library into openSUSE:Factory. Further information about the library is available here: http://www.libimobiledevice.org/ Currently confirmed is that Ubuntu, Fedora and Mandriva feature the stack in their next releases and it would be nice if openSUSE 11.3 would not be left behind. Especially since I am maintaining the packages in my OBS project home:FunkyM:iphone since the early beginnings of the library. Required new (source) packages are: - usbmuxd - libplist - libimobiledevice - ifuse This would enable libgpod4 (music/video sync) and GNOME's GVFS (filesystem access) to build with iPhone/iPod Touch support and would be a nice gain for marketing. Rhythmbox, latest Amarok and GTKPod use libgpod and thus will work, too. The question left is into which project to push the stack alongside the related libraries and how to get it into factory. Looking forward to your feedback. --- Martin S. -- 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] have choice for perl(Error) needed by perl-Mail-SPF: perl-Error git-core
by Christian 21 Mar '10

21 Mar '10

Hi, I get this expansion error in devel:languages:perl. When I search for "git-core" I do not get any reasonable result. Download_repositories <http://download.opensuse.org/repositories/Ports:/DebianBased:/Auto/> *git-core* <https://build.opensuse.org/package/show?package=git-core&project=Ports%3ADe…> (project Ports:DebianBased:Auto <https://build.opensuse.org/project/show?project=Ports%3ADebianBased%3AAuto>) [goto download repositories] <http://download.opensuse.org/repositories/Ports:/DebianBased:/Auto/> 36 fast, scalable, distributed revision control system Git is popular version control system designed to handle very large projects with speed and efficiency; it is used mainly for various open source ... Download_repositories <http://download.opensuse.org/repositories/home:/voronov84/> *git-core* <https://build.opensuse.org/package/show?package=git-core&project=home%3Avor…> (project home:voronov84 <https://build.opensuse.org/project/show?project=home%3Avoronov84>) [goto download repositories] <http://download.opensuse.org/repositories/home:/voronov84/> 36 git - stupid content tracker package /<no description>/ Download_repositories <http://download.opensuse.org/repositories/Ports:/DebianBased:/Auto/> *devscripts* <https://build.opensuse.org/package/show?package=devscripts&project=Ports%3A…> (project Ports:DebianBased:Auto <https://build.opensuse.org/project/show?project=Ports%3ADebianBased%3AAuto>) [goto download repositories] <http://download.opensuse.org/repositories/Ports:/DebianBased:/Auto/> 4 scripts to make the life of a Debian Package maintainer easier ...t] - debcommit: commit changes to cvs, svn, svk, tla, bzr, git, or hg, basing commit message on changelog [cvs | subversion | svk | tla | bzr | *git-core* | mercurial] - debdiff: compare two versions of a Debian package to check for added and removed files [wdiff, patchutils] - debi: install a just... I don't think any of these is inluded for build to d:l:p. But perhaps someone knows what to do and how to fix it. To get packages build I did a workaround in prjconf "Prefer: perl-Error" Thanks for help Chris -- 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] binary is linked against libraries in /usr/ or /opt
by Sascha 'saigkill' Manns 20 Mar '10

20 Mar '10

Hello Mates, today i've tried to build tuxcmd (home:saigkill). The Package builds to the brp-check brp-rootfs with the Issue: http://pastebin.ca/1846034 Does anyone know, how to fix this? Have a nice evening... -- Sincerely yours Sascha Manns 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) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 7

[opensuse-packaging] fixing an empty RPM
by doiggl＠velocitynet.com.au 20 Mar '10

20 Mar '10

Hello, A rpm I am building on opensuse build service looks like it builds the modules as i see a directory structure with files, but at the end the log says :- ... 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 bugzilla: An empty RPM is not allowed anymore in SuSE Linux Question: Is it the filelist that needs fixing here, if so how can it be populated ? Project -> https://build.opensuse.org/package/show?package=bugzillatest&project=home%3… Spec -> https://build.opensuse.org/package/view_file?file=bugzillatest.spec&package… Last build log -> https://build.opensuse.org/package/rawlog?arch=x86_64&package=bugzillatest&… Thanks Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 5

Re: [opensuse-packaging] binary is linked against libraries in /usr/ or /opt
by Sascha 'saigkill' Manns 19 Mar '10

19 Mar '10

Am Freitag, 19. März 2010 21:56:00 you wrote: > Hi Sascha, > > On Fri, 19 Mar 2010, Sascha 'saigkill' Manns wrote: > > today i've tried to build tuxcmd (home:saigkill). The Package > > builds to the brp-check brp-rootfs with the Issue: > > http://pastebin.ca/1846034 > > > > Does anyone know, how to fix this? > > Easy Rule: if a program (binary or script) uses libs or other > programs from the /usr/... hierarchy, the program also resides in > the /usr/... hierarchy, usually /usr/bin /usr/sbin /usr/local/bin > /usr/local/sbin or /opt. I've checked the Makefile: http://pastebin.ca/1846119 . The Path are set to: DEFAULT_DESTDIR=/usr And inside the install Section: $(INSTALL) -d $(DESTDIR)/bin $(INSTALL) -m 755 tuxcmd $(DESTDIR)/bin $(INSTALL) -d $(DESTDIR)/lib$(LIB_SUFFIX)/tuxcmd In my view this looks right... Binary in /usr/bin and Libs in /usr/lib(64). -- Sincerely yours Sascha Manns 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) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

Re: [opensuse-packaging] binary is linked against libraries in /usr/ or /opt
by Sascha 'saigkill' Manns 19 Mar '10

19 Mar '10

Am Freitag, 19. März 2010 21:56:00 you wrote: > Hi Sascha, > > On Fri, 19 Mar 2010, Sascha 'saigkill' Manns wrote: > > today i've tried to build tuxcmd (home:saigkill). The Package > > builds to the brp-check brp-rootfs with the Issue: > > http://pastebin.ca/1846034 > > > > Does anyone know, how to fix this? > > Easy Rule: if a program (binary or script) uses libs or other > programs from the /usr/... hierarchy, the program also resides in > the /usr/... hierarchy, usually /usr/bin /usr/sbin /usr/local/bin > /usr/local/sbin or /opt. > > In this case your build tries to install 'tuxcmd' in /bin, this can > not be allowed because all the libs it links against are under > /usr/... Aaah, sure. That i haven't noticed. Thanks for clarifying :-) -- Sincerely yours Sascha Manns 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) -- 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] noarch perl packages
by Ludwig Nussel 19 Mar '10

19 Mar '10

Hi, Many pure perl packages are not noarch just because of that .packlist file in %perl_vendorarch. Is that file good for anything in an rpm managed system? Ie could it be savely omitted from packages? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 3

[opensuse-packaging] compiler / devel files in package
by Dominique Leuenberger 19 Mar '10

19 Mar '10

Good day everybody, Today I have a question regarding the packaging policy. i'm building the package orc (which is the successor of liboil). now, orc is a compiler, called orcc and a bunch of libraries. The libraries are split in a package according shlib (no problem there). The binary orcc would be in the main package and the -doc contains the extensive documentation. now the question is mainly with focus on the development headers: Should those really be split in a -devel package? As I see it so far pretty much every package that will require orc compiler will need access to the specific headers (but who know, this might change). The -devel package without the compiler itself is rather useless too I think. What are your suggestions? 1) Having the devel files in the main package and make rpmlint quiet ? b) Move orcc to the -devel package? If I look at gcc45 for example this contains a list of header files as well, so I'm very much inclined to do the same for orc (so option a). Any comments / suggestions / recommendations / objections / [...]ions ? Dominique -- 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] apparmor help
by Peter Czanik 17 Mar '10

17 Mar '10

Hello, I'm working on upgrading syslog-ng from 2.0 to 3.0. My packages are available at http://download.opensuse.org/repositories/home:/czanik/openSUSE_11.2/ The current syslog-ng profile at /etc/apparmor.d/syslog-ng is for syslog-ng 2.0 and does not work for syslog-ng 3.0. I get: Mar 17 10:46:19 bigone112 syslog-ng[455]: Error opening control socket, bind() failed; socket='/var/run/syslog-ng.ctl', error='Address already in use (98)' First of all: is there anybody, who could help me to fix the apparmor profile? And of course I also have a packaging question: The apparmor profile file is not owned by syslog-ng, but by apparmor-profiles: bigone112:~ # rpm -qf /etc/apparmor.d/sbin.syslog-ng apparmor-profiles-2.3-50.2.noarch What is the proper way of packaging a new /etc/apparmor/sbin.syslog-ng, if I want to provide syslog-ng packages for 11.1, 11.2 and factory? Bye, CzP -- 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 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