October 2010 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Configure issue with new package
by Robert Schweikert 21 Oct '10

21 Oct '10

Hi, I am trying to build a new package that requires boost, thus I've added BuildRequires: boost-devel >= 1.35 to my spec file. Upon build I get the following error: checking boost/shared_ptr.hpp usability... no checking boost/shared_ptr.hpp presence... no checking for boost/shared_ptr.hpp... no configure: error: Missing required header files. But, -> ls /var/tmp/build-root/usr/include/boost/shared_p* /var/tmp/build-root/usr/include/boost/shared_ptr.hpp The configure script snippet that looks for the header looks as follows: for ac_header in boost/shared_ptr.hpp uuid/uuid.h do as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh` if { as_var=$as_ac_Header; eval "test \"\${$as_var+set}\" = set"; }; then { $as_echo "$as_me:$LINENO: checking for $ac_header" >&5 There's no option in the configure script for me to set the location of the boots headers, at least AFAICT. Any ideas on how to fix this? home:rjschwei:eucalyptus/apache-qpid-cpp I've not yet uploaded the spec file since it is still WIP. Help is much appreciated. Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Software Engineer Consultant LINUX rschweikert(a)novell.com 781-464-8147 Novell Making IT Work As One -- 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] Generating parts of spec
by Michal Smrž 20 Oct '10

20 Oct '10

Hello I want to ask, if is possible generate parts of spec file. I tried to experiment with macros but not luck (or bad hands) Idea is, in package where is very very much repeting work, do that work in loop. I am trying to do package with new Tesseract, which has about 32 supported languages, which are packed separately in previous package. I wanna continue with that. Yes, first possibility is use brute force and create huge spec. It is quickest and simplest. But I am donig packages for fun and want some inteligence in it. My idea is something about this (not exactly Python, would fight with bash if needed) languages = ("deu", "ell", "eng", ...) count = 1 for lang in languages: return "Source"+str(count)+": "+lang+".data.tar.gz" count = count + 1 and later the same with header, and description for subpackage, files etc. So supported languages could be added only with editing languages variable languages. Thank you Michal Smrž -- 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] Python 2.7 coming to Factory
by Jan Matejek 20 Oct '10

20 Oct '10

Fellow developers and users, just a heads-up: moments ago I have submitted a new Python version 2.7. This version contains many new and interesting features, and only a small chance of breaking existing code: no backwards-incompatible changes, and no big changes worth mentioning. For more details see [1]. There is one thing notable for people who write or maintain software that embeds Python: the new function PySys_SetArgvEx [2] does the job originally done by PySys_SetArgv, but closes a nasty security problem with the latter [3][4]. Most software should be fixed by now, but please review your packages anyway. have fun m. [1] http://docs.python.org/dev/whatsnew/2.7.html#porting-to-python-2-7 [2] http://docs.python.org/dev/c-api/init.html#PySys_SetArgvEx - the link points to python 3 docs, but applies to 2.7 as well [3] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5983 [4] http://www.openwall.com/lists/oss-security/2009/01/26/2 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 10

[opensuse-packaging] Need help with pdflatex was openSUSE Build Service ghostscript
by Dave Plater 19 Oct '10

19 Oct '10

I sent this request for assistance to the maintainer of ghostscript and tex but haven't had a reply for a few days, maybe somebody else can help? I apologize if I'm being impatient. I also realize that I should have put tex instead of ghostscript in the subject blame it on the mailto I used for the email and inexcusable laziness on my part, a good subject can make the email far easier to understand. Hi, I maintain multimedia libs and apps as wll as lilypond and I'm tracking down the reason why libcaca fails factory build on a texlive pdflatex command. Package log4c from devel:libs:c_c++ has an identical failure and the timing of the failures coincide with gs 9's debut in factory. I see that texlive uses ghostscript_x11, I'm assuming for pdf work. Can you perhaps point me in the right direction to solve this problem? The failure of libcaca, the only difference to the log4c failure is log4c uses the command "latex refman.tex" and libcaca - "pdflatex refman.tex" :- pdflatex refman.tex This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/openSUSE) entering extended mode (./refman.tex LaTeX2e <2009/09/24> Babel <v3.8l> and hyphenation patterns for english, usenglishmax, dumylang, noh yphenation, german-x-2009-06-19, ngerman-x-2009-06-19, ancientgreek, ibycus, ar abic, basque, bulgarian, catalan, pinyin, coptic, croatian, czech, danish, dutc h, esperanto, estonian, farsi, finnish, french, galician, german, ngerman, mono greek, greek, hungarian, icelandic, indonesian, interlingua, irish, italian, ku rmanji, latin, latvian, lithuanian, mongolian, mongolian2a, bokmal, nynorsk, po lish, portuguese, romanian, russian, sanskrit, serbian, slovak, slovenian, span ish, swedish, turkish, ukenglish, ukrainian, uppersorbian, welsh, loaded. make[3]: *** [refman.pdf] Error 1 This error possibly results in :- ! LaTeX Error: \cftchapfont undefined. See the LaTeX manual or LaTeX Companion for explanation. Type H <return> for immediate help. ... See : https://build.opensuse.org/package/rawlog?arch=x86_64&package=libcaca&proje… I looked through tex documentation and can't find a way of increasing the verbosity of the output from pdflatex. Attached refman.tex. Thanks for any assistance you can give, I'm not very tex literate. Dave P.

