Showing 100 of 1910 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
craft-parts issue #1644 |
Add explanation for how `organize` works | lengau | 113d | keep open | 38 | 84 | 24 | A maintainer-requested explanation of organize is still missing; a contributor volunteered a focused page and a correction to the existing build-area-to-stage wording. |
|
craft-providers issue #795 |
Verify present addresses when adding a remote | bepri | 450d | keep open | 38 | 68 | 16 | Enhancement remains open: RemoteImage.add_remote checks only remote_name, so an existing address under another LXC remote name is not detected; address-level handling and tests are missing. |
|
charmcraft pr #2669 |
tests: add reproducer for pack retaining deleted files between builds (#710) | lengau | 198d | needs review | 38 | 48 | 10 | Reproducer test for #710 (pack retains deleted files) plus Copilot-generated PartsLifecycle._clean_stale_parts workaround; +112/-310, 4 files, open 163 days, 0 reviewers, snap-tests and title-policy checks failing. |
|
charmcraft issue #2578 |
docs: The usage parameters show up as None | famulu | 258d | keep open | 38 | 90 | 27 | Generated `charmcraft release` reference documentation renders required arguments as `<None>` because the docs generator uses null argparse metavars; the triaged issue remains unresolved. |
|
charmcraft issue #2435 |
docs: permission docs are missing | beliaev-maksim | 428d | keep open | 38 | 64 | 13 | The login documentation omits valid --permission values; the maintainer confirmed the list is store-controlled and is awaiting a decision on a durable documentation source. |
|
snapcraft pr #5568 |
build: correctly set version of dev builds | bepri | 503d | close stale | 38 | 8 | 2 | Updates Snapcraft's development snap versioning, but the unreviewed two-file change has been inactive for 391 days and still has failing build and OSV-scanner checks. |
|
snapcraft issue #5770 |
docs: dump plugin docs don't provide enough information to even get started | artiepoole | 420d | keep open | 38 | 72 | 21 | Docs request: dump plugin reference lacks examples and key descriptions. Partly addressed by merged craft-parts PR #1547 and the include_files how-to, but the Keys section still has no per-key type/default/description; maintainer asked about reader context. |
|
snapcraft issue #5624 |
Add a pydantic validator for common-id | mr-cal | 476d | keep open | 38 | 72 | 15 | Enhancement to add a pydantic validator for App.common_id enforcing the AppStream desktop-app ID format, so bad IDs fail before a build environment starts. Still open at HEAD; two implementation PRs (#5625 closed unmerged, #5974 stalled) have failed so far. |
|
snapcraft issue #5517 |
remote build: internal error from 400 response | mr-cal | 527d | keep open | 38 | 84 | 21 | Remote builds expose an internal error when Launchpad returns HTTP 400 while pushing the repository; the triaged bug remains open and likely requires a Craft Application fix. |
|
snapcraft issue #4965 |
Document using Snapcraft under WSL | lengau | 813d | keep open | 38 | 58 | 13 | Docs request: split How-to > Set up Snapcraft into Linux and WSL sections covering systemd, snapd, reboot and install steps. Triaged (CRAFT-3231); mr-cal wants a WSL smoketest before endorsing. Restructure not yet done. |
|
snapcraft issue #4344 |
Treat the gadget.yaml like other snap meta files | dilyn-corner | 1161d | keep open | 38 | 72 | 14 | Enhancement to require gadget.yaml in snap/gadget.yaml instead of the project root. Triaged (CRAFT-3264); still unimplemented — both setup_assets.py (core22) and package.py (core24+) still read gadget.yaml from the project root. |
|
craft-application issue #922 |
Reference documentation about services in general | lengau | 406d | keep open | 38 | 76 | 19 | Triaged documentation work to broaden and rename the services reference, clarify what a service is, and make AppService secondary; the current app.rst remains AppService-only. |
|
craft-application issue #685 |
overlayfs tests break on plucky | lengau | 597d | needs triage | 38 | 74 | 12 | Plucky's AppArmor profile denies fuse-overlayfs mounts, breaking a lifecycle integration test; the report has a reproducer and audit log, but no triage, confirmed root cause, fix, or implementation link. |
|
craft-application issue #338 |
`pack` command gives wrong help message and doesn't support packing a directory | mr-cal | 918d | close resolved | 38 | 76 | 19 | Resolved: commit 13230eda removed the bogus pack part argument, and 309aa73b added a project-loading override for application-specific directory pack commands. |
|
craft-cli issue #68 |
Better output information when requesting help for a command with bad... | facundobatista | 1704d | keep open | 38 | 92 | 26 | Command help still rejects extra command arguments; help close --bad-args should select close and render its help instead of reporting too many parameters. |
|
starflow issue #48 |
Add publisher worflows | upils | 608d | keep open | 38 | 58 | 10 | Maintainer task to move/adapt a generic release-publish.yaml reusable workflow from the craft libs into starflow. Not yet implemented; no release-publish workflow exists in .github/workflows. One comment questions the value of release-drafter. |
|
craft-parts issue #427 |
Using `source-subdir` results in `No such file or directory` | sed-i | 1287d | close not a bug | 38 | 90 | 19 | Documented behavior: source-subdir sets the plugin build location, but override-build runs from the build root; callers must cd into the subdirectory themselves. |
|
snapcraft (launchpad) issue #1813942 |
`snapcraft clean <part>` doesn't ensure the project is mounted | ~saviq | 2836d | needs triage | 38 | 82 | 18 | Snapcraft 3.1 clean <part> fails in Multipass after manually unmounting the project; the report remains unlabelled and untriaged with no activity since submission. |
|
snapcraft (launchpad) issue #1660614 |
snapcraft's nodejs plugin does not refresh the global, user cache before... | ~gvancuts | 3565d | close resolved | 38 | 89 | 28 | The nodejs plugin's forced npm cache policy was superseded by configurable npm flags in #2038, and the legacy plugin was subsequently moved out in #2984; the issue remains open. |
|
snapcraft (launchpad) issue #1841892 |
snapcraft options are position-dependent | ~saviq | 2625d | needs triage | 38 | 62 | 11 | Request to make --use-lxd position-independent or reject it before a lifecycle command; still open and untriaged, while current code attaches --use-lxd to lifecycle command parsers. |
|
craft-parts issue #838 |
Validate snapd payload | sergiusens | 787d | needs triage | 38 | 62 | 16 | Validate snapd API JSON payloads in craft_parts/packages/snaps.py; raw json()["result"] access is still unvalidated, so TypeError: 'NoneType' object is not subscriptable can still surface. Maintainer-filed, no labels, no comments, untriaged. |
|
charmcraft issue #2087 |
Better document how platform names work | lengau | 657d | close resolved | 38 | 82 | 25 | Platform-name documentation now covers valid arbitrary names, recommended names, multi-base conventions, and shorthand requirements, resolving the original documentation gap. |
|
charmcraft issue #1371 |
Output a nice error message when docker breaks lxd | lengau | 1094d | needs triage | 38 | 63 | 13 | LXD launch timeouts lack guidance when Docker has changed firewall forwarding rules, despite a known iptables workaround being used in Spread configuration |
|
rockcraft pr #758 |
remove chisel part from Rockcraft's snap | linostar | 715d | needs review | 38 | 42 | 10 | Removes Chisel packaging from Rockcraft’s snap after craft-parts gained equivalent support. The prerequisite merged, but this 413-day-idle PR has no review or CI results. |
|
charmcraft issue #2423 |
Fix the CI for 2.7 | lengau | 447d | close resolved | 38 | 88 | 26 | CI repair for the 2.7 hotfix branch was completed by merged PR #2424 after dependency bugfix PR #2422; the tracking issue remains open. |
|
craft-providers issue #213 |
Use alternate lxd profiles | cmatsuoka | 1360d | keep open | 38 | 45 | 9 | Enhancement request (by maintainer cmatsuoka) to allow alternate LXD profiles, e.g. CRAFT_PROVIDERS_LXD_PROFILE(S), for devs with multiple pools. mr-cal replied with design questions (plural list, global vs per-app) still unanswered; no code implements profiles. |
|
rockcraft issue #1280 |
Docs: Tutorials assume an `amd64` host which causes `platforms:` and `.rock`... | minulo | 126d | keep open | 38 | 85 | 23 | Docs bug: hello-world, pyfiglet and Node.js tutorials hardcode `amd64` in `.rock` filenames/skopeo commands, breaking copy-paste on arm64 hosts. Maintainer assigned; fix in open PR #1289, not yet merged. |
|
craft-application pr #1162 |
fix: fail fast on unsupported lifecycle bases | lengaubot | 79d | needs review | 38 | 76 | 25 | Reorders the unsupported-base check ahead of lifecycle initialization to avoid an unnecessary LXC profile lookup; all completed checks pass, while several remain pending and review is pending. |
|
snapcraft issue #6270 |
docs: remove references to core18 | medubelko | 160d | keep open | 38 | 62 | 14 | Maintainer-filed docs cleanup to strip core18 from non-release docs once Snapcraft 9 is stable (now true: 9.0/9.1 are current). Triaged and volunteer PR #6292 open, but core18 references remain in specify-a-base, list-extensions, change-bases and example recipes. |
|
craft-providers issue #969 |
BuilddBaseAlias enum lookup raises bare ValueError — should raise a typed error | tonyandrewmeyer | 156d | close resolved | 38 | 94 | 28 | Resolved: compatibility checks now catch unknown host and guest Ubuntu VERSION_IDs and skip validation instead of leaking BuilddBaseAlias ValueError; no typed error was added. |
|
craft-providers issue #942 |
Feature Request for custom software mirror | Kxuan | 203d | keep open | 38 | 58 | 13 | Requests a craft-providers env var (like legacy SNAPCRAFT_BUILD_ENVIRONMENT_PRIMARY_MIRROR) to point Ubuntu build instances at a custom APT mirror; unimplemented, 0 comments, no maintainer response, still untriaged. |
|
craft-providers pr #1011 |
chore: reduce verbosity of timer logging | cmatsuoka | 68d | needs review | 38 | 45 | 14 | Changes the LXD instance heartbeat from 3 to 30 seconds and removes per-update timer logging; one slow test is failing and three review comments remain unresolved. |
|
starflow pr #189 |
ci: Add starbase smoketest workflow | lengau | 35d | needs review | 38 | 68 | 13 | Adds .github/workflows/smoketest.yaml (130 lines) that pushes bot/smoketest/starflow-<n> to canonical/starbase, opens a draft PR there and comments the link; needs a STARBASE_TOKEN fine-grained PAT. All CI green (incl. zizmor), verified live via starbase#607-609, 1 unresolved comment, awaiting maintainer review. |
|
rockcraft issue #1126 |
remote-build fails with build-base devel | lengau | 244d | keep open | 38 | 74 | 11 | Remote builds fail during Launchpad build creation with the documented build-base: devel value; the valid open report points to craft-application or Launchpad and awaits an upstream fix. |
|
charmcraft issue #2233 |
charmcraft should complain if the charm contains a bundle | PietroPasotti | 590d | needs triage | 38 | 70 | 19 | Feature request: charmcraft pack should error/warn when the produced charm contains a bundle.yaml, since juju deploy then deploys the bundle instead of the charm. Clear repro, but no maintainer triage or labels. |
|
craft-providers issue #383 |
bumping the compatibility tag should be more robust | mr-cal | 1176d | keep open | 38 | 84 | 22 | Tests still hardcode buildd-base-v7 while production derives it from Base.compatibility_tag, leaving compatibility-tag bumps vulnerable to inconsistent test updates. |
|
snapcraft (launchpad) issue #1815358 |
python package not updating during snap creation | ~falko-o | 2825d | needs triage | 38 | 62 | 15 | Python parts can produce snaps with stale package versions; the report needs maintainer triage into expected git-source behavior, lifecycle invalidation, or a historical plugin bug. |
|
snapcraft (launchpad) issue #1828600 |
Unicode non-ascii characters in channel specification cause a 500 response... | ~matiasb | 2736d | needs triage | 38 | 86 | 22 | A surrogate-escaped non-ASCII channel reproducibly causes a Store 500. The exact command and traceback are present, but the report remains open, unlabeled, and without maintainer triage. |
|
snapcraft (launchpad) issue #2039971 |
Add support for _daemon_ as a valid system-username in snapcraft.yaml | ~morrisong | 1112d | close resolved | 38 | 95 | 31 | Snapcraft formerly rejected `_daemon_` as a system username; current validation accepts arbitrary usernames, resolving the reported parsing failure. |
|
snapcraft (launchpad) issue #1848732 |
--shell does not make snapcraftctl available | ~racb | 2575d | needs triage | 38 | 67 | 18 | --shell and --shell-after reportedly omit snapcraftctl from the build environment; current packaging includes a compatibility wrapper, but the unversioned report remains untriaged. |
|
snapcraft (launchpad) issue #1852329 |
appstream parsing fails when comments exist | ~ken-vandine | 2550d | close resolved | 38 | 85 | 29 | AppStream description parsing broke on XML translator comments; fixed by commit e4dc754f2 (snapcraft#2832), which strips comments in the XSLT and adds a TRANSLATORS-comment regression test. Launchpad bug still open. |
|
snapcraft (launchpad) issue #1922490 |
conda plugin, use pkg on a custom channel | ~ycheng-twn | 2041d | needs triage | 38 | 58 | 16 | Feature request: conda plugin exposes only conda-packages/conda-python-version/conda-miniconda-version and has no way to add channels (e.g. conda-forge), so packages from custom channels cannot be installed |
|
debcraft issue #140 |
Handle unquoted multi-arch: no | cmatsuoka | 193d | needs triage | 38 | 62 | 17 | Unquoted YAML no becomes a boolean and fails multi-arch validation with a generic error; the fix is undecided between clearer guidance and accepting false as an alias. |
|
craft-application issue #1015 |
Improve craft tool dev experience with destructive mode | bepri | 261d | needs triage | 38 | 65 | 10 | Root-run destructive packing leaves root-owned lifecycle directories, blocking later non-root packing; the UX request remains untriaged with no selected solution. |
|
craft-providers issue #858 |
Error when setting up almalinux test | lengau | 335d | close resolved | 38 | 87 | 19 | AlmaLinux unit setup exposed a leaked InstanceTimer thread exception; cleanup was later fixed by #996, leaving this open issue apparently resolved. |
|
snapcraft (launchpad) issue #1827217 |
create-key without a passphrase is not possible using multipass | ~0-luke | 2745d | needs triage | 38 | 42 | 7 | Untriaged report that `snapcraft create-key` cannot accept an empty passphrase in Multipass; pressing Return returns to password confirmation, with details only in an external paste. |
|
snapcraft (launchpad) issue #1903046 |
Progressive release stops showing metrics when set to 100% target | ~noise | 2191d | keep open | 38 | 68 | 18 | snapcraft status hides progressive-release metrics once a release hits 100% (store nullifies percentage). Store-side API now returns progressive.current-percentage for all releases; client still only renders it for in-progress progressive releases. |
|
snapcraft (launchpad) issue #1844801 |
Organize has different move behavior when using wildcard | ~merlijn-sebrechts | 2603d | needs triage | 38 | 65 | 7 | Wildcard organize keys still preserve a matched directory name while explicit keys merge its contents; the reproducible report has no maintainer triage or discussion. |
|
snapcraft (launchpad) issue #1884683 |
snapcraft fail app | ~alandecunto | 2327d | close resolved | 38 | 86 | 25 | Snapcraft 2.43.1 crashed on missing executable /bin/Sastreria; newer code added invalid-command handling, and the maintainer says the Snapcraft snap fixes it, but no retest was posted. |
|
snapcraft (launchpad) issue #1911375 |
Priming warning: "not a dynamic executable" with cross build | ~woodrow-shen | 2123d | keep open | 38 | 72 | 11 | Cross-build priming emits misleading ELF/library-linter warnings; the maintainer identified disabling library checks as the needed fix, while current docs provide only a lint-disable workaround. |
|
snapcraft (launchpad) issue #1646081 |
Gadget snap cannot be built twice | ~zyga | 3627d | close resolved | 38 | 95 | 31 | Second gadget-snap builds failed on gadget.yaml versus prime/meta/gadget.yaml; fixed by PR #3767 (c06e4df03). |
|
snapcraft issue #5614 |
Expose the build base name in snapcraft.yaml | bschimke95 | 478d | keep open | 38 | 74 | 19 | Enhancement request to expose the build base name (e.g. core22) as an environment/project variable usable in snapcraft.yaml env and parts, avoiding hardcoding. Triaged; mr-cal agreed an env var is better than hardcoding; tracked internally as SNAPCRAFT-1187. Not implemented. |
|
snapcraft (launchpad) issue #1666161 |
Can’t dry-run a build to check snapcraft.yaml | ~mpt | 3545d | keep open | 38 | 68 | 13 | Requests a build-free snapcraft.yaml validation mode; the reporter narrowed the initial goal to schema validation, but no dedicated dry-run command or resolving change is evident. |
|
snapcraft (launchpad) issue #1810915 |
snapcraft can't tell when multipass is installed but disabled | ~popey | 2858d | needs triage | 38 | 66 | 14 | Snapcraft misclassified an installed but disabled Multipass snap as missing, prompting installation before failing. The 2018 report remains untriaged, and its behavior needs validation against the current provider architecture. |
|
craft-parts issue #1301 |
Chisel integration test failing on ppc64el | lengau | 416d | keep open | 38 | 65 | 9 | Chisel integration test fails on ppc64el with an archive digest mismatch. CI is only green because the test carries a skipif for ppc64el referencing #1301; the underlying chisel/manifest problem is still unaddressed. |
|
snapcraft (launchpad) issue #1830788 |
Electron apps won't cross-compile for armhf (raspberry pi) | ~zane470 | 2718d | close stale | 38 | 35 | 2 | Snapcraft 2.43.1 cannot armhf cross-compile Electron snaps using desktop-gtk3; the implicated plugin stack and core18 legacy path have since been removed. |
|
craft-parts issue #888 |
Create a plugin template and docs for how to write a plugin | lengau | 740d | close resolved | 38 | 65 | 14 | Feature request to add a plugin template and docs for writing Craft Parts plugins. The docs were delivered: create_plugin.rst how-to (PR #928) and document-plugin.rst template, both shipped in the docs index. |
|
rockcraft issue #579 |
fork/exec error when building Go rock with the 24.04 build-base | gruyaume | 895d | close not a bug | 38 | 86 | 16 | Bare Go rocks on ubuntu@24.04 need base-files_lib for the usrmerged ELF-loader paths. The reporter confirmed that adding the slice fixes the fork/exec failure. |
|
rockcraft issue #608 |
links that are emitted to the console must be tested | cjdcordeiro | 864d | keep open | 38 | 68 | 12 | Rockcraft hardcodes many documentation slugs used in console errors, but lacks automated validation that their URLs remain valid; using intersphinx is under consideration. |
|
rockcraft issue #555 |
Emit a warning to stdout when `$CRAFT_PART_INSTALL` is empty after `override-build` | sed-i | 930d | needs triage | 38 | 58 | 13 | Requests a warning when override-build leaves CRAFT_PART_INSTALL empty; it remains open, unlabeled, and untriaged, with only an automated Jira-sync comment. |
|
snapcraft (launchpad) issue #1883265 |
"loadinternal: cannot find runtime/cgo" with base: core20, go.mod but no cgo in code | ~jdstrand | 2337d | keep open | 38 | 90 | 20 | Core20 Go plugin builds with CGO_ENABLED=0 still invoke external linking and fail; removing the plugin-added -linkmode=external succeeds, but no root cause or fix is recorded. |
|
snapcraft (launchpad) issue #1948980 |
User specific font configuration does not survive snap updates | ~gunnarhj | 1835d | needs triage | 38 | 35 | 7 | Snaps ignore $HOME fontconfig config and rewrite fonts.conf per revision; reporter later narrowed it to fonts.conf edits (conf.d files do persist) and suggests documenting the workaround. Untriaged since Nov 2021. |
|
craft-platforms issue #45 |
Add go architectures and a way to convert between deb arches and go arches | lengau | 785d | keep open | 38 | 75 | 20 | Maintainer request to add Go architecture support (enum plus deb<->Go conversion) to craft_platforms, replacing rockcraft's architectures.py mapping. Still unimplemented; only an automated Jira sync (CRAFT-3380) comment exists. |
|
snapcraft (launchpad) issue #1670209 |
when building a classic snap, plugins cannot access value of LDPATH | ~mwhudson | 3532d | needs triage | 38 | 49 | 8 | Classic-snap custom plugins cannot obtain generated LDPATH linker flags; the report is unlabelled and unanswered, and its legacy API predates the craft-parts architecture |
|
craft-parts issue #1290 |
Unnecessary priming of dependency when priming a part | upils | 420d | keep open | 38 | 76 | 19 | Triaged bug report reproduces dependency foo being primed when bar is primed; current code still maps Step.PRIME to Step.PRIME, while a maintainer questions whether dependencies must be primed. |
|
imagecraft issue #95 |
Incorporate `mount` and `umount` from `imgmount.py` into `imagecraft` itself | mattculler | 622d | needs triage | 38 | 48 | 9 | Feature proposal to package tools/imgmount.py as imagecraft.mount and imagecraft.umount entrypoints; it remains unimplemented and untriaged, with the exact CLI design awaiting maintainer direction. |
|
rockcraft issue #371 |
Add a spread test for build-secrets | tigarmo | 1123d | keep open | 38 | 84 | 24 | Build-secrets Spread coverage is still missing. Its craft-application prerequisite (#100) was implemented in #104, and rockcraft now requires craft-application >=7.3.0. |
|
charmcraft issue #2854 |
charmcraft pack ignores -o option in version 4.4.1 | jw-can | 70d | needs triage | 38 | 68 | 17 | charmcraft 4.4.1 `pack -o .` does not place the charm in the -o folder when --project-dir points outside cwd. Exact repro given, but reported output location unspecified. Unlabelled, no maintainer response in 36 days. |
|
snapcraft (launchpad) issue #1848038 |
HACKING.md does not explain how to run snapcraft from a source tree | ~racb | 2579d | keep open | 38 | 82 | 27 | Source-tree execution remains undocumented: HACKING.md is gone, current contributor guides cover setup and tests, and a 2019 comment requested documentation for destructive mode. |
|
craft-platforms issue #125 |
Multiple platforms with `build-for: all` might need to be considered an error | lengau | 573d | keep open | 38 | 32 | 5 | Question whether multiple platforms with build-for: all must error. Generic planner still raises AllSinglePlatformError, but maintainers disagree on whether validation belongs here or in consumer schemas; Launchpad compatibility unresolved. |
|
snapcraft (launchpad) issue #1804682 |
Warn when python plugin is used for non-setuptools project | ~merlijn-sebrechts | 2905d | needs triage | 38 | 66 | 15 | Requests a clear diagnostic for bare or unsupported Python projects; the reported single-script case fails late with FileNotFoundError, but current behavior needs triage. |
|
snapcraft (launchpad) issue #1784372 |
snapcraft and other snap commands don't support a --debug for behind the... | ~rharding | 3020d | close resolved | 38 | 76 | 20 | Request for verbose diagnostics when Snapcraft store commands hang; modern Snapcraft provides --verbosity=debug across commands, and --trace now redirects users to that mode. |
|
craft-parts issue #1328 |
Clean up return of `install_packages` | bepri | 408d | needs triage | 38 | 64 | 12 | Cleanup remains open: install_packages still returns package manifests that internal callers discard; PR #1671 removed the related list_only parameter but not the return contract. |
|
craft-parts issue #1362 |
stage filter not applied to overlay content | upils | 391d | keep open | 38 | 64 | 13 | Enhancement to support '(overlay)/' prefixes in the stage filter so content organized into the overlay can be filtered during the stage step. Triaged; maintainers still debating bug vs feature, no implementation yet. |
|
snapcraft (launchpad) issue #1732501 |
it's not possible to close a channel for only one architecture | ~elopio | 3277d | keep open | 38 | 64 | 9 | Architecture-specific channel closing remains unimplemented and open: snapcraft close still targets all architectures, while the Store API has no scoped close operation. |
|
craft-parts issue #1546 |
Support download part source from FTP URLs | brlin-tw | 205d | needs triage | 38 | 62 | 12 | Feature request to support downloading part sources from FTP URLs; the code still raises NotImplementedError and the issue has no maintainer triage or comments. |
|
charmcraft issue #2806 |
Document need to recreate token due to Ubuntu One migration (invalid macaroon) | rene-oromtz | 107d | keep open | 38 | 72 | 22 | Docs request: warn that Candid-issued macaroons become invalid after the Ubuntu One auth migration (#2760), so tokens must be recreated; triaged, tracked as CHARMCRAFT-719, awaiting a docs change. |
|
craft-parts issue #1282 |
dotnet-v2 plugin integration tests fail on arm64 | lengau | 421d | close resolved | 38 | 82 | 18 | The ARM64 dotnet-v2 failure was caused by executing an incompatible staged SDK binary; subsequent test and CI changes removed that path and added ARM coverage. |
|
snapcraft (launchpad) issue #1826262 |
Error: The part has run through its entire lifecycle | ~saviq | 2752d | keep open | 38 | 76 | 9 | Snapcraft 3.5 fails incremental classic-mode rebuilds after adding a snap source to Multipass, reporting that the part exhausted its lifecycle; logs were supplied and another person reproduced it. |
|
snapcraft (launchpad) issue #2103599 |
Snap installation fails though library dependencies are in snap | ~maciek-borzecki | 596d | needs triage | 38 | 67 | 13 | Keepalived’s riscv64 snap cannot find staged libipset and libnetsnmpmibs. An LD_LIBRARY_PATH workaround emerged, but the cross-architecture fix and ownership remain unresolved. |
|
snapcraft (launchpad) issue #1778701 |
parse-info-all bool | ~apachelogger | 3054d | keep open | 38 | 52 | 7 | Requests automatic discovery of all AppStream metadata; current Snapcraft still requires explicit parse-info paths, and metadata-selection semantics remain unresolved. |
|
snapcraft (launchpad) issue #1865230 |
snapcraft --use-lxd should have message about requring sudo | ~haydenb | 2442d | needs triage | 38 | 35 | 6 | LXD setup can leave a non-group user with an inaccessible socket, but the reporter never confirmed lxd-group membership; requiring sudo was rejected. |
|
snapcraft (launchpad) issue #1777659 |
Snapcraft version string doesn't allow certain characters | ~popey | 3061d | keep open | 38 | 60 | 4 | Snapcraft still rejects upstream-style 2018_931-01 because underscores are outside snap version grammar; the misleading "just for humans" wording remains and grammar changes span snapd, review-tools, and snapstore. |
|
snapcraft (launchpad) issue #2081962 |
Core24 accepts integer version, Core22 does not and gives obscure error | ~nteodosio | 771d | needs triage | 38 | 84 | 21 | Core22 crashes with a Pydantic traceback for an unquoted numeric version that Core24 accepts; the report remains open and untriaged. |
|
snapcraft (launchpad) issue #2048898 |
No helpfull message when command doesn't exist | ~gbeuzeboc | 1030d | close resolved | 38 | 88 | 23 | Snapcraft gave only a generic pack failure when an app command was absent from the staged snap; commit 44930f709 and PR #3321 later added command-not-found validation. |
|
snapcraft issue #4328 |
Hard to see what the causes an error for a 404 network error | sergiusens | 1175d | close resolved | 38 | 90 | 27 | Source downloads now report 404s with the failing URL instead of an opaque generic network error. |
|
snapcraft (launchpad) issue #1771218 |
Could not execute process 'rustc -vV' (never executed) | ~mmacedoeu | 3097d | needs triage | 38 | 28 | 5 | An inactive 2018 report says Travis could not find rustc after Rust installation; it lacks maintainer assessment, copied diagnostics, and a current reproducer. |
|
snapcraft (launchpad) issue #1859424 |
Multipass/VMs by default discourages newcomers | ~lool | 2488d | keep open | 38 | 32 | 5 | Feature request: make Snapcraft's Multipass/VM-by-default build path more newcomer friendly (prominent messaging, KVM/nested-virt detection, LXD fallback, docs); partially addressed by health checks, docs, and LXD default on Linux |
|
rockcraft issue #190 |
Improve output when different parts list the same file | arturo-seijas | 1365d | needs triage | 38 | 58 | 11 | Collision diagnostics need clearer part, file, and conflict-type details; craft-parts now reports parts and files, but still groups content and permission clashes together. |
|
snapcraft (launchpad) issue #1886388 |
Parameterized builds are required for snapcraft build | ~muthiahn | 2313d | needs triage | 38 | 47 | 6 | Request for user-defined build parameters that can select a part's Git branch; it remains open, unlabelled, and untriaged with no maintainer response. |
|
charmcraft issue #1598 |
Linter to warn if the summary field is over 78 characters | lengau | 968d | needs triage | 37 | 88 | 24 | Requested summary-length warning remains unimplemented: summaries are capped at 200 characters, and no checker warns above 78; only an automated Jira-sync comment exists. |
|
snapcraft (launchpad) issue #1769519 |
Setting the snapcraft.yaml version field to 'git' produces undocumented and... | ~njmcphail | 3105d | keep open | 36 | 64 | 14 | Documentation now includes version: git examples, but GitSource.generate_version() still lets tags containing characters such as underscores produce invalid snap versions that build successfully and fail installation. |
|
charmcraft issue #1980 |
Check for major charm library updates | lucabello | 735d | keep open | 36 | 66 | 12 | Add major LIBAPI detection to charmcraft fetch-libs for CI. The request remains valid but low priority; fetching is currently limited to configured API versions, and a workaround exists. |
|
rockcraft issue #953 |
Enable the maven plugin spread test for Ubuntu 25.10 | lengau | 433d | keep open | 36 | 78 | 21 | Triaged task to add Maven spread coverage for Ubuntu 25.10; current code supports the base, but no evidence confirms the test was enabled after the ROCKS-2054 dependency. |
|
snapcraft (launchpad) issue #1666366 |
Need --autoclean or similar | ~michihenning | 3545d | keep open | 36 | 72 | 12 | Requested opt-in automatic cleanup of stale lifecycle steps. The maintainer agreed with the opt-in approach, but current Snapcraft exposes no autoclean option or equivalent. |
|
craft-application issue #99 |
Means to reduce duplication of plugin fields | sed-i | 1253d | keep open | 36 | 74 | 11 | Maintainer-acknowledged request to support top-level YAML definitions and anchors for reusing repeated part source fields; implementation awaits upstream framework work tracked as CRAFT-2612. |
|
snapcraft (launchpad) issue #1825792 |
Support `no-install` build attribute in cmake plugin | ~brlin | 2754d | needs triage | 36 | 72 | 21 | CMake parts without an install target are unsupported; the current craft-parts plugin still unconditionally runs the install target, and the request remains untriaged. |
|
snapcraft (launchpad) issue #1843404 |
snapcraft export-login doesn't provide meaningful error messages when an... | ~johanlorenzo | 2613d | keep open | 36 | 84 | 19 | export-login masks Store 4xx/5xx details behind “Failed to get macaroon”; maintainer analysis confirms useful API errors are available, but no fix is evidenced. |
|
snapcraft (launchpad) issue #1982401 |
snap-based programs complain about locale, permission | ~mardy | 1569d | keep open | 36 | 84 | 18 | Desktop snap launchers emit bogus locale warnings and read an AppArmor-blocked BASH_ENV file. The .bashrc cause is confirmed, but no fix is recorded; locale tracking was split into #1983399. |
|
snapcraft (launchpad) issue #1670749 |
classic confinement requires manually setting PATH and PYTHONPATH | ~corey.bryant | 3530d | close not a bug | 36 | 55 | 9 | Classic snaps may need explicit PATH/PYTHONPATH, but the reporter and snappy team said this was by design; current metadata handling intentionally omits injected PATH and library paths. |