May 2011 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Desktop-related macros for scriptlets
by Vincent Untz 20 Nov '11

20 Nov '11

Hi, Something I probably failed to document properly in 11.4 is the new macros that got introduced for desktop-related things (some of them being, arguably, GTK+-only). They were introduced to fix various issues, and move away from the SuSEconfig scripts. With rpm 4.9, we might be able to use another solution. In that case, the macros listed below will just expand to an empty string and do nothing. So it won't harm to use them either. Desktop-related macros ====================== a) Package installs a .desktop file in /usr/share/applications Macros: %desktop_database_post/%desktop_database_postun What it does: calls update-desktop-database to update a cache mapping MIME types to apps handling them. This is needed to make the desktops aware that an app can handle a MIME type. b) Package installs a MIME definition (in /usr/share/mime): Macros: %mime_database_post/%mime_database_postun What it does: calls update-mime-database to update the database containing information about all MIME definitions. c) Package installs an icon in hicolor (/usr/share/icons/hicolor): Macros: %icon_theme_cache_post/%icon_theme_cache_postun What it does: calls gtk-update-icon-cache (if existing) to update the GTK+ icon cache for hicolor, as specified by the spec. This is needed to make the icon visible to GTK+ apps. d) Package installs an icon in another icon theme (let's say "geeko" theme, /usr/share/icons/geeko) Macros: %icon_theme_cache_post geeko / %icon_theme_cache_postun geeko What it does: calls gtk-update-icon-cache (if existing) to update the GTK+ icon cache for geeko. This is needed to make the icon visible to GTK+ apps. e) Package installs a GSettings schema (in /usr/share/glib-2.0/schemas): Macros: %glib2_gsettings_schema_post/%glib2_gsettings_schema_postun %glib2_gsettings_schema_requires (similar to %py_requires) What it does: calls glib-compile-schemas to build the blob containing the data for all schemas. This is needed to have your app not crash :-) f) Package installs a gio module (in /usr/lib/gio/modules): Macros: %glib2_gio_module_post/%glib2_gio_module_postun %glib2_gio_module_requires (similar to %py_requires) What it does: calls gio-querymodules to update a cache listing all gio modules and the extension points they are using. This is needed to make the gio module known to gio. g) Package installs a gdk-pixbuf loader (in /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders): Macros: %gdk_pixbuf_loader_post/%gdk_pixbuf_loader_postun %gdk_pixbuf_loader_requires (similar to %py_requires) What it does: calls gdk-pixbuf-query-loaders to update a cache listing all gdk-pixbuf loaders and their abilities. This is needed to make the gdk-pixbuf loader known to gdk-pixbuf. h) Package installs a GTK+ (2 or 3) IM module (in /usr/lib/gtk-2.0/2.10.0/immodules or /usr/lib/gtk-3.0/3.0.0/immodules): Macros: %gtk2_immodule_post/%gtk2_immodule_postun %gtk2_immodule_requires %gtk3_immodule_post/%gtk3_immodule_postun %gtk3_immodule_requires What it does: calls gtk-query-immodules-2.0/gtk-query-immodules-3.0 to build a cache listing all IM modules and the locale/language they apply to. You obviously need to only call the gtk2/gtk3 version, depending on which version of GTK+ you target. This is needed to make the IM module known to GTK+. i) Package installs a pango module (in /usr/lib/pango/1.6.0/modules): Macros: %pango_module_post/%pango_module_postun %pango_module_requires (similar to %py_requires) What it does: calls pango-querymodules to update a cache listing all pango modules and information about what they handle. This is needed to make the module known to pango. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- 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

5 10

[opensuse-packaging] My rpmlint/brp series continues (Today: I: Statement might be overflowing a buffer in strncat.)
by Dimstar / Dominique Leuenberger 15 Jun '11

15 Jun '11

Hi, As some of you are certainly already aware, I am creating a series of blog posts around rpmlint errors and brp-check errors that can arise in packages. So on the weekend, Thanks to the input of Malcolm Lewis, a new post went online, which addresses this error: I: Statement might be overflowing a buffer in strncat. The b log post with explanation why it happens and how to solve it can be found at http://dominique.leuenberger.net/blog/?p=189 Hope it helps you all out. Dominique PS: The offer still stands of course: whichever brp/lint you struggle with, just send me a message and I will try to come up with a post about it. -- 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] Can packages in the 11.4 standard or update repos build against tumbleweed?
by Dave Plater 03 Jun '11

03 Jun '11

