Bug 6898 - php-smarty doesn't upgrade
Summary: php-smarty doesn't upgrade
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Oliver Burger
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-29 03:10 CEST by Thomas Spuhler
Modified: 2012-08-06 16:49 CEST (History)
1 user (show)

See Also:
Source RPM: php-smarty
CVE:
Status comment:


Attachments

Description Thomas Spuhler 2012-07-29 03:10:58 CEST
Description of problem:
urpmi gives:
installing php-smarty-3.1.11-1.mga3.noarch.rpm from /var/cache/urpmi/rpms
Preparing...                     #########################################################################################################
      1/1: php-smarty            #########################################################################################################
error: unpacking of archive failed on file /usr/share/php/smarty: cpio: rename failed - Is a directory
error: php-smarty-3.1.11-1.mga3.noarch: install failed
error: php-smarty-3.1.10-1.mga3.noarch: erase skipped
Manuel Hiebel 2012-07-30 11:36:16 CEST

Assignee: bugsquad => oliver.bgr

Comment 1 Oliver Burger 2012-07-30 12:06:39 CEST
It does work, when installing it fresh.
Must be related to the change in naming (capital letter and a symlink for compatibility).
I'm not sure if this could be handled by adding a Conflicts to older smarty versions...
Comment 2 Jani Välimaa 2012-07-30 21:55:38 CEST
How about removing the old dir in %pre if it exists?

Something like:

%pre
if [ -d %{_datadir}/php/smarty ]; then
  rm -rf %{_datadir}/php/smarty
fi

CC: (none) => jani.valimaa

Comment 3 Thomas Spuhler 2012-08-05 00:37:01 CEST
Ca you please take at shot at fixing this. It's very annoying if smarty is installed.
Comment 4 Oliver Burger 2012-08-06 16:49:12 CEST
Fixed for smarty and smarty2.

The old dir is now removed in %pre.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.