October 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] rpmlint-checks: adding new gnome/desktop-related checks
by Vincent Untz 13 Feb '11

13 Feb '11

Hi, I've been adding some macros to make life easier when packaging things for GNOME, or desktop applications in general. See [1] for some of those, and I guess I'll send a new mail later for the others -- I just need to figure out where some of them should live. Anyway. The thing is that those macros are all nice, but nobody will think about using them if they don't have rpmlint checks. So I wrote some checks. Can we add this to the rpmlint-checks git repo, and to our rpmlint package? Thanks, Vincent [1] http://lists.opensuse.org/opensuse-packaging/2010-08/msg00059.html -- Les gens heureux ne sont pas pressés.

3 19

[opensuse-packaging] What is wxGTK/wxWidgets all about?
by Dave Plater 28 Dec '10

28 Dec '10

Hi, my package home:plater kicad based on Science kicad, which I need for money making work, eshceema gui freezes after my box goes on standby which I suspect without lengthy debugging is due to wxGTK. I see that the openSUSE wxGTK is actually wxPython and not even wxGTK although the url in the spec file points to the wxwidgets site. Kicad is supposed to use wxWidgets but this is only available from packman and causes problems with other packages which build from wxGTK (wxPython). Why are there all of these different types of wx's? 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 9

[opensuse-packaging] /etc/sysconfig/foo is not allowed .. not even as %ghost ?
by Cristian Rodríguez 15 Nov '10

15 Nov '10

Hi: When you remove a package that adds sysconfig files, /etc/sysconfig/foo are kept on the system, even i9f you didnt modified them. I am missing something of the respective packages should own those files but mark them as %ghost ? Cheers. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

8 15

[opensuse-packaging] Desktop File Error
by Sascha 'saigkill' Manns 06 Nov '10

06 Nov '10

Hello Mates, i've created an *.desktop File (attached). Inside the Spec: %__install -d -m 755 %{buildroot}%{_datadir}/pixmaps %__install -m 644 %{SOURCE2} %{buildroot}%{_datadir}/pixmaps/%{name}.png %suse_update_desktop_file -i %{SOURCE1} Source1 is the File. While building with OSC i'm getting: ERROR: No sufficient Category definition: /usr/src/packages/BUILDROOT/freediams-0.4.2.961-1.x86_64//usr/share/applications/freediams.desktop WARNING: Empty GenericName: /usr/src/packages/BUILDROOT/freediams-0.4.2.961-1.x86_64//usr/share/applications/freediams.desktop Errors in installed desktop file detected. Please refer to http://en.opensuse.org/SUSE_Package_Conventions/RPM_Macros Maybe anyone knows, what happend? -- 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

6 22

[opensuse-packaging] drop %suse_update_desktop_files macro
by Pavol Rusnak 02 Nov '10

02 Nov '10

Hi all! In order to make our specs more cross-distro-friendly we would like to drop %suse_update_desktop_files macro. It is currently being discussed in this feature: https://features.opensuse.org/310621 . Ludwig suggested that all translation magic we do could be moved into brp-script instead of doing it in %install phase. Is it possible? Do we have an expert in this area who could help porting it? :-) Once this is done, we can replace %suse_update_desktop_files with desktop-file-install if needed (but for most cases removing the call should be enough). -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9 prusnak[at]opensuse.org Czech Republic -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

7 17

[opensuse-packaging] Library naming dilemma
by Dave Plater 01 Nov '10

01 Nov '10

Hi, I'm packaging openCOLLADA which consists of libraries needed by the soon to be released blender-2.5x. ATM I have the libs in a separate sub package for each and a devel package. I see that I'm allowed to package all the libraries in one rpm, which one is preferable? My other question is - although I've packaged libOpenCOLLADAFramework.so.0.0.775 in sub package libOpenCOLLADAFramework0 I still get an rpmlint warning - libOpenCOLLADAFramework0.x86_64: W: shlib-policy-missing-lib and libOpenCOLLADAFramework0.x86_64: W: no-soname /usr/lib64/libOpenCOLLADAFramework.so.0.0.775. What am I doing wrong? I get these warnings for each lib. Package is at home:plater:blender openCOLLADA 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 12

[opensuse-packaging] Do not use AM_SILENT_RULES in packages
by Cristian Rodríguez 01 Nov '10

01 Nov '10