Can packages in 11.4 standard or update repositories build against packages provided in the tumbleweed update repository.? I've filed bnc#696826 about 11.4's lv2core-devel's lv2config being unable to function due to a lack of package python-redland. The LV2 plugin system cannot be used at all if the package can't build against lv2core and slv2, I submitted new packages lv2core, slv2 and an updated redland package that included the python bindings before 11.4's release, lv2core is in the 11.4 distribution but slv2 is still in review, here is it's history : 62079 State:declined By:autobuild When:2011-02-18T16:30:51 submit: multimedia:libs/slv2 -> openSUSE:Factory note: obsoleted by submitreq 62078 From: plater(new) Descr: Removed conflict for libslv2-8 62078 State:review By:coolo When:2011-03-28T16:14:46 submit: multimedia:libs/slv2 -> openSUSE:Factory From: plater(new) -> saschpe(review) Descr: Removed conflict for libslv2-8 60049 State:declined By:autobuild When:2011-02-18T16:30:43 submit: multimedia:libs/slv2 -> openSUSE:Factory From: plater(new) Descr: Add slv2-0.6.6-licencefix.patch to remove file with conflicting GPLv2 statement in the header. See bnc#669117 and slv upstream drobillad #630 59638 State:declined By:autobuild When:2011-02-04T17:25:01 submit: multimedia:libs/slv2 -> openSUSE:Factory From: plater(new) Descr: New package slv2 is a library to make the use of LV2 plugins as simple as possible for applications.slv2 is free software (GPL v2 or later) written in C99 using the Redland RDF toolkit, and is known to work on GNU/Linux and Mac OS X. This package is the other part of the slv2 lv2core needed for openSUSE packages to use the LV2 plugin system and compliments submit request sr#59624 the home url for this package is http://drobilla.net/software/slv2/ apart from the url and licence all of the other relevant information is contained in submit request id 59624 and this is sr#62078 the last request which is still open : Request #62078: submit: multimedia:libs/slv2(r5) -> openSUSE:Factory/slv2 Message: Removed conflict for libslv2-8 State: review 2011-03-28T16:14:46 coolo Comment: run checker Review: new darix None None None Please decide accepted None factory-auto 2011-03-29T16:16:48 coolo Builds for all Factory repos found Output of check script (non-fatal): History: review 2011-03-18T10:39:07 saschpe new 2011-02-18T16:18:50 plater This last request effectively blocks slv from even going into factory. There was a comment made in a reply during one of my many emails pleading for slv2 to be accepted that it was a duplicate of a Packman package and I replied that it's purpose was to enable multimedia applications to build with support for LV2 plugins and openSUSE packages cannot build against Packman packages. I'm busy updating qtractor from 0.7.8 to 0.7.9 the earlier version would have been in 11.4 had slv2 been present and now it seems that version 0.7.9 is also going to be blocked. Reference threads : http://lists.opensuse.org/opensuse-factory/2011-02/msg00678.html http://lists.opensuse.org/opensuse-factory/2011-02/msg00004.html http://lists.opensuse.org/opensuse-factory/2011-01/msg00377.html I originally created the lv2core and slv2 packages when a user requested LV2 plugin support for ardour which isn't in the main distribution but he was happy with the result and this verifies that there isn't anything wrong with the package. Maybe I violated an openSUSE rule inadvertently but if nobody explains what it was I may do it again. I'm passionate about openSUSE multimedia and I feel that it presents an important face of openSUSE. Regards Dave Plater -- 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] Adding useful Provides to cups drivers (with python-cups)
by Vincent Untz 31 May '11

31 May '11

Hi, I just updated python-cups to a new version, and it is now shipping files to automatically add Provides tag to packages that are shipping cups drivers (thanks to the new rpm 4.9). It's matching those files: %__psdriver_path ^(/usr/lib/cups/driver/.*|%{_datadir}/cups/drv/.*\.drv)$ %__psdriver_magic ^PPD file.*$ It'd be cool to have all our packages that are shipping drivers for cups use this. It's just a matter of adding a python-cups BuildRequires. For instance, for gutenprint, this would add Provides like this: postscriptdriver(hp;photosmart_100;) This will enable configuration tools to know which package to install, if one is needed, when configuring a printer. I've submitted the change to gutenprint, so you can take a look at it to if you need to change another package in a similar way (but it's really easy): https://build.opensuse.org/request/show/71723 There are likely other packages than gutenprint that should be changed, and I don't know which ones, so I'd appreciate if others could do this or at least tell me which packages to change. Cheers, 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

5 5

[opensuse-packaging] Dependency generators in rpm-4.9.0 and rpm dependencies
by Michal Vyskocil 31 May '11

31 May '11

Hi all, first of all big thanks to mls for rpm 4.9. I've a question about the dependency generators introduced in rpm 4.9 - I want to reuse the Fedora maven.attr and maven.prov they added into jpackage-utils. It will add the maven styled provides into maven packages, so on the end all maven packages can have cross-distro compatible names. There's a problem I see with their approach. The maven.prov is written in Python, that means you have to handle this as dependency somehow. I thought about few ways, but noone seems to me like a good way 1.) add a Requires: python into jpackage-utils, so you have to have python with every java package, because j-u is needed for every JVM we have 2.) move those files into maven package and let it Require python - this is not much far from the 1.) 3.) add BuildRequires: python into every package have BuildRequires: maven - this seems as the best one, even it is confusing for packagers What's your opinion? Regards Michal Vyskocil

2 2

[opensuse-packaging] Naming conventions for Python and Ruby packages
by Sascha Peilicke 31 May '11

31 May '11

Hi guys, recently we already had some discussion about how to fix our Python (and Ruby) packages. One rule was to (re)name all packages so that they match their upstream counterparts as closely as possible. For Python this would be python-$UPSTREAM_PYPI_NAME and for Ruby it is currently rubygem-$UPSTREAM_GEM_NAME. Sometimes this leads to ugly ducklings like 'python-python-daemon', but that already is the perfect example why we have to name it like that [1]. Darix discovered a similar offender for Ruby [2][3]. Therefore we suggest to enforce this rule for new Factory packages. Furthermore we would have to gradually fix offending packages in devel:languages:ruby:extensions and devel:languages:python (aledr is already quite active fixing the latter). Sometimes we have to break this for characters that can't be part of RPM names (like the dot for older distros). In this case, we may want to replace them with "_". Along these lines, it would be great to also provide the upstream name like Perl packages do nowadays: Provides: python($UPSTREAM_GEM_NAME) Ideally, this should be part of our Python macros. Footnotes: [1] http://lists.opensuse.org/opensuse-packaging/2009-09/msg00148.html [2] http://rubygems.org/gems/libarchive [3] http://rubygems.org/gems/libarchive-ruby -- Mit freundlichen Grüßen, Sascha Peilicke http://saschpe.wordpress.com

