#361 Issue closed: RPM upgrade pre-check script for older release¶
Labels: bug, fixed / solved / done
gdha opened issue at 2014-01-24 13:24:¶
Sometimes upgrading rear is not quite successful (e.g. rear-1.10 to
rear-1.15) and frankly doesn't work.
Also referring to issue #355 where old traces of rear screwed up a
successful run.
Perhaps, we need to foresee a pre-install section to clean up the
/usr/share/rear part?
schlomo commented at 2014-01-24 14:12:¶
We should not just wipe /usr/share/rear because users might have added
their own customizations (as we also advice them to do).
Better to have a %pre that specifically deals with known problems.
On 24 January 2014 14:24, gdha notifications@github.com wrote:
Sometimes upgrading rear is not quite successful (e.g. rear-1.10 to
rear-1.15) and frankly doesn't work.
Also referring to issue #355 https://github.com/rear/rear/issues/355where old traces of rear screwed up a successful run.
Perhaps, we need to foresee a pre-install section to clean up the
/usr/share/rear part?—
Reply to this email directly or view it on GitHubhttps://github.com/rear/rear/issues/361
.
gdha commented at 2014-02-21 16:12:¶
OK, good idea. We should list up what must be removed:
- output/NETFS directory is obsolete
other items?
gdha commented at 2015-02-11 10:15:¶
added to the release notes so we can close this issue
[Export of Github issue for rear/rear.]