Issue & PR triage
Loading...
Showing 100 of 809 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
rockcraft issue #132 |
Rockcraft wipes working directory | jardon | 1469d | keep open | 84 | 78 | 34 | Maintainers agreed to prevent `organize` rules from wiping the working directory mounted at `/root/project`, but no safeguard or resolving fix is evident and the issue remains open. |
|
rockcraft issue #122 |
`rockcraft pack` uses all available memory | gruyaume | 1478d | keep open | 80 | 31 | 7 | Reported LXD-backed rockcraft pack host memory exhaustion remains unconfirmed; the 2022 0.0.1.dev1 repro used a disputed branch, and maintainers await current version and LXD profile details. |
|
craft-parts issue #1460 |
`organize` with mapping like `{app: app/app}` when `app` is a directory not... | javierdelapuente | 255d | keep open | 75 | 85 | 35 | Bug in `organize` mapping where moving a directory into itself (`app: app/app`) causes silent file deletion or crashes. A fix is being prepared and approved by maintainers. |
|
craft-parts pr #1757 |
perf(state): cache source outdated checks within planning | chris-bainbridge | 24d | keep open | 75 | 40 | 12 | Adds planning-scoped cache for source outdated checks in StateManager, keyed by part and pull-state serial, with defensive report copies. ~96% planning speedup on large SDK. CI failing lint/files and OSV-scanner; one unresolved review comment. |
|
snapcraft (launchpad) issue #1711333 |
snaps must have accompanying source available | ~jr | 3360d | keep open | 74 | 57 | 7 | Maintainer-acknowledged request to persist and publish snap source and build assets for license compliance remains open, with no implementation found. |
|
craft-providers issue #430 |
Improve integration tests | mr-cal | 1105d | keep open | 72 | 68 | 11 | Integration tests remain disk-bound: LXD images consume nearly all GitHub runner storage, and the proposed Spread migration or pytest cleanup/parametrization overhaul is still unresolved. |
|
rockcraft issue #350 |
Support pinning of snap revisions for build-snaps and stage-snaps | shayancanonical | 1157d | keep open | 72 | 76 | 23 | Unresolved feature request to pin exact Snap Store revisions in build-snaps and stage-snaps for reproducible ROCK builds; current syntax accepts only a snap name and channel. |
|
snapcraft (launchpad) issue #1933224 |
Recent changes completely break 32bit snaps | ~ogra | 1955d | keep open | 72 | 76 | 23 | Base-snap library filtering omits armhf runtime libraries from armhf/arm64 snaps, silently producing broken Raspberry Pi releases; maintainers acknowledge the bug, but no fix is recorded. |
|
snapcraft issue #6066 |
Filter libraries included in content snaps | mr-cal | 246d | keep open | 72 | 57 | 7 | Triaged research to prune duplicate libraries from content snaps; extension-specific cleanup remains a workaround while defaults and provider compatibility are unresolved. |
|
rockcraft issue #1351 |
Changing from basefull to baseless silently produces an incomplete rock | lczyk | 62d | keep open | 72 | 83 | 25 | Rebuilding a project after switching `base: ubuntu@26.04` to `base: bare` reuses stale state, silently producing a rock missing ~520 base-provided files; pack exits 0 with no warning. Labeled as a bug, awaiting triage/fix. |
|
rockcraft issue #889 |
uv plugin rewrites non-python shebangs | mr-cal | 519d | keep open | 70 | 80 | 42 | uv plugin rewrites all executable shebangs, corrupting staged package scripts such as dpkg-maintscript-helper; valid bug with clear reproducer, no fix yet. |
|
rockcraft issue #562 |
bug: run umoci in --rootless mode | cjdcordeiro | 905d | keep open | 70 | 80 | 45 | umoci unpack fails for non-root users in destructive mode; extract_to supports --rootless but image service doesn't use it |
|
craft-providers issue #584 |
Catch `FileNotFound` for all `subprocess.run()` calls | mr-cal | 861d | keep open | 70 | 80 | 28 | Enhancement to catch FileNotFoundError from subprocess.run() calls across craft-providers and raise ProviderError for better user-facing error messages. Still open. |
|
snapcraft issue #6509 |
Update patchelf | mr-cal | 9d | keep open | 70 | 80 | 34 | Maintainer proposes updating bundled patchelf from 0.9 to 0.19.2 to fix ELF corruption bugs and improve performance; test plan and results included. |
|
snapcraft issue #6410 |
Bundled patchelf drops PT_NOTE coverage for .note.qt.metadata, making every... | desvaters | 57d | keep open | 70 | 80 | 25 | Vendored patchelf relocates .note.qt.metadata out of PT_NOTE coverage when growing .dynstr, making staged Qt 6 plugins unloadable. Triaged; maintainer confirms patchelf update is needed. |
|
charmcraft issue #2788 |
uv plugin fails on core26: dispatch script uses system Python instead of venv | zyga | 106d | keep open | 68 | 78 | 24 | uv plugin breaks core26 charm builds: craft-parts strips venv python symlinks, dispatch falls back to system Python lacking ops. Acknowledged by lengau, ownership moved into Charmcraft (CHARMCRAFT-714). |
|
craft-providers issue #508 |
LXD Provider requires a local installation of LXD on macOS | jat-canonical | 994d | keep open | 68 | 70 | 10 | Remote-LXD builds remain unavailable on macOS and Windows because provider checks still require a local LXD install, despite acknowledged demand and partial low-level remote support. |
|
snapcraft (launchpad) issue #2041182 |
Desktop extension doesn't update GDK pixbuf module cache when reverting | ~gbeuzeboc | 1099d | keep open | 68 | 86 | 42 | Desktop extensions keep a revision-specific .last_revision while sharing its GDK pixbuf cache, so snap reverts can reuse loaders from another revision and crash; the maintainer-approved move is not implemented. |
|
craft-application issue #1143 |
LifecycleService should turn on part_builld_subdir for future bases (e.g.... | lengau | 99d | keep open | 68 | 70 | 29 | Maintainer-filed change to use Craft Parts' part_build_subdir for Ubuntu 27.04+ builds; valid but blocked on canonical/craft-parts#1652. |
|
craft-parts issue #1015 |
rust plugin does not cross-compile | lengau | 626d | keep open | 68 | 80 | 20 | Rust plugin remains unable to cross-compile and emits host-architecture binaries; target mapping and toolchain setup are identified, but linking and core implementation remain unresolved. |
|
craft-parts issue #786 |
Python plugin. Python is broken in core24 classic snaps if snap is used on... | NucciTheBoss | 834d | keep open | 68 | 87 | 20 | Core24 classic snaps using the Python plugin fail on older Ubuntu LTS hosts because staged Python cannot find its stdlib; Snapcraft 8.3.2's fix proved incomplete, with follow-up in snapcraft#5144. |
|
snapcraft (launchpad) issue #2036424 |
Mantic s390x install fails: grep-status: *** stack smashing detected ***: terminated | ~dbungert | 1137d | keep open | 66 | 72 | 17 | Snapcraft-built Subiquity on Mantic s390x had a missing ELF RPATH, mixing core22's loader with host glibc. Edge core22 worked, but stable core22 still failed on LPAR; the issue remains open. |
|
craft-providers issue #828 |
Allow getting the apt proxy from the user's apt settings | lengau | 408d | keep open | 66 | 78 | 22 | Add support for propagating host APT proxies, including Proxy-Auto-Detect results refreshed during each machine warmup; the enhancement remains open and unimplemented. |
|
craft-parts issue #538 |
Deduplicate files that already exist in base layer | cmatsuoka | 1154d | keep open | 66 | 62 | 15 | Overlay builds still prime copies of files already present in the base layer, increasing image size; the request remains open with only an autogenerated Jira-ticket comment. |
|
snapcraft issue #6491 |
Task: Wokr with LXQT to achieve their theme without integration into... | ScarlettGatelyMoore | 16d | keep open | 65 | 45 | 10 | Discussion about separating LXQt theme support from kf6-core integration to avoid snap crashes; active multi-party discussion ongoing with no resolution yet. |
|
craft-parts issue #1763 |
Ensure proper /proc, /sys and /dev contents in build-slices chroot | tigarmo | 21d | keep open | 65 | 85 | 41 | Build-slices chroot lacks /proc, /sys, and /dev because mountpoints are absent; needs manual directory creation and test verification. Code already creates the dirs via _prepare_build_slices_root, but tests do not yet verify contents. |
|
craft-parts issue #933 |
pulling repository can hang execution indefinitely | dariuszd21 | 686d | keep open | 65 | 80 | 39 | Git sources still allow credential prompts during clone and fetch, so inaccessible private or nonexistent HTTPS repositories can leave pull blocked indefinitely. |
|
rockcraft issue #583 |
support project directory with remounted path | henrymao-zz | 870d | keep open | 65 | 70 | 20 | Bind-mounted paths in project directory are not accessible inside rockcraft's build environment (chroot/container). Issue open 863 days with no maintainer response. |
|
snapcraft-rocks issue #112 |
Provide snapcraft-rocks based on core26 | brunvonlope | 178d | keep open | 65 | 82 | 37 | Requests a core26-based snapcraft-rocks image for CI use; maintainer mr-cal confirms it is on the roadmap (SNAPCRAFT-1387). README still lists only 7_core22/8_core22/8_core24; experimental PR #118 for Snapcraft 9/core26 is unmerged. |
|
snapcraft (launchpad) issue #1882535 |
[focal/core20][python3.7+] staging conflicts when multiple python parts have... | ~dmitriis | 2334d | keep open | 65 | 65 | 11 | Overlapping Python dependencies generate nondeterministic bytecode, RECORD, and venv artifacts that block staging; confirmed to affect multiple users, with workarounds but no complete fix. |
|
snapcraft issue #6297 |
Task: kde-neon-6 core26 support | ScarlettGatelyMoore | 133d | keep open | 65 | 75 | 22 | Triaged enhancement task for kde-neon-6 core26 support, actively being worked on by an assigned contributor with recent progress updates. |
|
snapcraft (launchpad) issue #1887096 |
not able to install MAAS from snap on ppc64le | ~jhusakowski | 2303d | keep open | 65 | 85 | 23 | MAAS snap installs segfault on ppc64le in older and stable releases because of libsnapcraft-preload; 3.3/edge installs successfully, but stable-channel resolution remains unconfirmed. |
|
snapcraft issue #5661 |
Snapcraft hangs forever if a GitHub repository doesn't exist | vandah | 454d | keep open | 65 | 90 | 46 | Snapcraft 8.10.2 hangs during part pulls when Git prompts for credentials; maintainers assigned the fix to craft-parts, where the equivalent issue remains open. |
|
imagecraft issue #363 |
Overlay debconf configuration | lengau | 127d | keep open | 65 | 72 | 20 | Triaged enhancement requesting a plugin to apply package debconf selections to image overlays, replacing chroot-based override scripts; it remains open and unimplemented. |
|
rockcraft issue #1261 |
stage-packages with deb packages create /etc/ssl/certs/ca-certificates.crt... | javierdelapuente | 134d | keep open | 65 | 55 | 11 | stage-packages deb pulls a host-generated /etc/ssl/certs/ca-certificates.crt that conflicts with the base/chisel copy, breaking 12-factor extensions on non-bare bases; root cause still under investigation |
|
craft-parts issue #777 |
Reduce the scope of the public API | lengau | 839d | keep open | 65 | 55 | 5 | Planned API cleanup remains open: internal modules are not consistently underscored, and eight __all__ declarations show the public surface is still being narrowed. |
|
snapcraft (launchpad) issue #2012503 |
wrong arch of stage packages | ~ondrak | 1317d | keep open | 64 | 88 | 27 | Confirmed cross-build stage packages are fetched for amd64 instead of arm64; no fix or verification is recorded, so the valid cross-compilation bug remains open. |
|
craft-application issue #792 |
http auth token occasionally leaked | setharnold | 490d | keep open | 64 | 88 | 37 | Triaged security bug: short-lived Launchpad HTTP tokens can appear in remote-build git failure logs; current code still streams unsanitized git output. |
|
snapcraft issue #5144 |
error out if core24 classic python snap is created with the non-staged python binary | dariuszd21 | 714d | keep open | 64 | 83 | 37 | Add a Python-plugin guard for classic snaps staged without the python3-minimal symlink; current post_prime only rewrites pyvenv.cfg, leaving the core24 failure mode unresolved. |
|
craft-application issue #914 |
Allow building/packing multiple platforms in parallel. | lengau | 407d | keep open | 64 | 76 | 14 | Triaged enhancement to run builds for multiple planned platforms concurrently; lifecycle commands still process build-plan items sequentially through provider.run_managed. |
|
snapcraft issue #4373 |
library linter fails on foreign archs and can't be disabled for core20 | alexclewontin | 1134d | keep open | 62 | 95 | 38 | Cross-arch core20 builds still lint foreign ELF files, causing missing-loader failures or QEMU segfaults and potentially 20+ GB core dumps; open PR #6249 proposes the fix. |
|
snapcraft issue #5137 |
Fails to login when Kwallet is default keyring | eeickmeyer | 728d | keep open | 62 | 88 | 45 | KWallet-backed Snapcraft login fails with “python-dbus not installed”; maintainers agreed to add python3-dbus as a stage package, but the current snap manifest still omits it. |
|
craft-parts issue #851 |
Removed files from local sources remain in the part | lengau | 769d | keep open | 62 | 88 | 30 | Local-source updates leave deleted files in the part source tree; a maintainer-added regression test confirms the bug remains reproducible. |
|
snapcraft (launchpad) issue #1834207 |
removing parts should clean stage and prime… stages? | ~saviq | 2683d | keep open | 62 | 88 | 31 | Removing a part leaves its prior files in stage/prime and packages them; the report has a clear reproducer and maintainer confirmation, but no fix reference is recorded. |
|
craft-cli issue #385 |
Provide a way to handle multiple simultaneous sources of information | lengau | 407d | keep open | 62 | 61 | 7 | Enhancement to multiplex concurrent information streams for parallel and remote builds; it remains triaged and open, while the API still uses one process-wide Emitter. |
|
craft-providers issue #830 |
Provide an asynchronous API for starting and handling instances | lengau | 407d | keep open | 62 | 40 | 5 | Triaged enhancement to add a non-blocking API for launching/handling provider instances, unblocking parallel multi-base builds. No async code has landed; core design (true async vs non-blocking) still undecided. |
|
charmcraft issue #1900 |
Charm plugin can include unexpected files | lengau | 776d | keep open | 60 | 65 | 14 | Charm plugin packs all non-ignored files from project root, potentially including sensitive files like .envrc in subdirectories. Maintainer proposes filtering or warnings; no fix yet. |
|
snapcraft (launchpad) issue #1995424 |
A way to get debug symbols | ~ilya-fedin | 1458d | keep open | 60 | 45 | 4 | Requests debug-symbol distribution for diagnosing snap crashes; maintainer reports active design work, while uploadable components offer a partial path but are documented as not production ready. |
|
craft-providers issue #531 |
Provide a way to set Multipass CPU and memory | mr-cal | 960d | keep open | 60 | 80 | 34 | Enhancement request to make Multipass CPU and memory configurable instead of hardcoded 2 CPU/2GB, which currently causes slow or failed builds. |
|
imagecraft issue #303 |
Gadget snap extension | lengau | 218d | keep open | 60 | 52 | 9 | Maintainer feature request: an extension that reads a local gadget snap's gadget.yaml and applies its values to imagecraft.yaml, removing duplicated partition config. Blocked on an extensions mechanism that still does not exist in the codebase. |
|
rockcraft issue #901 |
Rockcraft fails to run on FIPS-enabled hosts | cjdcordeiro | 499d | keep open | 60 | 75 | 16 | Rockcraft crashes on FIPS-enabled hosts during startup when urllib3 creates an SSLContext. Valid bug with clear reproducer, confirmed on edge, and workaround references; awaiting fix. |
|
rockcraft issue #1385 |
`plugin: python` uses `$CRAFT_PART_INSTALL` in console-script polyglot... | himax16 | 22d | keep open | 60 | 80 | 24 | Python plugin console scripts embed build-time $CRAFT_PART_INSTALL shebangs; long paths trigger pip polyglot shebang not rewritten, causing runtime exit 127. Triaged, awaiting fix. |
|
craft-parts issue #1364 |
File source handler ignores changes to the file | dmitry-lyfar | 381d | keep open | 60 | 90 | 28 | Confirmed triaged bug: source-type: file lacks pull-step change detection, so touched or edited files are not recopied; dump and Python plugin cases are affected. |
|
snapcraft issue #5684 |
Support a `-f|--file` or `-C|--directory` flag | dilyn-corner | 448d | keep open | 60 | 68 | 13 | Enhancement request for lifecycle flags to select a snapcraft.yaml file or project directory, enabling monorepo and variant builds. Maintainers recognize the need and called it a possible Snapcraft 9 candidate; implementation is not present. |
|
craft-parts pr #1742 |
feat!: replace OsRelease with distro | lengau | 35d | keep open | 59 | 35 | 8 | Replaces the public OsRelease wrapper with distro across chroot checks, platform detection, Poetry, and tests. Open with lint/files and both minimum-dependency jobs failing; eight checks remain pending. |
|
snapcraft (launchpad) issue #1921397 |
Cant build snaps with snapcraft when snap store is down | ~bugraaydogar | 2044d | keep open | 58 | 61 | 12 | Reported Snap Store outages can block builds; maintainers identified refresh, base, extension, injection, and default-provider paths, but no complete fix or current reproducer is documented. |
|
imagecraft issue #258 |
Support using gadget.yaml volumes as a source for imagecraft.yaml volume definitions | alderic-coroir | 286d | keep open | 58 | 55 | 5 | Importing gadget.yaml volume layouts into imagecraft.yaml remains open under design discussion, with gadget/snapd consistency and import semantics unresolved. |
|
charmcraft issue #1042 |
add `charmcraft purge` or `charmcraft cleanall` command to clean all instances | sed-i | 1333d | keep open | 58 | 71 | 13 | Proposed `charmcraft purge` to reclaim disk space by clearing provider caches and build instances; the design is taking shape, but implementation is absent and the former blocker is resolved. |
|
debcraft issue #127 |
Run lintian automatically as a linter | steinbro | 199d | keep open | 58 | 68 | 22 | Triaged feature request to run Lintian on generated .deb files for parity with traditional Debian builds; override installation exists, but package validation is not implemented. |
|
snapcraft (launchpad) issue #1921418 |
wrong architecture of stage-snaps when cross building | ~ondrak | 2044d | keep open | 58 | 87 | 26 | Cross-building downloads host-architecture stage-snaps instead of build-for artifacts; the acknowledged craft-415 bug appears unresolved in current craft-parts. |
|
snapcraft (launchpad) issue #1908061 |
gnome-3-34 extension is missing libraries | ~christianrauch | 2145d | keep open | 58 | 69 | 10 | GNOME 3.34 extension users can get startup crashes when staged HarfBuzz, GLib, or GIO libraries shadow the content snap; the cause and deletion workaround are known, but no general conflict detection fix is identified. |
|
snapcraft (launchpad) issue #1684225 |
retry store actions when it returns a 503 error | ~elopio | 3480d | keep open | 58 | 72 | 20 | Maintainer-requested resilience for temporary Store 503 responses remains open: all store commands should retry with backoff, but current request handling has no 503-specific retry path. |
|
snapcraft (launchpad) issue #1917919 |
snapcraft validate (and possibly other operations requiring gpg passphrases)... | ~roadmr | 2064d | keep open | 58 | 76 | 26 | GPG-backed assertion signing can fail on headless systems because no terminal is passed to gpg-agent; exporting GPG_TTY=$(tty) is reported to fix it |
|
snapcraft (launchpad) issue #1965814 |
snap contains python 3.8 and 3.9 libs | ~kenneth-loafman | 1683d | keep open | 58 | 45 | 8 | A core20 build staged Python 3.8 and 3.9 files; Duplicity added a packaging workaround, but the underlying Snapcraft conflict and potential side effects remain unresolved. |
|
craft-parts issue #817 |
Local file changes are not detected | mr-cal | 801d | keep open | 58 | 74 | 17 | Triaged enhancement to mark dump-plugin pull steps dirty when local sources change, including permission-only edits; a maintainer confirmed in 2026 that it remains unimplemented. |
|
craft-application issue #1119 |
Prepare instance environment in LP builds | cmatsuoka | 115d | keep open | 58 | 59 | 13 | Launchpad builds still need instance proxy configuration equivalent to local policy-enabled builds; the maintainer-authored requirement is triaged and open, with only an internal CRAFT-5255 sync comment. |
|
snapcraft issue #5214 |
Please add revisions of `stage-snaps` to `manifest.yaml` | jhenstridge | 646d | keep open | 58 | 80 | 15 | Record resolved stage-snaps revisions in manifest.yaml for reproducibility and debugging; maintainers recognize the gap and describe a craft-parts state/API approach, but no implementation is present. |
|
craft-archives issue #217 |
craft-archives does not remove managed repositories that are no longer in... | lengau | 344d | keep open | 58 | 69 | 8 | Confirmed bug: repositories installed by craft-archives remain configured after removal from craft.yaml; the repro is clear, but safe package rollback and cleanup behavior remain unresolved. |
|
snapcraft-rocks issue #37 |
Building snaps with `kde-neon` extension is not working | hhromic | 914d | keep open | 58 | 88 | 27 | Snapcraft Rocks images resolve extension sources to the wrong path, breaking kde-neon and GNOME extension builds; the issue remains unresolved. |
|
snapcraft issue #6076 |
Differentiate “need manual review” status in "snapcraft upload" from errors | Jehan | 240d | keep open | 58 | 79 | 22 | `snapcraft upload` needs a documented, distinct outcome for revisions awaiting manual review so CI can distinguish them from failures; maintainer linked open work in #6081. |
|
snapcraft issue #5997 |
Stage package filtering doesn't deal with foreign arch packages (e.g. i386 on amd64) | Saviq | 272d | keep open | 58 | 82 | 15 | Foreign-architecture stage packages such as xz-utils:i386 are mishandled by Snapcraft's name-only base-package filter, duplicating i386 libraries in core24/core26 snaps; maintainers recognize it as a design-first craft-parts bug, still unresolved. |
|
snapcraft (launchpad) issue #1759740 |
Library discovery for rpath patching needs to be deterministic | ~kyrofa | 3137d | keep open | 58 | 90 | 23 | RPATH patching still resolves duplicate SONAMEs with an unsorted os.walk, so Snapcraft may choose a library contrary to ld precedence; this maintainer-authored issue remains open. |
|
snapcraft (launchpad) issue #1918999 |
stage-packages for classic snaps silently drop core20 snap debs | ~racb | 2057d | keep open | 58 | 78 | 25 | Classic snaps using stage-packages lose dependencies already present in core20 because base-package filtering silently omits them; a bare-base workaround exists, but the underlying filtering bug remains open. |
|
snapcraft-rocks issue #109 |
Failed to pull source: unable to determine source type of... | jkbeg | 386d | keep open | 58 | 86 | 35 | The :8_core22 image stages extensions under site-packages while Snapcraft expects them under /usr/share; the mismatch remains open, with a symlink workaround reported. |
|
craft-parts issue #770 |
NPM Plugin: wrong node version is used to build the package | dimaqq | 847d | keep open | 58 | 72 | 19 | NPM node setup is skipped when override-build replaces built-in steps, so builds fall back to system Node 12.22.9; a manual-install workaround and future pre-build hook are proposed. |
|
snapcraft (launchpad) issue #1893262 |
pygtk apps fail with gnome-3-34 extension | ~ken-vandine | 2254d | keep open | 58 | 82 | 26 | Python GTK apps using GNOME extensions still fail in core20/core22 because runtime Python module paths remain incompatible; a minimal reproducer is provided despite an earlier PYTHONPATH fix attempt. |
|
craft-parts issue #766 |
The prime step uses the install dir when creating a list of migrateable filesets | mr-cal | 849d | keep open | 58 | 70 | 10 | Prime can fail after stage exclusions because its fileset is computed from install rather than staged content; the proposed fix is blocked by undefined overlay-cleaning semantics. |
|
snapcraft issue #4440 |
snapcraft configure hook fails: segmentation fault | barrettj12 | 1087d | keep open | 58 | 55 | 10 | Snapcraft installation segfaults in the configure hook on an AWS aarch64 runner; the workflow is reproducible, but the requested hook-task logs are still missing. |
|
charmcraft issue #2461 |
uv plugin doesn't cache wheels to LXC host | carlcsaposs-canonical | 384d | keep open | 58 | 84 | 19 | uv with no-binary builds caches inside the LXC guest instead of CRAFT_SHARED_CACHE; the bug remains open and is blocked on craft-providers PR #900. |
|
craft-parts issue #1390 |
Warn on outward relative path sources | bepri | 359d | keep open | 58 | 80 | 27 | Warn when parsed part sources are absolute or resolve above Path.cwd(), since managed builds can misread paths or copy the root; triaged and still open. |
|
craft-cli issue #278 |
Support output formats | mr-cal | 759d | keep open | 58 | 48 | 8 | Maintainer-filed feature request (Aug 2023) for a craft-cli API to render data as tables or machine-readable JSON; still unimplemented, tracked as CRAFT-3513, and blocking snapcraft#5060. |
|
craft-parts issue #1076 |
Give organize access to variables set during the build step #5241 | mr-cal | 556d | keep open | 58 | 67 | 14 | Enhancement to let organize reference variables populated during the build step, enabling paths known only at build time; triaged and still open with no implementation evidence. |
|
craft-parts issue #1174 |
Craft parts should rebuild all parts if the list of partitions changes | mr-cal | 471d | keep open | 58 | 89 | 30 | Partition-list changes are not tracked in lifecycle state, so stale builds can place files in incorrect stage or prime partitions; the bug remains open and triaged. |
|
craft-parts issue #1369 |
Chisel slices always cut for the host architecture | lengau | 380d | keep open | 58 | 76 | 23 | Confirmed bug: Chisel cuts stage and build slices without the target architecture, causing cross-compiles to receive host-architecture payloads. The issue remains open and needs implementation. |
|
craft-providers issue #381 |
Improve integration tests | mr-cal | 1170d | keep open | 58 | 74 | 10 | Integration-test overhaul is partially implemented: weekly macOS fast/slow jobs and pytest timing exist, but base-instance behavior tests and full base/provider coverage remain absent. |
|
snapcraft issue #5485 |
Provide option to filter stage packages | kubiko | 535d | keep open | 58 | 79 | 18 | Enhancement to exclude unwanted dependency packages from stage-packages after base migrations; triaged and maintainer-endorsed, with reproducible core22/core24 examples showing major snap-size growth, but remains unimplemented. |
|
rockcraft issue #683 |
File capabilities (xattrs) are not preserved in final ROCK image layers. | aznashwan | 793d | keep open | 58 | 90 | 17 | Maintainer-acknowledged bug with a complete reproducer: security.capability xattrs on primed files are lost when ROCK image layers are packaged |
|
snapcraft (launchpad) issue #2012504 |
PATH auto extended with stage paths | ~ondrak | 1317d | keep open | 58 | 76 | 25 | Cross-builds can prepend target-architecture staged binaries to a part's build PATH, executing tools such as Python from the wrong architecture. Maintainers acknowledged the defect, which remains open. |
|
fetch-service issue #329 |
Is the support complete for `rock` images? (potentially new inspector required) | Vyom-Yadav | 641d | keep open | 58 | 74 | 14 | Rockcraft's Ubuntu OCI base remains unsupported: gzip layer blobs are rejected as unknown; a maintainer says an OCI inspector is planned. |
|
craft-parts issue #1001 |
npm plugin fails in the presence of `base-files` | tigarmo | 636d | keep open | 57 | 76 | 14 | Cross-part staging rejects directory-vs-symlink collisions such as npm's bin/lib and base-files' usrmerge links; the valid repro remains unresolved and affects more than the npm plugin. |
|
charmcraft issue #2211 |
Kubernetes Resource Requests in charmcraft.yaml | alexdlukens | 602d | keep open | 57 | 43 | 4 | Valid feature request for charm-declared default container CPU and memory requests; maintainers acknowledge it but say Juju-side support and a cross-project design are required. |
|
fetch-service issue #653 |
Force upstream cache revalidation for mutable repository metadata | lengau | 35d | keep open | 57 | 70 | 19 | Maintainer-filed: stale proxy-cached apt InRelease can predate a newly published Packages.gz, triggering validatePackagesFile checksum failures (HTTP 403). Proposed fix: inject Cache-Control: max-age=0, must-revalidate on upstream metadata requests; approach still under discussion. |
|
craft-providers issue #880 |
Support LXD backend on non-Linux hosts | lengau | 318d | keep open | 57 | 64 | 12 | Maintainer-authored enhancement to use the LXD provider on non-Linux hosts through a configured remote or VM. Remote arguments exist, but availability checks still require local LXD. |
|
craft-parts issue #751 |
Silent failure on certain store issues | lengau | 874d | keep open | 56 | 92 | 37 | Transient snap-store HTTP 500s exhaust five retries in get_store_snap_info and return None, silently skipping required build-snaps; the triaged bug remains in current code. |
|
imagecraft issue #300 |
Race condition when mounting loop devices | lengau | 220d | keep open | 56 | 70 | 13 | Loop partition nodes can disappear during asynchronous udev processing, intermittently breaking mounts. Although the code now waits for initial node creation, the race remains triaged and open. |
|
craft-archives issue #221 |
Support adding private repositories | lengau | 216d | keep open | 56 | 70 | 16 | Triaged enhancement remains open: add auth.conf.d credential support for private APT repositories and PPAs so Imagecraft can build images using them. |
|
snapcraft (launchpad) issue #2025447 |
Incorrect Downloads directory for LDAP user in snapped firefox & chromium | ~dgadomski | 1218d | keep open | 56 | 91 | 38 | LDAP/AD users' Firefox and Chromium snaps download into snap data instead of ~/Downloads; reproduced on 22.04, confirmed for multiple users, and a SNAP_REAL_HOME fix was validated. |
|
snapcraft (launchpad) issue #1889741 |
Snapcraft concurrent build | ~lawrencegripper | 2281d | keep open | 56 | 84 | 23 | Concurrent first-time builds can race during pyxdg cache-path creation; the flaw was still reported on Snapcraft 8.2.12 despite a 2022 upstream fix attempt. |
|
craft-providers issue #454 |
Using default compatibility tag can cause DNS name conflicts | mr-cal | 1084d | keep open | 56 | 89 | 28 | Missing compatibility tags still produce identical LXD base-instance names across projects, causing DNS conflicts and failed launches; the proposed warning and API redesign remain unimplemented. |
|
charmcraft issue #710 |
`charmcraft pack` retains no longer existing files from previous packs | sed-i | 1694d | keep open | 55 | 80 | 18 | Repacking reuses the part's build container, so files deleted from the working tree linger in the resulting charm until `charmcraft clean <part>`. Maintainers confirmed it still reproduces; root cause tracked upstream in craft-parts#851. |