4 5

[opensuse-packaging] Directory creation for pid and log files
by Robert Schweikert 30 May '11

30 May '11

Hi, Trying to get OpenNebula into a more usable state. The startup script of the daemon puts pid files into /var/run/one/one.pid and log files into /var/log/one/one.log. This is of course perfetly reasonable, with the exception that the startup fails if /var/run/one and var/log/one do not exists. Question now is should the startup script create the directories if they do not exists or is this a job of the package in %post? Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rschweikert(a)novell.com rschweikert(a)ca.ibm.com 781-464-8147 -- 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] opensuse development
by Frank 29 May '11

29 May '11

Hallo, i've downloaded and install openSuse 11.4. Cause of i want to help develop openSuse, i need a lot of hints. The documentation of development don't help me, cause i'm at the moment a non experience user. I've read, that there was a package for suse development, but the current version i've didn't find. i would like to improve applications or wan't write new stuff. can you give me a easy reading tutorial or a step to step howto. Must i download the development version of suse ... ???? Please help me. Thanks and best regards. Frank >Hallo Freunde, > > ich hab mir jetzt openSuse 11.4 heruntergeladen und installiert. > > Da ich mich an der Entwicklung von openSuse gerne einbringen würde, > bräuchte ich dringend ein paar Tipps. > > Die Dokumentation für Entwickler hilft mir leider nicht weiter. > > Es gab da wohl mal ein Paket für die openSuse Entwicklung, was es wohl > nicht mehr aktuell ist. > > Ich würde gerne Anwendungen erweitern/verbessern und habe auch Ideen > für neue Programme. > > Bitte helft mir, sonst geb ichs auf. > > > Viele Grüße > > Frank > > -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 4

[opensuse-packaging] Mono packages...
by Nelson Marques 29 May '11

29 May '11

Hi all, Gabriel recently asked me if I could maintain the Banshee Project repositories, which I accepted. Now this brings me a few issues... Banshee repository inherits some packages from Mono which seem to be based on what I would call 'fedora' specs and could use some love. Well, I'm available to improve a bit this packages (the ones used for Banshee) and resubmit them to Mono project, and then branch them over to Banshee. The reason why they are all there is because currently (and in the future) Banshee will be served to all supported platforms through those reps, so those mono packages provide the requirements for it. Now, there's two things I've noticed: 1. Mono packages are 'noarch' and install always on /usr/lib (which suggests %libexecdir can be used); 2. Mono packages are placing the .pc file on /usr/share/pkgconfig; 3. Mono packages have sometimes a devel package which only provides the .pc file and no real development files. My questions are quite simple: 1. Can we use a '%define _libdir %{libexecdir}? This would make the packages always install on /usr/lib (or as an alternative, '%define _libdir %{prefix}/lib'); 2. Why would we want to drop the .pc file on /usr/share? If we would use the macro above, shouldn't it also be sane to dump the .pc file on /usr/lib/pkgconfig ? 3. In the cases where we have a devel package only for the .pc file, could we merge it and have a 'Provides: %{name}-devel' ? I really would love to make the best possible for Banshee repositories, and sorting out this mono things would be something really cool. Any help/comments will be appreciated. NM -- 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] perl-Gnome2-Wnck / perl-Gtk2-Uniqueq
by Sascha Manns 29 May '11

29 May '11

Hello Mates, actually i'm wondering whay such packages in devel:languages:perl are not building. The Logs are in http://bit.ly/kEGuXF and http://bit.ly/jbpf4b. It builds for all released Versions but not for Factory. Maybe anyone knows more? cu Sascha -- Sincerely Yours Sascha Manns open-slx Community & Support Agent openSUSE Membership Comitee openSUSE Marketing Team Web: http://saigkill.homelinux.net German Community Portal: http://community.open-slx.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 5

Re: [opensuse-packaging] linker error - need help
by Philipp Thomas 28 May '11

28 May '11

On Sat, 28 May 2011 06:50:53 +0400, Ilya Chernykh <anixxsus(a)gmail.com> wrote: >still fails for older openSUSE releases: You can't have accepted my SR (from psmt) as otherwise you would have -lsqlite in that command line. Philipp -- 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] linker error - need help
by Ilya Chernykh 28 May '11

28 May '11

