Bug 118403 - RPM rollback silently fails to store backup data if directory is not existing
Summary: RPM rollback silently fails to store backup data if directory is not existing
Status: VERIFIED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: RC 1
Hardware: PC SUSE Other
: P5 - None : Enhancement
Target Milestone: ---
Assignee: Michael Schröder
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-22 14:37 UTC by Friedmund Lassmann
Modified: 2011-05-04 15:01 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Friedmund Lassmann 2005-09-22 14:37:59 UTC 
We've checked that the RPM rollback functionality works with RPM 4.1.1 
(even if http://www.linuxjournal.com/article/7034 suggests RPM >= 4.2)
but there is a little caveat: rpm does not save the old version in the
backup directory if that directory has not been created manually.
If you now run 'rpm --rollback' then the command returns after some time
but did not do anything.

I would expect some error or warning instead!

This is what we did:

erle:/tmp # more /etc/rpm/macros
%_repackage_all_erasures 1
%_unsafe_rollbacks 1059710400
%_repackage_dir /var/spool/repackage

erle:~ # rpm -q mysql
mysql-4.0.21-4.2
erle:~ # you
erle:~ # rpm -q mysql
mysql-4.0.21-4.6
erle:~ # rpm -Uvh --rollback '17:20'
erle:~ # rpm -q mysql
mysql-4.0.21-4.6
Comment 1 Michael Schröder 2005-09-22 15:01:18 UTC 
Yes, that's rpm, lots of subtle bugs and inconsistencies. ;-) 
I changed the severity to "enhancement".
Comment 2 Michael Schröder 2011-05-04 15:01:45 UTC 
In the meantime
- the rollback directory was added to the rpm package
- the rollback code has been removed from rpm by upstream