### Bug Description This is a distillation of the `dump` plugin portion of https://github.com/canonical/charmcraft/issues/2969. It goes alongside https://github.com/canonical/craft-parts/issues/1780 If the `dump` plugin fails partway through, it will continue to error until explicitly cleaned, because the `cp` command used doesn't allow overwriting files. A case where this happens could be that the copy results in some sort of transient write error. ### To Reproduce An example test for this: ```python @pytest.mark.xfail( raises=errors.PluginBuildError, reason="https://github.com/canonical/charmcraft/issues/2969", strict=True, ) def test_dump_retry_build_after_failure(new_dir, partitions, install_dir): _parts_yaml = textwrap.dedent( """\ parts: foo: plugin: dump source: src override-build: | craftctl default if [ ! -f "$CRAFT_PART_INSTALL/failed_once" ]; then touch "$CRAFT_PART_INSTALL/failed_once" exit 1 fi """ ) parts = yaml.safe_load(_parts_yaml) source_dir = Path("src") source_dir.mkdir() Path(source_dir / "foobar.txt").touch() lf1 = craft_parts.LifecycleManager( parts, application_name="test_dump", cache_dir=new_dir, partitions=partitions ) with lf1.action_executor() as ctx: ctx.execute(Action("foo", Step.PULL)) with pytest.raises(craft_parts.errors.ScriptletRunError): ctx.execute(Action("foo", Step.BUILD)) lf2 = craft_parts.LifecycleManager( parts, application_name="test_dump", cache_dir=new_dir, partitions=partitions ) with lf2.action_executor() as ctx: ctx.execute(Action("foo", Step.BUILD)) ``` Here we would expect the second build to succeed, and in fact if you switch the plugin to `nil` it does exactly that. ### part yaml ```shell ``` ### Relevant log output ```shell n/a ```