October 2010 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] [Ann] New package: pdfgrep
by David Haller 25 Oct '10

25 Oct '10

Hello all, please give this program and package a test / lookover. If all works, I plan to submit it to Factory. OBS: https://build.opensuse.org/package/show?package=pdfgrep&project=home%3Adnh Repo: http://download.opensuse.org/repositories/home:/dnh/ Any comments are appreciated. -dnh PS: a fine example, why *I* don't like versioned libfooN packages. In the set I build for, I'd have to find what distribution has what from libpoppler4 to libpoppler7 and do a %if 0%{?suse_version} cascade. Fun? Not. I'd prefer "libpoppler >= $ver" and "multiversion" should take care of the rest, though one might want a UI in zypper/yast to manage "multiversion", best together with a "cleanup" feature to remove old versions (but the last N, for example). At least, the libpopplerN seem to provide "poppler". -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 5

[opensuse-packaging] how can these 'nothing provides' messages be resolved
by doiggl＠velocitynet.com.au 23 Oct '10

23 Oct '10

Hello. How can these 'nothing provides' messages be resolved from this spec file [1] Thanks Glrnn nothing provides perl(Email::Send) >= 2.00, nothing provides perl(Email::MIME) >= 1.861, nothing provides perl(Email::MIME::Encodings) >= 1.313, nothing provides perl(Email::MIME::Modifier) >= 1.442, nothing provides perl(Template::Plugin::GD::Image), nothing provides perl(PatchReader) >= 0.9.4, nothing provides perl(HTML::Scrubber), nothing provides perl(Email::MIME::Attachment::Stripper), nothing provides perl(Email::Reply), nothing provides perl(TheSchwartz), nothing provides perl(Daemon::Generic), nothing provides /usr/bin/cvs, nothing provides /usr/bin/diff, nothing provides /usr/bin/interdiff, nothing provides fakeroot [1] -> https://build.opensuse.org/package/view_file?file=bugzilla.spec&package=bug… -- 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] build error help needed
by Robert Schweikert 21 Oct '10

21 Oct '10

Hi, For home:rjschwei:eucalyptus/apache-qpid-cpp I get the following build error: + /usr/lib/rpm/brp-check-la found trace of $RPM_BUILD_ROOT or $RPM_BUILD_DIR in installed .la file /usr/src/packages/BUILDROOT/apache-qpid-cpp-0.6-2.1.x86_64/usr/lib64/_qmfengine.la I think this is triggered by the following inside the _qmfengine.la file. -L/usr/src/packages/BUILD/qpidc-0.6/src/.libs This is part of the "dependency_libs" assignment. The file is generated by libtool. I think this file is left behind to support the build of the Python interface for this library. It appears to me that this dependency should be expressed as DESTDIR/{ALL_THE_LIBRARIES}. But I have no idea if/how I can influence libtool to the right thing. I can build the package without generating the troublesome .la file. However, this would potentially preclude the build of the Python interface. Help is 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

2 1

[opensuse-packaging] Question about the presence of expletives in package libcaca
by Dave Plater 21 Oct '10

21 Oct '10

Hi, I'm trying to update multimedia:libs libcaca a quick check shows it's only required by gstreamer-0_10-plugins-good. I've had a good laugh after examining it, even the license is "WTFPL - Do What The F@#k You Want To Public License" - expletive deleted - and it has a large patch to delete the many other expletives scattered throughout the package which needs to be remade. So far I've searched for the F word and found 153 instances mostly due to the license header and comments in the changelog and a quick search for another slang word used for excretement only find 8 and once again these are merely comments. My question is - what are the chances of a faint hearted person going through the source rpm and as long as there isn't any actual display of naughty words during usage and the changelog is purged is it really necessary to patch all these words out? The name itself is naughty and seeing the authors penchant for french I'm sure some words that might offend a puritanical frenchman (are there any?) are still present in the package. I've had a good laugh but I'm not keen to take on the task of removing these words to update a package . My reason for doing this in the first place - the package is failing to build for factory. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

7 15

[opensuse-packaging] Re: [opensuse-buildservice] tar_src documentation
by Adrian Schröter 21 Oct '10

21 Oct '10

Am Donnerstag, 21. Oktober 2010, 00:28:19 schrieb Troy Telford: > Is there any documentation (yet) about how to use the tar_scm service? > > Specifically, I'm wondering about how one would specify a particular > tag/branch. With SVN, it's just in the URL, IIRC. But how do you > specify the branch when pulling from a git repo? The packaged .service file should contain all this informations. The webui is showing it on mouse-over (not very good UI yet). bye 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

1 0

[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