I have a package that fails at the link stage, reporting undefined references as follows, and the --no-as-needed option does not help :( /bin/sh ../libtool --silent --tag=CXX --mode=link g++ -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -L/opt/kde3/lib64 -L/usr/lib/qt3/lib64 -L/usr/lib64 -Wl,--no-as-needed -Wl,--enable-new-dtags -L../src/fs -Wl,-Bsymbolic-functions -o ktagebuch main.o -lkio library/ui/libktagebuchui.la library/libktagebuch.la -lfilesystem -lkdeui -lkdecore /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_exec' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_column_text' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_bind_blob' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_step' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_open' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_column_bytes' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_column_blob' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_prepare' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_close' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_mprintf' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_errmsg' build log link: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=ktage… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 8

[opensuse-packaging] -devel package name constrained by shlib package name
by Atri 27 May '11

27 May '11

Hi! I am trying to package [1] the scientific visualisation and data plotting software Plplot. The intention is to push it to a devel project and then to Factory by the next Milestone. However, I am facing a few problems with the naming policy to be adhered to for the shared-library and *-devel sub-packages provided by plplot. I have gone through the guidelines for shared library package names [2] and have tried to strictly adhere to it (because I want this package to end up in factory later). However, this has lead to several sub-packages having awful names such as:- 1. libplplotqtd0 : provides the shared library libplplotqtd.so.0 (I have no problem with this name, though Fedora uses the prettier name plplot-qt for this) 2. plplotqtd-devel : -devel package that depends on the libplplotqtd0 shared library alone and thus apparently has to have such a name (otherwise RPMLint complains). If I wanted to name this package as plplot-qt-devel instead, would this be possible, without violating the guidelines? (Fedora uses plplot-qt-devel, and I think that's a better name for this package) Similarly for the sub-package plplottcltk-devel, which depends on the shlib libplplottcltk9.so.9. While I have no problem with the shlib package names themselves (as these packages will invariably be installed as dependencies and not by an user), to name the devel packages in accordance with the shlib package makes the name look awful and difficult for a user to search for the package. I would expect a user to search for the package plplot-qt-devel when he/she wants the qt development files for plplot. If someone could tell me if it possible for the -devel package depending on a single shlib package to have a different name instead of following the shlib package name closely, without getting rpmlint to throw warnings, it would be a big help. Thanks, and bye -- Atri [1] https://build.opensuse.org/package/show?package=plplot&project=home:badshah… [2] http://en.opensuse.org/openSUSE:Shared_library_packaging_policy -- 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] python 2.7.1
by Sascha Manns 27 May '11

27 May '11

Hello Mates, actual we have python 2.7 checked in into the repos. Sadly the new calibre needs python 2.7.1 (atm it isn't compatible with any 3.x version). So i just would like to ask, if anyone can update this package. Have a nice weekend Sascha -- Sincerely Yours Sascha Manns open-slx Community & Support Agent openSUSE Membership Comitee openSUSE Marketing Team Web: http://saigkill.homelinux.net German Community Portal: http://community.open-slx.de -- 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] Preblem building against boost
by Ilya Chernykh 27 May '11

27 May '11

I receive the following error message: /usr/include/boost/filesystem/v2/operations.hpp:534:14: error: 'unnamed_Path' was not declared in this scope I wonder how it happens that the file included with boost has undeclared references? -- 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] What prevents this SR from being accepted?
by Ilya Chernykh 26 May '11

26 May '11

Hi! I want to know what prevents this submit request from being accepted? https://build.opensuse.org/request/show/66899 It has been submitted to 11.4:Uptade:Test already 6 weeks ago and still no response. It fixes this issue: https://bugzilla.novell.com/show_bug.cgi?id=686786 which is very critical for all KDE3 users. It is even more strange that the sr has been accepted to Factory but still is not accepted to 11.4:Update:Testing. As a temporary measure we included the fixed package in our KDE3 repository(and changed the dependencies accordingly) but this is not how the things should be as the package is not KDE3-specific. We received 100%-positive feedback on this fix. So how much we have to wait now? Until 11.5 is out? It seems some other requests in 11.4:Update:Test are waiting even longer, for two months and more. -- 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] Package does not build for 32-bit
by Ilya Chernykh 25 May '11

25 May '11

A package builds well for 64-bit architecture, but fails for 32-bit one with the following output: kallery.cpp:198:64: error: invalid conversion from 'long unsigned int*' to 'size_t*' What should I do to make it build well for both architectures? The package link: https://build.opensuse.org/package/show?package=kallery&project=home%3AAnsu… -- 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] 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] Rpm-4.9.0 is in Factory
by Michael Schroeder 24 May '11

24 May '11

Hi Packagers, I've spent the last week to upgrade rpm from 4.8.0 to 4.9.0. The package was submitted to Factory yesterday and is already checked in. Besides some bug fixes and an update to a newer BerkeleyDB library rpm-4.9.0 contains plugin architecture for dependency generation. In older rpms, the internal dependency generator was pretty much hardcoded in C, so we always used the old external one to generate dependencies. With rpm-4.9.0, the internal generator has become flexible enough so that we can use it. This means for you, that rpm will no longer use the %__find_provides and %__find_requires macros. Some packages redefined those macros to be able to filter the generated dependencies. This will no longer work in rpm-4.9.0. Instead, support for dependency filtering was added to rpm. You can now use %define %__requires_exclude_from ^/foo.*bar to tell rpm to ignore files matching the regexp when generating requires (the $RPM_BUILD_ROOT is already stripped). You can use %define %__requires_exclude libfoo.* to remove a generated dependency. The same is possible for %__provides_ and %__supplements_. As the generator definitions are now pluggable, I'll migrate them from the rpm package into the corresponding packages in the next days, i.e. the mono plugin definition into the mono package. Have fun with rpm-4.9.0, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- 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] branding packages ?
by Nelson Marques 24 May '11

24 May '11

Hi all, I'm currently finishing the packaging of unity-2d and need to a small branding package (so that we have the icon of openSUSE and not the one of Ubuntu). Anyone can point documentation for this, or the best procedures to make this happen? NM -- 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] Why this package dies so early?
by Ilya Chernykh 23 May '11

23 May '11

Why this package dies so early when building for Factory? https://build.opensuse.org/package/show?package=piklab&project=KDE%3AKDE3 It builds well for other releases including openSUSE 11.4 but when building for factory it dies just after spec file parsing starts without any error message: ----------------------------------------------------------------- I have the following modifications for piklab.spec: 12c12 < Release: 5 --- > Release: 10.1 84a85 > %changelog ----------------------------------------------------------------- ----- building piklab.spec (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://build.opensuse.org/KDE:KDE3/openSUSE_Factory/503bc5dc77020451f29ecc7f…' --eval %suse_insert_debug_package /usr/src/packages/SOURCES/piklab.spec [ 149.879976] SysRq : Power Off [ 151.396405] Power down. -- 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] mysql-devel
by Ilya Chernykh 23 May '11

23 May '11

Hi! I have several packages which depend on mysql-devel. But it seems that this package is not available any more in Factory. So my question is was it made intentionally? Is there a compatible replacement? -- 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] rpmlint status update
by Ludwig Nussel 22 May '11

