December 2011 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] RFC: Fonts Repo and Renaming Questions
by Thomas Schraitle 14 Dec '11

14 Dec '11

Hi, thanks to Darix, we have a M17N:fonts repository now! :) I've copied the first LinuxLibertine font from the M17N repo into M17N:fonts and renamed it according to the packaging guidelines: LinuxLibertine -> linux-libertine-fonts I've looked in our openSUSE Wiki and found a page about how to rename a package[1]. Basically, it's just adding the Provides and Obsolete keywords to the spec file. However, before I proceed further, maybe someone can answer my questions? 1. Can anybody confirm the mentioned URL[1] is still the correct way to do it? 2. Current version of Linux Libertine is 5.1.3. Which one is the correct line and why: a) Obsoletes: LinuxLibertine < 5.1.3 b) Obsoletes: LinuxLibertine < %{version} 3. Is the URL about replacing a package by another[2] an option in regards to fonts? 4. Anything else that should be observed? Thanks! :) ------ [1] http://en.opensuse.org/openSUSE:Package_dependencies#Renaming_a_package [2] http://en.opensuse.org/openSUSE:Package_dependencies#Replace_a_package_by_a… -- Gruß/Regards, Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX Products GmbH (o< Maxfeldstrasse 5 /\\ Documentation Specialist 90409 Nuernberg, Germany _\_v http://www.suse.com http://lizards.opensuse.org/author/thomas-schraitle/ SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 6

[opensuse-packaging] Shutter near by release
by Sascha Manns 13 Dec '11

13 Dec '11

