February 2010 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Build fails: Errors in installed desktop file detected
by Richard Bos 15 Feb '10

15 Feb '10

Build fails: Errors in installed desktop file detected, but I can't determine what is wrong. Hope someone can point me to the problem; ERROR: No sufficient Category definition: /usr/src/packages/BUILDROOT/kfritz-0.0.1-2.x86_64//usr/share/applications/kde4/kfritz.desktop ERROR: Icon file not installed: /usr/src/packages/BUILDROOT/kfritz-0.0.1-2.x86_64//usr/share/applications/kde4/kfritz.desktop (internet-telephony) Errors in installed desktop file detected. The desktop has the following contents: $ cat /usr/src/packages/BUILDROOT/kfritz-0.0.1-2.x86_64//usr/share/applications/kde4/kfritz.desktop [Desktop Entry] X-SuSE-translate=true Name=KFritz Exec=kfritz Icon=internet-telephony Type=Application GenericName=Call notificator Comment=Access call history and phone book of your Fritz!Box and get notifications on incoming and outgoing calls. Terminal=false Categories=Qt;KDE;Utility; X-KDE-StartupNotify=true The icon is installed: $ find /usr/share/icons | grep internet-telephony /usr/share/icons/oxygen/32x32/apps/internet-telephony.png .............. /usr/share/icons/oxygen/128x128/apps/internet-telephony.png Why does the rpm check (xdg-menu) complain about the desktop file, what's wrong with it? -- Richard -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 9

[opensuse-packaging] What should own /usr/share/man/zh_CN?
by Cristian Morales Vega 15 Feb '10

15 Feb '10

Hi, I have a package that added a chinese translation of the man page in the latest release. The package fails with ... running 04-check-filelist ... checking filelist mkvtoolnix-3.2.0-1.x86_64.rpm: directories not owned by a package: - /usr/share/man/zh_CN While /usr/share/locale/<lang> dirs are owned by the "filesystem" package /usr/share/man/<lang> aren't, only /usr/share/man/. What's the correct fix? - Make my package own /usr/share/man/zh_CN - Fix 04-check-filelist to not complain about /usr/share/man/<lang> - Fix the filesystem package - Another -- 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] cpanspec
by Stephan Kulow 12 Feb '10

12 Feb '10

Hi, Just a short notice: I packaged cpanspec for devel:languages:perl, so if you need a cpan package, you don't need to start from scratch, but can use that script (originally from fedora, it's patched to follow suse style). In my tests, it worked for ~60% of cpan packages without any modifcations. If you package a new perl package not yet in devel:languages:perl, please do a submit request so we have one repo with uptodate perl modules, not 100. Greetings, Stephan -- 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] how to update perl modules
by Stephan Kulow 12 Feb '10

12 Feb '10

Hi, I'm unable to compile some perl modules as they require newer versions of modules than those shipped with perl distribution. E.g. perl-IO-Compress-Bzip2 in devel:languages:perl/openSUSE_11.2 fails because it requires IO::Compress::Base version 2.015 but perl only ships with 2.008 and the installed perl-IO-Compress-Base-2.015 is not taken ;( Is there a way to overwrite perl modules or is the only way to patch perl package? Greetings, Stephan -- 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] keep .conf files at uninstall
by Andre Hübner 12 Feb '10

12 Feb '10

Hello, is there a way to keep config files unchanged as xxx.conf even when uninstalled with rpm -e ? %config directive in %files section protects my config when updating with newer packages but there seems to be no fitting directive which does the protection at uninstalling. How can this be solved? Thanks, Andre -- 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] rpm %post and %postun react differently then I expected
by Joop Boonen 09 Feb '10

09 Feb '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 All, I have a question. I've packaged a package that uses scripts in %post and %postun When do zypper install <package> and a zypper update and a rpm -i <package> and a rpm -U <package> I exactly see what is described in http://www.stearns.org/rsync-backup/rsync-backup.spec <quote> ##Here are the scripts run at first install, in this order: ##pre - 1 - first install ##post - 1 - first install # ##Here are the scripts run during an upgrade, in this order: ##pre - 2 - upgrade ##post - 2 - upgrade ##preun - 1 - upgrade ##postun - 1 - upgrade # ##Here are the scripts run at final erase, in this order: ##preun - 0 - final erasure ##postun - 0 - final erasure </quote> I don't understand why during an upgrade %postun is run after %post? As I expect %postun = post uninstall? I would expect that during an upgrade the %preun and %postun would be run before %pre and %post Can someone please explain, why it's like this? Regards, Joop. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iF4EAREIAAYFAktx7/8ACgkQajPXGT73MfhkSgEAitESv4COVKH2fJVveaIFLpsP RVQHJcfDX7NnSCr0du0BAORRYyZWygZTWzDIbutW0BALDCGyEKrOUlM2tbld3fdO =Ekoy -----END PGP SIGNATURE----- -- 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] libsensors3 is gone soon
by Jean Delvare 06 Feb '10

06 Feb '10

Hi all, With the migration of net-snmp from libsensors3 (lm-sensors 2.x) to libsensors4 (lm-sensors 3.x), the last known openSUSE Factory package needing libsensors3 is gone. So this is a notice that I will fill a drop request for package libsensors3 really soon now. If you are maintaining any package which depends on libsensors3, please get in touch with me and I'll help you migrate your application to libsensors4. -- Jean Delvare Suse L3 -- 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] Versioning issues
by Guido Berhoerster 04 Feb '10

04 Feb '10

I'm trying to clean up and update the tidy packge, for whatever reason it has the version number 1.0 in openSUSE although tidy uses 0.99.0 internally (it has a VERSION macro set to this and its SONAME is libtidy-0.99.so.0). So the correct version number should be 0.99.0.20100204cvs which is however smaller than 1.0. For the libtidy subpackage this would probably not be a problem since it could be renamed to libtidy0 in order to conform to the packaging policy and quieten rpmlint but that does not solve it for the tidy package. Since using epoch is not allowed, what would be an appropriate solution for this? -- Guido Berhoerster -- 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] h5utils.spec
by Kristian Medri 04 Feb '10

04 Feb '10

How do I get a copy of h5utils.spec mentioned in: http://download.opensuse.org/repositories/science/openSUSE_11.2/ Inline text, an attachment, a url, or a svn repository url would be great. Thanks! -- 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] Upstream not providing a source tarball
by Guido Berhoerster 03 Feb '10

03 Feb '10

What is the procedure when upstream does not provide a source tarball, e.g. when the source is only avaliable through CVS? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 5