Hi: I see an increasing amount of stuff using automake's new AM_SILENT_RULES feature, remember to use --disable-silent-rules or "make V=1" when you submit the package for build. This feature breaks current build checks that rely on analizing the output of the build log. Thanks for flying with openSUSE :-) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 6

[opensuse-packaging] looking for official prj for xca
by Christian 31 Oct '10

31 Oct '10

Hi, what would be the right PROJECT for 'xca' An RSA key and certificate management tool Graphical certification authority is an interface for managing RSA keys and certificates, and the creation and signing of PKCS#10 requests. It uses the OpenSSL library and a Berkeley DB for key and certificate storage. It supports importing and exporting keys and PEM DER PKCS8 certificates, signing and revoking of PEM DER PKCS12, and the selection of x509v3 extensions. A tree view of certificates is presented. Cheers -- 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

2 1

[opensuse-packaging] A "Sanitizing sources" with pre_checkin.sh question.
by Dave Plater 30 Oct '10

30 Oct '10

Hi, when I first started maintaining blender it had a pre-checkin.sh to remove it's built in ffmpeg, x264 and other banned items, from it's source. I was very happy when it was stated on the blender devel list that 2.5x would no longer have these but now I've found internal blender sources with ffmpeg in the name. Blender builds either "WITH_FFMPEG=yes" or "WITH_FFMPEG=no" does this mean that I now have to reinstate a pre_checkin.sh? The old blender-2.49b src rpm contains both the full and sanitized blender tarballs so I really don't understand the logic of it all. 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 1

[opensuse-packaging] Horde and Pear packaging in server:php:applications
by Ralf Lang 30 Oct '10

30 Oct '10

Hi list, in the last days I have been busy updating and submitting packages related to Horde php applications and horde pear packages. While Horde had been in mainstream repositories even way before suse became opensuse, nowadays most horde rpms in Buildservice are outdated or wouldn't even build. I think it is time to communicate with you about the best way we can improve the situation, as I am new to openSUSE packaging and don't know all the rules and ways to handle things. My goal for now is to have most or all officially released "stable" horde modules and dependencies as in http://www.horde.org/projects.php in a current state, working for SLE_11, Factory and OpenSUSE 11.3, but preferably also for older supported targets. I would also like to maintain them for the forseeable future and probably bring them to Factory if there is nothing against it. My questions: What to do now? I have just targeted my submit requests for two new packages and several updates/fixes at the server:php:applications repository. While the fixes and updates all have been accepted, the new packages are currently waiting for some review or so I think. I am not sure if I have to do anything about them right now. Whom to contact? I have found out that the php5-pear-role_web package does not build on any current platform. The source archive pearified.com is gone for good. Searching the net, I read that the role_web has been incorporated to php-pear proper and is not needed anymore. I think it is best to drop this package and remove Requires: on it. Who should I ask? Who does kolab? The Kolab Groupware uses horde as its web client. While I don't want to intentionally break compatibility of horde packages with kolab, I am not involved enough to know which kolab patches of old packages are really still required in the newer versions. There is an ongoing upstream effort to make horde just work with kolab without any patches. I would like to communicate with somebody who does the kolab packages about these issues. -- Ralf Lang lang(a)b1-systems.de http://www.b1-systems.de -- 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] creating/applying a patch
by Robert Schweikert 28 Oct '10

28 Oct '10

Hi, Sorry if this arrives twice, mail server issues.... I am creating a new package and I need to create a patch. I followed what I could find here (the steps describing how to use quilt): http://en.opensuse.org/openSUSE:Fixing_bugs The first step failed as there are no packages yet. Thus I didn't quite know what to do and just remained in my "top level directory", i.e. the directory that contains the .spec file and the tarball. I unpacked the tarball and following the steps outlined I managed to get my patch created. Now I have a patches directory with my patch file (qpidc-0.6-fix-xqill-interface-problem.patch) and a file named "series". In my spec file I added: Patch0: %{short_name}-%{version}-fix-xqill-interface-problem.patch and %prep %setup -q -n %srcdir_name-%{version} %patch0 (the %patch0 line is new) Upon build I get: error: Bad source: /usr/src/packages/SOURCES/qpid-cpp-0.6-fix-xqill-interface-problem.patch: No such file or directory That doesn't really surprise me since I have no idea how this is all supposed to work together. Can someone please guide me through this process? 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 2