22 May '11

Hi, Heads up and status update from the rpmlint front. rpmlint will soon be updated to version 1.2 in Factory. It brings one check that could turn out to be annoying: 'incorrect-fsf-address' warns about outdated or misspelled fsf addresses in files. That's usually something for upstream to fix. We'll see how many packages it catches. A new SUSE specific check warns about init scripts for runlevel 4. That runlevel is supposed to be admin defined so distro packages should not use it. Just remove the '4' from 'Default-Start'. The /var/run check got accepted upstream as non-ghost-in-var-run (was dir-or-file-in-var-run before). I plan to mark that check fatal in near the future as aaa_base now actually mounts tmpfs on /var/run so anything in there must be created at run time. You need to create files in /var/run at run time and mark them as %ghost in the package. Similarly 'non-ghost-in-var-lock' was introduced as /var/lock may use tmpfs too in the future. Packages should actually not use /var/lock at all. It's supposed to be only used for legacy device lock files (e.g. LCK..ttyS0). The new check 'non-position-independent-executable' is a port of prp-pie which in turn got dropped. All setuid binaries as well as network facing daemons should be compiled as position independent executables to make exploits more difficult. The list of binaries where this applies is manually maintained. So if anything is missing please let us know. Additionally we now have the possibility to make certain checks no longer filterable via package specific rpmlintrc. Initially that will be used for mandatory security checks. The shared library packaging policy is probably the next. If you are hit by this outside of Factory you can still get your package to build by setting the badness to zero¹ cu Ludwig [1] http://en.opensuse.org/openSUSE:Packaging_checks#Disarming_Fatal_Errors -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- 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] RFC: Packaging 3rd party channel pear packages with %php_pear_gen_filelist
by Ralf Lang 22 May '11

22 May '11

I've been trying to convert some of the pear packages in server:php:applications to the handy %php_pear_gen_filelist macro. At first it didn't work because the pear command in the buildroot isn't aware of the 3rd party channel (in my case: Horde). My solution to the problem was to copy the channel registry to the buildroot. %{__mkdir_p} %{buildroot}%{php_peardir}/.channels/ %{__cp} %{php_peardir}/.channels/pear.horde.org.reg \ %{buildroot}%{php_peardir}/.channels/ Full example here: http://www.ralf-lang.de/2011/05/21/howto-packaging-3rd-party-pear-channel- software-with-php_pear_gen_filelist-macro/ Before I begin widespread use of this approach I just want to ask you if there is a better, cleaner or simpler solution. -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- 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] Multiple licenses in one RPM
by Johannes Weberhofer 20 May '11

20 May '11

Hello! I have one PHP application having AGPL license; it uses some BSD and AGPL libraries; can I includes those? how should the license be set in the spec file? The bigger libs I have split off in seperated packages. Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- 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] Need help with rpm 4.9 error.
by Dave Plater 19 May '11

19 May '11

I'm updating rosegarden and have a factory build failure that doesn't make sense, the previous version built ok and the only other change I've made is added source services. home:plater rosegarden and to make it easier : https://build.opensuse.org/package/show?package=rosegarden&project=home%3Ap… The error is : + /usr/lib/rpm/find-debuginfo.sh /usr/src/packages/BUILD/rosegarden-11.06 extracting debug info from /usr/src/packages/BUILDROOT/rosegarden-11.06-70.1.x86_64/usr/bin/rosegarden /usr/lib/rpm/debugedit: canonicalization unexpectedly shrank by one character error: Bad exit status from /var/tmp/rpm-tmp.bBMHcn (%install) I didn't take note of the last build, maybe it was with rpm 4.8 Thanks for any help. 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] Spec-file generator in OBS, or third party software
by Kim Leyendecker 19 May '11

19 May '11

Dear packagers! For some projects (between a little home program like hello world and a full KDE desktop), I need something like a generator for spec-files, so that I don´t need to write them on my own ;) . Does anyone knows about such a magical piece of software, or even better, is there a feature like this on OBS? thanks in advance -- Kim Leyendecker (kimleyendecker(a)hotmail.de) openSUSE Ambassador / openSUSE Wiki Team DE HAVE A LOT OF FUN! http://www.opensuse.org | http://www.suse.de Have you tried SUSE Studio? Need to create a Live CD, an app you want to package and distribute , or create your own linux distro. Give SUSE Studio a try. www.susestudio.com. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 7

