Showing 100 of 1948 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
snapcraft (launchpad) issue #1636981 |
when a validation already exists, the error message is not nice and is... | ~elopio | 3664d | keep open | 32 | 88 | 17 | Duplicate validation still prompts for a passphrase before the store returns a raw 409; current code signs before posting and needs a preflight error. |
|
snapcraft issue #4951 |
Consider adding flag to extensions to list experimental extensions | hartmutobendorf | 828d | needs triage | 32 | 45 | 12 | Feature request to add an --all flag to the extensions listing command and surface the SNAPCRAFT_ENABLE_EXPERIMENTAL_EXTENSIONS hint, so users can identify experimental extensions. The target command has since been renamed from list-extensions to extensions; the gap still exists. Untriaged. |
|
snapcraft issue #6049 |
The documentation for `how-to/publishing/authenticate.rst` should at least... | linghengqian | 261d | keep open | 32 | 88 | 25 | Docs request (triaged, maintainer-agreed) to name an example system keyring (gnome-keyring) in authenticate.rst, since WSL users hit 'No keyring found' at snapcraft login. Still open; PR #6073 is stalled. |
|
starbase issue #598 |
Prettier should always be run when linting | bepri | 47d | keep open | 32 | 70 | 16 | Maintainer-filed CI gap: Prettier runs only under lint-code, so Starflow's lint-docs path for docs-only changes (e.g. README) skips formatting. No labels or discussion yet. |
|
craft-application issue #1032 |
Some fetch service tests are hard-coded to amd64 | lengau | 235d | keep open | 32 | 74 | 18 | Maintainer-triaged test portability task: fetch-service tests need architecture-independent expectations so the suite can validate behavior beyond amd64. |
|
snapcraft (launchpad) issue #1640721 |
Feature Request: Would be nice to have a way to refresh .deb files | ~aacid | 3650d | needs triage | 32 | 58 | 6 | Request for incremental .deb refreshes to avoid redownloading about 300 MB for unity8; one design comment exists, but the issue has no labels, assignee, or concrete implementation plan. |
|
rockcraft pr #855 |
docs: refactor tutorial | alesancor1 | 580d | close stale | 32 | 18 | 3 | Docs refactor merging tutorials into a single NGINX static-site tutorial and reclassifying 12-factor/PyPI/node tutorials as how-to guides (76 files, +1291/-540). Open, changes requested, dormant 413 days; main docs tree has since evolved without it. |
|
craft-application issue #241 |
Launchpad: Handle invalid credentials files better | lengau | 985d | keep open | 32 | 82 | 17 | Enhancement request (maintainer-filed, triaged) to make Launchpad.login recover from a corrupt/invalid launchpad credentials file by deleting it and re-authenticating, instead of surfacing a raw configparser.NoOptionError internal traceback. Still unaddressed in craft_application/launchpad/launchpad.py. |
|
snapcraft (launchpad) issue #1716054 |
It is not possible to install a build-snap with the default track | ~elopio | 3347d | needs triage | 32 | 74 | 14 | Build-snaps shorthand name/edge raised KeyError because the default latest track was not normalized. The old implementation is gone, so behavior in the current craft-parts backend needs verification. |
|
snapcraft (launchpad) issue #1794955 |
snapcraft erroneously errors when deleting non-existent multipass container | ~popey | 2963d | needs triage | 32 | 80 | 15 | snapcraft clean treats an absent Multipass instance as a deletion error after Multipass was reinstalled; the report is concrete but untriaged and may need validation against the current clean path. |
|
craft-parts pr #1452 |
feat: Add `UV_LINK_MODE=copy` | carlcsaposs-canonical | 271d | needs review | 32 | 58 | 16 | Adds UV_LINK_MODE=copy to the uv plugin build environment to fix hardlink failures when the cache dir is LXD-mounted; companion to craft-providers#900. Approved by 4 reviewers, 1 unresolved comment, some slow CI tests failing. |
|
craft-application issue #750 |
internal errors for platform string | mr-cal | 558d | keep open | 32 | 96 | 25 | Malformed platform entries containing strings still produce an AttributeError instead of a project validation error; the bug remains present at current HEAD. |
|
snapcraft (launchpad) issue #1858994 |
snapcraft list-keys doesn't show the non-registered key when no key is registered | ~ethan.hsieh | 2495d | close resolved | 32 | 85 | 21 | list-keys hid local unregistered keys when no key was registered (snapcraft 3.8). Fixed by 1c44a58fc; today's 'keys' command lists local keys and marks unregistered ones, and list-keys was removed in Snapcraft 9. |
|
snapcraft (launchpad) issue #1617565 |
'snapcraft plugins' should replace list-plugins and show a proper list | ~sabdfl | 3724d | keep open | 32 | 62 | 11 | The list-plugins-to-plugins rename shipped, but snapcraft plugins still prints names only; aligned descriptions and the discussed maintainer-field option remain open. |
|
craft-cli issue #159 |
Allow to show the current progress in the window titlebar | sergio-costas | 1235d | keep open | 32 | 76 | 13 | Feature request to add a bool param to Emitter.progress() that also sets the progress text as the terminal window title via ANSI OSC codes; proposed implementation PR #160 is open but stalled for ~3 years. |
|
snapcraft issue #4541 |
Identical `parts` in different snaps contain different contents | dilyn-corner | 1018d | needs triage | 32 | 58 | 10 | A reported core24 build produced different stage_packages for ostensibly identical netplan parts; the original reproducer is detailed, but a later core22 test could not reproduce it and no triage followed. |
|
snapcraft (launchpad) issue #1683827 |
snapcraft list-revisions strip trailing 0's from versions | ~matiasb | 3490d | keep open | 32 | 92 | 26 | Version strings such as 0.10 are still numerically reformatted by snapcraft revisions; the old list-revisions alias is removed, but the underlying tabulate bug remains. |
|
snapcraft (launchpad) issue #1640897 |
snapcraft doesn't validate gadget.yaml | ~elopio | 3649d | needs triage | 32 | 45 | 5 | Enhancement (filed 2018 by a maintainer): gadget snaps only copy gadget.yaml into the snap without validating its contents. Still unimplemented — both setup_assets.py and services/package.py just copy/read the file. No labels or comments; needs triage. |
|
snapcraft (launchpad) issue #2028047 |
Calling snapcraft clean shouldn't load the project | ~gbeuzeboc | 1209d | close stale | 32 | 20 | 5 | ROS host PYTHONPATH can make legacy `snapcraft clean` import a colliding `catkin` module; the implicated plugin loader was removed in ffb164b7a. |
|
snapcraft (launchpad) issue #1990549 |
snapcraft isn't context aware in displaying help text | ~dilyn-corner | 1507d | keep open | 32 | 38 | 5 | Requests base/context-aware `snapcraft --help`; concrete --verbosity gap for core20 was unified in 8.11 (PRs #5646/#5680) and core20 dropped in 9.0, but general context-aware help remains planned. |
|
craft-providers issue #172 |
Check for docker upstream iptables installation for proper error message | sergiusens | 1461d | keep open | 32 | 66 | 11 | Enhancement to detect docker-installed iptables rules that break LXD networking and fail early with a fix suggestion. Tracked as CRAFT-1683; not implemented in source (only docs added). |
|
charmcraft issue #319 |
hard to run help to figure out your args | jameinel | 2020d | keep open | 32 | 84 | 12 | Command help should ignore extra or invalid arguments and still show help for the named command; maintainers moved implementation to canonical/craft-cli#68, which remains open. |
|
craft-parts pr #1631 |
docs: document autotools disable-parallel key | GreyViperTooth | 123d | needs review | 32 | 52 | 15 | Docs-only PR adding the autotools `disable-parallel` key and a parallel-build note plus a changelog entry to the Autotools plugin reference. Approved by one reviewer but 2 unresolved comments remain; author agreed to revert the "How it works" line and awaits maintainer guidance; 3 CI checks failing. |
|
rockcraft issue #556 |
Have the `--debug` shell inform the user which part and step failed | sed-i | 933d | needs triage | 32 | 48 | 9 | Enhance the --debug failure shell to identify the failed part and lifecycle step; this unlabelled request has only an automated Jira-sync comment and still needs maintainer triage. |
|
snapcraft (launchpad) issue #1928779 |
OSError: [Errno 122] Disk quota exceeded: '/usr2/vikassri/.config' | ~vikassri | 2000d | needs triage | 32 | 66 | 15 | Snapcraft 2.43 login could not save credentials because ~/.config hit its filesystem quota; the long-unconfirmed report has no maintainer diagnosis or fix. |
|
starbase issue #438 |
Use starflow's dev environment workflow | mr-cal | 429d | keep open | 32 | 35 | 6 | Add a workflow using starflow's dev environment workflow. Blocked by upstream starflow#85, which is still open with only a failing WIP PR (starflow#127). Triaged as Enhancement; no real discussion yet. |
|
craft-store issue #243 |
Snap store endpoints test is flaky | lengau | 696d | close resolved | 32 | 85 | 22 | Flaky unit test tests/unit/test_endpoints.py::test_snap_store: expires timestamp differs by one second under load. Root-caused to the `expires` fixture; fix merged in PR #391 (c42cd69) but the issue was never closed. |
|
snapcraft issue #6381 |
Openstack spread tests randomly fail with `Failed to run:... | mr-cal | 87d | keep open | 32 | 48 | 4 | Intermittent LXD 'forkstart' failures (<0.5%) in the OpenStack spread environment across craft repos; reproduced under heavy host memory/CPU pressure and reported upstream to canonical/lxd#18857, no snapcraft-side fix yet |
|
snapcraft (launchpad) issue #1608932 |
multiple parts with same git repo makes build checkout out redundant repos | ~adam-stokes | 3749d | keep open | 31 | 61 | 5 | Confirmed, low-priority build inefficiency: parts using the same Git URL each clone the tree. No fix or newer reproduction is documented. |
|
snapcraft issue #4801 |
Doesn't tell you about conflicting files in staging before exiting the debug shell | seb128 | 912d | needs triage | 31 | 76 | 16 | Staging conflict diagnostics are omitted before --debug opens a shell, forcing users to find the conflicting parts and files in the log; the exact-reproducer report remains open and untriaged. |
|
rockcraft pr #828 |
docs: clarify documentation | alesancor1 | 613d | needs review | 31 | 55 | 13 | Updates 11 tutorial files to standardize directory creation, show project layouts, and simplify Node.js code blocks; remains open with no reviewers, reported checks, or substantive review activity for 413 days. |
|
craft-parts issue #196 |
Consider capturing all potentially invalid stage-packages before bailing | sergiusens | 1676d | needs triage | 30 | 72 | 14 | Requests validating all stage-packages and reporting every missing entry at once; still open, unlabelled, and awaiting maintainer triage beyond an automated Jira-sync comment. |
|
snapcraft (launchpad) issue #1683422 |
post-stop-command not wrapped | ~mabnhdev | 3491d | close resolved | 30 | 88 | 22 | Reported $SNAP install failure appears resolved: Snapcraft 8.5.1 (#4999) now accepts $ in post-stop-command, though the field is still emitted verbatim. |
|
snapcraft issue #5691 |
Proposal: Metadata Separation of Snap Versions | erik78se | 455d | keep open | 30 | 35 | 2 | Proposal to split snap 'version' metadata into separate workload-version and snap-version fields; maintainer mr-cal acknowledged and pointed to snapcraft forum thread; no implementation, still open. |
|
rockcraft issue #1314 |
expose bundled `umoci` as `rockcraft.umoci` | lczyk | 100d | keep open | 30 | 55 | 13 | Enhancement to expose the snap's already-bundled umoci v0.6.0 as a rockcraft.umoci app, mirroring rockcraft.skopeo. Maintainer raised a pre-1.0 API-stability concern; contributor withdrew, awaiting maintainer direction. |
|
snapcraft issue #5275 |
docs: update build-environment for the kde-neon and kde-neon-6 extensions | mr-cal | 625d | keep open | 30 | 88 | 20 | Triaged documentation task remains open: the KDE neon extension reference still shows one build environment, although the code supports distinct core22 and core24 environments; PR #6456 was closed unmerged. |
|
snapcraft (launchpad) issue #1719348 |
meson plugin builds to /usr/local by default | ~popey | 3330d | keep open | 30 | 70 | 16 | Requests the meson plugin default to --prefix=/usr instead of meson's /usr/local. Still unimplemented: craft-parts MesonPlugin passes only user meson-parameters; the plugin moved out of snapcraft, so fix must be upstream. |
|
snapcraft (launchpad) issue #1660302 |
foreign architecture builds doesn't work with classic snaps | ~popey | 3568d | close not a bug | 30 | 35 | 1 | The classic-snap --target-arch build is unsupported because architecture selection is plugin-specific; the sole maintainer response said general support required Debian cross-compilation, and the issue remains open. |
|
snapcraft (launchpad) issue #1839604 |
build-base seems broken | ~niemeyer | 2648d | close resolved | 30 | 90 | 22 | Closed as implemented: current Snapcraft supports `base: bare` with a required `build-base`, including core22/core24/core26, and documents the configuration. |
|
snapcraft issue #5211 |
Docs: Cover the minimum versions for build providers | medubelko | 656d | keep open | 30 | 35 | 6 | Docs request to list minimum LXD/Multipass build provider versions in system requirements. Valid and triaged, but maintainer says it can't start until craft-providers documents and exposes those versions to all craft apps. |
|
snapcraft pr #6292 |
docs: remove core18 references outside of release information | munlicode | 146d | needs review | 30 | 32 | 7 | Docs-only PR closing #6270: strips core18 from how-to/reference docs and swaps in core22 examples (14 files, +29/-119). No maintainer review in 109 days; 3 author questions unanswered. |
|
craft-application issue #552 |
Add a way for applications to customize the `InitService` | mr-cal | 730d | keep open | 30 | 70 | 16 | Enhancement: let apps customize InitService name validation and emit per-template messages. Name validation is done (constructor params name_regex/default_name/invalid_name_message, PR #567); per-template message hook still missing. |
|
snapcraft (launchpad) issue #1668242 |
"snapcraft gated" output doesn't have a clear order | ~ara | 3540d | keep open | 30 | 88 | 22 | snapcraft gated still emits validations in store-response order; requested ordering is snap name A-Z and revisions by descending validation timestamp |
|
snapcraft issue #6291 |
New version gives error | silicology1 | 149d | needs triage | 30 | 25 | 3 | Snapcraft 9.0.0 fails `snapcraft pack` with git clone exit 128 cloning canonical/gpu-snap for the gnome extension's gpu/cleanup part; no snapcraft.yaml or logs supplied, maintainer asked for a reproducer. |
|
snapcraft issue #5448 |
Add deprecation warning for the `snap_daemon` system username | mr-cal | 557d | keep open | 30 | 82 | 18 | Maintainer-filed enhancement (triaged) to warn when `snap_daemon` appears in system-usernames, per snapd's deprecation. Still unimplemented on HEAD; PR #6250 exists but is open with failing CI and unresolved review comments. |
|
charmcraft issue #1458 |
Feature request: remove build base version from cache folder | carlcsaposs-canonical | 1039d | needs triage | 30 | 45 | 7 | Feature request to drop the build base version from the pip cache path so wheels persist across base updates; unlabelled and untriaged. |
|
snapcraft (launchpad) issue #1674124 |
trying to push with the wrong macaroon return non user-friendly error | ~elopio | 3520d | close stale | 30 | 55 | 9 | Legacy enable-ci should explain macaroon permission 403s, but the command is absent from the current codebase and the report needs reassessment against today's authentication flow. |
|
snapcraft issue #6460 |
docs: add guidance for progressive release pause and resume capability | shaloo | 37d | keep open | 30 | 80 | 22 | Documentation request to add guidance on pausing and resuming progressive releases in snapcraft. |
|
snapcraft issue #5683 |
Investigate why `list-keys` makes repeated API calls | mr-cal | 457d | close resolved | 30 | 60 | 12 | Repeated API calls affected the legacy `list-keys` command; it is now removed, and its `keys` replacement makes one local key lookup and one account-info request. |
|
charmcraft issue #2094 |
Create a reference page for the reactive plugin | lengau | 659d | needs triage | 30 | 88 | 20 | Reactive plugin remains registered, but has no dedicated reference page or plugin-index entry; its details are still buried in the charmcraft.yaml parts documentation. |
|
snapcraft issue #6424 |
Add `snapd-info` key for snapd snaps | mr-cal | 52d | keep open | 30 | 80 | 17 | Enhancement to add a `snapd-info` key to `snap.yaml` for `type: snapd` snaps. Issue is triaged and has a willing contributor waiting to begin work. |
|
craft-providers pr #949 |
test: failing reproducer - no error for high UID (>65535) | lengau | 200d | keep open | 30 | 25 | 7 | Adds failing reproducer test test_set_id_map_raises_for_high_uid showing _set_id_map() lacks a uid>65535 check; the actual fix is described but NOT implemented. Red by design on 4 test-basic jobs, 0 reviews, idle 163 days. |
|
craft-application issue #485 |
Provide a better error message when loading a multi-document yaml | lengau | 778d | keep open | 30 | 80 | 18 | Requests a clearer unsupported multi-document YAML error instead of PyYAML ComposerError/internal error. Current safe_yaml_load wraps YAMLError but lacks a specific multi-document message. |
|
craft-grammar issue #188 |
Test on Python 3.14 and Ubuntu 26.04 (Resolute) | lengau | 157d | close resolved | 30 | 80 | 22 | Request to add Python 3.14 and Ubuntu 26.04 testing to CI. The qa.yaml already includes both Python 3.14 and Ubuntu 26.04 in the test matrix for fast and slow tests. |
|
snapcraft pr #5981 |
chore: use pathlib to interact with craft-parts | EdmilsonRodrigues | 285d | close stale | 30 | 10 | 2 | Pathlib migration for craft-parts is now redundant on main; the PR is inactive after 249 days with four unresolved comments and multiple failing checks. |
|
snapcraft pr #5974 |
feat(project): add pydantic validator for common_id field | soumyaDghosh | 290d | needs review | 30 | 25 | 6 | Adds a pydantic validator for App.common_id enforcing appstream desktop-ID format, with unit tests and docs. Successor to closed #5625 for issue #5624. Dormant 252 days, 3 unresolved review comments, 3 CI checks failing. |
|
craft-cli issue #125 |
When the Printer stops it needs to clean the last line if it was transient progress | facundobatista | 1493d | close resolved | 30 | 85 | 18 | Reporter (maintainer facundobatista) asked the Printer to clear the transient progress line when stopping or pausing. Implemented in PR #126 (commit 9f9df27, merged as 2cbced2); issue left open. |
|
charmcraft issue #1566 |
CI: remote build tests time out when the build queue is busy | lengau | 982d | close resolved | 30 | 80 | 19 | CI remote-build tests timed out on busy Launchpad queue; proposed amd64-only builds, longer timeout, weekly scheduling. All three appear implemented via PRs #1573, #1632, #1705. |
|
snapcraft issue #4958 |
Recommend using newer versions of snapcraft | mr-cal | 817d | keep open | 30 | 88 | 22 | Enhancement to emit a warning recommending a newer Snapcraft for older bases; rescoped by maintainer to 8.x recommending 9.x for core22/core24/core26, contributor assigned, open PR #6240 stalled with failing CI. |
|
snapcraft (launchpad) issue #1612373 |
Numerical value for 'source-tag' key causes confusing error | ~wesley-wiedenmeier | 3740d | keep open | 30 | 82 | 16 | Numeric source-tag values must be quoted to avoid YAML float truncation; typed models now appear to reject them cleanly, but no explicit resolution is recorded. |
|
snapcraft pr #6214 |
feat(extensions): support filtering by base | gcomneno | 197d | needs review | 30 | 45 | 11 | Adds `--base` filtering to `snapcraft extensions`, mirroring `plugins --base`, plus unit tests (+67/-4, 2 files). Fixes #4360. Open 160 days, no reviewers; lint/fast+slow unit test CI jobs failing, author says unrelated (core24 spread). |
|
craft-parts pr #1545 |
Add integration tests for the organize keyword with parametrized YAML fixtures | Copilot | 207d | needs review | 30 | 76 | 14 | Adds 11 integration cases using parametrized real-world YAML fixtures for organize mappings. Canonical CLA is green, but no maintainer review has occurred after 170 days. |
|
charmcraft issue #2552 |
docs: what are the values that the `source-type` can have? | panlinux | 286d | needs triage | 30 | 85 | 23 | Untriaged docs gap: the dump plugin recommends `source-type` but omits its values; the current PartSpec reference documents 7z, deb, git, rpm, snap, tar, zip, local, and file. |
|
snapcraft issue #6239 |
Update package repositories test | mr-cal | 186d | needs triage | 30 | 42 | 7 | core26 package-repositories spread test still short-circuits test_apt_ppa with a 'no Release file' MATCH because the snappy-dev/deadsnakes PPAs lack resolute suites. Blocked on external Launchpad state; a volunteer offered to help with no maintainer reply. |
|
rockcraft issue #169 |
Review SPDX package | tigarmo | 1423d | keep open | 30 | 60 | 14 | Maintainer-raised request to replace the discontinued spdx-license-list dependency; #168 used spdx-lookup as a stop-gap and JJMC89's recreated spdx-license-list is proposed but rockcraft still depends on spdx-lookup 0.3.3 |
|
rockcraft issue #182 |
Provide more meaningful output when rockcraft.yaml is invalid | arturo-seijas | 1370d | needs triage | 30 | 88 | 21 | Malformed rockcraft.yaml exposes a location-less PyYAML ScannerError. The request is reproducible but untriaged, and newer craft-application YAML handling may already cover it. |
|
charmcraft issue #1842 |
Output build times for each pip package built | sed-i | 806d | needs triage | 30 | 55 | 7 | Feature request (untriaged, no labels/comments): print per-package pip build times when packing with --no-binary so charm authors can see which deps (e.g. pydantic_core) dominate build time. |
|
charmcraft pr #2975 |
fix(preprocess): report empty metadata.yaml clearly | abhiramshaji-cyber | 11d | needs review | 30 | 80 | 22 | Adds a check for empty metadata.yaml files to provide clearer error messages. Addresses issue #2071. PR is clean, tests updated, CI failures unrelated, awaiting maintainer review. |
|
craft-parts issue #839 |
Spread tests for documentation examples | lengau | 789d | keep open | 30 | 68 | 9 | Maintainer request (lengau) to add spread tests for craft-parts docs examples like Rockcraft has; still open and unimplemented — only the hello-craft-parts tutorial has a spread-ready task.yaml. |
|
craft-actions pr #136 |
docs: consistentize the READMEs | copilot-swe-agent | 16d | needs review | 30 | 60 | 15 | Documentation PR making README files across craft-actions consistent. Under review with 5 unresolved comments, CI passing. |
|
fetch-service issue #257 |
Document how to generate captures for test data | lengau | 759d | needs triage | 30 | 65 | 16 | Open, untriaged maintainer doc request: add a how-to page describing how to generate pcap captures (tshark + SSLKEYLOGFILE git clone) used as fetch-service test data. No such docs exist yet. |
|
craft-platforms pr #254 |
ci: add workshops | lengau | 115d | needs review | 30 | 82 | 18 | Maintainer-authored PR adding Canonical 'workshop' usage to craft-platforms: a 'dev' workshop for local development plus workshops for testing across Python versions and Ubuntu releases. 15 new files, +131/-0, additive only; all 40 CI checks green, no review comments yet. |
|
craft-application issue #996 |
RemoteBuild raises uncaught MissingSchema error | mr-cal | 283d | keep open | 30 | 60 | 13 | RemoteBuild raises uncaught MissingSchema error when build_log_url is the string 'None' instead of None for cancelled builds |
|
charmcraft issue #1713 |
Autodocs: Updates for pydantic models | lengau | 859d | keep open | 30 | 72 | 14 | Documentation task has two concrete goals: one charmcraft.yaml schema and alphabetised schema entries. Schema generation now exists, but ordering and autodoc integration remain unverified. |
|
snapcraft issue #5411 |
Fail to fetch packages for non-host architecture | joulsen | 571d | keep open | 30 | 50 | 8 | Cross-arch stage-packages fetch fails for ros-jazzy-ros-base:arm64. Maintainer and reporter traced it to ROS 2 repo deps marked Architecture: All, i.e. likely upstream, not snapcraft. Triaged as a question (SNAPCRAFT-1026) with no resolution since Apr 2025. |
|
snapcraft (launchpad) issue #1886717 |
Wrong version installed even when explicit | ~kenneth-loafman | 2314d | close stale | 30 | 22 | 4 | Reporter claims a pip3 system install ignored 'six>=1.12.0' and shipped 1.11.0 from base dist-packages; reporter self-closed in Feb 2022 saying it can no longer be reproduced. |
|
snapcraft (launchpad) issue #2012950 |
Can "snapcraft extensions" support "--base=" option like plugins? | ~rpjday | 1321d | keep open | 30 | 78 | 19 | Asks for a `--base=` filter on `snapcraft extensions`, matching `plugins --base`. Unimplemented at HEAD; tracked on GitHub as canonical/snapcraft#4360 with an open, unreviewed PR #6214. |
|
charmcraft issue #1512 |
Improve error message for provider not installed. | PietroPasotti | 1005d | keep open | 30 | 80 | 18 | Improve uninformative 'Provider is required but not installed' prompt to clarify LXD init and what 'y' does; maintainers acknowledge quick fix after craft-providers PR 366. |
|
imagecraft issue #505 |
Document the volumes environment variables | lengau | 16d | keep open | 30 | 80 | 22 | Documentation request to add CRAFT_VOLUME_* environment variables to the step execution environment reference page. A related PR (#506) exists but is awaiting review. |
|
snapcraft (launchpad) issue #1859008 |
PyQt5 does not work from pip | ~jakobdev | 2494d | needs triage | 30 | 25 | 3 | Untriaged report that pip-installed PyQt5 fails in a snap ("Could not load the Qt platform plugin xcb"); reporter wants pip PyQt5 supported instead of the stage package. No recipe, versions, or maintainer response. |
|
rockcraft issue #486 |
overlay-packages is not documented in rockcraft.yaml reference | samuelallan72 | 996d | keep open | 30 | 80 | 22 | Documentation gap for overlay-packages in rockcraft.yaml part properties; maintainer confirmed it originates from craft-parts docs. |
|
rockcraft issue #533 |
Please test against non-EOL Fedora release | zyga | 941d | close resolved | 30 | 100 | 27 | Request to update spread.yaml from EOL Fedora 37 to a supported release. Resolved by PR #580 (commit d81fc0cb); spread.yaml now uses fedora-44-64. |
|
debcraft pr #197 |
fix: make build base type a union | jahn-junior | 33d | keep open | 30 | 30 | 7 | Changes BuildBaseT to include None in the union, removing the pydantic validate_default warning; under review with fast tests failing and author yet to validate. |
|
rockcraft issue #755 |
Can't redirect the output of go run to a file | kian99 | 719d | needs triage | 30 | 68 | 11 | Reported empty redirected output from go run in override-build; an exact repro exists, but no debug log or maintainer triage was provided and current Rockcraft uses classic confinement. |
|
charmcraft issue #1886 |
Make 2.x version of Charmcraft docs on RTD | lengau | 789d | keep open | 30 | 55 | 8 | Maintainer request to publish a versioned 2.x copy of Charmcraft docs on Read the Docs so users can compare 2.x and 3.x behavior. Still open with no comments or implementation. |
|
starbase issue #642 |
Add `ty-pre-commit` hook | mr-cal | 12d | needs triage | 30 | 80 | 20 | Feature request to add astral-sh/ty-pre-commit hook to .pre-commit-config.yaml alongside the existing ruff hook. |
|
charmcraft issue #786 |
Improve status report to expose unregistered tracks | facundobatista | 1606d | keep open | 30 | 75 | 14 | Status command omits tracks present in channel-map but absent from package.channels; should display them flagged as (unregistered). |
|
snapcraft issue #5995 |
Documentation doesn't describe which keys can use advanced grammar | waveform80 | 282d | keep open | 30 | 80 | 22 | Documentation gap: snapcraft's advanced grammar reference page doesn't list which keys support it. A volunteer (@caglarkc) has been assigned by a maintainer (@mr-cal) to document the supported keys. |
|
craft-artifacts pr #95 |
Add Python 3.14 and Resolute CI testing | lokeshannapurreddy-jpg | 23d | close superseded | 30 | 10 | 3 | Duplicate PR proposing to add Python 3.14 and Resolute CI testing, superseded by craft-artifacts#90 which is already approved with passing CI. |
|
snapcraft pr #6461 |
experimental: use binary craftctl | cmatsuoka | 37d | needs review | 30 | 45 | 9 | Maintainer's experimental +44/-9 change to snap/snapcraft.yaml to use a binary craftctl in the snap build. Open 1 day, 0 reviews, 4 unresolved review comments; CI fails Conventional Commits title and lint/files. |
|
rockcraft issue #483 |
Summarise what has/has not been completed when failing or entering a... | ca-scribner | 998d | needs triage | 30 | 80 | 14 | Feature request to display a summary of completed/failed build steps when `rockcraft pack` fails or enters `--debug` mode. Unlabelled, awaiting maintainer triage. |
|
fetch-service issue #284 |
Create a CLI tool to inspect a specific file | lengau | 740d | keep open | 30 | 58 | 10 | Maintainer-authored request for a path-based file-inspection CLI remains open; maintainers said it would shorten inspector development cycles and linked it to internal ticket CRAFT-3965. |
|
craft-application issue #1217 |
Bad error handling for ill-formatted platforms | cmatsuoka | 29d | keep open | 30 | 80 | 22 | Crash with AttributeError when platforms is declared as a list instead of a dict in snapcraft.yaml. Triaged, with a developer interested in fixing it. |
|
craft-parts issue #1329 |
Investigate error conditions of fuse-overlayfs | bepri | 410d | close resolved | 30 | 80 | 17 | The fuse-overlayfs opaque-whiteout cleanup TODO was removed, and unnecessary whiteouts are filtered by #274; the investigation appears resolved in the current codebase. |
|
snapcraft (launchpad) issue #1858020 |
export-login --acls are not documented | ~abitrolly | 2502d | keep open | 30 | 80 | 21 | export-login --acls values still undocumented: CLI help and docs only link to the macaroon API reference; no per-ACL explanation/table. Maintainer agreed in 2020 it should be in help/docs; partial link-only fix landed in e40e68f37 (#6136). |
|
craft-parts issue #1232 |
ant plugin: Support `disable-parallel` parameter | lengau | 431d | needs triage | 30 | 45 | 10 | Ant plugin support for disable-parallel is unimplemented; the request remains open as Needs information, with maintainers requesting a real-world case that fails under parallel builds. |
|
charmcraft issue #1096 |
Spread tests should ensure that juju can correctly parse the output. | lengau | 1293d | keep open | 30 | 55 | 9 | Maintainer-filed enhancement to install juju on spread runners and verify juju can parse built charm/bundle output. No comments, labels, or resolution evidence. |
|
snapcraft (launchpad) issue #1666160 |
Can’t distinguish programmatically between snapcraft.yaml errors and other errors | ~mpt | 3548d | keep open | 30 | 55 | 11 | Requests a programmatic distinction (exit code) between snapcraft.yaml errors and other snapcraft failures, for build.snapcraft.io UI. Still unimplemented: errors.py subclasses set retcode in only 3 cases. Needs re-triage. |
|
snapcraft (launchpad) issue #2054194 |
GIt-LFS not pulled automatically | ~saviq | 994d | needs triage | 30 | 25 | 4 | Feature request to automatically run `git lfs pull` for LFS-enabled `source-type: git` sources. Untriaged: no maintainer comments, labels, or reproducer. The git source plugin now lives in craft-parts, not snapcraft. |
|
rockcraft issue #991 |
Provide instructions on authentication using Skopeo when publishing rock | sinapah | 397d | needs triage | 30 | 72 | 19 | Doc request to add a --dest-creds authentication section to the 'Publish a rock to a registry' how-to. Page (now docs/how-to/crafting/publish-a-rock.rst) still has no auth guidance; no maintainer reply in ~1 year. |