Showing 100 of 1910 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
rockcraft issue #617 |
Cannot build multiple ROCKs from the same repo with local source | alnvdl-work | 863d | keep open | 45 | 65 | 15 | Request to restore `rockcraft pack <part-name>` or provide an alternative for building multiple ROCKs from a single local source. Maintainer acknowledged the accidental removal and apologized. |
|
rockcraft pr #1070 |
build(pro): update to use pro guest attachment | tigarmo | 288d | close superseded | 45 | 95 | 21 | Updates craft-providers for LXD Pro guest attachment and adopts uv-based snap builds; stale, unreviewed, and superseded by merged Pro-source work. |
|
charmcraft issue #907 |
`charmcraft pack` does not handle updating a file's execution permissions... | ca-scribner | 1480d | keep open | 45 | 70 | 17 | charmcraft pack keeps stale file permissions in the build container unless `charmcraft clean` is run; root cause is craft-parts' outdated check only comparing mtime. Reproduced upstream, workaround `touch` documented, still open. |
|
charmcraft issue #1990 |
Cannot stage packages with charmcraft | yanksyoon | 721d | keep open | 45 | 55 | 6 | stage-packages in charmcraft.yaml fails with apt method driver error; maintainer says blocked by #1839 and #1844, internal ticket CRAFT-4393 created. |
|
charmcraft issue #1790 |
Set a charm version from `charmcraft.yaml` | lengau | 821d | needs triage | 45 | 30 | 6 | Maintainer request to accept a `version` field in charmcraft.yaml and store it in the built charm. Unimplemented: the model accepts `version` but it is hidden from the schema and unused. Blocked on design of where version lives. |
|
charmcraft issue #244 |
"Tracks" management from charmcraft | facundobatista | 2087d | keep open | 45 | 40 | 8 | Track listing and default-track management remain blocked on Charmhub; create-track support exists, but the requested list and set-default-track commands are absent. |
|
imagecraft issue #311 |
Add support for suite components to mmdebstrap plugin | dilyn-corner | 223d | keep open | 45 | 58 | 13 | Feature request to let the mmdebstrap plugin specify APT suite components (e.g. universe), since only main is bootstrapped; maintainer steinbro noted mmdebstrap's own limitation and suggested a future chisel-style plugin instead. |
|
craft-parts issue #1041 |
Plugin integration tests should test for re-entrancy | mr-cal | 602d | keep open | 45 | 84 | 17 | Triaged enhancement to make plugin integration tests repeat lifecycle runs and verify source changes are not ignored; coverage is still absent. |
|
craft-actions issue #37 |
[Feature request] Support proper caching when packing multi-architecture... | chanchiwai-ray | 608d | needs triage | 45 | 60 | 20 | Feature request to make the pack action's cache key architecture-aware so multi-arch matrix charm builds don't collide/override each other's cache. No maintainer response, no labels, still open. |
|
charmcraft issue #2605 |
Re-enable MacOS tests | lengau | 224d | keep open | 45 | 80 | 16 | macOS CI (macos-smoke-test) is commented out since PR #2606 because Homebrew's libgit2@1.7 disappeared. A maintainer-endorsed proposal to drop brew libgit2 and use pygit2 wheels is in progress via PR #2907. |
|
craft-grammar issue #125 |
`for` grammar: support `else on` and `else for` | lengau | 427d | keep open | 45 | 70 | 16 | Maintainer-filed enhancement to add `else on` and `else for` clauses to the `for` grammar, with example YAML. Still open after plain `else` support landed in commit db3217b (#137); no discussion beyond an autogenerated Jira link. |
|
snapcraft (launchpad) issue #1948464 |
Please add support for advanced grammar in organize | ~xnox | 1840d | keep open | 45 | 80 | 15 | Advanced grammar in organize is requested, including try and on $arch; a maintainer acknowledged core22+ support in craft-parts, but no implementation is recorded. |
|
charmcraft issue #2482 |
`charmcraft test` v4.0.1 lost `--list` support | taurus-forever | 351d | needs triage | 45 | 91 | 26 | charmcraft test --list regressed in 4.0 after PR #2385 replaced the custom Spread wrapper; v4.0.1 rejects the flag. The issue is reproducible but remains unlabeled and untriaged. |
|
charmcraft issue #2687 |
Should support keyrings.alt backend for headless systems | panlinux | 182d | needs triage | 45 | 75 | 22 | Headless systems can't persist charmcraft credentials; setting PYTHON_KEYRING_BACKEND=keyrings.alt.file.EncryptedKeyring fails with ModuleNotFoundError because keyrings.alt isn't bundled in the snap. Requests keyrings.alt support. |
|
rockcraft issue #1198 |
docs: Rockcraft 1.18.0 documentation claims Ubuntu 26.04 support but it... | GregCasbolt | 196d | close resolved | 45 | 80 | 25 | Rockcraft 1.18.0 docs claim ubuntu@26.04 support but build-base ubuntu@26.04 raises KeyError; maintainer clarified devel workaround and stabilization planned. Now resolved in main via PR #1200. |
|
snapcraft (launchpad) issue #1936671 |
Crystal projects don't properly install and build due to "pull" copying lib/... | ~koffeinfrei | 1938d | keep open | 45 | 76 | 16 | Crystal source pulls can include host-built bin/lib artifacts, breaking isolated builds; the issue remains open with a manual cleanup workaround and an unmerged quick-fix PR. |
|
rockcraft pr #938 |
ci: add arm64 snap build | cjdcordeiro | 441d | close stale | 45 | 15 | 5 | Adds an arm64 snap build job to the Snap CI workflow. Arm64 build passes, but several test/lint/scan jobs fail and there has been no review activity in 407 days. |
|
rockcraft issue #892 |
organize with `app: app/app` is not working correctly | javierdelapuente | 524d | needs triage | 45 | 80 | 13 | fastapi-framework extension fails to pack when app code is in app/ directory; generated organize app: app/app causes FileNotFoundError in craft-parts. No maintainer response; root cause tracked in craft-parts#1460. |
|
craft-parts issue #1781 |
`dump` plugin is not idempotent | lengau | 14d | keep open | 45 | 80 | 22 | dump plugin fails to rebuild after partial failure due to cp not overwriting files; maintainer indicates PR #1782 should resolve this by cleaning install directories on non-update runs. |
|
charmcraft pr #2978 |
ci: deduplicate snap packaging across spread and test workflows | LoweRAM | 7d | needs review | 45 | 30 | 8 | Consolidates four CI workflows into a single spread.yaml to deduplicate snap builds, removing redundant workflows and adding path filtering. Has 18 unresolved review comments and 2 failing CI checks. |
|
craft-parts issue #237 |
Allow disabling common-directory removal code in tar source | zyga | 1598d | needs triage | 45 | 68 | 21 | Tar sources still unconditionally strip their detected common top-level directory. The opt-out request remains open, unlabeled, and awaiting maintainer triage; only an automated CRAFT-2968 Jira-sync comment exists. |
|
fetch-service issue #518 |
Merge bundled ACLs with custom ones | lengau | 356d | keep open | 45 | 82 | 24 | Custom acl.yaml still replaces the bundled ACL, forcing users to track every new destination or default change; this triaged enhancement remains open and unimplemented. |
|
craft-parts issue #812 |
maven plugin should install maven build-package | vpa1977 | 812d | keep open | 45 | 75 | 19 | Maven plugin still adds no build packages, so basic Maven parts fail unless users provide Maven/JDK or a maven-deps part; maintainers agreed system Maven should be the default. |
|
fetch-service issue #353 |
Control from a unix domain socket | lengau | 609d | needs triage | 45 | 55 | 15 | Feature request: let the fetch service control API (currently TCP-only, bound to all interfaces via --control-port) also listen on a unix-domain socket when a path is given. Still open, no labels, no discussion. |
|
craft-parts issue #1315 |
Add the ability for plugins to mark their build step as clean or dirty | lengau | 414d | keep open | 45 | 78 | 15 | Triaged enhancement to let plugins classify an otherwise-current build as clean or dirty, enabling UPDATE instead of unconditional SKIP; no implementation is present in the current codebase. |
|
charmcraft pr #2502 |
fix: add missing build metadata in reactive charm artifacts | copilot-swe-agent | 337d | needs review | 45 | 55 | 12 | Adds .build.manifest preservation and charmtool_version to manifest.yaml for reactive charms. Under active review with 4 unresolved comments; most CI checks pending. |
|
craft-parts pr #1581 |
feat: deprecate OsRelease in favor of distro | lengau | 177d | needs review | 45 | 35 | 6 | Deprecates os_utils.OsRelease in favor of the distro PyPI package across 18 files (+179/-132). Approved by 1 reviewer, but 3 unresolved review comments and 19 failing checks; no author activity for 128 days. |
|
imagecraft pr #497 |
fix(bootloader): stage unicode font for grub | lengau | 22d | needs review | 45 | 65 | 25 | Stages the guest's unicode.pf2 font alongside GRUB modules for correct menu glyph rendering. Open, 0 reviewers, most CI passing. |
|
craft-parts pr #1553 |
fix(deb): avoid re-downloading cached stage-packages | gcomneno | 198d | needs review | 45 | 45 | 9 | External-contributor PR adding a narrow monkey-patch of apt.package._file_is_same (binary mode, order-independent hash compare) around candidate.fetch_binary in AptCache.fetch_archives, so warm-cache .deb files count as cache hits. +90/-5, 2 files, no reviewers yet. |
|
starflow issue #28 |
Use osv-scanner to scan `uv.lock` files | lengau | 696d | keep open | 45 | 68 | 17 | Enhancement: make the scan-python reusable workflow scan uv.lock directly with osv-scanner. Blocker google/osv-scanner#1406 reported resolved in a May 2025 comment, but it is still unimplemented — the workflow deletes uv.lock whenever uv-export is enabled. |
|
rockcraft issue #102 |
Allow customization/removal of automatic "go generate" step | tigarmo | 1499d | close resolved | 45 | 98 | 39 | Automatic Go generation is now opt-in: craft-parts added go-generate, which defaults to no generation, and Rockcraft exposes the option in its schema. |
|
charmcraft issue #2507 |
Cannot build charm when base is Questing and build-base is devel | lmlg | 335d | close resolved | 45 | 75 | 29 | Build with base ubuntu@25.10 and build-base ubuntu@devel fails with 'Couldn't get EOL data for devel' in charmcraft 4.0.1; fixed in craft-providers 3.2.0 by skipping EOL checks for devel. |
|
charmcraft issue #1054 |
Charmcraft fails to launch LXD instance with high uid (`raw.idmap=both 595156457 0`) | jamesbeedy | 1320d | close resolved | 45 | 80 | 23 | High host UID causes LXD launch failure via raw.idmap=both; diagnosed as craft-providers idmap issue, fixed upstream by separate uid/gid maps and charmcraft now depends on fixed version. |
|
snapcraft issue #5836 |
`enable-patchelf` build-attribute uses `ld` for the build-on host, not the... | lengau | 380d | keep open | 45 | 85 | 23 | enable-patchelf picks the dynamic linker from the build-on host arch, so cross-compiled armhf binaries get ld-linux-aarch64.so.1 instead of ld-linux-armhf.so.3. Still unfixed; fix PR #6455 was closed unmerged. |
|
starflow pr #205 |
fix(ci): lint workflow run steps in shellcheck-actions.sh | ayushpratap27 | 9d | needs review | 45 | 75 | 25 | Expands shellcheck-actions.sh to lint both composite actions and workflow YAML files, fixing issue #200 where workflow steps were never checked. Clean diff, CI passing, awaiting review. |
|
snapcraft issue #5827 |
The uv plugin reference does not explain the dependencies | bepri | 386d | keep open | 45 | 85 | 23 | Snapcraft's uv plugin reference drops the craft-parts "Dependencies" section (uv-deps part / astral-uv build-snap) that explains how to provide uv, causing user confusion. Triaged, still open (SNAPCRAFT-1250). |
|
snapcraft issue #5432 |
Add a linter for external symlinks | mr-cal | 560d | keep open | 45 | 72 | 21 | Triaged enhancement remains open: Snapcraft has no external-symlink linter in its registry, leaving build-time detection to store upload review. |
|
snapcraft issue #5145 |
snapcraft fails to launch multipass instance when multipass isn't pre-installed | sed-i | 717d | keep open | 45 | 72 | 16 | Snapcraft emits cryptic 'Remote "snapcraft" is unknown or unreachable / exit code 2' when Multipass can't launch the build instance; maintainer traced it to image-server unavailability or non-amd64 hosts, fix tracked in craft-providers#211 |
|
snapcraft issue #4931 |
Failed to upload snap created with `assumes: - command-chain` | chanchiwai-ray | 836d | keep open | 45 | 92 | 36 | Declaring `assumes: [command-chain]` in snapcraft.yaml duplicates the entry, producing a snap.yaml rejected by snap-review. Still unfixed at HEAD; fix PR #6445 was closed unmerged. |
|
craft-application issue #1034 |
`test` command fails to allocate LXD VMs when verbosity is `verbose` or `debug` | lengau | 233d | keep open | 45 | 86 | 22 | Triaged bug: snapcraft test allocates LXD VMs at default verbosity but fails at verbose or debug, with spread receiving no ADDRESS output; no resolving change is evidenced. |
|
snapcraft issue #5114 |
bash gets built with a /bin/bash that is missing the executable bit | basak | 753d | keep open | 45 | 85 | 33 | Staging bash+quilt in a classic core24 snap produces a non-executable bin/bash: craft-parts' normalize.py _try_copy_local uses shutil.copyfile, which drops file modes. Confirmed root cause, no fix landed. |
|
snapcraft issue #5115 |
component does not take snap version when no version provided | stephensp | 753d | close resolved | 45 | 92 | 19 | Component version inheritance was triaged as an enhancement; maintainers adopted component-level adopt-info, and follow-up #5240 was closed after implementation merged in canonical/snapcraft#5753. |
|
charmcraft issue #1435 |
`charmcraft release` doesn't use output text from the store. | lengau | 1060d | needs triage | 44 | 84 | 22 | charmcraft release ignores Charmhub's response and prints resource details from CLI arguments, potentially reporting a different revision than was attached; no fix or maintainer response is recorded. |
|
craft-application issue #698 |
Some valid `spread.yaml` files don't get parsed correctly. | lengau | 590d | close resolved | 44 | 94 | 34 | Valid spread backends with bare system-name strings are now accepted; this report was resolved by merged PR #737, commit 2f11fe33. |
|
charmcraft issue #2428 |
docs: dedicated doc for uploading of OCI images | sed-i | 443d | keep open | 44 | 76 | 16 | Triaged OCI upload documentation remains incomplete: guidance omits transport/archive forms and multi-architecture handling, while CLI help conflicts with the docs about sha256 prefixes. |
|
snapcraft (launchpad) issue #1670162 |
publish complains about desktop file un-necessarily | ~popey | 3532d | close resolved | 44 | 85 | 16 | Store review incorrectly demanded a .desktop file for an x11-enabled CLI snap; maintainers reported the review-tools correction released on 2017-03-20, but the issue remains open. |
|
rockcraft issue #428 |
add the typical environment variables to any interactive session, like with `--debug` | ca-scribner | 1071d | needs triage | 44 | 73 | 12 | Rockcraft debug and shell sessions omit step-specific CRAFT_* variables; the open, untriaged request overlaps the still-open craft-application issue #435. |
|
imagecraft issue #276 |
Support human-friendly GPT partition types | steinbro | 265d | keep open | 44 | 80 | 20 | Triaged feature request to support readable aliases for common GPT partition types in imagecraft.yaml while retaining arbitrary GUID support; aliases remain unimplemented. |
|
snapcraft (launchpad) issue #2065278 |
flutter plugin: cache SDK across parts | ~saviq | 910d | needs triage | 44 | 72 | 16 | Flutter plugin stores its SDK in each part's build directory, causing separate clones and precaches; the optimization remains valid but untriaged and has no maintainer response. |
|
snapcraft (launchpad) issue #1795642 |
Ignore vcs folders for `source-type: local` builds | ~saviq | 2956d | keep open | 44 | 57 | 9 | Request to exclude VCS metadata such as .git, .bazaar, and .hg from local sources remains open; Snapcraft still filters only *.snap, and the 2018 design discussion never concluded. |
|
snapcraft (launchpad) issue #2014963 |
Snapcraft fails to build snap if Snapcraft itself is installed using `snap try` | ~brlin | 1314d | needs triage | 44 | 71 | 18 | `snap try` Snapcraft could not self-inject into legacy LXD builds because snapd cannot download a try snap; the affected provider is removed, but current behavior needs retesting. |
|
rockcraft issue #661 |
feat: add support for "log-targets" | cjdcordeiro | 825d | needs triage | 44 | 52 | 13 | Pebble log-targets remain unimplemented in Rockcraft's schema and generated layer; the sole commenter has no concrete use case, leaving validation and test setup unclear. |
|
craft-parts pr #1682 |
feat(package/apt): validate all stage packages | cmatsuoka | 76d | keep open | 43 | 48 | 13 | APT stage-package validation now aggregates every invalid entry before failing; tests pass and 3 reviewers approve, but lint fails, 2 comments remain unresolved, and merge conflicts need resolution. |
|
snapcraft (launchpad) issue #1824077 |
IsADirectoryError occurred when migrating /usr/bin/X11 symlink in stage step | ~brlin | 2766d | close resolved | 43 | 89 | 24 | Snapcraft 3.3 staging aborted on IsADirectoryError for the usr/bin/X11 symlink to '.'; later commits fixed directory-targeted symlink handling. |
|
charmcraft issue #2078 |
`charmcraft clean` does not clean all platforms for charm | carlcsaposs-canonical | 660d | keep open | 43 | 90 | 17 | Open, reproducible cleanup bug: charmcraft clean uses current project platforms to derive build instances, leaving containers for removed platforms; no resolving fix is linked. |
|
snapcraft (launchpad) issue #1976290 |
extension files get repeated over and over each time snapcraft is recreated | ~rastersoft-gmail | 1620d | needs triage | 43 | 58 | 11 | Incremental builds reportedly accumulate stale GNOME extension sources in Python build/lib, growing the snap; the 2022 report remains open without maintainer triage or a confirmed fix. |
|
snapcraft (launchpad) issue #1831752 |
Missing grammar for conditional configflags on/to architecture | ~fnordahl | 2710d | needs triage | 43 | 77 | 14 | Architecture-conditional configflags remain unsupported for plugin-specific part keys; this old, untriaged proposal has only an author follow-up and no maintainer response. |
|
snapcraft (launchpad) issue #1575188 |
Fix for bug #1572664 had broken my snap package build | ~townsend | 3845d | close resolved | 43 | 82 | 23 | The 2016 chroot build failure involved dangling symlinks; later commit 221a43803 stopped hard-linking symlinks, so the reported build path appears resolved. |
|
snapcraft (launchpad) issue #2004544 |
Rebuilding a Go project results in error "error obtaining VCS status" in... | ~saviq | 1372d | close resolved | 43 | 92 | 20 | Go rebuilds in privileged LXD fail with Git dubious-ownership errors from mixed host/container ownership; this duplicates #1990298 and is addressed by craft-providers 1.7.2. |
|
snapcraft (launchpad) issue #1823512 |
`snapcraft --shell` shouldn't run the lifecycle steps | ~brlin | 2769d | keep open | 43 | 72 | 13 | Bare snapcraft --shell runs lifecycle actions before opening the shell. The one-line reproducer is confirmed, but the default snap command semantics and a definitive resolution are not documented. |
|
rockcraft issue #746 |
Investigate dropping virtual envs from the python-based plugins | tigarmo | 728d | needs triage | 43 | 66 | 12 | Replace per-part Python/Poetry venvs with direct system-Python pip installs; still open and unimplemented, with current code retaining venv and sitecustomize handling. |
|
charmcraft issue #2204 |
[3.4.3] Charmcraft fetch-lib fails with `Library None not found in Charmhub.` | phvalguima | 610d | keep open | 43 | 92 | 25 | Bulk fetch-lib aborts on an unavailable local library and misleadingly prints “Library None not found”; current code still uses the absent CLI argument, while PR #2505 remains open. |
|
snapcraft (launchpad) issue #1617907 |
Two python parts in the same snapcraft.yaml result in not installing the... | ~liu-xiao-guo | 3720d | needs triage | 43 | 55 | 10 | Snapcraft 2.14 fails when multiple Python parts stage conflicting interpreter files. Similarity to resolved bug #1531570 was disputed, and the old report remains unverified. |
|
snapcraft (launchpad) issue #1958282 |
Pass proxy settings to override-pull | ~mr-cal | 1752d | close resolved | 43 | 76 | 25 | Proxy variables are now forwarded from Launchpad into Snapcraft's provider environment, resolving override-pull's reported lack of proxy access. |
|
rockcraft issue #167 |
Take "stack" of layers into account when adding a new layer | tigarmo | 1421d | keep open | 43 | 85 | 15 | Rock packing still considers only the extracted base when adding later layers; a payload symlink such as /.rock can be overwritten by metadata, and the big spread test documents the limitation. |
|
craft-providers issue #449 |
Handle SIGINT | mr-cal | 1093d | keep open | 43 | 76 | 18 | Maintainer-labeled enhancement remains open: Ctrl-C during LXD base setup can leave a non-ephemeral base running; current code stops many setup failures but does not guarantee removal. |
|
rockcraft issue #121 |
Allow setting of a working directory for the resulting ROCK in rockcraft.yaml | gruyaume | 1485d | keep open | 43 | 64 | 16 | PR #305 provides service-level working-dir support, avoiding cd wrappers, but the requested image-wide OCI WorkingDir for arbitrary exec sessions remains unimplemented. |
|
snapcraft (launchpad) issue #1617253 |
snapcraft syntax documentation is incomplete | ~rogpeppe | 3723d | close resolved | 43 | 88 | 25 | The former syntax page omitted app-level plugs; the current source-backed snapcraft.yaml reference documents App plugs and other project fields. |
|
snapcraft (launchpad) issue #2006599 |
using advanced grammar to build towards a certain arch does not work with stage-snaps | ~ogra | 1366d | needs triage | 43 | 68 | 15 | Cross-build grammar selects a foreign-architecture stage snap, but its download lacks the target store architecture and reports the snap missing. A workaround exists; the report remains untriaged. |
|
charmcraft issue #1246 |
K8s profiles: Add `--image` arg to `charmcraft init` | sed-i | 1157d | needs triage | 43 | 64 | 12 | Requested repeatable image arguments for Kubernetes profiles during charmcraft init; the option remains unimplemented and untriaged, with no maintainer response. |
|
charmcraft issue #1896 |
Create a way to adjust the operator endpoint when not using the charm plugin | lengau | 785d | keep open | 43 | 84 | 22 | Auto-generated dispatch files outside the charm plugin still default to src/charm.py; the entrypoint override remains a TODO, leaving non-default operator entrypoints unsupported. |
|
rockcraft pr #745 |
Adds run_once_command rock build option | claudiubelu | 731d | close superseded | 43 | 7 | 2 | Proposes an untested run_once_command build option for one-shot rocks, but remains unreviewed and inactive; canonical/rockcraft#939 later shipped entrypoint-command to bypass Pebble. |
|
charmcraft issue #1199 |
Utility to obtain all PYDEPS | sed-i | 1196d | keep open | 43 | 79 | 24 | Open, triaged enhancement to expose all fetched charm libraries' PYDEPS for tox or pip; collection exists internally, but no CLI utility is available. |
|
craft-application issue #249 |
remote build: provide a way to clean up all of a user's remote builds | lengau | 982d | keep open | 43 | 80 | 17 | Triaged enhancement remains open: add a command to remove stopped, app-prefixed builds left in the user's Launchpad remote-build project after crashes. |
|
snapcraft (launchpad) issue #2019489 |
build fails pip update of pip setuptools wheel | ~kenneth-loafman | 1272d | needs triage | 43 | 64 | 12 | Python-part builds can fail after automatically upgrading pip, setuptools, and wheel because system pkg_resources requires the old pip; the report remains open and untriaged. |
|
rockcraft issue #109 |
tests: spread tests fail intermittently | mr-cal | 1498d | keep open | 42 | 68 | 22 | Spread tests flake when the docker snap daemon never starts. Still present in-tree: spread.yaml does 'snap install docker' then a bare 'retry -n 10 --wait 2 docker run --rm hello-world' with no failure diagnostics. Fix proposed (log capture, longer retry) not yet implemented. |
|
charmcraft issue #1154 |
Use craft-application's store service | lengau | 1211d | close resolved | 42 | 98 | 19 | Store interactions now use a craft-application AppService, and all store commands inherit AppCommand; completed by commit 5dcad2af and related craft-application migration work. |
|
imagecraft issue #148 |
Keep overlayfs mounted when running with --debug and something fails | toabctl | 535d | keep open | 42 | 78 | 14 | Debug shells start after a failed overlay's fuse-overlayfs mount is already unmounted; the requested behavior remains unresolved and may require craft-parts support. |
|
rockcraft issue #1031 |
Support uv plugin in fastapi extension | jneo8 | 350d | close resolved | 42 | 84 | 18 | FastAPI uv integration is implemented for Ubuntu 26.04+; projects with uv.lock and pyproject.toml use the uv plugin without requirements.txt. |
|
rockcraft issue #730 |
improve error messages for LXC operations | cjdcordeiro | 755d | close resolved | 42 | 91 | 31 | LXC copy failures hid useful stderr, including disk exhaustion, until trace verbosity; craft-cli 2.13.0 now displays error details in every non-quiet mode, resolving the report. |
|
fetch-service issue #225 |
Add GitHub workflow that builds and tests the fetch-operator charm | lengau | 773d | needs triage | 42 | 58 | 11 | Maintainer task (lengau) to add a CI workflow that builds the fetch-operator charm and runs `charmcraft test` with charmcraft.yaml pinned to the current fetch-service commit; still unimplemented. |
|
rockcraft issue #553 |
Add `list-plugins` command | sed-i | 931d | keep open | 42 | 68 | 15 | Rockcraft still lacks a CLI command for discovering supported plugins; declarative per-base plugin groups have since been added, addressing the main design prerequisite. |
|
rockcraft issue #447 |
Consider creating and making the _daemon_ user available before running any steps | merkata | 1058d | needs triage | 42 | 52 | 5 | Open feature request to provision _daemon_ before part steps for su-based build commands; packing still creates the user afterward, while the writable PEBBLE_PATH concern is now covered by mode 1777. |
|
rockcraft issue #334 |
Declaring ca-certificates in stage-packages doesn't populate the... | weiiwang01 | 1198d | keep open | 42 | 88 | 24 | Stage packages do not run maintainer scripts, so ca-certificates symlinks are absent; overlay-packages works, and the promised documentation update remains tracked under ROCKS-1696. |
|
rockcraft issue #319 |
Building for arm not possible on Raspberry Pi 3 (32 bit) | ghislainbourgeois | 1219d | close resolved | 42 | 91 | 25 | 32-bit ARM builds on Raspberry Pi 3 now use the Debian architecture name armhf; PR #380/commit 340064d2 resolved the obsolete arm/armv7l host compatibility error. |
|
rockcraft issue #57 |
Leftover files affecting consecutive runs of "rockcraft pack" | tigarmo | 1535d | keep open | 42 | 84 | 17 | Failed pack leaves part-install files that break the next pack; a triage update asks whether the supported rockcraft clean reset resolves the hard-link failure. |
|
snapcraft pr #6250 |
feat: deprecation warning for snap_daemon system username | lengau | 174d | needs review | 42 | 34 | 10 | Adds typed snap_daemon deprecation metadata and a craft-cli warning; core tests pass, but schema and integration checks fail and 3 review comments remain unresolved. |
|
snapcraft issue #5918 |
Add a how-to for controlling package versions | bepri | 330d | keep open | 42 | 82 | 20 | Open documentation request to explain base-specific APT versions and how to select or override them using PPAs such as Deadsnakes; current docs only mention package sources briefly. |
|
snapcraft issue #5716 |
Use hkps by default | dilyn-corner | 442d | keep open | 42 | 82 | 27 | Triaged documentation gap: explain that hkps://keyserver.ubuntu.com can work around GPG key-fetch failures on core22/core24; Snapcraft 8.12 inherits craft-archives PR #189's fallback. |
|
snapcraft issue #5531 |
build-on is/isn't mandatory/optional? | waveform80 | 519d | keep open | 42 | 92 | 35 | Snapcraft rejects empty platform mappings despite docs allowing omitted keys; maintainers chose a documentation fix, but current docs still don't distinguish `{}` from `null`. |
|
craft-application issue #806 |
Use `snapcraft test` for spread tests | lengau | 484d | keep open | 42 | 70 | 14 | Maintainer dogfooding task: switch CI from invoking spread directly to `snapcraft test`. Triaged but unimplemented — .github/workflows/spread.yaml still calls `spread ${{ matrix.spread }}`; open PR #1038 attempts it with failing CI. |
|
snapcraft issue #5138 |
Feature request to formally support importing private keys | CharleeSF | 730d | keep open | 42 | 61 | 11 | Private-key import for clean CI signing remains unresolved; a maintainer proposed initializing ~/.snap/gnupg, but no accepted import/export implementation is recorded. |
|
snapcraft issue #5079 |
Cannot run snapcraft in docker anymore | om26er | 766d | keep open | 42 | 70 | 14 | Snapcraft extracted into Docker fails with a snapctl/snapd-socket internal error; a custom Python-module launcher workaround succeeds, while a maintainer keeps the triaged issue open to improve errors. |
|
snapcraft issue #4268 |
[cross-compile] when a deb package that has a dependency to non-architecture... | bugraaydogar | 1213d | keep open | 42 | 63 | 14 | Core22 cross-compilation can treat an architecture-independent dependency as target-specific; cross-architecture behavior was reproduced, but current core24 behavior remains unverified. |
|
craft-application pr #1038 |
ci(spread): switch from manually running spread to using snapcraft test | lengau | 231d | keep open | 42 | 18 | 3 | Migrates dogfooding Spread runs to snapcraft test; after 197 days it remains unreviewed with seven CI failures, including all craft-test jobs and snap-tests. |
|
craft-application issue #719 |
Raise an error for unfiltered build plans | mr-cal | 581d | needs triage | 42 | 74 | 15 | The requested guard remains unimplemented: create_build_plan() still accepts three None filters and selects one build-on per platform; LifecycleService also depends on that fallback. |
|
craft-application pr #664 |
feat: add line number to error messages | alesancor1 | 617d | needs review | 42 | 28 | 7 | Adds line numbers to project/config error messages across nine files (+157/-14). It has had no review or CI for 482 days; one comment is unresolved and the changelog entry is unchecked. |
|
craft-cli issue #132 |
The help produced for a command options should give more information | facundobatista | 1394d | needs triage | 42 | 49 | 8 | Enhance option help to show value requirements, defaults, cardinality or repeatability, and choices. The current help pipeline renders option names and messages only, with no recorded design decision. |
|
snapcraft-rocks issue #57 |
Service "snapcraft" stopped unexpectedly with code 70 | abitrolly | 772d | keep open | 42 | 74 | 18 | OCI builds hid Snapcraft's ConstructorError; verbose mode traced it to stale build directories, whose removal restored the build. Clearer default diagnostics remain open through #58 and #59. |
|
craft-store issue #97 |
Confusing error message on expired macaroon | sergiusens | 1177d | keep open | 42 | 70 | 18 | Expired macaroon yields misleading store errors (macaroon-permission-required / macaroon-authorization-required). Triaged bug; maintainer proposed a client-side expiry check; confirmed reproduced but still unfixed. |