[opensuse-packaging] New pkg-config introducing a build loop
by Vincent Untz 17 May '11

17 May '11

Hi, pkg-config 0.26 is out and one of the changes is the removal of an internal copy of the glib code. That means that pkg-config now requires glib to build. However, glib requires pkg-config to build. Hence a fun build loop. Does anyone have any idea how we should deal with this situation? 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

9 11

[opensuse-packaging] boinc-client: bnc#689499
by Sascha Manns 16 May '11

16 May '11

Hello Mates, i've got a bugreport for the boinc-client package: https://bugzilla.novell.com/show_bug.cgi?id=689499. Maybe anyone can help me with this bug? I have searched the whole Packaging Sources, but doesn't found anything and haven't any idea. So it would be great, if anyone can help. Have a nice Rest Weekend. :-) Sascha -- Sincerely Yours Sascha Manns open-slx Community & Support Agent openSUSE Membership Comitee openSUSE Marketing Team Web: http://saigkill.homelinux.net German Community Portal: http://community.open-slx.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 10

[opensuse-packaging] Problems packaging yuicompressor
by Johannes Weberhofer 16 May '11

16 May '11

Dear all, I'm currently packaging yuicompressor, which is licensed under BSD; it includes a library (jargs) licensed under BSD, and another (RHINO) licensed under the MPL; Is it allowed to use "BSD and MPLv1.1" as license? yuicompressor extracts the packages classes and inherits them, while overwriting some of them. So I have to merge the libraries and to create one resulting library. The source package from yahoo contains binary versions of the above mentioned libraries, which are simply unpacked. Is this an allowed process for packaging? Or can I alternatively include the compiled versions (RPMs) of the libraries and unpack them and merge the contained jars to the resulting jar? Thank you for your support, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- 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] Icon not working on KDE for a package...
by Nelson Marques 14 May '11

14 May '11

Dear all, I've packaged a game called Unknown Horizons which installs the desktop file in /usr/share/applications/%{name}.desktop. This file has an icon file entry in the following format: Icon=unknown-horizons Which seems cool to me. The icon is installed on /usr/share/pixmaps/unknown-horizons.svg. Everything works just fine in GNOME, but in KDE the icon for the applications isn't rendered on the menus. Anyone familiar with KDE knows what is happening? Nelson -- 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] Re: debian *.install files ignored?
by Sergey Vlasov 12 May '11

12 May '11

Hello, I have created two packages that share the same source tarball but built with different techniques as described in http://en.opensuse.org/openSUSE:Build_Service_Debian_builds In the first package the "alternative" method is used, tarball + diff + dsc http://bit.ly/mcmODK And in the second package all the files from debian/ directory were renamed accordingly and uploaded separately as source files http://bit.ly/mxCrFh The goal is to create several .deb packages from the same source file. While it works well with the "alternative" method in the second package it creates empty .debs. Does OBS support *.install files? -- Sergey -- 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] How do I go about submitting openCOLLADA--svn839 to 11.4 update?
by Dave Plater 12 May '11

12 May '11

I've finally finished polishing the openCOLLADA collada import/export libraries with a bit of help from Fedora and cmake and it's now in Factory. I can either push it to Packman where an ffmpeg blender-2.57b is destined or tumbleweed to take care of <= 11.3 but it was suggested that I push it as an update to 11.4 due to "undefined-non-weak-symbol"s present in older scons builds. What and how do I do? Suggestions and guidance are welcome. Dave P P.s. I'm also wondering when python3-3.2 is going to factory, this is needed by blender, I have to patch to build with py3.1. I'm busy pleading with the Packman folks to allow me to push it there. Blender and a couple of minor gnome apps are all that use python3, 3.2 is totally backward compatible with 3.1 the blender devs managed to replace pages of 3.1 code with a few lines of 3.2 code so one can understand why they have no wish to use py3.1. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 6

[opensuse-packaging] OBS takes wrong dependency (not mine) for my project
by Grenzlaeufer 10 May '11

10 May '11

Hallo list! I have a strange problem with a dependency when building a package: Package: perl-MIME-Tools Dependency: perl-File-Temp (min. 0.18, installed 0.16, my-version 0.22) Target: CentOS 5 AMD64 The problem occurs when building perl-MIME-Tools: ------- snip ------- t/ticket-11901....................File::Temp version 0.18 required--this is only version 0.16 at /usr/src/redhat/BUILD/MIME-tools-5.502/blib/lib/MIME/Tools.pm line 14. ------- snap ------- I have my own package for "File::Temp"/perl-File-Temp in Version 0.22 which is built in the same project as perl-MIME-Tools. I had expected that my version would have been taken, because prior building it, it was a missing dependency for perl-MIME-Tools. I can also query the package from my CentOS-Test-System ------- snip ------- [root@centtest ~]# yum info perl-file-temp Loaded plugins: fastestmirror, priorities Loading mirror speeds from cached hostfile ... 68 packages excluded due to repository priority protections Available Packages Name : perl-File-Temp Arch : noarch Version : 0.22 Release : 1.el5.rf Size : 46 k Repo : rpmforge Summary : Return name and handle of a temporary file safely URL : http://search.cpan.org/dist/File-Temp/ License : Artistic/GPL Description: Return name and handle of a temporary file safely. [root@centtest ~]# ------- snap ------- It seems that the build environment pulls the dependency from a wrong source, because it is older than what I have built. Could anyone tell me why my version is not used in the build-environment and how to solve the problem? Greetings Grenzlaeufer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 3

