openSUSE Packaging February 2009

packaging@lists.opensuse.org

43 participants
33 discussions

[opensuse-packaging] boinctray: rpmlint Warnings
by Sascha 'saigkill' Manns 21 Feb '09

21 Feb '09

Package: boinctray Project: home:saigkill Hello Mates, i've got 4 Warnings from RPMLint: * no-soname * unstripped binary or object. Can anyone review it, please? -- Sincereley yours Sascha Manns openSUSE Marketing Team (Weekly News) openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://lizards.opensuse.org/author/saigkill -- 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] Java Program spec File
by Günther J. Niederwimmer 20 Feb '09

20 Feb '09

Hello, can any please help, to create a correct spec file for this non opensource program ? http://www.buergerkarte.at/de/voraussetzungen/software.html it is a 64 Bit and 32 Bit Linux Software but with problems to install, on openSUSE :(. -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

Re: [opensuse-packaging] Confusion with spec file
by Suman Manjunath 19 Feb '09

19 Feb '09

>>> Andrew Wafaa <awafaa(a)opensuse.org> 02/19/09 11:07 PM >>> > ... testing for serious compiler warnings > (using /usr/lib/build/checks-data/check_gcc_output) > (using //.build.log) > E: bongo-snapshot 64bit-portability-issue > src/libs/cal/bongo-cal-object.c:262 > E: bongo-snapshot 64bit-portability-issue > src/libs/cal/bongo-import-tz.c:41 > E: bongo-snapshot 64bit-portability-issue > src/libs/msgapi/msgcollector.c:435 Check those 3 lines in the build log. They would have compiler warnings. You will need to fix that. Your spec file is not related to this build failure. -Suman -- 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] Desktop categories: mismatch in brp-desktop and rpmlint
by Michal Vyskocil 18 Feb '09

18 Feb '09

Hi, I have a problem with a desktop file. The upstream one has Categories=Application;AudioVideo; but brp-desktop stops the build with Insufficient Category. ERROR: No sufficient Category definition: /var/tmp/playitslowly-1.1.0- build//usr/share/applications/playitslowly.desktop Errors in installed desktop file detected. Please mail stbinner(a)suse.de, if you think this is wrong. error: Bad exit status from /var/tmp/rpm-tmp.79930 (%install) So I changed it according SUSE Packaging Conventions [1] to Categories=Multimedia;Player;AudioVideo;AudioVideoPlayer; but now I got a rpmlint warning: playitslowly.x86_64: W: invalid-desktopfile /usr/share/applications/playitslowly.desktop value "Multimedia;Player;AudioVideo;AudioVideoPlayer;" for key "Categories" in group "Desktop Entry" contains an unregistered value "Multimedia"; values extending the format should start with "X-" /tmp/playitslowly-1.1.0-1.x86_64.rpm.23739/usr/share/applications/playitslowly.desktop: .desktop file is not valid, check with desktop-file-validate So what should be in Categories which will pass brp-desktop and rpmlint checks? And is there any reason why we have a double check of the same thing? [1] http://en.opensuse.org/SUSE_Package_Conventions/Desktop_Menu#9.4.6._Multime… Regards Michal Vyskocil -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 16

[opensuse-packaging] gcc 4.4 preparations
by Stephan Kulow 18 Feb '09

18 Feb '09

Hi, gcc 4.4 is nearing it's release date and so we put it up in openSUSE:Factory/staging to see how hard it hits us. The "porting to 4.4" guide is pretty short, but still it affects a good portion of packages. We have currently 44 failing packages in standard repo (gcc 4.3) and > 200 in staging repo (gcc 4.4). There are quite some follow up problems, e.g. with boost and gcj. Still if you want to see if your packages are affected - or want to help others, look here: http://tinyurl.com/ac8se4 We have no concrete plan to put gcc44 as default compiler into factory, but it might still be a good idea to fix compilation with it as you update packages. The porting guide can be found here: http://gcc.gnu.org/gcc-4.4/porting_to.html Most packages failures I looked at were either about missing includes (stdio or stdint) and broken #if statements. Both are pretty trivial to fix, so everyone is welcome to file submit requests against the devel projects. Please note that both debian and fedora already put effort into gcc 4.4 porting, so there might be patches already floating around upstream to fix these issues. Might not hurt to use google ;) Of course as plans to make gcc 4.4 the default emerge, you will get more details. Greetings, Stephan -- 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] ln -s to every $USER
by Sascha 'saigkill' Manns 17 Feb '09

17 Feb '09

Hello Mates, i woul'd like to make "ln-s /path/file" to every Users/home. Has anyone an Idea? -- Sincereley yours Sascha Manns openSUSE Marketing Team (Weekly News) openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://lizards.opensuse.org/author/saigkill -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

8 10

[opensuse-packaging] Packager Tag
by Sascha 'saigkill' Manns 16 Feb '09

16 Feb '09

Hello Mates, i've found an Message that irritate me. First time RPMLint says "no Packager Tag". Now i added: Packager: Sascha.Manns <Sascha.Manns(a)directbox.com> and now RPMLint says: hardcoded-packager-tag Sascha. That i'm not understand. Without Packager Tag is false, and with Packager Tag is false,too. Why is it so? -- Sincereley yours Sascha Manns openSUSE Marketing Team (Weekly News) openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://lizards.opensuse.org/author/saigkill -- 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] Error: /usr/lib/debug/.build-id" may only be packaged in the -debuginfo subpackage
by Magnus Boman 14 Feb '09

14 Feb '09

Hello, I'm building a package in one of my projects [1] and it fails [2] if I have debuginfo enabled in that project. The failure only happens for i586, not for x86_64. Is this a bug in my .spec file or in OBS? Any ideas what I can do to fix it? Thanks, Magnus [1] https://build.opensuse.org/package/show?package=DeviceKit-power&project=hom… [2] ... checking filelist DeviceKit-power: "/usr/lib/debug/.build-id" may only be packaged in the -debuginfo subpackage DeviceKit-power: "/usr/lib/debug/.build-id/0c" may only be packaged in the -debuginfo subpackage DeviceKit-power: "/usr/lib/debug/.build-id/0c/687bb71e10f3e3d518987685149ac136abf158" may only be packaged in the -debuginfo subpackage DeviceKit-power: "/usr/lib/debug/.build-id/0c/687bb71e10f3e3d518987685149ac136abf158.debug" may only be packaged in the -debuginfo subpackage DeviceKit-power: "/usr/lib/debug/.build-id/27" may only be packaged in the -debuginfo subpackage DeviceKit-power: "/usr/lib/debug/.build-id/27/afe55ba779c59b4c85eeb47c76a5f9112bf478" may only be packaged in the -debuginfo subpackage DeviceKit-power: "/usr/lib/debug/.build-id/27/afe55ba779c59b4c85eeb47c76a5f9112bf478.debug" may only be packaged in the -debuginfo subpackage DeviceKit-power: "/usr/lib/debug/usr" may only be packaged in the -debuginfo subpackage DeviceKit-power: "/usr/lib/debug/usr/bin" may only be packaged in the -debuginfo subpackage DeviceKit-power: "/usr/lib/debug/usr/bin/devkit-power.debug" may only be packaged in the -debuginfo subpackage DeviceKit-power: "/usr/lib/debug/usr/lib" may only be packaged in the -debuginfo subpackage DeviceKit-power: "/usr/lib/debug/usr/lib/devkit-power-daemon.debug" may only be packaged in the -debuginfo subpackage -- 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] Error: /usr/lib/debug/.build-id" may only be packaged in the -debuginfo subpackage
by Magnus Boman 14 Feb '09

14 Feb '09

1 0

[opensuse-packaging] xsane needs new maintainer
by Johannes Meixner 12 Feb '09

12 Feb '09

Hello, I can no longer maintain the package xsane xsane contains the scanner user frontend program xsane http://www.xsane.org/ "whatdependson -R xsane" results nothing "whatdependson xsane-frontends" results only - beagle-index (gnome-maintainers(a)suse.de) but as far as I know this is no hard build dependency. FYI: "whatdependson" is an internal Suse/Novell tool "whatdependson package" shows build dependencies i.e. for which other packages is the package needed to build the other packages. "whatdependson -R package" shows run-time dependencies i.e. which other packages require the package to be installed so that the other packages work o.k. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging February 2009