openSUSE Packaging August 2010

packaging@lists.opensuse.org

34 participants
22 discussions

[opensuse-packaging] Right usage of libexecdir?

by Vincent Untz

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

10 years, 11 months

[opensuse-packaging] Python 2.7 coming to Factory

by Jan Matejek

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

11 years, 6 months

[opensuse-packaging] packaging openoffice extensions oxt

by Denny Beyer

Dear all, does anyone have experience packaging openoffice extensions? - althogh it might not be a bad idea to package openoffice extentions in general for system wide installation and usage - in this case, I only need it for one/two required extensions. Apparently, something like that exists in ubuntu. Telling from what I found the following might be possible: - set requirement to have openoffice installed - take the oxt file and copy it to the machine - take the correct path and install oxt with the opensuse packager on the command line called unopkg - call: /path/to/unopkg add --shared my-extension.oxt oxt files are renamed zip archives, so in another scenario one could just rename the archive, extract it and install the files in the right location ... but I'm not sure how to register the extension. Please share your idea/experience. cheers, Denny -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

11 years, 8 months

[opensuse-packaging] Recommends/Requires for lang files

by Andreas Jaeger

For -lang files that only contain .mo files (translations) and no doc files etc., we should use Recommends and not Requires. This allows users that run an English only system to remove the lang files completely. Please keep this in mind when packaging and change the spec files. I've just gone through a couple of packages and will send submitrequests for these, 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

11 years, 8 months

[opensuse-packaging] set environment variable

by Denny Beyer

Dear all, I need to set an environment variable for package scala in order to make it work properly. How do I achieve that? I checked the openjdk package, but couldn't find out how it's been done (to set JKD_Home=....) Any help will be much appreciated. -Denny -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

11 years, 8 months

[opensuse-packaging] Need Help in KDE:Extra/skrooge

by Sascha 'saigkill' Manns

Hello Mates, i have some trouble with my skrooge Package. Building and installing goes good. If i run it via console i'm getting: skrooge(21668)/kdecore (trader) KServiceTypeTrader::defaultOffers: KServiceTypeTrader: serviceType "SKG GUI/Plugin" not found skrooge(21668)/kdeui (kdelibs): Attempt to use QAction "view_context" with KXMLGUIFactory! Then the Program Starts with Splashscreen and the Main Program. But i just can see the frames, but no other things. The Menue is near empty. Maybe anyone can help me to localize my Error? -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English)

11 years, 8 months

[opensuse-packaging] perl "versioning" and rpm

by Christian

Hi, fell over the problem, that perl usually is using other versioning scheme than rpm is. Example: Version changes of perl-Sub-Uplevel 0.22 Tue Nov 17 05:38:42 EST 2009 0.21_01 Sat Nov 29 15:24:49 EST 2008 0.2002 Thu Sep 11 14:33:09 EDT 2008 0.2001 Tue Sep 9 22:22:40 EDT 2008 0.20 Tue Sep 9 19:23:35 EDT 2008 perl is using a decimalized versioning, where 0.22 > 0.2002, but for rpm it isn't. I think most perl Module Authors do not really know, that they are using a decimalized versioning. IMHO ther perl version should be normalized for packaging. 0.22 would be normalized to 0.220.0 (version->new(0.22)->normal) and 0.2002. would be normalized to 0.200.200. I can adopt cpanspec to do this for newly created packages, but this will only work for perl(version) >= 0.77 (openSuSE >= 1130). And the two scripts (perl.prov, perl.req) delivered with rpm should be adopted too, cause "find-provides". What do you think ? Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

11 years, 8 months

[opensuse-packaging] New rpm macros in 11.4 for GTK+ IM modules, GIO modules, gdk-pixbuf loaders, GSettings schemas

by Vincent Untz

Hi, In 11.4, we're introducing a new set of rpm macros (shipped in the devel packages of gtk2, gtk3, gdk-pixbuf and glib) to make it easy to register GTK+ IM modules, GIO modules, gdk-pixbuf loaders and GSettings schemas. At the moment, not all of this is in Factory, but it will reach Factory in the next few days, so if you're aware of a package that needs to be fixed, be ready to fix it. Note that some of this replaces the old SuSEconfig way of doing things (for gtk2 IM modules and for gdk-pixbuf loaders). I grepped for run-gtk in Factory, and as far as I can tell, at least those packages need to be fixed for this change: ibus imhangul scim-bridge scim tamil-gtk2im uim If help is needed for those packages, please tell me. The macros for GIO modules and GSettings schemas are actually new: nothing was registering GIO modules correctly earlier (as far as I know) and GSettings schemas are new in 11.4. Here's the documentation from the macros.* files shipped in the packages. Don't hesitate to ask if you have any question. ### # # When a package installs a GSettings schemas, it should use all # three macros: # # - %glib2_gsettings_schema_requires in the preamble # - %glib2_gsettings_schema_post in %post # - %glib2_gsettings_schema_postun in %postun # ### # # When a package installs a GIO module, it should use all # three macros: # # - %glib2_gio_module_requires in the preamble # - %glib2_gio_module_post in %post # - %glib2_gio_module_postun in %postun # # Note that %glib2_gio_module_post and %glib2_gio_module_postun can # optionally take the path to the directory where modules live. This # is useful for applications using the GIO module system on their own, # since they will install modules in their own directory. If no # argument is passed, the path for the modules for GIO itself is used. # ### ### # # When a package installs a gdk-pixbuf loader, it should use all # three macros: # # - %gdk_pixbuf_loader_requires in the preamble # - %gdk_pixbuf_loader_post in %post # - %gdk_pixbuf_loader_postun in %postun # ### ### # # When a package installs a GTK+ IM module, it should use all # three macros: # # - %gtk2_immodule_requires in the preamble # - %gtk2_immodule_post in %post # - %gtk2_immodule_postun in %postun # ### ### # # When a package installs a GTK+ IM module, it should use all # three macros: # # - %gtk3_immodule_requires in the preamble # - %gtk3_immodule_post in %post # - %gtk3_immodule_postun in %postun # ### 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

11 years, 8 months

[opensuse-packaging] calibre: python setup.py problem

by Sascha 'saigkill' Manns

Hello Mates, atm i'm building calibre 0.7.15. Sadly i've got: + cd calibre + export 'CFLAGS=-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 - fstack-protector -funwind-tables -fasynchronous-unwind-tables -fno- strict-aliasing' + CFLAGS='-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack- protector -funwind-tables -fasynchronous-unwind-tables -fno-strict- aliasing' + /usr/bin/python setup.py build Traceback (most recent call last): File "setup.py", line 13, in <module> import setup.commands as commands File "/usr/src/packages/BUILD/calibre/setup/commands.py", line 38, in <module> from setup.install import Develop, Install, Sdist File "/usr/src/packages/BUILD/calibre/setup/install.py", line 87 if self.libdir is None: ^ IndentationError: unexpected indent The full Buildlog can be found there: http://bit.ly/8ZNf3B. Has anyone an Idea how to fix it? Project: home:thomas-schraitle:calibre/calibre -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English)

11 years, 8 months

[opensuse-packaging] about ati-fglrxG02

by Christian

Hi, where does the pci_ids-8.xxx{,.new} come from. Just preparing a update to 10.7 aka 8.753 Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

11 years, 9 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging August 2010