Showing 100 of 1936 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
snapcraft (launchpad) issue #1778719 |
appstream support lacking provided ids (impairing backwards compat) | ~apachelogger | 3055d | keep open | 35 | 40 | 4 | AppStream extractor and snap.yaml `common-id` accept only one id, ignoring `<provides><id>` legacy ids used when desktop files are renamed; maintainers say it needs snapd/store support and rediscussion. Still unimplemented. |
|
charmcraft issue #919 |
unpublish command and revision history for channel | jneo8 | 1464d | keep open | 35 | 33 | 5 | Feature request for `charmcraft revision <charm> --channel` (per-channel release history) and an `unpublish` command. Maintainer agreed it needs Charmhub backend support; neither option exists in code (revisions command has no --channel, no unpublish command). |
|
craft-parts issue #659 |
Docs: Document/cross-reference working directory and environment variables... | thp-canonical | 1001d | needs triage | 35 | 84 | 22 | Open, untriaged documentation gap: Part properties does not cross-reference step environments, leaving override-pull/build/stage/prime working directories and variables hard to find. |
|
snapcraft (launchpad) issue #1922140 |
unable to run on centos 7 VM | ~anonymouse67 | 2046d | needs triage | 35 | 60 | 16 | Untriaged CentOS 7 locale failure prevents Snapcraft 4.6 from starting; no maintainer response or resolution is recorded. |
|
craft-parts pr #1673 |
ci: run tests on Ubuntu 26.04 | lengau | 79d | needs review | 35 | 55 | 14 | Adds CI testing on Ubuntu 26.04 LTS with Python 3.14. Approved by 2 reviewers with 0 unresolved comments, but CI has failing checks (OSV-scanner, minimum dependencies, ubuntu-22.04 fast tests). |
|
snapcraft issue #6482 |
feat: pause progressive release | medubelko | 29d | keep open | 35 | 80 | 21 | Feature request to add CLI support for pausing progressive releases, currently only possible via the Snap Store API. Triaged with an internal ticket (SNAPCRAFT-1401). |
|
craft-store issue #279 |
Add a login client | mr-cal | 599d | needs triage | 35 | 74 | 21 | Add a login client that accepts host, macaroon, and application name and stores the macaroon via Auth.set_credentials; it remains unimplemented and untriaged. |
|
craft-parts issue #648 |
Provide better errors for failures to clear the apt cache | mr-cal | 1008d | needs triage | 35 | 85 | 24 | Enhancement request to wrap the apt cache rmtree in _populate_stage_cache_dir with try/except and raise an actionable error when the cache cannot be removed (e.g. sudo then non-sudo destructive runs). Still open, untriaged, tracked as CRAFT-2937. |
|
snapcraft (launchpad) issue #1753965 |
Error installing Python packages fails with trace | ~kalikiana | 3166d | keep open | 35 | 86 | 19 | Python package failures show pip's error plus a long internal traceback; linked PR #2004 was incomplete because _pip bypassed the plugin execution API, with no later resolution reported. |
|
craft-parts pr #1719 |
test: add regression coverage for base-files/usrmerge staging collisions | copilot-swe-agent | 56d | needs review | 35 | 76 | 21 | Adds focused integration regression coverage for base-files-style bin/lib usrmerge symlinks staging alongside a usr-merged part. Relevant slow CI passes; maintainer review is pending. |
|
snapcraft (launchpad) issue #1747097 |
patch fewer elf files | ~jamesh | 3199d | keep open | 35 | 72 | 11 | Classic ELF patching still iterates every discovered file; DT_NEEDED/DT_SONAME filtering from PR #1959 was merged and then reverted, leaving the optimization open pending safer dlopen handling. |
|
snapcraft issue #4227 |
Autodetect credentials | abitrolly | 1233d | close stale | 35 | 15 | 2 | Snapcraft 7.4.3 failed to infer Candid credentials from export-login; Candid authentication has since been removed, making the requested auto-detection obsolete. |
|
craft-application issue #741 |
Refactor to return packaged resource names | cmatsuoka | 562d | needs triage | 35 | 60 | 10 | PackageService.pack still returns only artifact paths and exposes resource_map in the legacy path; newer artifact-aware packing bypasses it, so the requested API cleanup needs reassessment. |
|
charmcraft issue #2443 |
Add `AGENTS.md` to templates | sed-i | 422d | keep open | 35 | 45 | 10 | Enhancement request to add AGENTS.md agentic-coding instructions to charmcraft init templates. Under discussion; maintainers seek a concrete generic example to adapt. |
|
rockcraft issue #591 |
Errors should have links to our documentation | sergiusens | 870d | needs triage | 35 | 20 | 5 | Feature request to add documentation links to error messages. Issue is vague with no specific errors identified or scope defined. |
|
snapcraft (launchpad) issue #1743428 |
Exception raised when trying to operate on a snap that I don't own nor... | ~nataliabidart | 3217d | close resolved | 35 | 90 | 24 | 403 package_upload responses made snapcraft release fail with a StoreReleaseError formatting KeyError and raw traceback; historical permission and error-formatting fixes address the reported path. |
|
charmcraft issue #2652 |
12-factor plugin installs unnecessary package into charm's venv | dimaqq | 207d | needs triage | 35 | 65 | 10 | 12-factor fastapi charm venv contains build deps (setuptools, wheel, packaging) and pydantic extras not in requirements.txt. Unlabelled, no maintainer response. |
|
snapcraft issue #5329 |
Colcon build failed with extension ros2-humble-ros-base | czarekk215 | 603d | keep open | 35 | 45 | 10 | ROS 2 humble extension colcon build fails with ModuleNotFoundError: lark when compiling msg/srv packages; maintainer gave a python3-lark build-packages workaround, no author response since Mar 2025 |
|
snapcraft (launchpad) issue #1734400 |
Include/exclude patterns improvements | ~lool | 3269d | needs triage | 35 | 43 | 5 | Requests stage/prime include/exclude precedence changes; remains open and untriaged after 3233 days, with lifecycle handling now delegated to craft-parts. |
|
snapcraft (launchpad) issue #1731003 |
node app builds forked, but not referencing upstream source | ~popey | 3285d | needs triage | 35 | 60 | 9 | Remote-source Yarn builds in Snapcraft 2.34 omit the devDependency rimraf, but the root cause remains unidentified and the legacy nodejs plugin path needs investigation. |
|
charmcraft issue #1811 |
Document using Charmcraft under WSL | lengau | 814d | keep open | 35 | 80 | 22 | Documentation request to add a how-to for running Charmcraft on Windows via WSL (enable systemd, snapd, reboot, install snapcraft). No labels or comments; still open. |
|
craft-parts issue #919 |
Opt out of adding git as a build-package | lengau | 704d | keep open | 35 | 72 | 18 | Maintainer-filed feature request (JIRA CRAFT-3763) to skip adding the git build-package when craft.git is on the system; prerequisite #900 landed via #925/11be8c7a, but deb/dnf/yum get_packages_for_source_type still return {"git"} unconditionally |
|
charmcraft issue #2915 |
Add ability to specify/skip architecture for *craft promote... | taurus-forever | 32d | needs triage | 35 | 65 | 13 | Feature request to add an --arch option to charmcraft promote so CI/CD can promote only selected architectures instead of all at once. New, unlabelled, awaiting triage. |
|
charmcraft issue #2866 |
docs: Document that resources are bound to channels, not revisions. | marcusboden | 66d | needs triage | 35 | 72 | 21 | Docs request: clarify resources bind to channels, not revisions, since 'charmcraft release --resource' help text implies per-revision pinning. Behavior is correct; misleading docs/help only. No maintainer response yet. |
|
craft-parts issue #934 |
Rust plugin prevents from building a single package in workspace | artivis | 694d | needs triage | 35 | 75 | 21 | Rust plugin hardcodes `cargo build --workspace` in the virtual-workspace branch, so users cannot build a single/selected package; the `rust_cargo_parameters` workaround fails. Still present at HEAD, untriaged and unacknowledged. |
|
charmcraft issue #1282 |
[refactor] Separate unit and integration tests | lengau | 1138d | close resolved | 35 | 84 | 19 | Unit and integration test separation is already implemented, with dedicated tests/unit and tests/integration directories; the craft-application rebase appears to have delivered it. |
|
craft-providers issue #901 |
Remove mypy and pyright | mr-cal | 273d | keep open | 35 | 88 | 23 | Drop mypy/pyright in favour of ty. Makefile, CI and pyproject already use ty only; common.mk still defines lint-mypy, lint-pyright, install-pyright, and stale .gitignore/type: ignore entries remain. Mirrors snapcraft#6007 and craft-cli#420, both completed. |
|
craft-parts issue #1313 |
go-use test isn't working on arm64 github-hosted runners | lengau | 416d | close resolved | 35 | 95 | 27 | The go-use test was made arm64-compatible by pinning Go sys v0.41.0; GitHub-hosted aarch64 jobs are skipped because that runner only has Go 1.22. |
|
debcraft issue #92 |
Add a short form for platform `all` | lengau | 246d | keep open | 35 | 91 | 20 | Maintainer-authored feature request: accept platform name all as shorthand for any build architecture and the current target architecture; only a long-form workaround exists. |
|
craft-parts issue #1018 |
Provide a way to mimic a build host when expanding an environment | lengau | 625d | keep open | 35 | 50 | 10 | Maintainer enhancement request: expand_environment() in craft_parts/executor/environment.py has no way to override/mimic the build host architecture; arch values come solely from ProjectInfo._host_arch. Triaged, tracked as CRAFT-4735, still unimplemented. |
|
craft-parts issue #1367 |
Craft parts swallows chisel errors if logging level is info or higher | lengau | 388d | keep open | 35 | 88 | 25 | Chisel slice failures still lose command output at INFO or higher because the error stream is captured through logger.debug; the triaged bug remains reproducible. |
|
charmcraft issue #2591 |
Add reuse-packages documentation | lengau | 245d | keep open | 35 | 80 | 21 | Maintainer requests adding reuse-packages-between-builds how-to doc, mirroring Snapcraft's. Common doc exists in craft-application; Charmcraft needs wrapper page and index entry. |
|
craft-application issue #110 |
docs: Add developer documentation | lengau | 1113d | keep open | 35 | 32 | 6 | Maintainer tracking issue asking for developer documentation so apps can move to craft-application without reading source. Partly delivered: docs/ now has how-to, reference and explanation sections, but no tutorial/get-started guide remains. |
|
craft-application issue #540 |
Document parallel build count environment variables | mr-cal | 746d | keep open | 35 | 85 | 24 | Documentation request to define and explain CRAFT_PARALLEL_BUILD_COUNT and CRAFT_MAX_PARALLEL_BUILD_COUNT; docs/reference/environment-variables.rst still omits them while util/system.py defines precedence. |
|
craft-application issue #682 |
Upstream Charmcraft's store service | mr-cal | 599d | needs triage | 35 | 58 | 9 | Move Charmcraft's store service into craft-application to remove duplicated code; it remains open, unlabeled, and unresolved pending triage. |
|
starflow pr #116 |
docs: Add a how-to for publishing an app's snap | lengau | 260d | needs review | 35 | 60 | 18 | Adds a how-to guide for publishing an app's snap, currently covering the debcraft edge flow, plus how-to index update. Approved by one reviewer with 4 unresolved review comments; all CI checks pass. |
|
snapcraft (launchpad) issue #1918969 |
No support for unsigned package-repositories | ~racb | 2065d | keep open | 35 | 84 | 18 | Unsigned file:// APT repositories remain unsupported; maintainers agreed to add an `insecure: true` opt-in when `key-id` is absent, but it is not yet implemented. |
|
snapcraft (launchpad) issue #1742585 |
snapcraft version number output inconsistent | ~popey | 3222d | needs triage | 35 | 78 | 16 | Snapcraft 2.35 displays 3.10 for push but 3.1 for release and status; the detailed report remains open with no maintainer response. |
|
starbase issue #640 |
AGENTS.md should require draft PRs | bepri | 16d | keep open | 35 | 92 | 30 | AGENTS.app.md and AGENTS.lib.md need a policy requiring agents to open draft PRs and obtain human review before marking them ready. |
|
charmcraft issue #2584 |
Enable and integrate the Ruby plugin | lengau | 245d | keep open | 35 | 70 | 11 | Maintainer-authored enhancement request to enable Ruby plugin for charms, explicitly open to outside contributors; lists plugin enablement, spread test with Juju deploy, and base restrictions. |
|
craft-application issue #1092 |
Some tests will require the charm plugin to be enabled | lengau | 144d | needs triage | 35 | 55 | 13 | Open, unlabelled issue: charmcraft PR #2722 may make craft-application tests depend on the charm plugin; the maintainer asks to remove that dependency, but no affected test or fix is identified. |
|
rockcraft issue #1211 |
Reconsider the Pebble binary location | cjdcordeiro | 168d | needs triage | 35 | 30 | 4 | Design discussion (opened by maintainer,0 comments, unlabelled): /usr/bin/pebble may collide with Ubuntu's `pebble` package; proposes a rock-specific path such as /.rock |
|
craft-application pr #607 |
feat: allow use of interceptable `mknod` in `ProviderService` | mattculler | 660d | keep open | 35 | 30 | 8 | Wires ProviderService’s LXD setup to craft-providers’ new intercept_mknod argument, with tests. No failures are reported, but two requested-change reviews remain unresolved and many checks are pending. |
|
craft-parts issue #1729 |
Make error names more idiomatic | bepri | 46d | keep open | 35 | 72 | 10 | Maintainer-authored style task: 38 exception/warning classes in craft_parts/errors.py and craft_parts/packages/errors.py carry `# noqa: N818`; maintainers agreed to add correctly named errors and deprecate old names at the next major release. |
|
snapcraft (launchpad) issue #1864589 |
“ModuleNotFoundError: No module named ‘distutils.util’” when trying to build... | ~pieq | 2447d | close resolved | 35 | 70 | 15 | Launchpad/bionic builds failed with 'No module named distutils.util' due to missing python3-distutils; fixed in python plugin commits cec1a111c (#2058) and d1fd9a226, still open with workarounds confirmed. |
|
snapcraft (launchpad) issue #1857006 |
snapcraft updates don't download in an IPv6 + NAT64 environment | ~mythicbeasts | 2514d | needs triage | 35 | 25 | 2 | IPv6-only/NAT64 hosts fail `snap install`: snapd dials api.snapcraft.io over IPv4 (91.189.92.20) with no v6 fallback. Fault is in the snap/snapd client, not snapcraft. Unlabelled, no maintainer response since 2019. |
|
snapcraft (launchpad) issue #2161191 |
python plugin messing with snapcraft env | ~t-a-k | 111d | needs triage | 35 | 12 | 1 | Vague report that the Python plugin alters Snapcraft's own Python version/modules instead of isolating part deps in a venv; links a core26 forum thread. No labels, no maintainer response, zero comments, no reproducer. |
|
charmcraft issue #2212 |
Resources/containers reference info for extensions | lengau | 610d | keep open | 35 | 84 | 22 | Maintainer-authored docs request remains open: extension reference pages lack coverage of resources and containers generated by framework extensions. The manage-extensions guide has an expanded-output example, but the pages remain incomplete. |
|
snapcraft (launchpad) issue #1968303 |
remote-build: support for snap relative sources | ~gbeuzeboc | 1673d | needs triage | 35 | 55 | 7 | ROS 2 parts sourcing files from SNAPCRAFT_EXTENSIONS_DIR build locally but fail remote-build because the variable path is treated as an unknown source type; the report remains unconfirmed. |
|
craft-parts issue #1470 |
Integration test for poetry plugin requires root/apt state (not marked,... | gcomneno | 257d | needs triage | 35 | 95 | 30 | Poetry integration tests run in non-privileged CI despite invoking apt; replacing the file marker with requires_root is locally validated, but maintainer triage is still absent. |
|
snapcraft (launchpad) issue #1950867 |
remote-build: Support passing --enable-experimental-extensions & options in general | ~ppd | 1819d | needs triage | 35 | 55 | 4 | Valid request for remote-build to forward Snapcraft options, blocked on Launchpad API support; the original core20-specific use case is now obsolete. |
|
snapcraft (launchpad) issue #1932032 |
Progress shown in snapcraft status output is not accurate | ~suligap | 1970d | keep open | 35 | 76 | 20 | Progressive-release status still infers the non-progressive revision’s share as 100 minus the progressive share; it should use that release’s Store-provided current percentage. |
|
snapcraft (launchpad) issue #1629910 |
init-plugin command for new plugin creation | ~jaymell | 3686d | keep open | 35 | 65 | 11 | Proposed Snapcraft init-plugin scaffolding would generate plugin directories, subclasses, and documentation hooks; maintainer requested BasePlugin stubs, but no implementation or resolution is recorded. |
|
snapcraft (launchpad) issue #1858785 |
go plugin doesn't strip binaries | ~ack | 2494d | keep open | 35 | 65 | 15 | The Go plugin still has no option to strip debug symbols from built binaries, leaving snap size reduction dependent on an override-build workaround. |
|
snapcraft (launchpad) issue #1766101 |
Snapcraft not handling cmake nested builds, not including build script files... | ~anoncoward8348 | 3120d | needs triage | 35 | 42 | 6 | Old, untriaged report bundles three FeedReader failures: nested CMake, override-build staging, and Meson runtime ABI mismatches. No maintainer assessment or current reproducer exists. |
|
craft-cli issue #351 |
Remove sphinx directives from overview texts | lengau | 499d | keep open | 35 | 72 | 19 | Enhancement: strip reST/sphinx directives from command overview texts, extending the double-backtick removal done in #306; triaged, linked to CRAFT-4623, still unimplemented in helptexts.py |
|
snapcraft (launchpad) issue #1747778 |
Snapcraft.yml in 'snap' directory. prime/parts/stage in '.' | ~8-launchpad-michaelcole-com | 3195d | keep open | 35 | 55 | 7 | Feature request (2018) to let snapcraft put parts/stage/prime build dirs next to snap/snapcraft.yaml instead of the project root. Maintainer kyrofa agreed it is desirable; no implementation exists — lifecycle still uses Path.cwd() as work_dir. |
|
snapcraft (launchpad) issue #1752957 |
Building classic snap without core snap installed succeeds, but creates snap... | ~kyrofa | 3171d | close stale | 35 | 12 | 1 | Legacy Snapcraft 2.x classic builds could emit a non-running snap when core was absent; the affected base and implementation are now obsolete. |
|
craft-application issue #889 |
Developer docs: Architecture explanation | lengau | 429d | close resolved | 35 | 80 | 21 | Maintainer doc request to explain purposes of commands, services, and what a craft app should/shouldn't do; largely delivered by docs/explanation/structure-of-a-craft-app.rst in PR #910. |
|
craft-providers issue #793 |
Warn about unused parameters in subprocess calls | bepri | 451d | keep open | 35 | 82 | 20 | LXC and Multipass still omit timeout and check when exec uses subprocess.Popen, so the requested warning for silently discarded parameters remains unimplemented. |
|
snapcraft (launchpad) issue #1986624 |
snapcraft points to wrong entry in apps as being invalid. | ~djacobs98 | 1544d | keep open | 35 | 85 | 22 | Snapcraft 6.1 misreports runtests as invalid even though get_cache_info, which contains an underscore, is the actual invalid app name; the issue remains open without a confirmed fix. |
|
craft-application issue #255 |
Properly represent multi-line yaml strings | cmatsuoka | 981d | close resolved | 35 | 95 | 29 | Reported multi-line YAML formatting is already implemented in dump_yaml and covered by a regression test; commit 51346d9b is the resolving fix. |
|
craft-providers issue #467 |
macOS CI is failing weekly tests | mr-cal | 1073d | needs triage | 35 | 25 | 3 | Maintainer-tracked CI issue: macOS runners drop connection after ~1h losing all logs, so flaky macOS integration tests were pushed out of PR CI (#452) into the weekly workflow. Still open, no logs or reproducer captured. |
|
starbase pr #351 |
feat: add a default snapcraft.yaml | upils | 632d | close stale | 35 | 18 | 5 | Adds a default 54-line snap/snapcraft.yaml to the starbase template so downstream craft projects can `make pack-snap`. Open 597 days, 1 approval, 8 unresolved review comments, no CI. |
|
debcraft pr #55 |
test: unit tests for control encoder and model | Copilot | 344d | close stale | 35 | 12 | 2 | Adds 21 unit tests for the Debian control model and encoder, but remains conflicted with main, fails the Conventional Commits policy, and has been inactive for 300 days. |
|
snapcraft (launchpad) issue #1800825 |
Missing account-key revocation support | ~adam-collard | 2928d | needs triage | 35 | 45 | 4 | Feature request (2020) for account-key revocation in snapcraft, plus interim CLI guidance on backing up/restoring GPG keys and key-name conflicts. Still unimplemented: no revoke-key command exists in snapcraft/commands/keys.py. |
|
snapcraft (launchpad) issue #1943603 |
snapcraft --target-arch=i386 does not build i386 images, because core20 does... | ~colin-king | 1879d | close resolved | 35 | 85 | 21 | Legacy Snapcraft accepted an unsupported core20/i386 target, wasted build time, and produced an amd64 snap; current validation excludes i386 and drops core20. |
|
craft-parts pr #1584 |
feat: Add agent skill to create new plugins | steinbro | 177d | needs review | 35 | 40 | 6 | Maintainer-authored feat adding a .github/skills agent skill (SKILL.md plus references, +2387/-0, 27 files) to guide writing new build-system plugins. No reviews yet; CI red on lint/files, minimum-deps and all test-other-plugins slow jobs, 7 unresolved review comments. |
|
craft-cli issue #361 |
Remove the default command | mr-cal | 479d | keep open | 35 | 58 | 9 | Maintainer tracking issue to remove the Dispatcher default_command/allow_default_command support once Snapcraft 10 (core28) ships. Intermediate step landed in PR #422 (error message path); full removal still pending. |
|
craft-application issue #722 |
test: CI backend needs to be system-specific | lengau | 575d | close resolved | 35 | 85 | 24 | Craft's CI testing backend now uses a host-matching OS; merged PR #733 fixed the system-specific backend requirement. |
|
snapcraft issue #4916 |
`--enable-manifest` and `--manifest-image-information` deprecation warnings... | jhenstridge | 845d | keep open | 35 | 85 | 21 | core22: spurious "'--enable-manifest'/'--manifest-image-information' is deprecated" warnings appear when only SNAPCRAFT_BUILD_INFO/SNAPCRAFT_IMAGE_INFO env vars are set. Confirmed by mr-cal; fix PR #6452 was closed unmerged, so still unfixed. |
|
snapcraft (launchpad) issue #1669854 |
Hidden files are not staged after "dump" | ~joeborg | 3535d | close not a bug | 35 | 92 | 23 | Hidden top-level files from dump are omitted by default during stage and prime; current fileset behavior and documentation treat this as intentional, with an explicit workaround. |
|
snapcraft issue #4989 |
Document post-prime and pack steps | mr-cal | 809d | keep open | 35 | 80 | 17 | Triaged documentation gap remains: the parts lifecycle page omits post-prime processing and does not explain metadata and asset generation or the full pack behavior before snap creation. |
|
snapcraft issue #5040 |
Docs: Add a tutorial dedicated to the "default plugin + multiple binaries" scenario | sed-i | 784d | needs triage | 35 | 68 | 17 | Docs request: tutorial for packing multiple Go/Rust binaries with the plugin and iterating parts to discover/prime them. Unlabelled, no maintainer response; docs/tutorials still only has craft-a-snap, so unimplemented. |
|
snapcraft-rocks issue #98 |
Use `rockcraft test` to test the rocks | lengau | 456d | needs triage | 35 | 45 | 9 | Maintainer-filed task to replace/augment spread tests in spread.yaml and CI workflows with `rockcraft test` so built snapcraft rocks are exercised; untouched for 421 days, no labels or discussion. |
|
craft-providers pr #808 |
chore: prepare for Python 3.14 | lengau | 448d | close superseded | 35 | 15 | 3 | Adds Python 3.14 and free-threaded CI coverage, but has 14 failing checks and was tracked as superseded by craft-providers#1509 after PyO3 0.26 support landed. |
|
charmcraft issue #1332 |
(CI) Parallel build test is flaky | lengau | 1116d | close resolved | 35 | 98 | 29 | Parallel-pack smoke-test flakiness was traced to a craft-providers base-instance race and addressed by the v1.18.0 upgrade; the test now runs separately. |
|
snapcraft (launchpad) issue #2161237 |
Build cannot install already installed build-snap | ~t-a-k | 110d | needs triage | 35 | 28 | 5 | Snapcraft 9 build aborts with SnapInstallError when a build-snap (mesa-2404) is already installed; traceback points to craft-parts snaps.py. Untriaged: no labels, no maintainer comments, no reproducer for 75 days. |
|
snapcraft (launchpad) issue #1866257 |
Can't sign ubuntu core model assertion | ~koldoon | 2437d | keep open | 35 | 30 | 5 | `snap sign` of a Ubuntu Core model assertion fails with "gpg: signing failed: No such file or directory"; ~ogra identified a stuck gpg-agent/pinentry lock in the user's environment and linked a forum workaround. Untriaged further. |
|
craft-platforms pr #114 |
feat(architectures): add Go architectures | lengau | 591d | needs review | 35 | 65 | 18 | Adds a GoArchitecture enum with deb<->Go conversions in _architectures.py, plus unit tests and public API exports (fixes #45). Small +56/-2 diff, all CI checks green, but no reviews and no activity in 475 days. |
|
snapcraft issue #5396 |
Export variables to testing environment | cmatsuoka | 572d | keep open | 35 | 82 | 19 | Triaged enhancement to export project and architecture variables into the testing environment so lifecycle tests can reliably locate generated snaps; no resolution evidence is present. |
|
snapcraft issue #5387 |
Warn if `--platform` is used for remote builds | mr-cal | 576d | keep open | 35 | 92 | 26 | Remote-build still rejects removed --platform input without clear migration guidance; triaged issue remains open because PR #6453 was closed unmerged. |
|
craft-parts issue #318 |
Provide a way to return all project variables | merlijn-sebrechts | 1453d | needs triage | 35 | 66 | 14 | Feature request to list all project variables through craftctl for debugging; it remains unimplemented and untriaged. |
|
snapcraft (launchpad) issue #1741900 |
Add file-a-bug functionality on errors | ~lucyllewy | 3224d | needs triage | 35 | 48 | 5 | Opt-in error reporting existed in legacy Snapcraft, but its Sentry implementation was removed; the missing CI-safe behavior was split into follow-up #1790455. |
|
snapcraft (launchpad) issue #1982843 |
Passthrough stopped working in 7.x | ~ted | 1564d | close resolved | 35 | 95 | 22 | App-level passthrough was rejected in Snapcraft 7.x; support is now implemented and covered by a core22 spread test, leaving the issue resolved but open. |
|
fetch-service issue #221 |
create a cache for the unpacked git repositories | dariuszd21 | 778d | close resolved | 35 | 80 | 15 | Request to cache/reuse unpacked git pack repositories so inspectors share one copy instead of unpacking per-inspector; addressed by PR #290 (commit 2ca0dfe) which unpacks once into CacheDir and shares via git-checkout-path annotation |
|
snapcraft (launchpad) issue #2059787 |
inaccurate error output in snapcraft release if given invalid revision | ~cderici | 952d | needs triage | 35 | 92 | 18 | Valid CLI parsing bug: an invalid revision makes snapcraft release claim the release command does not exist; current code still uses type=int, and an exact duplicate remains open. |
|
snapcraft pr #6290 |
docs: Add documentation for new BASH syntax | sergio-costas | 148d | needs review | 35 | 75 | 24 | Adds 12 lines documenting snapd 2.77+ ${VAR:+value} and ${VAR:-default} expansion; approved by two reviewers, no failures, but build, lint, and test checks remain pending. |
|
craft-application issue #960 |
Docs: In CLI messages, compose URLs with app's minor version | medubelko | 352d | keep open | 35 | 82 | 22 | Maintainer-filed, triaged request to make render_doc_url in craft_application/util/docs.py substitute the app's minor version (not major) in RTD doc URLs, matching the planned switch to minor-only Read the Docs publishing. Still unimplemented. |
|
snapcraft (launchpad) issue #1806083 |
snapcraft fails to locate multipass (inside a multipass session) | ~saviq | 2898d | close resolved | 35 | 86 | 21 | Snapcraft 3.0.1 falsely reported Multipass missing inside a Multipass guest; Darwin-only detection in e9ae8d29f addressed the old path, but the Launchpad record remains open. |
|
craft-providers issue #582 |
Add support for Xenial | jugmac00 | 871d | keep open | 35 | 60 | 7 | Enhancement request to add Xenial (16.04) support to craft-providers. Mapping is missing from remotes.py and snapd commands need version abstraction for older snapd on Xenial. Issue acknowledged by maintainer as non-trivial scope. |
|
snapcraft (launchpad) issue #1849707 |
stage-snap causes issues when mixing cores | ~joeborg | 2570d | needs triage | 35 | 58 | 11 | Staging a core16 snap into core18 reportedly overwrote build tools and caused file collisions; the proposed mismatch warning is untriaged, and core18 support has since been removed. |
|
craft-providers issue #657 |
check the storage space before trying to spin container | dariuszd21 | 778d | keep open | 35 | 32 | 6 | Maintainer-filed enhancement to warn (or fail early) when host/LXD storage is nearly full before spinning up a build container; still open, with ownership and a concrete threshold unresolved after lengau questioned whether craft-providers is the right place. |
|
fetch-service issue #231 |
Fetch-service snap doesn't start after refresh | simonepelosi | 771d | close resolved | 35 | 82 | 25 | Fetch-service snap required manual `systemctl start snap.fetch-service.fetchd.service` after refresh; fixed in snap/snapcraft.yaml by setting refresh-mode: endure (commit bdbb27d, PR #273). |
|
snapcraft (launchpad) issue #1634038 |
Snapcraft should verify namespace before uploading | ~joetalbott | 3673d | needs triage | 35 | 50 | 10 | Requests a pre-upload check that the logged-in user has a short namespace, avoiding expensive uploads that the Snap Store rejects afterward; the issue remains untriaged. |
|
rockcraft issue #627 |
Insufficient documentation on how to build Rockcraft's documentation | hd9 | 855d | close resolved | 35 | 92 | 26 | Rockcraft now documents fresh-environment documentation setup, builds, linting and PR submission, and tests the guide; the obsolete docs/installdocs workflow has been replaced. |
|
rockcraft pr #809 |
fix: update plugin build error message | cmatsuoka | 634d | close superseded | 35 | 10 | 3 | Bumps craft-parts to capture combined plugin build output. Open with no review or CI for 597 days; current main requires craft-parts 2.37.0 and already contains the fix. |
|
charmcraft issue #1432 |
Ineffective Output Filtering Using 'charmcraft help --all | grep revision' Command | mateofloreza | 1061d | keep open | 35 | 65 | 13 | charmcraft help --all writes help text to stderr, so piping to grep fails to filter. Maintainer logged it upstream in craft-cli; upstream issue closed without code fix, charmcraft issue remains open awaiting decision. |
|
snapcraft issue #4869 |
Truncated error in hash mismatch output | sergiusens | 868d | needs triage | 35 | 70 | 13 | Hash-mismatch diagnostics are truncated in the concise CLI output, hiding parts of the expected and obtained digests; the full log contains both values, but the report remains unlabelled and untriaged. |
|
rockcraft pr #846 |
docs: modify internal user guide to create a rootless rock | alesancor1 | 590d | close stale | 35 | 14 | 3 | Reworks the internal-user guide into a rootless-rock how-to with run-user and manual-user examples, but it has been inactive for 413 days and targets a reorganized docs structure. |