the charm entry point must be executable
Metadata
Current evaluation
Reinstalling the charmcraft snap resolved the false positive executable check error. The issue was closed without code changes after the user confirmed the workaround worked.
Suggested action: —
No scores available.
Issue body
Hi,
Trying to run ```charm build``` locally but for some reason, it's failing:
```
[hloeung@dharkan charm-k8s-content-cache]$ charmcraft build
the charm entry point must be executable: '/home/hloeung/haw/charm-k8s-content-cache/src/charm.py' (full execution logs in /home/hloeung/snap/charmcraft/common/charmcraft-log-1_t20hlj)
```
With the full log:
```
2020-08-31 14:41:26,735 charmcraft.guard DEBUG Starting charmcraft version 0.4.0
2020-08-31 14:41:26,735 charmcraft.main DEBUG Commands loaded: {'version': <charmcraft.commands.version.VersionCommand object at 0x7efd435707f0>, 'build': <charmcraft.commands.build.BuildCommand object at 0x7efd43570850>, 'init': <charmcraft.commands.init.InitCommand object at 0x7efd435708b0>, 'login': <charmcraft.commands.store.LoginCommand object at 0x7efd43570910>, 'logout': <charmcraft.commands.store.LogoutCommand object at 0x7efd43570970>, 'whoami': <charmcraft.commands.store.WhoamiCommand object at 0x7efd435709d0>, 'register': <charmcraft.commands.store.RegisterNameCommand object at 0x7efd43570a30>, 'names': <charmcraft.commands.store.ListNamesCommand object at 0x7efd43570a90>, 'upload': <charmcraft.commands.store.UploadCommand object at 0x7efd43570af0>, 'revisions': <charmcraft.commands.store.ListRevisionsCommand object at 0x7efd43570b50>, 'release': <charmcraft.commands.store.ReleaseCommand object at 0x7efd43570bb0>, 'status': <charmcraft.commands.store.StatusCommand object at 0x7efd43570c10>}
2020-08-31 14:41:26,741 charmcraft.main DEBUG Parsed arguments: Namespace(_command=<charmcraft.commands.build.BuildCommand object at 0x7efd43570850>, entrypoint=None, from=None, quiet_command=False, quiet_global=False, requirement=None, verbose_command=False, verbose_global=False)
2020-08-31 14:41:26,741 charmcraft ERROR the charm entry point must be executable: '/home/hloeung/haw/charm-k8s-content-cache/src/charm.py' (full execution logs in /home/hloeung/snap/charmcraft/common/charmcraft-log-1_t20hlj)
```
src/charm.py is definitely executable:
```
[hloeung@dharkan charm-k8s-content-cache]$ ls -la src/charm.py
-rwxr-xr-x 1 hloeung warthogs 2938 Aug 31 14:17 src/charm.py
[hloeung@dharkan charm-k8s-content-cache]$ src/charm.py
Traceback (most recent call last):
File "src/charm.py", line 5, in <module>
from ops.charm import CharmBase
ModuleNotFoundError: No module named 'ops'
```
Any ideas what's wrong here?
```
$ mount | grep /home
/dev/mapper/nvme0n1p5_crypt on /home type ext4 (rw,nosuid,nodev,relatime)
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Reinstalling the charmcraft snap resolved the false positive executable check error. The issue was closed without code changes after the user confirmed the workaround worked. | |
| qwen/qwen3.6-35b-a3b | — | — | Reinstalling the charmcraft snap resolved the false executable permission error during local builds. The issue was a snap environment glitch, not a code defect, and the report was closed after the user confirmed the fix. | |
| qwen/qwen3.6-35b-a3b | — | — | Reinstalling the charmcraft snap resolved a false positive error where the build command incorrectly reported the entry point as non-executable. The issue stemmed from local snap corruption and was closed as resolved. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | charmcraft incorrectly flagged the entry point as non-executable. Reinstalling the charmcraft snap fixed the problem, indicating a local snap corruption rather than a code defect. The issue was closed as resolved. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | The charmcraft build command falsely reported a non-executable entry point. The author resolved the issue by removing and reinstalling the charmcraft snap. Closed without code changes. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.