[opensuse-packaging] how can this error be resolved -> nothing provides perl = 5.10.0 needed by perl-XML-Parser
by doiggl＠velocitynet.com.au 28 Oct '10

28 Oct '10

Hello how can this error be resolved ? - nothing provides perl = 5.10.0 needed by perl-XML-Parser project ->https://build.opensuse.org/package/show?package=pitivi&project=home%3Adoiggl spec -> https://build.opensuse.org/package/view_file?file=pitivi.spec&package=pitiv… Thanks Glenn -- 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] New devel project proposal: storage
by Andreas Jaeger 28 Oct '10

28 Oct '10

I'm currently cleaning up the home:hennevogel:TODO project and discussed with Hannes the following: Create: * storage:fcoe (and move network:fcoe to it) * storage:scsi - for userspace scsi stuff like scsi-eventd * storage:admin: could contain e.g. smartmontools Does the above make sense and should we create these devel projects? 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

6 5

[opensuse-packaging] New package for graphics - openCOLLADA
by Dave Plater 28 Oct '10

28 Oct '10

Hi, I've submitted (sr#51576) openCOLLADA to graphics to enable me to update blender to 2.55. OpenCOLLADA is a set of libraries which enable the exchange of 3D graphics files between 3D applications such as blender, Maya and Max. See http://collada.org/ 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] TeXmacs 1.0.7.7 update error (openSUSE:Factory:Contrib Repo)
by Sascha 'saigkill' Manns 27 Oct '10

27 Oct '10

Hello Mates, i'm try to packaging TeXmacs 1.0.7.7. The build goes near to the End. But before rpmlint comes, the says to me: I: Program returns random data in a function E: TeXmacs no-return-in-nonvoid-function ./Data/Tree/tree_analyze.cpp:269 E: TeXmacs no-return-in-nonvoid-function ./Plugins/Bibtex/bibtex_functions.cpp:659, 566 E: TeXmacs no-return-in-nonvoid-function ./System/Language/packrat_grammar.cpp:234 So i've checked the tree_analyze.cpp and in Line 269 i found a return. So i'm wondering wha it breaks. Has anyone an idea? My actual Build can seen in openSUSE:Factory:Contrib/TeXmacs... -- 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 1

[opensuse-packaging] mozilla-xulrunner192 and system cairo
by Mariusz Fik 27 Oct '10

27 Oct '10

Hi! Since oS 11.3 mozilla-xulrunner192 doesn't use system cairo. Many of us has lcd monitor and use some "patched" cairo packages (subpixel) to get fonts looking good. All gtk/gnome apps use system cairo but Mozilla Firefox _doesn't_. Can We revert this option in mozilla-xulrunner192 spec file? from %define has_system_cairo 0 to %define has_system_cairo 1 -- Pozdrawiam / Best regards, Mariusz Fik, openSUSE Community Member

4 6

[opensuse-packaging] [reminder] openSUSE 11.4 Milestone 3 is next week
by openSUSE Roadmap Reminder 27 Oct '10

27 Oct '10

Hello all, openSUSE 11.4 Milestone 3 will be released next week, on Friday 05 November 2010. Please submit your packages before Friday afternoon (UTC time) to make sure they will get included in this release. Leaf packages submitted during the week-end might also get accepted on Monday. For a quick overview of the openSUSE Roadmap, please see: http://en.opensuse.org/Roadmap Thanks, -- openSUSE Roadmap Reminder -- 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] New Category in the *.desktop File
by Sascha 'saigkill' Manns 26 Oct '10

26 Oct '10

Hello Mates, actually i'm working for the openSUSE medical Distribution, and i have a question. I'd like to group all packaged Applications as "Medical" so that Medical is showed in KDE-Menue. Is it possible to do that? 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] Axis2/C packaging
by Robert Schweikert 25 Oct '10

25 Oct '10

Hi, I am fighting with packaging Axis2/C after getting things built (finally) I am getting a bunch of warnings about non FHS compliance. As I investigated these in more detail I figured out that Axis2/C basically expects to be installed in one given directory, configuration, libraries etc. This is described here: http://ws.apache.org/axis2/c/docs/axis2c_manual.html#repo_folder Based on my understanding of the documentation I cannot take this appare, i.e. put configuration in /etc somewhere, libraries in /usr/lib64 etc. Thus, the question is, where should this, what is being called "repository" the in Axis2C documentation end up, is /usr/share/axis2c the correct place? 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 5

[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

[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