[opensuse-packaging] libraries could not be found from package
by Denny Beyer 10 May '11

10 May '11

Dear all, I'm having an issue with some libraries in a program I'm helping to package using obs. The program is called gnuaccounting and you'll find the obs project under Build Service > Projects > home:lumnis > gnuaccounting ( https://build.opensuse.org/package/show?package=gnuaccounting&project=home%… ) It is mainly a java progam, but using some native libraries for viewing documents etc. All the java stuff and pics/icons/doc goes into /usr/share/gnuaccounting. All platform depended libraries (here: libnativeview.so ) go into /usr/lib or /usr/lib64 Because the dev team put the latter ones in the project directory also (now the /usr/share/gnuaccounting directory), this is the tested setup. For packaging and QA checks during rpm build, this is not acceptable and package build breaks with badness error in rpm lint check. Could anybody help pointing me/the developers in the right direction to find a solution to that. Isn't it so, that libraries, when located in /usr/lib should be picked up by programs automatically. What is required, to make that happen (e.g. system variables for path). regards, Denny -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 14

[opensuse-packaging] debian.conffiles not working?
by Schlomo Schapiro 09 May '11

09 May '11

Hi, I am trying to mark some files as configuration files in Debian packages and created a debian.conffiles file. However, the resulting packages ignore this. For an example see home:sschapiro/rear-snapshot Is there another way how to get DEBs to also mark conf files properly? Kind Regards, Schlomo -- 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] what the eqivalent names of these packages in obs
by doiggl＠velocitynet.com.au 09 May '11

09 May '11

Hello. What the eqivalent names of these packages in obs to these ? Thanks Glenn nothing provides elfutils-libelf, nothing provides elfutils-devel, nothing provides bzip2-devel >= 1.0, nothing provides perl >= 2:5.8.0 spec file link https://build.opensuse.org/package/view_file?file=rpm.spec&package=rpm&proj… -- 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] subscribe
by Michal Vyskocil 09 May '11

09 May '11

s -- 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] "library /lib/udev/hid2hci is linked against libraries in /usr or /opt"?
by Stefan Seyfried 07 May '11

07 May '11

Hi, bluez-4.93 got hid2hci back, it was on holiday in the udev sources for some time. Unfortunately, the test build fails: + /usr/lib/rpm/brp-rpath + /usr/lib/rpm/brp-pie + /usr/lib/rpm/brp-rootfs library /lib/udev/hid2hci is linked against libraries in /usr or /opt libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007f77e36e7000) libusb-1.0.so.0 => /usr/lib64/libusb-1.0.so.0 (0x00007f77e2f5d000) Please adjust the paths in your package But the hid2hci from udev is: seife@susi:~> rpm -qf /lib/udev/hid2hci udev-166-7.1.x86_64 seife@susi:~> ldd /lib/udev/hid2hci|grep usr libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007f764b901000) libusb-1.0.so.0 => /usr/lib64/libusb-1.0.so.0 (0x00007f764b17d000) The rpmlintrc from udev in FACTORY looks innocent. Why did it build at all? And how do I get rid of that error? I don't care about "separate /usr" crap. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

8 19

[opensuse-packaging] fixing error: Installed (but unpackaged) file(s) found:
by doiggl＠velocitynet.com.au 04 May '11

04 May '11

Hello How this error be fixed [1] I suspect I'm missing lines in %files section what should the lines look like ? Thanks Glenn Spec file at [2] Full Log at [3] [1] Checking for unpackaged file(s): /usr/lib/rpm/check-files /usr/src/packages/BUILDROOT/CodeAnalyst-2_13_2_0156-15.1.x86_64 error: Installed (but unpackaged) file(s) found: /usr/lib64/libCA.a /usr/lib64/libCAbba.a /usr/lib64/lib_tbp_output.a /usr/lib64/libopdata.a RPM build errors: Installed (but unpackaged) file(s) found: /usr/lib64/libCA.a /usr/lib64/libCAbba.a /usr/lib64/lib_tbp_output.a /usr/lib64/libopdata.a [ 826.145642] SysRq : Power Off [ 827.780449] Power down. [2] spec file https://build.opensuse.org/package/view_file?file=CA-test.spec&package=CA-t… [3] log https://build.opensuse.org/package/rawlog?arch=x86_64&package=CA-test&proje… -- 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] how to I cd to correct location after /bin/tar -xf -
by doiggl＠velocitynet.com.au 04 May '11

04 May '11

Hello How this error be fixed [1] ? Spec file at [2] Full Log at [3] It needs to cd to the correct location #cd CodeAnalyst-2_13_2_0156-Public instead of #cd: CodeAnalyst-2_13_2_0156-Public.tar.gz: No such file or directory Thanks Glenn [1] Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.h2OzIK + umask 022 + cd /usr/src/packages/BUILD + cd /usr/src/packages/BUILD + rm -rf CodeAnalyst-2_13_2_0156-Public.tar.gz + /usr/bin/gzip -dc /usr/src/packages/SOURCES/CodeAnalyst-2_13_2_0156-Public.tar.gz + /bin/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd CodeAnalyst-2_13_2_0156-Public.tar.gz /var/tmp/rpm-tmp.h2OzIK: line 32: cd: CodeAnalyst-2_13_2_0156-Public.tar.gz: No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.h2OzIK (%prep) [2] spec file https://build.opensuse.org/package/view_file?file=CA-test.spec&package=CA-t… [3] log https://build.opensuse.org/package/live_build_log?arch=x86_64&package=CA-te… [4] content of CodeAnalyst-2_13_2_0156-Public/ # ls CodeAnalyst-2_13_2_0156-Public AUTHORS COPYING INSTALL Makefile.am README autogen.sh careport.sh debian m4 mkNda.sh samples CAInstaller.sh ChangeLog INSTALLATION NEWS RELEASENOTES ca_manual_install.sh configure.in doc mkInternal.sh mkPublic.sh src -- 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] Need help: sed scripts
by Nelson Marques 04 May '11

