Differences

This shows you the differences between two versions of the page.

--- rpm5 [2012-11-24 17:39] – use spec syntax hiliting glen
+++ rpm5 [2015-01-13 16:01] (current) – [Fixing database problems] glen
@@ Line 1: / Line 1: @@
+====== RPM 5 quick guide ======
+===== General information =====
-====== RPM 5.x quick guide ======
-===== General information =====
 Changes in rpm operation that should interest both users and developers.
+==== Upgrading from rpm4 and/or older BDB or downgrading from BDB 5.3 ====
+Rpm database upgrade/downgrade is done automatically during package installation, so there is need to do anything.\\ //But//, in case that upgrade/downgrade did not happen for some reason, here is the command to do it manually:
-==== Upgrading from rpm4 and/or older BDB ====
+<code>
-Rpm database upgrade is done automatically during package installation, so there is need to do anything.\\ //But//, in case that upgrade did not happen for some reason, here is the command to do it manually:
+/usr/lib/rpm/bin/dbupgrade.sh
+</code>
-<file>/usr/lib/rpm/bin/dbconvert --rebuilddb
-</file>
+Remember to **back up** rpm database before running this script.
 ==== Fixing database problems ====
-You can't just do '''rm -rf /var/lib/rpm/%%__db*%%''' to fix problems anymore, also **--rebuilddb** is largely obsolete in rpm-5.3.x and isn't likely to "fix" anything. Instead:
-<file>cd /var/lib/rpm
+You can't just do ''rm -rf /var/lib/rpm/%%__db*%%'' to fix problems anymore, also **%%--rebuilddb%%** is largely obsolete in rpm 5 and isn't likely to "fix" anything. Instead do:
-dbX.Y_recover -ev
-</file>
+<code>
+cd /var/lib/rpm
+db5.2_recover -ev
+</code>
 ==== Querying database ====
-The semantics of rpm query option **-f** (**--file**) has changed in rpm 5.x; '''rpm -q -f <file-with-path>''' will **not** resolve all symlinks in queried file's path. So the query (assuming ///usr/src/linux// is a symlink to ///usr/src/linux-A.B.C-R//):
-<code>rpm -q -f /usr/src/linux/include/linux/fs.h
+The semantics of rpm query option **-f** (**%%--file%%**) has changed in rpm 5.x; ''rpm -q -f <file-with-path>'' will **not** resolve all symlinks in queried file's path. So the query (assuming ///usr/src/linux// is a symlink to ///usr/src/linux-A.B.C-R//):
+<code>
+rpm -q -f /usr/src/linux/include/linux/fs.h
 </code>
-That returned //kernel-headers-A.B.C-R.arch.rpm// with old rpm, will return nothing with rpm 5.x. You have to do '''readlink -f''' first, or change to symlinked directory and do relative path query.
+That returned //kernel-headers-A.B.C-R.arch.rpm// with old rpm, will return nothing with rpm 5.x. You have to do ''readlink -f'' first, or change to symlinked directory and do relative path query.
+==== poldek error "Too many open files" ====
+You have to remove .poldek-cache directory if, after rpm/poldek ugrade, you see error similiar to the following:
+<code>
+Loading [pndir]th...
+Loading [pndir]th...
+packages read
+Loading [rpmdbcache]/var/lib/rpm...
+rpmdb: /var/lib/rpm/__db.005: Too many open files
+error: db_init:db3.c:1087: dbenv->open(24): Too many open files
+error: cannot open Packages(0) index: Too many open files(24)
+        DB: Berkeley DB 5.2.36: (September 14, 2011)
+error: //var/lib/rpm: open rpm database failed
+Abort
+</code>
 ==== DB_BUFFER_SMALL error messages ====
-You may see errors like this:
+If running rpm built with BDB 5.3 you may see errors like this:
+<code>
+db3.c:1443: dbcursor->pget(-30999): BDB0063 DB_BUFFER_SMALL: User memory too small for return value
+</code>
-<file>db3.c:1443: dbcursor->pget(-30999): BDB0063 DB_BUFFER_SMALL: User memory too small for return value
-</file>
 It appears to be some type of a bug in the BerkleyDB 5.3.x.  In an attempt to workaround the problem, when we encounter this situation we attempt to adjust the size of the mmap buffer until the call works, or we end up trying 10 times.
 If DBI debugging is enabled, additional diagnostics are printed, otherwise a basic retry and success message is added to show that the failure was resolved.
+==== poldek: filesystem marks FHS (cap //) ====
+<code>
+# poldek -u filesystem
+Processing dependencies...
+filesystem-4.0-1.x86_64 obsoleted by filesystem-4.0-26.x86_64
+filesystem-4.0-26.x86_64 marks FHS-2.3-35.x86_64 (cap //)
+error: FHS-2.3-35.x86_64: equal version installed, give up
+</code>
-===== Packaging changes =====
+To fix, upgrade poldek, and invoke ''%%poldek --clean-all%%'', as the stored poldek indexes are invalid.
-Below is a list of changes in build system that should interest PLD developers.
+===== Vserver maintanance =====
+After upgrading rpm on a vserver host you need to convert rpm databases of vservers with external package management (default).
+For this purpose a special option has been added to vrpm wrapper from util-vserver in PLD. Use the following command to convert
+rpm database for a single vserver:
+<code>
+vrpm <vserver> --convertdb
+</code>
+===== Packaging changes =====
+Below is a list of changes in build system that should interest PLD developers.
 ==== Build options ====
@@ Line 57: / Line 93: @@
   * **-Wformat -Werror=format-security** options are added to compiler flags, more information about it can be found on [[http://wiki.mandriva.com/en/Development/Packaging/Problems#format_not_a_string_literal_and_no_format_arguments|Mandriva Wiki]]
   * **Stack Smashing Protector** is also enabled by default, if you really MUST disable SSP then undefine **_ssp_cflags** macro
 ==== Loading additional macros in .spec files ====
@@ Line 63: / Line 98: @@
 With old rpm 4.x several macro files were loaded in .spec files via **#include** directive:
+<code rpmspec>
-<file rpmspec>%include /usr/lib/rpm/macros.perl
+%include /usr/lib/rpm/macros.perl
-</file>
+</code>
 In rpm 5.x those macro files have been moved to ''/usr/lib/rpm/macros.d/'' directory, and must be loaded using %{load:} directive. However the old statement still works, as it contains the same code to load the macros.
+<code rpmspec>
-<file rpmspec>%{load:/usr/lib/rpm/macros.d/perl}
+%{load:/usr/lib/rpm/macros.d/perl}
-</file>
+</code>
 ==== Excluding dependencies ====
-Regexp patterns for '''%%_noauto*%%''' macros changed slightly, and '(' must be escaped now, for example:
+Regexp patterns for ''_noauto*'' macros changed slightly, and '(' must be escaped now, for example:
-<file rpmspec>
+<code rpmspec>
 %define _noautoreq 'perl\\(something::.*\\)'
-</file>
+</code>
 rpm-build-tools [[http://git.pld-linux.org/?p=packages/rpm-build-macros.git;a=commitdiff;h=0a9bb9747529d8f89a74f6db5f317abe1454d8ac|v1.654]] adds handy macros to have same syntax for rpm4/5 .specs:
@@ Line 92: / Line 127: @@
 ==== noarch subpackages ====
-Rpm 5.x supports **noarch** subpackages, a feature that can save space on ftp server and mirrors and ease use of multiarch packages.
+Rpm 5 supports **noarch** subpackages, a feature that can save space on ftp server and mirrors and ease use of multiarch packages.
 To use it within a package, add in the preamble of a subpackage that should be/is architecture independent:
-<file rpmspec>
+<code rpmspec>
 # noarch subpackages only when building with rpm5
 %if "%{_rpmversion}" >= "5"
 BuildArch:  noarch
 %endif
-</file>
+</code>
+==== changes in triggers ====
+in ''rpm-5.4.10-35'' webapp register was [[http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2012-November/023331.html|broken]] due triggers misbehave. here's quick fix for lighttpd:
+<code sh>
+for a in /etc/webapps/*/lighttpd.conf; do a=${a#/etc/webapps/}; a=${a%/*}; webapp register lighttpd $a; done
+</code>
+This problem has been identified and fixed rpm package will be released soon.