Showing 100 of 2043 issues
| Issue | Title | Author | Age | Action | Staleness ↑ | Confidence | Summary |
|---|---|---|---|---|---|---|---|
|
craft-cli issue #125 |
When the Printer stops it needs to clean the last line if it was transient progress | facundobatista | 1437d | keep open | 55 | 60 | Printer leaves transient progress text on screen when stopping or pausing; it should be overwritten by the next output. Open since 2022, no comments, but a related fix (PR #126) already enhanced ephemeral handover after pause/stop. |
|
charmcraft issue #2461 |
uv plugin doesn't cache wheels to LXC host | carlcsaposs-canonical | 337d | needs triage | 55 | 75 | uv plugin with no-binary=true does not persist built wheels to the LXC host shared cache (CRAFT_SHARED_CACHE); only the pip cache dir is mounted, so the uv cache stays container-local. |
|
snapcraft issue #4344 |
Treat the gadget.yaml like other snap meta files | dilyn-corner | 1107d | keep open | 55 | 72 | Enhancement to move gadget.yaml source location from project root to snap/gadget.yaml for consistency with other snap meta files. Triaged, acknowledged by maintainer who linked it to issue #4892 as a prerequisite. Code still reads from root; not yet implemented. |
|
imagecraft issue #380 |
[Feature] Support ppc64el bootloader installation via Open Firmware... | lengau | 53d | needs triage | 55 | 55 | Feature request to add ppc64el bootloader support via Open Firmware and PReP partitions; no maintainer response or labels after 46 days |
|
craft-platforms pr #254 |
ci: add workshops | lengau | 58d | needs review | 55 | 70 | Adds workshop tool for local development and cross-version testing. 51 days inactive, 0 reviewers, 8 unresolved review comments, all CI passing. |
|
charmcraft issue #2018 |
Package service integration tests fail on non-amd64 architectures | lengau | 644d | keep open | 55 | 78 | Package service integration tests hardcode amd64, causing failures on arm64 CI. Still open; QA workflow limits tests to amd64 as a workaround referencing this issue. No fix merged yet. |
|
charmcraft issue #2685 |
`uv` plugin produces architecture-mislabeled charm on cross-build... | UtkarshBhatthere | 129d | needs triage | 55 | 70 | uv plugin cross-build (build-on amd64, build-for arm64/ppc64el/s390x) silently packs a charm whose venv contains host-arch compiled wheels while manifest declares target arch. No maintainer response, no labels, 0 comments, 114 days old. |
|
snapcraft issue #5900 |
docs: Add `snap run --strace` discussion to the “Debug a Snap” Guide | hillpd | 281d | keep open | 55 | 70 | Docs request to add a `snap run --strace` section to the 'Debug a Snap' guide for capturing syscalls under confinement. Maintainer acknowledged it was likely lost in a docs migration; no strace content exists in the repo yet. |
|
craft-grammar issue #89 |
Unexpected behavior for multiple `to` statements | mr-cal | 509d | keep open | 55 | 70 | craft-grammar silently mishandles multiple `to` statements combined with `else`: armhf build yields [foo, baz] while riscv64 yields [bar], with no error or warning. Maintainer comment (2025-06-11) suggests supporting multiple `to` directives since `to` matches on AND criteria. No fix found in code or history; issue open, unlabelled. |
|
snapcraft issue #5944 |
docs: Discord isn't a great example for an electron app | lengau | 250d | needs triage | 55 | 78 | Docs improvement: the Discord example in the Electron how-to only shows deb extraction, not actual Electron app building. Suggests Signal as a better example. No maintainer response in 238 days; Discord example still present in docs. |
|
snapcraft issue #5613 |
Poor error reporting for bases earlier than 24 | dilyn-corner | 425d | keep open | 55 | 70 | Snapcraft 8.x crashes with a raw traceback (TypeError: 'NoneType' object is not iterable) instead of a friendly error when an empty/None grammar field (e.g. build-packages:) is used on core22 and earlier bases; core24 reports a proper error. Triaged as an enhancement, internal ticket SNAPCRAFT-1186 created, no fix yet. |
|
charmcraft issue #2605 |
Re-enable MacOS tests | lengau | 170d | keep open | 55 | 75 | Task to re-enable disabled macOS CI tests, blocked by a libgit2 version removed from Homebrew. Created by maintainer lengau as follow-up to PR #2606 which disabled the tests. Still open, unlabelled, no activity in 155 days; tests remain commented out in workflows. |
|
charmcraft issue #1543 |
`--force` Considered Harmful™ | lengau | 933d | needs triage | 55 | 75 | Feature request to replace the ambiguous --force CLI option in charmcraft commands (pack, init, analyse) with descriptive parameters like --override-linters, suppress it from help, and warn on use. Still unimplemented in current code; no labels, no assignee, awaiting maintainer decision on CLI guidelines. |
|
charmcraft issue #2578 |
docs: The usage parameters show up as None | famulu | 204d | keep open | 55 | 60 | charmcraft release docs show usage parameters as <None> <None> <None> instead of channel, name, revision; triaged with Jira ticket CHARMCRAFT-686, no fix yet |
|
snapcraft issue #6325 |
Skip repacking if artifact contents are unchanged | cmatsuoka | 68d | keep open | 55 | 50 | Triaged feature request to implement ST160 conditional repacking API; feature appears implemented in craft-application and snapcraft but issue remains open. |
|
craft-application issue #991 |
Add a prune-instances command | mr-cal | 234d | keep open | 55 | 75 | Feature request for a prune-instances command in craft-application to remove non-base provider instances, with optional provider flags and tests. Unimplemented; blocked on craft-providers work; still needed by charmcraft#1042. |
|
charmcraft issue #1917 |
Charmcraft cannot parse a dev version build for multipass | jat-canonical | 718d | keep open | 55 | 75 | Charmcraft pack fails with InvalidVersion on dev multipass builds (e.g. 1.15.0-dev.2929.pr661). Root cause traced to craft-providers version parsing; upstream fix landed in craft-providers. Issue is triaged and effectively resolved upstream. |
|
imagecraft issue #284 |
Support recommended dependencies in overlay-packages | rthill91 | 187d | needs triage | 55 | 70 | Feature request for a flag/config to install recommended dependencies when using overlay-packages in imagecraft. No maintainer activity in 175 days, but craft-parts (the underlying library) recently added an overlay-recommended-packages key that provides exactly this capability. |
|
rockcraft issue #910 |
Rockcraft ignores configured staging Pro contract URL when building with... | bschimke95 | 438d | keep open | 55 | 80 | Rockcraft ignores the staging Pro contract URL from /etc/ubuntu-advantage/uaclient.conf when building with --pro=fips-updates, hitting production and failing with 401. Triaged by clay-lake, who has a fix ready in craft-providers and will trigger a new build once merged. |
|
craft-application issue #540 |
Document parallel build count environment variables | mr-cal | 691d | keep open | 55 | 80 | Docs gap: CRAFT_PARALLEL_BUILD_COUNT and CRAFT_MAX_PARALLEL_BUILD_COUNT (and app-prefixed variants) are implemented in craft_application/util/system.py but not documented. Labeled enhancement/docs by a maintainer, open 679 days, no comments, still unaddressed. |
|
craft-parts issue #812 |
maven plugin should install maven build-package | vpa1977 | 757d | keep open | 55 | 60 | Maven plugin requires mvn pre-installed; reporter wants build-packages auto-added. Maintainers triaged (CRAFT-3257) and discussed making it behave like rust plugin. A self-contained build attribute was later added to maven/gradle plugins, partially addressing the need. |
|
debcraft issue #149 |
[Feature] Add support for dpkg-buildflags for C/C++/Rust | hector-cao | 138d | keep open | 55 | 75 | Feature request to automatically pass dpkg-buildflags (CFLAGS, CXXFLAGS, RUSTFLAGS, etc.) to the build environment. Triaged with Jira ticket DEBCRAFT-70. Code in lifecycle.py already implements this via _gen_dpkg_buildflags() added in PR #170. |
|
debcraft issue #42 |
Validate `depends` and related fields | lengau | 297d | needs triage | 55 | 70 | Feature request to add validation for the depends field and related Debian relationship fields (recommends, suggests, provides, breaks, replaces, conflicts) in debcraft package models, ideally upstreamed to python-debian. Open since Nov 2025 with no labels, no assignee, and no further activity. |
|
craft-parts issue #747 |
Python plugin. `pip install .` failing because of `pyproject.toml` file | javierdelapuente | 830d | needs triage | 55 | 70 | Python plugin runs `pip install .` when pyproject.toml exists, failing for projects using it only for tool config. Issue is 823 days old with recent suggestion for heuristic fix. |
|
charmcraft issue #1713 |
Autodocs: Updates for pydantic models | lengau | 803d | needs triage | 55 | 72 | Tracking issue for two action items: create a single charmcraft.yaml schema (done via PR #2183) and alphabetize schema items (not done). No labels, comments, or assignee; no activity for ~12.5 months. |
|
craft-parts issue #899 |
Craft parts should close stdin when cloning git projects | mr-cal | 674d | needs triage | 55 | 72 | Git source handler in craft-parts does not close stdin when cloning, causing hangs when repos require credentials. Filed by maintainer mr-cal; only a Jira-sync bot comment exists. No fix found in git_source.py or base.py _run. |
|
craft-archives issue #176 |
Allow modifying existing default repositories | lengau | 435d | close stale | 55 | 72 | Enhancement request (triaged, Jira CRAFT-4634) for a function like install_in_root that rewrites existing sources.list/ubuntu.sources to change default repo URLs, e.g. to old-releases.ubuntu.com for EOL releases. Appears implemented in craft-archives 2.2.0 via use_old_releases. |
|
craft-archives issue #221 |
Support adding private repositories | lengau | 168d | keep open | 55 | 78 | Enhancement to support adding private apt repositories with authentication via /etc/apt/auth.conf.d, including private PPAs. Triaged by maintainer, Jira ticket CRAFT-5074 created, no implementation work started. |
|
charmcraft issue #2591 |
Add reuse-packages documentation | lengau | 189d | keep open | 55 | 70 | Docs enhancement to add a Charmcraft 'reuse packages between builds' how-to, mirroring Snapcraft's page. Triaged by a maintainer; the shared craft-application doc is still excluded from the build, so the page has not been added yet. |
|
starbase issue #532 |
docs: app title isn't read in TOC | medubelko | 127d | needs triage | 55 | 55 | Rockcraft docs TOC title falls back to 'dev' instead of the Git tag because the RTD runner can't resolve the package version. Filed by a maintainer with no comments; related version/title fixes (#588, #590) landed since. |
|
imagecraft issue #285 |
Support the Discoverable Partition Standard for GPT partitions | lengau | 185d | keep open | 55 | 75 | Feature request to support Discoverable Partitions Specification GUIDs for GPT partitions in imagecraft. Triaged and tracked in Jira (IMAGECRAFT-100) but inactive for ~5.7 months with no implementation progress. |
|
craft-application issue #1022 |
docs: detail SPDX compatibility for `license` key | medubelko | 186d | keep open | 55 | 75 | Documentation improvement for the `license` key to clarify it accepts SPDX expressions, mention AND/OR support, provide richer examples, and link to the full SPDX spec. Partially addressed: docstring now says 'SPDX expression' and links to spec, but AND/OR mention and richer examples are still missing. |
|
craft-parts issue #975 |
Add CLI option to select the target architecture | lengau | 605d | keep open | 55 | 80 | Feature request to add a CLI option (e.g. --target-arch) to python -m craft_parts for selecting the target architecture, useful for demonstrating cross-compilation bugs like #974. Triaged by a maintainer, synced to Jira (CRAFT-4734), not yet implemented. |
|
snapcraft issue #6064 |
Extend advanced grammer to all keys of snapcraft | soumyaDghosh | 200d | needs triage | 55 | 75 | Request to extend advanced grammar (on/to/else) to all snapcraft.yaml keys (apps, plugin params like cmake-parameters, per-arch part skipping). Grammar currently limited to 6 part keys. Unlabeled; cross-referenced to craft-application#985. |
|
debcraft issue #140 |
Handle unquoted multi-arch: no | cmatsuoka | 139d | needs triage | 55 | 75 | YAML parser converts unquoted multi-arch: no to boolean false, producing a confusing generic validation error. Maintainer filed request to add a specific error message or accept false as synonym for "no". Unlabelled, no comments, no activity in 127 days. |
|
snapcraft issue #5102 |
Unable to set components version using craftctl set version | stephensp | 704d | close stale | 55 | 80 | Request to allow dynamically setting component versions via craftctl during override-build (currently errors with 'variable version can be set only once'). Triaged as enhancement; spec'd and prototyped in 2025 but unscheduled. Feature now implemented in snapcraft 8.13 via craftctl set components.<name>.version. |
|
snapcraft issue #5411 |
Fail to fetch packages for non-host architecture | joulsen | 514d | keep open | 55 | 55 | Cross-compile (amd64 build-on, arm64 build-for) fails to fetch stage-packages with :arm64 suffix (e.g. ros-jazzy-ros-base) even though present in repo; maintainer reproduced apt unmet-deps on arch-All python deps; reporter suspects ROS2 repo, not snapcraft. Awaiting reporter's working dpkg repro. |
|
craft-cli issue #361 |
Remove the default command | mr-cal | 424d | keep open | 55 | 80 | Maintainer task to remove the Dispatcher's default_command/allow_default_command support (added for Snapcraft compat). Feature still present in code; removal gated on Snapcraft 10 (core28) release. No labels, 0 comments. |
|
craft-application issue #413 |
Create a common documentation folder | lengau | 761d | keep open | 55 | 70 | Request to create a common documentation folder (like craft-parts) for docs reusable across applications. The docs/common folder now exists with reusable docs and is referenced in CONTRIBUTING.md, so the core ask appears implemented. |
|
snapcraft issue #5827 |
The uv plugin reference does not explain the dependencies | bepri | 332d | keep open | 55 | 80 | Snapcraft's uv plugin docs omit the craft-parts 'Dependencies' section (uv-deps/astral-uv provisioning), causing user confusion. Triaged, tracked as SNAPCRAFT-1250, awaiting a doc fix. |
|
snapcraft (launchpad) issue #2161191 |
python plugin messing with snapcraft env | ~t-a-k | 56d | close not a bug | 55 | 85 | Python plugin leaking snapcraft's site-packages into builds, causing environment pollution. This issue appears to describe the same problem fixed in snapcraft#2901. |
|
charmcraft issue #1997 |
Add ability to `charmcraft close` not supported base. | taurus-forever | 663d | keep open | 55 | 70 | Feature request to extend `charmcraft close` to close a specific base within a track/risk/branch, not just the whole channel. Q2 about re-appearing bases after close/re-release was answered and confirmed by the reporter. |
|
snapcraft (launchpad) issue #1712808 |
udev interface fails in privileged containers | ~saviq | 3306d | keep open | 55 | 75 | snapd fails to reload udev rules when installing snaps in privileged LXD containers (no udevd running). Fixed in snapd 2.68.5; verification done for noble/plucky/questing, jammy verification still pending. |
|
charmcraft issue #2642 |
Small bug in `charmcraft release` documentation | Gu1nness | 162d | needs triage | 55 | 75 | charmcraft release docs show None for parameter names due to gen_cli_docs.py using action.metavar directly (None when unset); bug still present in current code, no maintainer response in 147 days |
|
rockcraft issue #737 |
doc: use the Pebble docs | cjdcordeiro | 691d | keep open | 55 | 72 | Doc improvement to reshape the Pebble explanation page to rely on official Pebble docs. Intersphinx mapping updated to new Pebble docs URL, but the page's main Pebble link still points to GitHub and the page hasn't been reshaped. |
|
snapcraft issue #4454 |
Allow snapcraft to use remote lxd instances. | jat-canonical | 1026d | keep open | 55 | 70 | Feature request to let snapcraft build against a remote LXD instance (via lxc remote config) instead of requiring a local LXD install, enabling snap development on macOS/Windows. Triaged and tracked in Jira (CRAFT-2554); follow-up discussion moved to craft-providers#508, which remains open. |
|
rockcraft issue #293 |
Improve reference docs for rockcraft commands | tigarmo | 1198d | close stale | 55 | 75 | Request to improve bare-bones Rockcraft command reference docs; addressed by PR #318 which automated CLI reference doc generation via gen_cli_docs.py |
|
craft-parts issue #1390 |
Warn on outward relative path sources | bepri | 312d | keep open | 55 | 75 | Feature request to warn when a part's source path resolves outside Path.cwd(), preventing unexpected behavior in managed builds. Triaged by maintainer bepri; @lengau expanded scope to also warn on absolute paths. No implementation found in codebase. |
|
rockcraft issue #628 |
Improve article "Parts and Steps" | hd9 | 799d | needs triage | 55 | 75 | Request to clarify two ambiguous terms in the rockcraft 'Parts and Steps' reference doc: link 'craft-parts' to the Parts concept and define 'project'. Doc still contains the same generic wording; no maintainer response in 788 days. |
|
craft-store issue #208 |
Rewrite with `httpx` | lengau | 728d | keep open | 55 | 65 | Feature request to rewrite craft-store using httpx instead of requests, to work around requests version pinning issues. Partially implemented: httpx-based auth classes and Publisher Gateway client exist, but core clients still use requests. |
|
rockcraft pr #885 |
fix: Removed reference to snapcraft.yaml in expand extensions | RafaelJohn9 | 481d | needs review | 55 | 85 | One-line fix removing the snapcraft.yaml reference from the expand-extensions help text and docstring, fixing #658. Approved by 2 reviewers with all CI checks green, but unmerged and inactive ~6 months; the fix is still unapplied in the codebase. |
|
craft-application issue #889 |
Developer docs: Architecture explanation | lengau | 374d | keep open | 55 | 60 | Developer docs enhancement to explain the purpose of commands, services, and what the application should/shouldn't do. Triaged by maintainer; a structure-of-a-craft-app explanation page now exists in docs/explanation covering Application, Commands, and Services. |
|
imagecraft pr #330 |
fix: synchronize with udev via BSD flock after losetup to avoid race condition | Copilot | 143d | needs review | 55 | 75 | Adds BSD flock synchronization after losetup to avoid the udev race on loop partition nodes, in both pack and services attach paths, with unit and root integration tests. Changes requested; 6 unresolved comments; lint/files failing; awaiting maintainer review of latest commit. |
|
craft-application issue #806 |
Use `snapcraft test` for spread tests | lengau | 429d | keep open | 55 | 80 | Dogfooding task to switch craft-application CI from running spread directly to using snapcraft test. Triaged; open PR #1038 stalled ~165 days with failing CI; workflow still runs spread directly at HEAD. |
|
rockcraft issue #746 |
Investigate dropping virtual envs from the python-based plugins | tigarmo | 674d | keep open | 55 | 60 | Investigate dropping virtual envs from python-based plugins to fix 24.04 usrmerge breakage and simplify sitecustomize/symlink handling. Last activity 381 days ago; venv-based approach still present in codebase. |
|
craft-application issue #821 |
5.5.0 changes pack semantics if the project file has different metadata | javierdelapuente | 415d | keep open | 55 | 70 | Charmcraft pack skips repacking when only charmcraft.yaml metadata (e.g. summary, config, platforms) changes, leaving a stale .charm. Triaged and moved to craft-application; workaround is clean. Conditional repacking support added in #1111. |
|
rockcraft issue #859 |
Make python plugin integration tests work on non-LTS ubuntu series | lengau | 519d | keep open | 55 | 70 | Rockcraft python plugin integration test (tests/integration/plugins/test_python_plugin.py) only mapped LTS Ubuntu releases to expected values. Non-LTS (25.04/25.10) entries were later added via interim-base support; issue left open, unlabelled, no comments. |
|
starflow pr #127 |
feat: Create workflow for testing dev environments | me6262 | 155d | needs review | 55 | 60 | WIP workflow creating LXD containers in GitHub Actions to test makefile dev-environment commands, referenced as work for #85. No maintainer review, CLA check failing, author notes it fails when run; no activity for 143 days. |
|
craft-parts issue #1329 |
Investigate error conditions of fuse-overlayfs | bepri | 354d | keep open | 55 | 60 | Investigate whether fuse-overlayfs .wh..opq files still cause errors during whiteout cleaning in craft-parts, spawned by a XXX comment in part_handler.py. Triaged, no maintainer response yet; the referenced XXX comment no longer appears in current code. |
|
craft-parts issue #1174 |
Craft parts should rebuild all parts if the list of partitions changes | mr-cal | 424d | keep open | 55 | 75 | Craft-parts should persist the partition list in state files and force a full rebuild (including stage/prime) when partitions change, since files are organized into partitions during build. Triaged bug, tracked as CRAFT-4654, with a maintainer note that partition changes should also trigger reprime/repack. |
|
craft-parts issue #1333 |
Consolidate `os-release` utils with other repositories | bepri | 354d | keep open | 55 | 72 | Consolidate os-release parsing in Craft Parts with Craft Providers/Charmcraft. Triaged; maintainers agreed to switch to the `distro` library. No PR yet; OsRelease class still present in codebase. |
|
craft-application issue #493 |
Use a craft-providers callback hook to set the apt proxy by an app config | lengau | 717d | needs triage | 55 | 65 | Feature request to add an apt_proxy app config option and use a craft-providers callback hook to configure apt proxy in build instances. No maintainer response or labels; only a Jira bot comment. ProxyService exists but lacks apt_proxy config support. |
|
craft-artifacts issue #89 |
Test on Python 3.14 and Ubuntu 26.04 (Resolute) | lengau | 101d | needs triage | 55 | 60 | CI enhancement request to add Python 3.14 and Ubuntu 26.04 testing. Unlabelled, no maintainer engagement after 93 days. |
|
charmcraft issue #1154 |
Use craft-application's store service | lengau | 1157d | keep open | 55 | 70 | Refactor Store class into a craft-application Service and migrate store commands to AppCommand subclasses. Partially done: StoreService exists (PR #1459) and commands are AppCommand subclasses, but the legacy Store class is still used directly in 15+ places in store.py. |
|
snapcraft (launchpad) issue #1669908 |
Provide visible yaml settings or document organize plugin behavior for... | ~dmitriis | 3479d | needs triage | 55 | 55 | Request to document or expose a snapcraft.yaml knob for the organize plugin's directory-merging behavior, after a cryptic 'path ./ already exists' error from shutil.move when using '*' keys. No labels, no maintainer response, 0 comments; last activity 47 days ago on a ~9.5-year-old issue. |
|
craft-parts issue #1367 |
Craft parts swallows chisel errors if logging level is info or higher | lengau | 333d | keep open | 55 | 70 | Chisel slice install errors are swallowed when log level is info or higher, so users see no chisel output or error message. Triaged bug with an internal Jira ticket (CRAFT-4872); no fix or maintainer response yet. |
|
snapcraft issue #5836 |
`enable-patchelf` build-attribute uses `ld` for the build-on host, not the... | lengau | 326d | keep open | 55 | 82 | Cross-compilation bug: enable-patchelf uses platform.machine() (build host arch) instead of target arch for dynamic linker, producing broken armhf snaps from arm64 hosts. Triaged with Jira ticket SNAPCRAFT-1287, no fix yet. |
|
craft-application issue #301 |
Smarter docs URL handling | lengau | 890d | needs triage | 55 | 55 | Feature request to make docs URL handling smarter: when an error carries a docs slug, match it against the application's docs base URL so libraries can raise exceptions without the app catching/reraising them with a full docs URL. Tracked internally as CRAFT-2704; no maintainer response yet. |
|
snapcraft issue #6161 |
Support chart colours aren't dark-mode friendly | medubelko | 157d | keep open | 55 | 80 | Support-schedule chart in snapcraft docs renders release milestones and legacy add-on commitment in near-black (#111), unreadable in dark mode. Fix requested: Canonical colours with contrast for both modes. Unfixed; black fill still in support-chart.css, no activity since filing. |
|
craft-application issue #338 |
`pack` command gives wrong help message and doesn't support packing a directory | mr-cal | 864d | keep open | 55 | 70 | Pack command help incorrectly referenced part-name (fixed in #341) and no way to pack a directory without a project file (still open). |
|
craft-application issue #327 |
Support argument list passthrough | cmatsuoka | 866d | keep open | 55 | 70 | Enhancement to allow raw CLI argument passthrough to spread in the test command, addressing double-dash vs single-dash inconsistencies. Open since 2023, no implementation found in current code. |
|
snapcraft issue #5531 |
build-on is/isn't mandatory/optional? | waveform80 | 465d | keep open | 55 | 85 | Snapcraft 8.9.2 rejects empty-dict platform entries (e.g. amd64: {}) requiring build-on, contradicting docs. Maintainers confirmed behavior is intentional after craft-platforms refactor; decision made to update docs rather than restore empty-dict support. |
|
craft-application issue #331 |
Process grammar and non-grammar dictionary data | mr-cal | 865d | keep open | 55 | 60 | Feature request to make the `organize` keyword handle a mix of grammar entries (e.g. `on amd64 to arm64:`) and plain non-grammar dict entries in the same list, merging them into a single dict. Currently only pure-grammar lists are processed. |
|
craft-parts issue #962 |
CI: create test workflow to build application docs upon changing `docs/common` | lengau | 611d | needs triage | 55 | 70 | Feature request to add a CI workflow that builds downstream application docs when docs/common changes in craft-parts, to catch breakage before merge. Open, unlabelled, no maintainer response; only Jira-sync bot comments. docs/common is still actively maintained. |
|
charmcraft issue #2376 |
docs: options for links in charmcraft unclear | marcusboden | 422d | keep open | 55 | 78 | charmcraft.yaml links section docs don't list allowed fields (contact, documentation, issues, source, website). Maintainer acknowledged and pointed to model definition; docs redo in progress but not yet merged. |
|
craft-parts pr #1466 |
feat: Comment out replace statements to relative paths in go.mod | atandrewlee | 204d | keep open | 55 | 70 | Adds go-use plugin logic to strip relative-path replace statements from go.mod, with integration tests. Changes requested; maintainer notes *-use plugins are obsolete post-Madrid, deferring to tigarmo on whether to adapt to the newer Go plugin. |
|
rockcraft issue #185 |
Support for descriptors different from rockcraft.yaml | arturo-seijas | 1314d | close not a bug | 55 | 80 | Feature request to allow custom descriptor filenames beyond rockcraft.yaml for multi-rock repos. Maintainer declined on 2025-10-01 citing cross-craft-tool consistency; workaround via rocks-template suggested. Issue remains open, last activity 328 days ago. |
|
rockcraft issue #486 |
overlay-packages is not documented in rockcraft.yaml reference | samuelallan72 | 939d | keep open | 55 | 70 | overlay-packages (and other overlay part properties) are missing from the rockcraft.yaml reference docs; maintainer noted the fix belongs in craft-parts' part_properties.rst. Still open with no follow-up. |
|
craft-application pr #1003 |
docs: Add reference documentation for the RemoteBuildService | lengau | 225d | needs review | 55 | 78 | Adds 121 lines of reference documentation for RemoteBuildService across 2 files. CI passing, no reviews or comments. Author is a maintainer. Service still exists in codebase; target docs file not yet in main. |
|
rockcraft issue #1153 |
Feature request: support dynamically setting top-level `version` during build | srbouffard | 176d | needs triage | 55 | 60 | Feature request to allow dynamically setting the top-level version field in rockcraft.yaml during build, enabling rock versions computed from workload version plus packaging increment. No maintainer response yet. |
|
debcraft issue #138 |
Support XSBC entries in the project file | cmatsuoka | 141d | keep open | 55 | 70 | Feature request to support XSBC-prefixed custom fields in the project file, replacing the passthrough mechanism for binary package control entries. Triaged by maintainer, tracked as DEBCRAFT-65, no implementation yet. |
|
craft-application issue #99 |
Means to reduce duplication of plugin fields | sed-i | 1199d | keep open | 55 | 60 | Feature request for a top-level 'definitions' section in craft app YAML to reduce duplication of recurring repo/source fields via anchors. Transferred to craft-application; maintainer sought opinion on approach (similar to grammar changes) in March 2024, no resolution since. |
|
snapcraft issue #6025 |
Snapcraft ignores SNAPCRAFT_BUILD_ENVIRONMENT_* environment variables on MacOS | pachulo | 214d | keep open | 55 | 82 | SNAPCRAFT_BUILD_ENVIRONMENT_CPU/MEMORY env vars documented for Multipass VM sizing are ignored on macOS; maintainer confirmed values are hardcoded, fix blocked by upstream craft-providers#531 (open 2+ years). Triaged as enhancement, no progress since Feb 2026. |
|
rockcraft issue #1198 |
docs: Rockcraft 1.18.0 documentation claims Ubuntu 26.04 support but it... | GregCasbolt | 142d | keep open | 55 | 80 | Rockcraft 1.18.0 docs claim ubuntu@26.04 build-base support but the app raises KeyError; maintainer confirmed 26.04 was devel-only then and promised a better error message. 26.04 is now stabilized in 1.19, so the core issue is resolved. |
|
craft-parts issue #855 |
Add default building behavior to the documentation | dariuszd21 | 718d | keep open | 55 | 60 | Docs task to document that the CMake plugin builds in Debug by default and encourage switching to Release for packaged apps, with a bonus to cover the Rust plugin. Open, labelled Documentation, last activity 47 days ago; cmake docs already show a CMAKE_BUILD_TYPE example but do not state the Debug default. |
|
charmcraft issue #2304 |
Specify discouraged paths for mount points | sed-i | 467d | keep open | 55 | 82 | Docs enhancement to add discouraged mount paths (e.g. /charm, /tmp) to the storage location reference. Triaged, acknowledged by maintainer as a good idea requiring research, no progress since Sep 2025. |
|
charmcraft issue #2435 |
docs: permission docs are missing | beliaev-maksim | 374d | keep open | 55 | 70 | Charmcraft login reference docs lack a list of valid --permission values. A maintainer replied (2025-09-10) that permissions are store-controlled and the list can change, and asked @medubelko/@jahn-junior to weigh in on how to document them; no resolution yet. |
|
snapcraft issue #6032 |
New issue template - "check existing issues" is worded quite strong | YanisaHS | 213d | keep open | 55 | 85 | Suggests softening the 'Check existing issues' checkbox wording in issue templates from 'I've verified...' to a less strict phrasing. Maintainer agreed and looped in template author, but no fix applied yet; wording unchanged in all three templates. |
|
snapcraft issue #4972 |
Cannot create a snap with base:bare in destructive mode | nhathaway | 758d | keep open | 55 | 70 | Snapcraft 8.3.2 fails with 'cannot determine build-for architecture' when building a base:bare snap in destructive mode without build-base. Maintainer confirmed build-base is required for bare and plans an earlier, clearer validation error. |
|
craft-application issue #552 |
Add a way for applications to customize the `InitService` | mr-cal | 674d | keep open | 55 | 75 | Enhancement request for InitService to let applications customize project-name validation and emit template-specific messages. Name validation is already customizable via constructor args; unique per-template messages are not yet supported. |
|
craft-application issue #320 |
Set the project environment in the Lifecycle Service | mr-cal | 871d | keep open | 55 | 70 | Request to set CRAFT_PROJECT_NAME/VERSION env vars in the Lifecycle Service build environment. Code now has ProjectService.update_project_environment() hook, but only CRAFT_PROJECT_VERSION is set by default; CRAFT_PROJECT_NAME still missing. A July 2024 comment reports SNAPCRAFT_PROJECT_NAME=None in PULL phase. |
|
craft-application issue #458 |
Emit a warning when the fetch-service integration is enabled | tigarmo | 730d | close stale | 55 | 85 | Request to emit a warning when the fetch-service integration is enabled, so users know it is experimental. The warning was implemented in PR #496 and is present in the code; the issue is resolved but not yet closed. |
|
craft-application issue #485 |
Provide a better error message when loading a multi-document yaml | lengau | 722d | needs triage | 55 | 72 | Request to improve the error message when loading multi-document YAML files, currently showing a raw ComposerError instead of a clear 'not supported' message. Untriaged, no labels, no maintainer response since the Jira bot comment. |
|
craft-application issue #420 |
Rework PackageService API | lengau | 759d | needs triage | 55 | 72 | PackageService API rework: remove prime_dir from pack, remove metadata, make write_metadata abstract. prime_dir is now deprecated in pack but metadata and write_metadata(path) remain unchanged. No labels, comments, or assignee in ~2 years. |
|
snapcraft issue #4328 |
Hard to see what the causes an error for a 404 network error | sergiusens | 1121d | keep open | 55 | 60 | Enhancement: 404 network errors during source pull don't identify which part/source failed. Triaged by maintainer, synced to Jira SNAPCRAFT-1086. craft-parts NetworkRequestError now includes a source detail field. |
|
craft-cli issue #269 |
CraftError messages with new lines render inconsistently | mr-cal | 745d | keep open | 55 | 70 | CraftError messages containing new lines render with extraneous whitespace between the message and resolution sections. A maintainer commented that PR #210 (remove trailing spaces) likely fixes this indirectly. |
|
snapcraft issue #4991 |
Allow disabling file-based keyring fallback | mr-cal | 753d | keep open | 55 | 70 | Enhancement to add SNAPCRAFT_DISABLE_FILE_BASED_KEYRING env var and docs so snapcraft can avoid the file-based keyring fallback, which hides keys from tools like ubuntu-image. Triaged (Status: Triaged, Type: Enhancement) but no implementation yet; craft-store already exposes a file_fallback flag. |
|
craft-cli pr #338 |
logger pollutes strings with white spaces | dariuszd21 | 501d | needs review | 55 | 75 | Fixes broken output when streaming_brief=True and log entries contain whitespace (\n, \t). Small 1-file fix (+22/-1). Pending review, CI failing on linters and ubuntu-20.04, codecov 399 commits behind main. |
|
craft-archives issue #151 |
Update sources added by craft-archives | mr-cal | 585d | keep open | 55 | 70 | Enhancement to set architectures on craft-*.sources files (not just ubuntu.sources) for cross-compilation support. Triaged by maintainer, assigned to tigarmo, internal ticket CRAFT-4112 created. |
|
craft-cli issue #31 |
Error message formatting | cmatsuoka | 1768d | needs triage | 55 | 60 | Feature request to let the emitter error() method format error messages (e.g. add an 'Error: ' prefix) and optionally output them in red, respecting no-color.org. Open, unlabelled, with one maintainer comment endorsing the idea; no implementation yet. |