# What happened `charmcraft pack` will error out if you try to pack a charm with a `src/charm.py` that does not have execution permission on the file. If you fix the permissions and then `pack` again, it will respond with the same message. You need to `clean` the charmcraft env before packing for this to work as expected. # What did you expect If I change the permissions on a file locally, I expect `charmcraft pack` to either reproduce those changes in my container or error specifically telling me it cannot do that. Instead, the current implementation quietly ignores some differences between my local files and container, leading users to continue debugging things they've already fixed just because it is not transparent whether the fix made it into the container. # Reproduction ```bash git clone https://github.com/canonical/template-operator cd template-operator chmod a-x src/charm.py charmcraft pack # Fails with an error saying the charm file is not executable chmod a+x src/charm.py charmcraft pack # Still fails with an error saying the charm file is not executable charmcraft clean charmcraft pack # Works ``` # Additional comments A mitigation is to use `charmcraft clean` liberally whenever you're not sure if something will propagate to the container, but that is a poor user experience. Cold-start for charmcraft is slow (minutes vs 10's of seconds) and very disruptive to an iterative workflow