Hello mates, now i have a strange Error. In my tar.bz Source i have inside /share/shutter/resources/icons some content to install. So my way was: 1.) %{__install} -d -m 755 %{buildroot}%{_datadir}/%{name} 2.) %{__cp} -pfr share/%{name}/* %{buildroot}%{_datadir}/%{name} After packaging it looks good. Shutter starts, but he doesn't find a file. Datei �/usr/share/shutter/resources/icons/sel_window_tooltip.svg� konnte nicht ge�ffnet werden: And really if i'm going to that location all content are present. But not the needed sel__windows_tooltip.svg. It is in the Source but i can't find it in the Package. Maybe anyone knows more? Project: X11:Utilities/shutter -- Sincerly yours Sascha Manns Community &Support Agent open-slx GmbH http://www.open-slx.de This mail is written with Balsam Professional 12.1

1 1

[opensuse-packaging] %prep and %setup query
by doiggl＠velocitynet.com.au 13 Dec '11

13 Dec '11

Hello, How can I correct this error[1] The tar file contains [2] Spec file see [3] Thanks Glenn [1] Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.P5nauL + umask 022 + cd /home/abuild/rpmbuild/BUILD + cd /home/abuild/rpmbuild/BUILD + rm -rf cacti-0.8.7i + /usr/bin/gzip -dc /home/abuild/rpmbuild/SOURCES/cacti-0.8.7i-PIA-3.1.tar.gz + /bin/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd cacti-0.8.7i /var/tmp/rpm-tmp.P5nauL: line 32: cd: cacti-0.8.7i: No such file or directory [2] tar file cacti-0.8.7i-PIA-3.1.tar partial list: # tar -tvf cacti-0.8.7i-PIA-3.1.tar | head drwxr-xr-x roman/users 0 2011-12-12 13:14 cacti-0.8.7i-PIA-3.1/ -rw-r--r-- roman/users 10006 2011-12-12 12:56 cacti-0.8.7i-PIA-3.1/graph_templates_inputs.php drwxr-xr-x roman/users 0 2011-12-12 12:56 cacti-0.8.7i-PIA-3.1/cli/ -rw-r--r-- roman/users 5759 2011-12-12 12:56 cacti-0.8.7i-PIA-3.1/cli/poller_data_sources_reapply_names.php -rw-r--r-- roman/users 11403 2011-12-12 12:56 cacti-0.8.7i-PIA-3.1/cli/add_device.php -rw-r--r-- roman/users 5350 2011-12-12 12:56 cacti-0.8.7i-PIA-3.1/cli/poller_graphs_reapply_names.php -rw-r--r-- roman/users 33 2010-12-05 08:11 cacti-0.8.7i-PIA-3.1/cli/.htaccess -rw-r--r-- roman/users 5100 2011-12-12 12:56 cacti-0.8.7i-PIA-3.1/cli/data_template_associate_rra.php -rw-r--r-- roman/users 18738 2011-12-12 12:56 cacti-0.8.7i-PIA-3.1/cli/add_graphs.php -rw-r--r-- roman/users 4461 2011-12-12 12:56 cacti-0.8.7i-PIA-3.1/cli/rebuild_poller_cache.php . . . [3]Spec file location and %prep content: https://build.opensuse.org/package/view_file?file=cacti-PA.spec&package=cac… . %prep %setup -q -n cacti-%{version} %patch0 -p1 #%patch1 -p1 %patch2 -p1 #%patch3 -p1 . -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] Why this .ymp file does not open in Yast?
by Ilya Chernykh 13 Dec '11

13 Dec '11

When trying to open this file in Firefox it suggests gedit instead of Yast: http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_12.1/KDE3-DEFA… But for other .ymp files it correctly suggests Yast. Where could be the problem? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 4

[opensuse-packaging] S3QL Package - can I help?
by Nikolaus Rath 13 Dec '11

13 Dec '11

Hello, I noticed that the S3QL OpenSUSE package at https://build.opensuse.org/package/show?package=s3ql&project=filesystems lags far behind the upstream version and has also failed to build for quite some time. Is there anything I can do (as the upstream developer) to help getting this fixed? I'm not familiar with either OpenSUSE or RPM packaging (long-time Debian user), but I'd be happy to assist in any way I can. Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 10

[opensuse-packaging] What can I do to resolve these items in a RPMLINT report
by doiggl＠velocitynet.com.au 12 Dec '11

12 Dec '11

Hello, What can I do to resolve these items in a RPMLINT report [1] Thanks Glenn [1]https://build.opensuse.org/package/live_build_log?arch=x86_64&package=cac… RPMLINT report: =============== (none): E: badness 10000 exceeds threshold 1000, aborting. cacti.noarch: E: suse-filelist-forbidden (Badness: 10000) /usr/share/cacti/lib/functions.php.orig is not allowed in SUSE Your package installs files or directories in a location that have previously been blacklisted. Please have a look at the particular file and see if the SUSE Packaging Guidelines propose a better place on where to install the file or not install it at all. cacti.noarch: W: non-executable-script /usr/share/cacti/scripts/unix_processes.pl 0644L /usr/bin/perl cacti.noarch: W: non-executable-script /usr/share/cacti/cli/add_data_query.php 0644L /usr/bin/php cacti.noarch: W: non-executable-script /usr/share/cacti/scripts/3com_cable_modem.pl 0644L /usr/bin/perl cacti.noarch: W: non-executable-script /usr/share/cacti/scripts/ping.pl 0644L /usr/bin/perl cacti.noarch: W: non-executable-script /usr/share/cacti/cli/data_template_associate_rra.php 0644L /usr/bin/php cacti.noarch: W: non-executable-script /usr/share/cacti/cli/add_graphs.php 0644L /usr/bin/php cacti.noarch: W: non-executable-script /usr/share/cacti/scripts/diskfree.pl 0644L /usr/bin/perl cacti.noarch: W: non-executable-script /usr/share/cacti/scripts/loadavg.pl 0644L /usr/bin/perl cacti.noarch: W: non-executable-script /usr/share/cacti/scripts/unix_users.pl 0644L /usr/bin/perl cacti.noarch: W: non-executable-script /usr/share/cacti/scripts/diskfree.sh 0644L /bin/sh cacti.noarch: W: non-executable-script /usr/share/cacti/cli/analyze_database.php 0644L /usr/bin/php cacti.noarch: W: non-executable-script /usr/share/cacti/scripts/weatherbug.pl 0644L /usr/bin/perl cacti.noarch: W: non-executable-script /usr/share/cacti/cli/add_graph_template.php 0644L /usr/bin/php cacti.noarch: W: non-executable-script /usr/share/cacti/cli/add_perms.php 0644L /usr/bin/php cacti.noarch: W: non-executable-script /usr/share/cacti/scripts/loadavg_multi.pl 0644L /usr/bin/perl cacti.noarch: W: non-executable-script /usr/share/cacti/cli/add_device.php 0644L /usr/bin/php cacti.noarch: W: non-executable-script /usr/share/cacti/scripts/webhits.pl 0644L /usr/bin/perl cacti.noarch: W: non-executable-script /usr/share/cacti/scripts/linux_memory.pl 0644L /usr/bin/perl cacti.noarch: W: non-executable-script /usr/share/cacti/cli/add_tree.php 0644L /usr/bin/php cacti.noarch: W: non-executable-script /usr/share/cacti/scripts/query_unix_partitions.pl 0644L /usr/bin/perl cacti.noarch: W: non-executable-script /usr/share/cacti/scripts/unix_tcp_connections.pl 0644L /usr/bin/perl This text file contains a shebang or is located in a path dedicated for executables, but lacks the executable bits and cannot thus be executed. If the file is meant to be an executable script, add the executable bits, otherwise remove the shebang or move the file elsewhere. cacti.noarch: W: non-etc-or-var-file-marked-as-conffile /usr/share/cacti/include/config.php A file not in /etc or /var is marked as being a configuration file. Please put your conf files in /etc or /var. cacti.src:93: W: macro-in-comment %{prefix} There is a unescaped macro after a shell style comment in the specfile. Macros are expanded everywhere, so check if it can cause a problem in this case and escape the macro with another leading % if appropriate. cacti.noarch: W: incorrect-fsf-address /usr/share/doc/packages/cacti/LICENSE The Free Software Foundation address in this file seems to be outdated or misspelled. Ask upstream to update the address, or if this is a license file, possibly the entire file with a new copy available from the FSF. cacti.noarch: W: htaccess-file /usr/share/cacti/cli/.htaccess cacti.noarch: W: htaccess-file /usr/share/cacti/rra/.htaccess You have individual apache configuration .htaccess file(s) in your package. Replace them by a central configuration file in /etc/, according to the web application packaging policy for your distribution. cacti.noarch: W: files-duplicate /usr/share/cacti/cli/.htaccess /usr/share/cacti/rra/.htaccess cacti.noarch: W: backup-file-in-package /usr/share/cacti/lib/functions.php.orig You have a file whose name looks like one for backup files, usually created by an editor or resulting from applying unclean (fuzzy, or ones with line offsets) patches. 2 packages and 0 specfiles checked; 1 errors, 28 warnings. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] Hi, what if I packaged a non-free package?
by Marguerite Su 12 Dec '11

12 Dec '11

I recently make a package libspotify in my home repo. Depending on it and my another package projectM, I successfully packaged the real full version of Clementine with every feature ON. I want to submit my Clementine, but if so I have to submit libspotify first. So my question is: 1. What License should I use? I know if I just write "Commercial" it will be surely rejected by SUSE team. 2. Which repo should I submit it to? devel:openSUSE:Nonfree? Here's my package: https://build.opensuse.org/package/show?package=libspotify&project=home%3AM… Here's spotify's Term of Use license: http://developer.spotify.com/en/libspotify/terms-of-use-non-us/ And another quesion is, in my package, it seems static libraries are everywhere, So I can't use *-devel-static mentioned in WIKI, I just use "Provides: libspotify10-static = %{version}" in specfile, Is it acceptable? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] Appliance does not build in susestudio
by Ilya Chernykh 11 Dec '11

11 Dec '11

Hi! I am trying to build an appliance in Suse Studio. First two builds went well but then the build started to take more than 4 hour after which it simply disappears without even an error message. I do not remember what I did and I found no possibility to revert the changes :-( -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] Enhancement packaging policy / gobject introspection bindings
by Dimstar / Dominique Leuenberger 10 Dec '11

10 Dec '11

Hi Packagers and maintainers, As many of you are surely already aware, a bunch of libraries bring with them gobject-introspection based bindings to other languages (*.typelib and *.gir files in your packages). So far we packaged the *.typelib together with the shared library, which seemed logical at first, but is 'slightly' wrong. An example: A shared library can change its soname without the need of the binding being changed (ABI change, but API stayed compatible for example). So the binding would update the .typelib file, pointing to the new soname based library. Now, having the .typelib in the shared library package actually causes a conflict on file-level if two library version would need to be installed (for whatever reason). So the suggestion is to do the same as Debian does (slightly changed) and split the .typelib in their own sub-packages. Our proposal is to name those sub-packages in this form: typelib-<typeversion>-<gi-namespace>-<version> (all dots to be replaced with _) typelib: literal: identifier to group them all together and have them easy findable typeversion: the gi-repository is installed in a versioned directory (currently %{_libdir}/gi-repository-1.0) which indicates this can change. Files will conflict as long as they are in the same version only, so we 'split' this on a packaging level. gi-namespace: The namespace of the binding package. This is the name of the typelib file. without the 'version' part version: the version of the binding. An example: clutter installs the file(s) %{_libdir}/gi-repository-1.0/Clutter-1.0.typelib, so this is to be split in a package called: typelib-1_0-Clutter-1_0 (properly capitalized) As clutter installs a bunch of more typelib files, the same rule as with the libs is to be applied: are they kept in sync with their version? If so, they can go in the same package. Otherwise they need to be split in further packages. As the .typelib files themselves also have dependencies (to either other .typelib files and/or to an actual shared library) I wrote a dep-scanner for those yesterday that will add dependencies as needed. This will make sure that all works smoothly together. What does everybody think about this? Is this the way to go forward? Best regards, Dominique / DimStar -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 4

[opensuse-packaging] Permisson denied in %{_docdir}?
by Sascha Manns 09 Dec '11

09 Dec '11

Hello mates, i'm just asking about a little thing in my shutter package. I have in my %install # create a Folder in docdir and move all relevant content to it %{__install} -d -m 644 %{buildroot}%{_docdir}/%{name} %{__cp} -pfr share/doc/%{name}/* %{buildroot}%{_docdir}/%{name} %{__cp} %{S:1} %{buildroot}%{_docdir}/%{name} The buildlog says: + /usr/bin/install -d -m 644 /home/abuild/rpmbuild/BUILDROOT/shutter-0.88.1-19.1.i386/usr/share/doc/packages/shutter + /bin/cp -pfr share/doc/shutter/COPYING share/doc/shutter/README /home/abuild/rpmbuild/BUILDROOT/shutter-0.88.1-19.1.i386/usr/share/doc/packages/shutter /bin/cp: cannot stat `/home/abuild/rpmbuild/BUILDROOT/shutter-0.88.1-19.1.i386/usr/share/doc/packages/shutter/COPYING': Permission denied /bin/cp: cannot stat `/home/abuild/rpmbuild/BUILDROOT/shutter-0.88.1-19.1.i386/usr/share/doc/packages/shutter/README': Permission denied Have i misunderstood anything? cu Sascha -- Sincerly yours Sascha Manns Community &Support Agent open-slx GmbH http://www.open-slx.de This mail is written with Balsam Professional 12.1

3 3