2 3

[opensuse-packaging] gcov/lcov for -devel packages?
by Lars Marowsky-Bree 19 Oct '10

19 Oct '10

Hi all, it seems that gcov hard-codes the pathnames to the source files into the binary (yuck), making it quite hard to use with abse+-devel packages. Has anyone solved that before? I'd like to get coverage data for the code from a real install, not just from a special build. (And don't want to reinvent packaging magic if I can avoid it ;-) Regards, Lars -- Architect Storage/HA, OPS Engineering, Novell, Inc. SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- 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] specfile template
by Ralf Lang 19 Oct '10

19 Oct '10

On the opensuse wiki at http://en.opensuse.org/openSUSE:Specfile_guidelines#Specfile_Template it suggests I shall use the template from the page rpmdevtools. This page is currently non-existant (red link). Where can I get the "official template"? -- Ralf Lang Geschaeftsfuehrer: Ralph Dehner Linux Consultant / Developer Unternehmenssitz: Vohburg B1 Systems GmbH Amtsgericht: Ingolstadt Mobil: +49-(0)-170 6381563 Handelsregister: HRB 3537 EMail: lang(a)b1-systems.de http://www.b1-systems.de Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg GPG: http://pgpkeys.pca.dfn.de/pks/lookup?op=get&amp;search=0x0ACD5DB0727F5F… -- 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] RPM version question
by Stefan Seyfried 17 Oct '10

17 Oct '10

Hi, a question on RPM version number ordering: Is the following correct? 0.9.24 < 0.9.24.99.017 < 0.9.24.99.01720100123 < 0.9.24.99.018 or is 0.9.24.99.018 < 0.9.24.99.01720100123 ? The reason is: I'd like to package a "0.9.25beta17", but have room for a possible snapshot later on without breaking the monotonic nature of the version number ;-) Thanks, seife -- Stefan Seyfried "Any ideas, John?" "Well, surrounding them's out." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 13

[opensuse-packaging] Fixing %find_lang to not list C documentation
by Vincent Untz 14 Oct '10

14 Oct '10

Hi, Since we're changing lang package to be only recommended instead of required, I think it's really time to get my patch for rpm from https://bugzilla.novell.com/show_bug.cgi?id=449847 in. This changes %find_lang to not list C documentation, so that the C documentation will always be with the main package. Now, I'm unsure how to deal with this: it will probably cause tons of build failures because the C documentation will not be packaged anymore. Does anyone have an idea of how to make this change without creating big issues? 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

2 2

[opensuse-packaging] Package requires fixes confuse me
by Andreas Jaeger 12 Oct '10

12 Oct '10

Cristian, you have submitted fixes like SR#50243 which adds a requires on dbus-1. Why is this needed at all? The package already requires libdb-1.so.3, so there's no extra need for dbus-1. Or what do I miss? Andreas -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- 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] Help needed to get baselibs.conf right
by Vincent Untz 12 Oct '10

12 Oct '10

