Description of problem: Creating backup with full path as parameter leads to full paths in log (which may cause trouble when things are moved around). Version-Release number of selected component: spacewalk-dobby-1.9.22-17.el5sat How reproducible: always/deterministic Steps to Reproduce: 1. mkdir /tmp/backup; chmod a+w /tmp/backup # or whatever to make it writable... 2. db-control backup /tmp/backup 3. observe /tmp/backup/backup-log.dat, backuplog.coldfiles.fileentry.to Actual results: file contains absolute paths Expected results: file contains paths relative to backup dir
fixed in spacewalk master, commit: f32040f8d9d4f9cfcdf3919f0e1b588aa53aa5f3
Satellite 5.6 has been released. This bug was tracked under the release. This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly before release). Moving to CLOSED CURRENT_RELEASE. Text from Upgrade Erratum follows: Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1395.html