Showing 100 of 1910 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
craft-parts issue #1305 |
`cabal` plugin | lengau | 415d | keep open | 42 | 55 | 12 | Feature request to add a `cabal` plugin for building Haskell projects. Maintainer lengau acknowledged it ('not working on this but happy to accept PRs') and volunteer EdmilsonRodrigues offered to implement it, but got no reply. No cabal plugin exists in the codebase. |
|
craft-parts issue #1051 |
Rename overlay+partition specific env vars | upils | 594d | needs triage | 42 | 84 | 22 | Partition overlay variables still use CRAFT_[namespace_]partition_OVERLAY; the requested consistent CRAFT_[namespace_]partition_PART_OVERLAY rename remains unimplemented and needs triage. |
|
craft-parts issue #1613 |
uv: Support workspace packages arguments | pedro-avalos | 150d | needs triage | 42 | 58 | 18 | Feature request: add a `uv-packages` part property to the uv plugin so `uv sync` can be scoped with `--all-packages` or `--package=<name>`, enabling multi-package artifacts. Open, untriaged. |
|
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. |
|
craft-cli issue #350 |
Accept a total of `0` for a progress bar and behave well in this case. | lengau | 498d | keep open | 42 | 72 | 20 | Progress bars should accept total=0 as an unknown-total state instead of dividing by zero. The enhancement is triaged and remains open; the desired rendering needs definition and implementation. |
|
craft-cli issue #261 |
Disable long option abbreviation (`--destructive` vs `--destructive-mode`) | mattculler | 846d | needs triage | 42 | 90 | 29 | Long-option abbreviation remains enabled in _CustomArgumentParser, allowing prefixes such as --destructive to match longer options; the issue is open and awaiting triage. |
|
snapcraft (launchpad) issue #1899311 |
tarfile.ReadError: unexpected end of data | ~amodster | 2216d | keep open | 42 | 86 | 23 | A tar source outside the project is unsupported but triggers a misleading tarfile.ReadError; maintainers requested clearer validation because this occurs frequently. |
|
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 (launchpad) issue #1709674 |
Catkin plugin: consumer snap still pulls in packages contained in producer snap | ~kyrofa | 3375d | needs triage | 42 | 27 | 4 | Catkin underlay handling may duplicate producer-provided ROS packages in a consumer snap; the report remains open, untriaged, and without a concrete reproducer. |
|
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. |
|
craft-parts issue #485 |
Improve logging of Apt issues in Overlays | tigarmo | 1221d | keep open | 42 | 74 | 23 | Overlay package installation failures still collapse apt-get errors into a generic BuildPackagesNotInstalled message, omitting dependency and PPA diagnostics; the logging improvement remains unimplemented. |
|
craft-grammar pr #121 |
feat(experimental): dictionary evaluation | lengau | 428d | keep open | 42 | 22 | 4 | Adds experimental support for evaluating grammar passed as a bare dict instead of a list (GrammarProcessor + pydantic models, +52/-14). Maintainer PR idle 188 days; lint and fast/min-dep tests failing, 4 unresolved review comments, 0 reviewers. |
|
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`. |
|
snapcraft (launchpad) issue #1825820 |
Snapcraft doesn't update the `snapcraft-project` disk source when the path is moved | ~brlin | 2754d | needs triage | 42 | 68 | 13 | LXD builds reportedly fail after moving a project because the instance retains the old disk source. LXD remains supported, but this untriaged report needs verification against the current craft-providers integration. |
|
snapcraft issue #4459 |
icon 'discord.webp' must be either a .png or a .svg | merlijn-sebrechts | 1072d | needs triage | 42 | 64 | 19 | WebP snap icons remain blocked by Snapcraft’s PNG/SVG-only validation; the exact reproduction is clear, but a recent comment questions whether the Snap Store actually accepts WebP uploads. |
|
snapcraft issue #4832 |
`SNAPCRAFT_BUILD_ENVIRONMENT` takes priority over `--use-lxd` | mr-cal | 888d | keep open | 42 | 74 | 16 | Triaged bug: PR #4329 fixed core22 precedence for SNAPCRAFT_BUILD_ENVIRONMENT, but core24 remains unverified and its spread test is restricted to Ubuntu 22.04; CRAFT_MANAGED_MODE precedence is intentional. |
|
rockcraft issue #421 |
Show link to full execution logs when `rockcraft pack --debug` enters debug session | ca-scribner | 1073d | keep open | 42 | 82 | 15 | The requested pre-debug-session execution-log link is still not shown; the current path launches the shell after error handling, and useful inner logs are copied only when the outer process exits. |
|
snapcraft (launchpad) issue #1697468 |
snapcraft doesn't validate plugs: values | ~msweet | 3433d | keep open | 42 | 76 | 20 | Snapcraft accepts malformed plug entries such as plugs: [home x11] and fails later during publishing; maintainers acknowledged the diagnostic gap, but no implemented fix is evidenced. |
|
snapcraft (launchpad) issue #1822709 |
Snapcraft should consider dump part's file permission change as part changed | ~brlin | 2774d | keep open | 42 | 84 | 18 | Dump/local parts still ignore chmod-only source changes; craft-parts checks mtimes but not modes, requiring a manual clean after permission changes. |
|
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 (launchpad) issue #1627854 |
finalzed binary (step prime) are not stripped | ~servusoft | 3692d | keep open | 42 | 68 | 13 | Requested opt-in ELF stripping during stage/prime, including cross-architecture tool selection; acknowledged as roadmap work, but current Snapcraft has no general --strip option. |
|
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 (launchpad) issue #1835556 |
No way to natively build for the non-host arch | ~laney | 2680d | needs triage | 42 | 61 | 8 | A 2018 request for native i386 builds through matching LXD or Multipass environments remains open and untriaged; current --build-for support and provider image coverage need review. |
|
snapcraft (launchpad) issue #1594374 |
Use a user directory for temporary files | ~croepha | 3790d | keep open | 42 | 56 | 9 | Triaged 2016 feature request to make the parts, stage, and prime work directories configurable and move them out of the source tree; unmanaged builds still use the current directory. |
|
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. |
|
snapcraft (launchpad) issue #1848513 |
--debug does not expose appropriate environment variables | ~racb | 2576d | needs triage | 42 | 57 | 10 | The `--debug` failure shell launches bare bash without the failed action's Snapcraft or part environment, preventing faithful command reproduction. The old report remains unlabelled and untriaged. |
|
craft-parts issue #1256 |
Run CI on Focal | lengau | 428d | keep open | 42 | 92 | 30 | Focal remains supported, but the requested self-hosted amd64 Focal runner is absent from slow-test platforms, leaving reproducible full-lifecycle CI coverage unimplemented. |
|
craft-application issue #793 |
Opt-in configuration to always use git+ssh for remote builds | lengau | 497d | keep open | 42 | 78 | 20 | Triaged enhancement to add opt-in configuration forcing git+ssh for remote builds; public projects still use HTTPS, while private projects use SSH. |
|
snapcraft (launchpad) issue #1839399 |
snapcraft not pulling snap from lxd container | ~popey | 2647d | keep open | 42 | 62 | 12 | Snapcraft 3.7.1 reported a successful --use-lxd build but left the generated snap absent on the host; a maintainer identified possible CWD handling, and the case remains unresolved. |
|
snapcraft (launchpad) issue #1917897 |
Files created in override-stage fail to get copied to prime | ~racb | 2071d | keep open | 42 | 85 | 12 | A symlink created after snapcraftctl stage in override-stage is absent from prime; a maintainer said file registration was planned, but no resolution is recorded. |
|
craft-providers pr #876 |
ci: add weekly tests on a variety of distros | lengau | 327d | keep open | 42 | 12 | 3 | Adds a weekly LXD integration-test matrix for Debian, Fedora, Rocky Linux, CentOS Stream, AlmaLinux, openSUSE, and Mint; every new distro job is failing and the unreviewed PR has had no activity for 293 days. |
|
snapcraft (launchpad) issue #1849935 |
Generated 'git describe' based version strings can exceed 32 character version limit | ~ec0 | 2567d | close resolved | 42 | 90 | 27 | Historical version: git builds could generate a 38-character string rejected by snapd; snapcraft#3779 addressed the handling, and legacy support was later removed. |
|
snapcraft pr #6374 |
fix(desktop-file): verify theme icons before rewriting icon | soumyaDghosh | 101d | needs review | 42 | 35 | 12 | A two-line fix defers rewriting theme-resolved icons until existence validation, avoiding false missing-icon warnings. It awaits review with two unresolved comments and failing CLA/Ubuntu 26.04 checks. |
|
snapcraft (launchpad) issue #1655634 |
Unable to release classic snap to beta channel | ~stub | 3585d | keep open | 42 | 68 | 12 | Users are blocked when snapcraft release returns only “Package is not ready to be published”; maintainers traced this to the store’s InconsistentStateError, with no actionable reason or resolution yet. |
|
snapcraft (launchpad) issue #2080356 |
Two python3 parts using setuptools are always conflicting on core22 | ~gbeuzeboc | 785d | needs triage | 42 | 70 | 10 | Two python plugin parts always collide on core22 because each part's venv embeds its own install path in bin/activate*, __pycache__ and RECORD; only workaround is manual stage exclusions. No maintainer response. |
|
snapcraft issue #5060 |
Provide `status` output as a machine-readable format | lengau | 773d | keep open | 42 | 66 | 12 | Enhancement (triaged) to emit `snapcraft status` output in a machine-readable format such as JSON. Still open; implementation depends on general output-formatting support in craft-cli, tracked as canonical/craft-cli#278 (JIRA SNAPCRAFT-1098). |
|
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 (launchpad) issue #2051841 |
Plugs/Slots implicit assignment should be deprecated for `base: core24` | ~saviq | 1009d | needs triage | 42 | 70 | 14 | Configured top-level plugs/slots still create implicit core24 connections without warnings; only null-valued entries warn. The proposed deprecation or unused-connection warning remains untriaged. |
|
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-providers pr #723 |
feat(bases): make BaseName compatible with craft-platforms | lengau | 638d | close superseded | 42 | 10 | 2 | Adds BaseName convenience methods and DistroBase-compatible API types. Open for 603 days without reviews or reported CI and apparently superseded by craft-platforms#44. |
|
snapcraft (launchpad) issue #1613779 |
go plugin ignores the source-subdir keyword | ~jgrimm | 3733d | close resolved | 42 | 91 | 21 | Legacy Go plugin ignored source-subdir; later Go-module support replaced the GOPATH workflow and current craft-parts honors the configured source subtree. |
|
craft-application issue #320 |
Set the project environment in the Lifecycle Service | mr-cal | 925d | close resolved | 42 | 91 | 29 | Project-aware environment expansion from #101 is now in place, and current integration coverage verifies CRAFT_PROJECT_NAME and CRAFT_PROJECT_VERSION are exported during builds; the omission is resolved. |
|
snapcraft (launchpad) issue #1735004 |
Push issue with bad internet connection | ~hatari | 3264d | needs triage | 42 | 52 | 7 | Upload/push on a flaky connection fails with a bad gateway after the file reached the store; retrying then fails with 'binary_sha3_384: A file with this exact same content has already been uploaded'. Reporter asks for resumable uploads (returning an upload_id) and a workaround. No maintainer response or labels. |
|
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 (launchpad) issue #1637563 |
Add ability to automatically fetch Recommends from (a subset of) stage packages | ~3v1n0 | 3660d | needs triage | 42 | 43 | 6 | Feature request to let selected stage-packages pull their Debian Recommends automatically; it remains open, unlabelled, and untriaged after nearly 10 years. |
|
rockcraft issue #1171 |
investigate: why do we need a separate layer for the .rock metadata? | cjdcordeiro | 217d | keep open | 42 | 64 | 10 | Maintainer-led investigation into why /.rock/metadata.yaml is emitted as its own OCI layer and whether it can be squashed; work remains pending store-ingestion compatibility analysis. |
|
rockcraft pr #974 |
refactor: consolidate base-specific knowledge | tigarmo | 412d | keep open | 42 | 25 | 5 | Centralizes base-specific support, Pebble, and plugin behavior in one module. All tests pass, but lint/files fails and two review threads remain unresolved after 377 days. |
|
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 (launchpad) issue #1828252 |
i386 arch not enabled on amd64 build systems | ~popey | 2738d | close resolved | 42 | 92 | 25 | The i386-on-AMD64 limitation is implemented: current docs configure an i386 APT repository, and core24/core26 spread tests stage an i386 package in an AMD64 snap. |
|
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. |
|
snapcraft (launchpad) issue #2012290 |
Feature request: create log of build environment settings and flags | ~igorljubuncic-deactivatedaccount | 1326d | needs triage | 42 | 55 | 9 | Feature request for a build-environment log (OS/tool/compiler versions, CFLAGS, env overrides) via CLI flag. No maintainer response in 1292 days. Nearby SNAPCRAFT_BUILD_INFO manifest covers packages/project metadata but not compiler versions or effective build flags. |
|
snapcraft (launchpad) issue #1720207 |
snapcraft list-keys returns no keys, but the user has keys | ~elopio | 3325d | close resolved | 42 | 96 | 29 | Observed behavior is resolved: keys now displays registered remote-only key fingerprints separately from local keys; legacy list-keys was renamed and removed in Snapcraft 9. |
|
snapcraft (launchpad) issue #1662634 |
Please add snapcraft version key | ~ted | 3558d | needs triage | 42 | 58 | 11 | A snapcraft.yaml minimum-version key could produce a clear required-version message instead of a schema error; the proposal remains unimplemented and untriaged. |
|
snapcraft (launchpad) issue #1990298 |
fatal: detected dubious ownership in repository at '/root/project' when ran... | ~saviq | 1507d | close resolved | 42 | 90 | 20 | A reused LXD instance kept the first user's raw.idmap, making version: git builds fail for a later user; this was reproduced across core18/20/22 and fixed by a craft-providers update. |
|
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. |
|
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. |
|
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. |
|
snapcraft (launchpad) issue #1893850 |
Snapcraft doesn't inject itself into build VM if host rev doesn't change | ~kyrofa | 2256d | needs triage | 42 | 78 | 17 | An old, unlabeled report says sideloaded Snapcraft snaps with identical x1 revisions can leave a stale build-VM copy; the tracker has no follow-up or confirmed hash-based fix. |
|
charmcraft issue #913 |
Add `charmcraft fmt` command | sed-i | 1473d | keep open | 42 | 52 | 6 | A maintainer-endorsed feature request to add `charmcraft format` for semantics-preserving charm file formatting remains open pending agreement on scope and standards. |
|
rockcraft issue #496 |
Add support for `org.opencontainers.image.revision` annotation | carlcsaposs-canonical | 980d | keep open | 42 | 38 | 8 | Feature request to emit org.opencontainers.image.revision on packed rocks. Maintainer acknowledged the need but deferred implementation until the store exists, citing ambiguity with Craft's own revision concept; no code support yet. |
|
imagecraft issue #365 |
Clean the overlay | lengau | 134d | needs triage | 42 | 58 | 13 | Open, unlabeled maintainer request to automate pre-prime overlay cleanup, including APT caches and /tmp, /var/tmp, and /run; scope remains incomplete and untriaged. |
|
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. |
|
snapcraft (launchpad) issue #1792078 |
Snapcraft complain on a non-executable hook named `README.md` | ~brlin | 2976d | keep open | 42 | 65 | 17 | Snapcraft rejects a documentation-only snap/hooks/README.md; maintainers attributed the failure to snap check and proposed exempting non-executable README files, but no fix is recorded. |
|
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. |
|
snapcraft (launchpad) issue #1989149 |
File conflicts between parts should include files with identical contents | ~rpjday | 1519d | needs triage | 42 | 67 | 12 | Snapcraft still allows identical same-path files from different parts without warning; changing this collision behavior remains unresolved in craft-parts. |
|
charmcraft issue #1992 |
Document how `stage-packages` differs from installing a package on the system | lengau | 721d | needs triage | 42 | 57 | 14 | Documentation is still needed to distinguish build-time stage-packages from runtime apt installation; prerequisites #1839 and #1844 remain open, and current docs lack dedicated guidance. |
|
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. |
|
craft-parts pr #1588 |
Add Patches Directive | bryanfraschetti | 169d | needs review | 42 | 28 | 6 | Adds a `patches` part property to apply patch files over the source tree during pull. Approved once, but 6 unresolved comments, 13 failing checks (all test-common suites), and maintainer wants the hardcoded -p1 design revisited. |
|
charmcraft issue #2092 |
Create a reference page for the charm plugin | lengau | 657d | keep open | 42 | 91 | 29 | A maintainer-created documentation task remains open: add a standalone charm plugin reference page using uv as the template and replace the inline plugin details with a link. |
|
charmcraft issue #2225 |
Allow users to specify custom KNOWN_GOOD_PIP_URL for air-gapped CI/CD pipelines | TresSims | 598d | keep open | 42 | 68 | 17 | Feature request to let users override the hardcoded KNOWN_GOOD_PIP_URL (pip 24.1.1 from pythonhosted) via a --pip-url flag for air-gapped builds. Maintainer lengau replied it is unlikely soon and gave a nil-plugin wheel-swap workaround; still open. |
|
snapcraft (launchpad) issue #1666739 |
Content interface parsing too lenient | ~michihenning | 3544d | keep open | 42 | 61 | 6 | Current models partially validate content plugs but still accept arbitrary interface data; maintainers acknowledged the UX gap without settling on an implementation or owner. |
|
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. |
|
starflow pr #186 |
fix: add retry logic for snap installs across CI workflows | lengau | 44d | needs review | 42 | 76 | 21 | Maintainer-authored CI-only PR adding retry/backoff around snap installs (astral-uv, osv-scanner, codespell, ruff, shellcheck) in lint-python/scan-python/scan-golang, plus actionlint/prettier/shellcheck fixes. All checks green except macos-14. |
|
snapcraft (launchpad) issue #1807871 |
Does not warn/error when no apps are defined | ~ev | 2886d | needs triage | 42 | 72 | 19 | Requests early detection of snapcraft.yaml files without apps via lint and a warning or error; it is reproducible but remains unlabeled and unmaintainer-reviewed. |
|
craft-providers pr #824 |
feat: add a `get_base` factory function | lengau | 421d | needs review | 42 | 76 | 17 | Adds a public get_base factory with documentation and tests; all 13 CI checks pass, but after 386 days it remains unreviewed with no comments. |
|
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. |
|
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. |
|
snapcraft issue #5782 |
Error when validating the model if a `snapcraftctl` command is used | lengau | 413d | close resolved | 42 | 92 | 32 | snapcraftctl is now rejected during project-model validation for core26 override scripts by PR #5983; despite the issue remaining open, the requested behavior has shipped. |
|
craft-providers issue #212 |
Incorrectly handling SNAPCRAFT_MAX_PARALLEL_BUILD_COUNT | stolk | 1367d | keep open | 42 | 64 | 10 | SNAPCRAFT_MAX_PARALLEL_BUILD_COUNT not honored and Multipass instances hardcoded to 2 CPUs. Maintainer triaged; still unfixed in craft-providers (cpus=2 at multipass_provider.py:300), provider-side work split out to #531, snapcraft-side partly fixed in 8.4.4. |
|
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-cli pr #338 |
logger pollutes strings with white spaces | dariuszd21 | 555d | needs review | 41 | 28 | 8 | Fixes newline/tab corruption in ephemeral BRIEF logger output; the unreviewed branch is 399 commits behind main and has failing linters and Ubuntu 20.04 tests. |
|
snapcraft issue #4802 |
No debug information about conflicting files in staging error in the... | seb128 | 910d | needs triage | 40 | 82 | 17 | Launchpad shows only the brief staging-conflict failure while the conflicting parts and files remain in the execution log; this valid diagnostic gap awaits maintainer triage. |
|
snapcraft (launchpad) issue #1869542 |
snapcraft unable to find snap/snapcraft.yaml file | ~keshavnrj | 2413d | close stale | 40 | 18 | 2 | Snapcraft 3.11 on Multipass intermittently lost the project dir in the VM ('Could not find snap/snapcraft.yaml'), only fixable by `snapcraft clean`. Reproducer never supplied; reporter redirected it to the Multipass tracker and never followed up. |
|
rockcraft pr #1208 |
perf: lazy-load extension framework modules | lczyk | 175d | needs review | 40 | 72 | 16 | Lazy-loads extension framework modules to avoid eager imports of all six frameworks; CI green, awaiting maintainer review. |
|
fetch-service pr #501 |
draft: reorder some lxd calls to trigger launchpad behavior | tigarmo | 366d | keep open | 40 | 30 | 8 | Reorders LXD requests to trigger Launchpad behavior. The draft has been inactive for 332 days, has no reviews, and has a failing OSV-scanner check while core CI and tests pass. |
|
craft-providers issue #703 |
Allow pointing to daily or release buildd images for LXD | mr-cal | 735d | keep open | 40 | 76 | 19 | Enhancement to let LXD select Ubuntu buildd daily or release images, including through app configuration, remains open; the current remote is hard-coded per Ubuntu alias. |
|
rockcraft pr #1081 |
chore: use pathlib to interact with craft-parts | EdmilsonRodrigues | 283d | needs review | 40 | 70 | 22 | Adapts rockcraft's craft-parts calls to pathlib after upstream API changes; +10/-12 across 4 files, CI passing, awaiting review for 249 days. |
|
craft-parts issue #1023 |
`subprocess.run` emitting wrapper | mattculler | 622d | needs triage | 40 | 42 | 8 | Feature request for a general subprocess.run-style wrapper that logs the command and prefixes each output line with ':: '; existing os_utils.process_run is a starting point. Awaiting maintainer direction on placement; volunteer asked in July 2026. |
|
craft-parts issue #855 |
Add default building behavior to the documentation | dariuszd21 | 772d | keep open | 40 | 88 | 27 | Open, triaged documentation task to explain CMake's default Debug mode, show packaged applications how to select Release, and optionally cover equivalent Rust settings. |
|
craft-parts issue #1333 |
Consolidate `os-release` utils with other repositories | bepri | 408d | keep open | 40 | 78 | 14 | Replace Craft Parts' hand-rolled os-release parser with the distro library; maintainers agreed on this direction, but no implementation has landed and the work remains open. |
|
craft-actions issue #144 |
Packing rocks with 20.04 build-base fails on ubuntu-24.04 runners due to... | LoweRAM | 5d | needs triage | 40 | 80 | 29 | CI failure: legacy rock builds with ubuntu@20.04 build-base fail on ubuntu-24.04 runners due to kernel 7.0 AppArmor incompatibility. Root cause identified with workaround provided. |
|
charmcraft issue #1998 |
Add published date column to `charmcraft statsus` output | taurus-forever | 717d | keep open | 40 | 88 | 25 | Maintainer-acknowledged feature to show Charmhub's per-channel "when" value as a Published column in charmcraft status; current code still discards that field. |
|
craft-cli pr #481 |
feat: error early when help message is missing | cmatsuoka | 67d | needs review | 40 | 66 | 18 | Raises a CommandError during help generation when an argument lacks help text, fixing the IndexError from #242. Small 2-file diff (+52/-50), all CI checks green; awaiting maintainer review with 1 unresolved comment, inactive 32 days. |
|
snapcraft issue #4697 |
The partial organize operations of parts are missing | LaiderLai | 954d | close resolved | 40 | 55 | 15 | Organize globs using ${SNAPCRAFT_ARCH_TRIPLET} silently matched nothing on core20 cross-builds because the variable resolved to the host triplet; root cause fixed pre-8.0.0 by #4313, core20 since dropped |
|
craft-platforms issue #189 |
Merge Starbase every week | lengau | 367d | needs triage | 40 | 45 | 7 | Maintainer request for a scheduled + manually-dispatchable GitHub Action merging canonical/starbase upstream, using Copilot to decide which changes to take. Unlabelled, no comments, no implementation found. |
|
snapcraft (launchpad) issue #1813925 |
"version: 0.2" returns confusing error message (trunk) | ~gerboland | 2836d | needs triage | 40 | 84 | 19 | Unquoted YAML numeric versions such as 2.11 are parsed as floats and rejected with a misleading snap-version error; quoting works, but compatibility or clearer messaging remains unaddressed. |
|
craft-application issue #1105 |
remote-build should be asynchronous by default | steinbro | 133d | keep open | 40 | 55 | 12 | Maintainer proposal to make remote-build non-blocking: exit after submitting the job, print a status URL and follow-up command, with an opt-in --detach/--bg flag. Discussed and converging, not implemented. |
|
snapcraft (launchpad) issue #2066040 |
snapcraft.yaml validation errors are presented in a very user unfriendly way | ~jamesh | 902d | needs triage | 40 | 74 | 20 | A core24 snapcraft.yaml error leaked raw Pydantic details; current code has friendlier validation paths, but the exact regression and its resolution are not confirmed. |
|
snapcraft issue #5171 |
home interface plug attribute "read: all" triggers ValidationError | florcabral | 698d | needs triage | 40 | 65 | 14 | Untriaged report that Snapcraft rejects app-level home plug attributes such as read: all despite documented snapd support; the reproducer contains conflicting list and scalar syntax. |
|
snapcraft (launchpad) issue #2158699 |
Github build randomly inventing stage-packages | ~t-a-k | 128d | needs triage | 40 | 38 | 5 | Snapcraft 9.0.0 core26 GitHub builds intermittently downloaded and extracted undeclared packages; two affected builds are linked, but the report lacks maintainer triage and a reproducible failure. |