openSUSE Packaging October 2010

packaging@lists.opensuse.org

51 participants
45 discussions

[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

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging October 2010