## Bug description `source` paths resolve against the directory Snapcraft is invoked from, not the location of `snapcraft.yaml`. Packing from inside `snap/` when the yaml lives there causes the relative paths to resolve incorrectly, and the resulting error names the wrong problem: ``` Failed to pull source: unable to determine source type of 'snap/local'. ``` `source` types are fine here — `snap/local` is a perfectly valid local source. The error should say the path was not found, ideally naming the absolute path that was searched. As written it sends the reader looking for a source-type problem that doesn't exist. See also #5721 for the same message arising from a different cause. ## Steps to reproduce Repository: `juju/juju`, branch `3.6`, commit `cd60f5a`. 1. `git clone --depth 1 --branch 3.6 https://github.com/juju/juju.git && cd juju` 2. `cd snap && snapcraft pack --use-lxd` — fails with the error above 3. `cd .. && snapcraft pack --use-lxd` — succeeds, pulls all parts Identical command and checkout; only the working directory differs. The same layout is used by Snapcraft's own `snap/snapcraft.yaml` and by snapd's `build-aux/snap/snapcraft.yaml`, so this is a reasonably common convention to hit. ## Environment - Snapcraft 9.2.0 (`snapcraft_c`), craft-parts 2.37.2 - LXD build provider, not destructive mode - Ubuntu 26.10, x86_64 ## snapcraft.yaml Relevant parts from `snap/snapcraft.yaml` in the repo above: ```yaml parts: wrappers: plugin: dump source: snap/local jujud: plugin: nil source: . ``` ## Log output ``` Launching managed ubuntu 24.04 instance... Creating instance from base instance Starting instance Initializing lifecycle Failed to pull source: unable to determine source type of 'snap/local'. Failed to run snapcraft in instance Full execution log: '/home/user/.local/state/snapcraft/log/snapcraft-20261015-105925.309457.log' ```