Hi, I've struggled with two baselibs.conf issues yesterday, and I'd need help to solve them. First, one question: my understanding is that we can't assume that the packages that will be created will be for 32-bit only, they could well be 64-bit too. Is that right? (We only do 32-bit ones in openSUSE, afaik, though) My two issues can be seen with this example from gtk2 (submitted to G:F): post "%if %_lib == lib64" post "%{_bindir}/gtk-query-immodules-2.0-64 > %{_sysconfdir}/gtk-2.0/gtk64.immodules" post "%else" post "%{_bindir}/gtk-query-immodules-2.0 > %{_sysconfdir}/gtk-2.0/gtk.immodules" post "%endif" Usage of quotes in scriptlets ============================= I initially wanted to write something like: %if "%_lib" == "lib64" So I tried the following: post "%if \"%_lib\" == \"lib64\"" post "%if \\"%_lib\\" == \\"lib64\\"" post "%if \\\"%_lib\\\" == \\\"lib64\\\"" post '%if "%_lib" == "lib64"' They all caused failures. I worked around the issue by just removing the quotes: post "%if %_lib == lib64" But is there anyway to use quotes there? Paths for x86 packages ====================== The files in x86 packages are all put in a /emul/ia32-linux prefix. So I get /emul/ia32-linux/usr/bin/gtk-query-immodules-2.0 and /emul/ia32-linux/etc/gtk-2.0/gtk.immodules. However, the post scriplet above will expand to: /usr/bin/gtk-query-immodules-2.0 > /etc/gtk-2.0/gtk.immodules So it will just not do what is intended. What's the right way to do things here? Is it a bug in the spec file generated from baselibs.conf for x86? 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 8

[opensuse-packaging] controlling package release numbers for snapshot packages
by Hans-Peter Jansen 11 Oct '10

11 Oct '10

Hi, I'm in the process of creating a project for automated PyQt snapshot builds (home:frispete:PyQt-next), that should replace the packages of some other repo (home:frispete:PyQt), but that should be superimposable from the former, if a new released package exist. (Sorry people for this convoluted description). Let's talk in examples: home:frispete:PyQt has python-sip-4.11.1-4.4 home:frispete:PyQt-next has python-sip-4.11.2-8.1 the latter is linkpac'ed to the former I hoped to be able to use a snapshot release date as the release number, e.g.: 0.20101010.043033.1 ^ snapshot ^^^^^^^^ date ^^^^^^ time ^ generation home:frispete:PyQt-next should read: python-sip-4.11.2-0.20101010.043033.1 If a package gets released, it will >= python-sip-4.11.2-1 In short, how do I control the release numbers in build service? I know, that osc has an setlinkrev option, and linkpac has the magical --cicount. Is it enough the set --cicount=local and it it possible to set this later on? TIA, Pete -- 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] Package to give away: GNU patch
by Andreas Gruenbacher 07 Oct '10

07 Oct '10

Hello, is anybody interested in taking over maintainership of the GNU patch package? I won't have the time for maintaining it myself anymore. https://build.opensuse.org/package/show?package=patch&project=devel%3Atools The package lives in devel:tools and only has a single, trivial SUSE specific patch. Very few bugs are being reported, and they are usually fixed upstream pretty quickly. Thanks, Andreas -- 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] Submission to factory of libraw1394, libavc1394 and libdc1394
by Dave Plater 07 Oct '10

07 Oct '10

Hi, I've submitted the following three packages, all part of the libraw1394 update, to factory : srs #49953, #49954 and #49956 It would be a good idea to accept all three at the same time, especially libdc1394 which has been fixed to build with the updated libraw1394. 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 0

[opensuse-packaging] Re: [opensuse-kernel] kernel-debuginfo packages for Open Suse 11.3
by Tony Jones 04 Oct '10

04 Oct '10

On Mon, Oct 04, 2010 at 03:11:24PM -0700, Alok Kataria wrote: > The kotd site has debuginfo packages for the KOTD at > http://ftp.suse.com/pub/projects/kernel/kotd/openSUSE-11.3/x86_64/ > is there a similar repository where the debuginfo package exists for all > the released kernels ? http://download.opensuse.org/debug/distribution/11.3/repo/oss http://download.opensuse.org/debug/update/11.3 First contains the debuginfo for the release, second for updates. I see debuginfo for several past kernel updates but I'm not sure what the exact policy is wrt retention. Tony -- 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] a library naming question.
by Dave Plater 04 Oct '10

04 Oct '10

Hi, I'm trying to update multimedia:libs libraw1394 but it has a sub package called libraw1394-8 with a file called libraw1394.so.8 which is required specifically by a ton of packages. The new package has a lib called libraw1394.so.11, it's close to my bedtime so the brain isn't 100% but updating libraw will at least cause a major rebuild hopefully no missing dependencies. The rebuild would take care of Requires: naming. My question is - should I just leave the 8 in libraw1394-8 or should it become libraw1394-11 and have I missed anything? I've already contacted the upstream maintainer about it's patch for streaming video that prevented it building and was a fix for a novell bug. The package wasn't updated for years possibly due to the fact that the Url: pointed to a defunct domain which is up for sale. I'm working on it in home:plater libraw1394 if somebody can have a look. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 17

