| 2008-02-26 17:15:50 |
David Futcher |
description |
Binary package hint: purrr
Feature Freeze Exception request for purrr 0.8.0. A new upstream version has been released with these changes:
New in 0.8:
- BIG user interaction improvement: no longer can templates that would lead
to clashing filenames be applied. This removes possible data loss scenario
- BIG user interaction improvement: if generated names conflict with already
existing files, rename will be aborted and warning shown. This removes
another possible data loss. Conflicting filenames are marked with appropriate
icon to make spotting them easy
- BIG improvement: renaming is now done in safe way, using temporary files
to ensure nothing is accidentally overwritten
Granting this FFe would allow Bug #195806 to be closed.
**Rationale:
No updates for Purrr have been released since it was first uploaded on the 17th March 2007 (Version 0.5.1, the latest upstream is 0.8.0) in Feisty. The upstream release notes say that the latest version is much safer to use on real data (renaming done in a safer way, clashing file-names impossible, warning when process will overwrite existing data) |
Binary package hint: purrr
Feature Freeze Exception request for purrr 0.8.0. A new upstream version has been released with these changes:
New in 0.8:
- BIG user interaction improvement: no longer can templates that would lead
to clashing filenames be applied. This removes possible data loss scenario
- BIG user interaction improvement: if generated names conflict with already
existing files, rename will be aborted and warning shown. This removes
another possible data loss. Conflicting filenames are marked with appropriate
icon to make spotting them easy
- BIG improvement: renaming is now done in safe way, using temporary files
to ensure nothing is accidentally overwritten
[...]
Granting this FFe would allow Bug #195806 to be closed.
**Rationale:
No updates for Purrr have been released since it was first uploaded on the 17th March 2007 (Version 0.5.1, the latest upstream is 0.8.0) in Feisty. The upstream release notes say that the latest version is much safer to use on real data (renaming done in a safer way, clashing file-names impossible, warning when process will overwrite existing data) |
|
