From: Jørn A. <Jor...@nt...> - 2008-10-05 18:55:59
|
The libpng rpm's are ugly at the best. The %files section of the spec file reads: %files ... /usr/lib/ /usr/bin/ %files devel ... /usr/include/ So, the rpm attempts to take control over the bos.rte /usr/lib, /usr/bin and /usr/include directories. (!) Fortunately, it attempts an rm on the plain directory path if removing or updating the rpm, and does not appear to remove any contents: [snip from rpm -vv -Uhv] ... D: file: /usr/include action: remove cannot remove /usr/include - directory not empty ... D: file: /usr/lib action: remove cannot remove /usr/lib - directory not empty D: file: /usr/bin/libpng12-config action: remove D: file: /usr/bin/libpng-config action: remove D: file: /usr/bin action: remove cannot remove /usr/bin - directory not empty Furthermore, when trying to update the beast, /usr/bin/rpm figures out the release 1.2.8 > 1.2.32 and bails out on update: ... D: installing binary packages package libpng-1.2.8-6 (which is newer than libpng-1.2.32-1) is already installed package libpng-devel-1.2.8-6 (which is newer than libpng-devel-1.2.32-1) is already installed This applies to rpm-3.0.5-43 as well as rpm-3.0.5-44. --joern |