[opensuse-packaging] libraw1394 is in mmlibs
by Dave Plater 03 Oct '10

03 Oct '10

Hi, libraw1394-2.0.5 is now in multimedia:libs and the only possible casualty I can see so far is libdc1394. I've gota go sing and drum in a band so I'll follow up tomorrow. 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] BuildRequires pkgconfig()?
by Cristian Morales Vega 03 Oct '10

03 Oct '10

Now that RPM provides automatically things like "pkgconfig(gtk+-2.0)"... should we use them explicitly? I mean change "BuildRequires: gtk2-devel" by "BuildRequires: pkgconfig(gtk+-2.0)". Not depending of package names would improve inter-distro compatibility, but would this be a good solution? -- 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] boinc-client to sale
by Sascha 'saigkill' Manns 03 Oct '10

03 Oct '10

Hello Mates, since a few years i'm serving as Maintainer of the BOINC Package. Sadly the last Versions can't driven correctly. So i would like to give the Maintainer Job another, better Person. Maybe we can place then a running Version into Factory. All needed Files (my latest Status) can seen under home:saigkill:boinc. cu Sascha -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.saschamanns.de Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English) Open-SLX : Linux convenient, simple, secure and complete

2 2

[opensuse-packaging] Need help with 11.2 qtractor build failure
by Dave Plater 02 Oct '10

02 Oct '10

Hi, I have an 11.2 and 11.1 buld failure for qtractor, it succeeds for 11.3, factory and strangely KDE:Distro:Factory 11.2 which has qt4.7. The failure is :- qtractorMainForm.cpp: In constructor 'qtractorMainForm::qtractorMainForm(QWidget*, Qt::WindowFlags)': qtractorMainForm.cpp:357: error: 'QGtkStyle' was not declared in this scope qtractorMainForm.cpp:357: error: parse error in template argument list qtractorMainForm.cpp:357: error: no matching function for call to 'qobject_cast(QStyle*)' qtractorMainForm.cpp: At global scope: qtractorMainForm.cpp:4855: warning: unused parameter 'pvSessionArg' make[2]: *** [.obj/qtractorMainForm.o] Error 1 The KDF11.3, KDF11.2, 11.3 and factory builds give no warnings and sail through the build. Maybe somebody has come across a similar failure? 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 0

[opensuse-packaging] Why should an unstable released package be favoured over a stable svn package?
by Dave Plater 01 Oct '10

01 Oct '10

Hi, I've been trying to submit an svn derived version of KTrafficAnalyzer to KDE:Extra, the package used to be in the old kde3 community repo and has been around in openSUSE for quite a while. It's been ported to kde4. I've been using the package from the authors home project and it occasionally crashed and lost the usage stats but after my recent update from KDE:Distro:Factory it consistently segfaulted on start up. This is a good thing that enabled me to track down the problem and patch it. It's now stable on a patched svn revision 44 so I decided to submit this very usefull package to KDE:Extra and am quite happy to maintain it as I use it all the time and it's a simple package only to have it rejected on the grounds that it's svn derived. This seems a bit stupid because the released package is unstable and even has a source forge bug against it from an openSUSE 11.3 user. I've had problems submitting a package fix to KDE:Extra before but in that case the maintainers reply was rather rude that issue was simply bad communication and was resolved and that particular maintainer accepted my second submit attempt of KTrafficAnalyzer pointing out that there wasn't a Url: in the spec file and asking me to fix it. I decided to patch the released tarball to svn 44 and submit that along with the fixed spec file but alas the first anti subversion maintainer caught the request and declined it. I was under the assumption that I'm helping to make openSUSE a better distribution but my encounters with KDE:Extra have made me think that that particular repository is an ego circus, it's easier to get a new package into Factory than into KDE:Extra, I've two new packages in 11.3 one of them totally new to openSUSE and one that the previous maintainer didn't have time for so it was dropped so I speak from experience. The point of this email are the questions :- am I flogging a dead horse trying to be a useful member of the community? Why do I get the impression that KDE:Extra is maintained a an exclusive club? Thanks for taking the time to read my rant. Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 6