openSUSE Packaging July 2011

packaging@lists.opensuse.org

40 participants
29 discussions

[opensuse-packaging] Desktop-related macros for scriptlets

by Vincent Untz

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

9 years, 8 months

[opensuse-packaging] Packaging policy for systemd .unit file

by Frederic Crozat

Hi all, as part of systemd integration in openSUSE, Michal suggested we might want to create our own openSUSE policy for packaging systemd .unit file, similar to Fedora policy http://fedoraproject.org/wiki/Packaging:Systemd , moreover the scriptlets part : http://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd However, I'm not sure we should directly add those direct call to systemctl in %post but instead, use some macros, similar to the one we have for sysvinit and / or update those macros to be systemd compliant : %stop_on_removal / %insserv_force_if_yast / %{fillup_only} / % restart_on_update / etc.. Opinions ? -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

9 years, 11 months

[opensuse-packaging] New lightdm user and group

by Guido Berhoerster

Hello, I'd like to ask for a new user and group lightdm to be registered for the LightDM display manager which I intend to submit to Factory. This is necessary to safely run greeters, the following non-standard directory ownership and permissions are needed: /var/run/lightdm lightdm:lightdm 751 /var/log/lightdm lightdm:lightdm 750 /var/lib/lightdm lightdm:lightdm 750 The package is X11:xfce/lightdm. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 years

[opensuse-packaging] python 2.7.1 and calibre

by Filipe Pires Alvarenga Fernandes

Hi, I read some time ago a thread about calibre and python 2.7.1 on opensuse 11.4, unfortunately I deleted that e-mail and missed the thread. So, calibre only need python 2.7.1 for "calibre/src/calibre/ebooks/metadata/sources/cli.py", more specifically a "option parser" problem reported here: http://susepaste.org/31237540 I made a crazy modification here (not a patch, actually a broken program) that consists of eliminating this parser. Since most users do not use the calibre's CLI interface, that should be OK as (ugly) a work around until python 2.7.1 is on opensuse 11.4... ... or some more skilled than I could made a real patch :-) Anyways, I'm running it here and so far I could use all of calibre's GUI features. -Filipe

10 years

[opensuse-packaging] License Question

by Christian

Hi, are pkgs with such a license (http://git.atheme.org/libguess/tree/COPYING) redistributable by build-service ? Thanks in Advance -- 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

10 years

[opensuse-packaging] Killing processes in %post?

by Vincent Untz

Hi, I'm wondering if it's fine to kill processes in %post. Obviously, it should be avoided in general, but I'm faced with a case where it could be appropriate. Here's some bits from the NEWS file in dconf 0.9: ========= There has been an extremely minor incompatible change in the D-Bus API of dconf this release. From a practical standpoint, this change will have no effect. However, it serves as a reminder that the dconf D-Bus API is private and can change from version to version (and will likely change in the future). As such, it is appropriate for those packaging dconf to kill all running instances of dconf ('killall dconf-service') as part of their postinst for the package. It will be dbus-activated again on the next use. ========= How do people feel about this? 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

10 years

[opensuse-packaging] Problems with upgrading a package

by Guido Berhoerster

Hello, I've run into a problem with upgrading a package (bnc#705989). Basically, in the old package /usr/share/doc/packages/xfce-utils/html/el/images is symlinked to /usr/share/doc/packages/xfce-utils/html/C/images and in newer versions that symlink has become a directory itself. In addition, fdupes now hardlinks two of the files from /usr/share/doc/packages/xfce-utils/html/C/images to their corresponding duplicates in /usr/share/doc/packages/xfce-utils/html/el/images which freaks out rpm/cpio: Error: RPM failed: error: unpacking of archive failed on file /usr/share/doc/packages/xfce-utils/html/C/images/xfce-mouse.png;4e1f6273: cpio: link failed - File exists Any ideas how to work around this RPM bug? I suppose I could disable fdupes but I think replacing the symlink with a directory will still cause problems? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 years

[opensuse-packaging] Function returning random data : build failed, ideas for fixes ?

by Bruno Friedmann

Hi, I'm building a mapserver5 version in With the latest version which contain security bug fixes I'm now getting a build failed I: Program returns random data in a function E: mapserver5 no-return-in-nonvoid-function mapogr.cpp:3500 Here the function /************************************************************************/ /* msOGREscapeSQLParam */ /************************************************************************/ char *msOGREscapeSQLParam(layerObj *layer, const char *pszString) { char* pszEscapedStr =NULL; #ifdef USE_OGR if(layer && pszString && strlen(pszString) > 0) { char* pszEscapedOGRStr = CPLEscapeString(pszString, strlen(pszString), CPLES_SQL ); pszEscapedStr = strdup(pszEscapedOGRStr); CPLFree(pszEscapedOGRStr); return pszEscapedStr; } #else /* ------------------------------------------------------------------ * OGR Support not included... * ------------------------------------------------------------------ */ msSetError(MS_MISCERR, "OGR support is not available.", "msOGREscapeSQLParam()"); return NULL; #endif /* USE_OGR */ } How can I ride off of the error ? return pszString (string untouched ?) sorry my c/c++ knowledge are very limited. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 years

[opensuse-packaging] cannot find files for debugsource?

by Ilya Chernykh

I receive the following build error: Processing files: kde3-cpuinfo-debugsource-0.5.2-2.1.x86_64 error: Could not open %files file /usr/src/packages/BUILD/cpuinfo-0.5.2/debugsources.list: No such file or directory This happens only in one project. The same package in another project builds well. Buildlog: https://build.opensuse.org/package/rawlog?arch=x86_64&package=kde3-cpuinfo&… What should I do to avoid the error? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 years

[opensuse-packaging] Almost under GPL

by Ilya Chernykh

Hi! I have downloaded an icon theme and in a file shipped with it it says that "almost all icons in the theme are under GPL license". I wonder, can I build it in openSUSE? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 years

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging July 2011