Bug #51021
closed
"trash purge" shouldn't stop at the first unremovable image
Added by Ilya Dryomov almost 3 years ago.
Updated almost 3 years ago.
Backport:
nautilus,octopus,pacific
Description
As there is no inherent ordering, there may be multiple removable images past the unremovable image. In addition, removing a clone image may make its parent image removable.
Ensure that a single "trash purge" call cleans up as much as possible. A repeated "trash purge" call with nothing in between should be a no-op.
- Pull request ID set to 41588
- Status changed from In Progress to Fix Under Review
- Backport set to nautilus,octopus,pacific
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #51057: nautilus: "trash purge" shouldn't stop at the first unremovable image added
- Copied to Backport #51058: pacific: "trash purge" shouldn't stop at the first unremovable image added
- Copied to Backport #51059: octopus: "trash purge" shouldn't stop at the first unremovable image added
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Also available in: Atom
PDF