04 May '11

Good people, As some people are aware I'm trying to get Unity going and there's a few itches in which I need some help. I've been paying a lot of attention to the packaging done by Ubuntu and they are currently are using a sed script to change a few values, the file is included on here[1] and it's named "compiz-keybindings.sed". What would be the best way (without making patch) to use it on OBS/RPM spec to change the values? NM -- Nelson Marques /* As cicatrizes lembram-nos de onde estivemos, mas não ditam para onde vamos */ -- 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] enabled openSUSE_Factory in devel projects
by Stephan Kulow 03 May '11

03 May '11

Hi, As factory-auto will reject packages that are build disabled in devel projects, I wrote a little check and found 368 factory packages still (from initial devel project setup) in build disabled. Those I enabled for "openSUSE_Factory". In case this a problem in your project, you should seriously rethink the devel project of the packages. This is not meant to be static forever, if it does not make sense, change it, but for a devel project I see 0 use cases of build disabled against Factory. Greetings, Stephan -- 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] Build failures because of GNOME 3, and how to fix them
by Vincent Untz 03 May '11

03 May '11

Hi all, GNOME 3 should reach Factory soon as it got pushed this morning. Since that's a big change, it will likely have some impact in terms of build failures, and create some new ones in Factory. Here are the common cases that should help you fix those issues. If you hit something else, don't hesitate to ask the GNOME team for help. Common causes for build failures ================================ a) Some devel packages got renamed Because we have both gtk2 and gtk3 versions of some libraries, some devel packages have been renamed. For example, what used to be gtksourceview-devel in 11.4 is now gtksourceview2-devel. Same for libunique-devel (now libunique1-devel), libwnck-devel (now libwnck2-devel), and more. The solution here is to move to pkgconfig() BuildRequires: the devel package renaming won't have an impact anymore. This is available since openSUSE 11.3, if I'm not mistaken. For instance, instead of using BuildRequires: gtksourceview-devel you would use: BuildRequires: pkgconfig(gtksourceview-2.0) gtksourceview-2.0 is the basename (without the .pc extension) of the pkg-config file provided by the library. b) configure fails, complaining about a library that cannot be found It's obviously hard to know what the exact issue is, but it's possible that you were relying on the fact that one of your BuildRequires was requiring a package that should have been in your BuildRequires (a direct dependency of your package). So it was working before, but that was a bit lucky. The solution here is to explicitly list all the build dependencies as BuildRequires, instead of relying on another package to bring them in (unless some well-known cases, like glibc-devel, or the glib2-devel/pkgconfig(glib-2.0) when you have GTK+ as BuildRequires, etc.) c) NetworkManager API changed With the move to NetworkManager 0.9, some API got changed. I'm not aware of any good guideline on how to fix this; I'd advise to check upstream in git/svn if there's a fix for this. Else, ping us. But that shouldn't affect too many packages, hopefully. d) libnotify API changed A few functions were removed, and an argument to notify_notification_new() was removed. The solution for this issue is not too hard. The first thing to do is to check upstream if a fix got committed already. Else, a patch can be easily written. An example can be found at: https://build.opensuse.org/stage/package/view_file?file=tsclient-libnotify0… e) Package tries to build a gnome-panel applet Because of the port to GTK+ 3 and D-Bus, the libpanel-applet API has changed, and some porting is needed. This is not a trivial task, although it's definitely doable. It's unclear to me how many packages outside of GNOME:Apps/GNOME:Factory are affected. Note that it can affect some python apps that need the gnomeapplet module (which isn't built anymore). There are several solutions: + look what upstream did in git/svn, and: - if they removed it, just stop building the applet - if they ported it, take the patch and apply it + if nothing is done, ping me so I know how many packages are affected. I might invest time in writing a compatibility layer if it turns out to be needed. 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

5 6

[opensuse-packaging] RPMLINT warning: W: non-etc-or-var-file-marked-as-conffile /srv/www/htdocs/*
by Ralf Lang 02 May '11

02 May '11

Hi folks, while packaging horde4 I noticed the rpmlint warning horde4.noarch: W: non-etc-or-var-file-marked-as-conffile /srv/www/htdocs/horde4/config/conf.php.dist If config files are allowed to live in /var (where web apps used to live in old times) why are they not allowed in /srv ? -- Ralf Lang Linux Consultant / Developer B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 12

[opensuse-packaging] FTLibrary.h not in ftgl-devel
by Javier Llorente 01 May '11

01 May '11

Hi list-mates, I'm trying to compile OpenCASCADE 6.5.0 and I'm getting ../../../src/OpenGl/OpenGl_FontMgr.cxx:4:23: fatal error: FTLibrary.h: No such file or directory compilation terminated. OpenCASCADE.spec has "BuildRequires: ftgl-devel." I have seen that that package doesn't provide FTLibrary.h. Is it a packaging bug? Thanks, -- Javier Llorente

2 3