Showing 100 of 1948 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
snapcraft (launchpad) issue #1845276 |
snapcraft shouldn't complain about snap/README.md | ~anonymouse67 | 2601d | needs triage | 30 | 83 | 21 | Snapcraft’s current snap-directory allowlist still rejects snap/README.md; the long-open request remains untriaged and has no maintainer feedback. |
|
charmcraft issue #2376 |
docs: options for links in charmcraft unclear | marcusboden | 478d | keep open | 30 | 85 | 22 | Docs gap: charmcraft.yaml reference doesn't list which sub-keys are allowed under `links:`; reporter's `upstream` key was rejected. Maintainer confirmed valid values live in the Links model; docs redo in progress. |
|
snapcraft issue #6484 |
Bad error handling for ill-formatted platforms | cmatsuoka | 29d | keep open | 30 | 90 | 22 | Crash when platforms is incorrectly specified as a list instead of a mapping; requests a user-friendly error message instead of an AttributeError traceback. |
|
charmcraft issue #2304 |
Specify discouraged paths for mount points | sed-i | 523d | keep open | 30 | 66 | 11 | Triaged documentation enhancement to warn against unsuitable filesystem storage mount paths; guidance remains absent and maintainers say research is needed to define the list. |
|
charmcraft issue #1771 |
Determine whether requiring `libyaml-devel` on yum-based systems creates... | lengau | 830d | keep open | 30 | 75 | 12 | Investigate whether adding libyaml-devel to yum-based charm build packages produces working charms, for consistency with libyaml-dev added for apt in #1766. Open, unassigned, no comments. |
|
craft-parts issue #788 |
launchpad builder won't clone one of three identical repos | popey | 841d | close not a bug | 30 | 90 | 23 | Root cause identified: grype declares an SSH submodule URL that cannot authenticate on Launchpad. HTTPS submodules or omitting unused submodules provide workarounds; #788 remains open. |
|
craft-parts issue #730 |
Remove base support | lengau | 906d | keep open | 30 | 82 | 16 | Maintainer-filed cleanup: remove the deprecated 'base' parameter (LifecycleManager.__init__ line 110) and all its references, still present in main.py --base, ProjectInfo, StepInfo and packages/deb.py. |
|
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-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. |
|
charmcraft issue #2112 |
doc: Unexpected None values in CLI description | alex-ramanau | 652d | needs triage | 30 | 70 | 17 | Generated CLI reference docs show `<None>` for positional args (e.g. `close`'s `name` and `channel`) because the doc generator uses `action.metavar`, which is unset for those args. Unlabelled and untriaged. |
|
snapcraft (launchpad) issue #1567524 |
Support tar.lzma | ~olivier-interfasys | 3866d | keep open | 30 | 70 | 14 | Open, maintainer-acknowledged enhancement for clean tar.lzma source extraction; an old reproducer emitted errors despite eventually producing files. |
|
rockcraft issue #425 |
clarify the impact of the global rockcraft.yaml fields in the final ROCK | cjdcordeiro | 1074d | keep open | 30 | 78 | 14 | Rockcraft’s rockcraft.yaml reference does not explain how global fields populate OCI labels/annotations and internal ROCK metadata; the documentation task remains open with a contributor requesting assignment. |
|
rockcraft issue #813 |
`rockcraft pack` with go-framework fails with `FileNotFoundError` | Aflynn50 | 633d | keep open | 30 | 92 | 24 | go-framework packing a module with no .go sources ends in a low-level FileNotFoundError; the cause is confirmed and open PR #1114 proposes clearer early validation. |
|
charmcraft issue #2960 |
docs: no relevant results for "set default track" | sed-i | 23d | needs triage | 30 | 60 | 16 | Documentation gap: no charmcraft command or docs found for setting a default track on Charmhub. Reporter provided a workaround script using the Charmhub API. |
|
rockcraft pr #832 |
docs: added download pdf button | alesancor1 | 607d | keep open | 30 | 35 | 9 | Adds three lines to enable a PDF download button in Rockcraft docs; open for 571 days with no reviews, comments, or CI results. |
|
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. |
|
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 #1291 |
Execute parts as `run_user` | sed-i | 122d | needs triage | 30 | 45 | 5 | Feature request: run all parts as the non-root UID/GID when `run_user: _daemon_` is declared, removing manual chown/chmod overrides. Open, unlabelled, no maintainer response; only an outside contributor asked to work on 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. |
|
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. |
|
craft-parts issue #1240 |
java plugin: Support `disable-parallel` parameter | lengau | 431d | keep open | 30 | 45 | 7 | Java base disable-parallel support remains open and Needs information: the property is not implemented, and no real-world Java build failing under parallelism has been supplied. |
|
rockcraft issue #185 |
Support for descriptors different from rockcraft.yaml | arturo-seijas | 1370d | keep open | 30 | 58 | 9 | Custom descriptor filenames remain unsupported; maintainers cite consistency with other Craft tools, and the rocks-template repository is suggested to avoid per-rock subdirectory logic. |
|
craft-parts issue #1243 |
maven plugin: Support `disable-parallel` parameter | lengau | 431d | keep open | 30 | 65 | 13 | Maven plugin support for disable-parallel remains unimplemented; the open enhancement is maintainer-marked Needs information and deliberately low priority pending a real-world failing build. |
|
charmcraft issue #2119 |
Configure spread tests on noble | lengau | 649d | close resolved | 30 | 80 | 19 | Request to add Ubuntu 24.04 to spread test backends because the Google backend lacked 24.04. Current spread.yaml uses OpenStack and already includes ubuntu-24.04-64, so the request appears resolved by the backend migration. |
|
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. |
|
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. |
|
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. |
|
snapcraft (launchpad) issue #1816858 |
Set snap name to a human readable name in store upload | ~sil | 2817d | keep open | 30 | 82 | 18 | Proposed a human-readable Store title fallback for hyphenated snap names, such as Adobe Photoshop; it remains open, and current code only sends a title when explicitly provided. |
|
snapcraft (launchpad) issue #1778530 |
rust plugin. failed build with RUST ver. 1.27 | ~general-beck | 3057d | needs triage | 30 | 45 | 6 | An old core18 Rust-plugin report says Rust 1.27 fails to execute rustc -vV while 1.26.2 succeeds; no triage comments or resolution are recorded. |
|
snapcraft issue #4982 |
Support `kernel.yaml` similar to `gadget.yaml` | dilyn-corner | 811d | keep open | 30 | 75 | 18 | Enhancement to handle kernel.yaml as a first-class metadata file (looked up alongside snap/snapcraft.yaml). Core support already exists (copied from project root to meta/ for core22 and mediated for core24+), but snap/kernel.yaml placement is unimplemented; design agreed with maintainer, tracked as CRAFT-3263. |
|
snapcraft (launchpad) issue #1811362 |
Cannot package Python3 package - missing binary | ~radek-sprta | 2858d | close stale | 30 | 40 | 8 | Snapcraft 2.43.1 on Mariner crashes with raw FileNotFoundError for prime/bin/mariner when wrapping the app command; report unlabelled, no maintainer reply, and the 2.x _snap_packaging code path no longer exists upstream. |
|
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. |
|
starbase issue #532 |
docs: app title isn't read in TOC | medubelko | 183d | close resolved | 30 | 72 | 14 | Rockcraft’s RTD/TOC title lacked its version; Starbase fixes #588 and #590 now format versioned docs titles and remove the html_title override. |
|
snapcraft-rocks issue #36 |
Add a template for Github issues | tigarmo | 936d | keep open | 28 | 72 | 17 | Maintainer request for a GitHub issue template covering failing rock versions and snapcraft.yaml; no ISSUE_TEMPLATE directory exists in the current repository tree. |
|
rockcraft issue #1154 |
Pydantic warning: PydanticSerializationUnexpectedValue | dimaqq | 230d | keep open | 28 | 84 | 14 | Pydantic warns while marshaling projects with an ExecCheck because the tagged Check union cannot obtain a discriminator; a minimal reproducer confirms the dumped data remains correct. |
|
craft-archives issue #82 |
gnupg-related failures possibly hide their output | tigarmo | 1255d | needs triage | 28 | 48 | 9 | Maintainer-filed improvement: craft-archives logs only that the gpg command failed without exposing gpg's stderr/verbosity, making keyserver failures hard to diagnose (e.g. rockcraft#287). No labels or follow-up comments yet. |
|
snapcraft (launchpad) issue #1798205 |
Underscores in app names not reported properly | ~roger.light | 2944d | close resolved | 28 | 86 | 17 | The misleading invalid-app diagnostic was addressed by PR #1615 (baef97109); this report remains open but appears obsolete because clearer schema errors replaced the cryptic message. |
|
rockcraft pr #801 |
test(spread): mark doc tests as manual | tigarmo | 645d | close stale | 28 | 14 | 3 | Marks 24 docs spread test task files as manual so they stop running on every code change. Maintainer-authored, never reviewed, no activity for 413 days; branch predates the google→openstack spread migration. |
|
charmcraft issue #2201 |
Review and update minimum RAM requirements in docs | medubelko | 613d | keep open | 28 | 52 | 10 | Maintainer-filed docs task: docs still advertise a 4GB minimum RAM (release notes + Multipass tutorial setup snippets use `--memory 4G`) despite reports that tutorials are slow even at 8GB; value still undetermined and no fix landed. |
|
craft-parts issue #1238 |
go-use plugin: Support `disable-parallel` parameter | lengau | 431d | keep open | 28 | 48 | 9 | Support for disable-parallel in go-use remains open and is explicitly deferred pending a real-world Go project that fails under parallel builds. |
|
snapcraft (launchpad) issue #1851240 |
using source-branch and source-tag not possible but no explanation in help... | ~ogra | 2560d | needs triage | 28 | 88 | 21 | Source branch, tag, and commit are intentionally exclusive, but the sources help still describes them separately without documenting the restriction. |
|
craft-parts issue #1242 |
make plugin: Support `disable-parallel` parameter | lengau | 431d | keep open | 28 | 82 | 19 | Enhancement: make plugin should honor the disable-parallel part property (currently always emits make -j"N"). Filed by a maintainer, labeled Triaged/Enhancement, and explicitly deferred as "extremely low priority" until a real-world non-parallel-build use case is supplied; autotools already has it via PR #1167. |
|
snapcraft (launchpad) issue #1654768 |
rust plugin doesn't check if the Cargo.toml file exists | ~elopio | 3591d | needs triage | 28 | 84 | 20 | Rust plugin downloads its toolchain before Cargo reports a missing manifest when the build directory is empty; historical source-subdir handling was fixed, but explicit preflight validation remains absent. |
|
snapcraft (launchpad) issue #1683823 |
snapstore returns multiple instances of the same publication (was snapcraft... | ~apw | 3490d | keep open | 28 | 55 | 9 | Snap Store data repeated the edge publication three times in revisions output despite two release-map entries; ownership and current reproducibility remain unresolved. |
|
snapcraft-rocks issue #60 |
Set `WORKDIR /workdir` on Docker level | abitrolly | 774d | keep open | 28 | 40 | 9 | Feature request to set Docker WORKDIR to /workdir as a base-image convention for snapcraft rocks. Discussed by maintainers, who are skeptical (GH search shows /app far more common); no agreement or implementation. |
|
snapcraft (launchpad) issue #1860550 |
Defining base snap breaks snapping Subiquity | ~nwessels | 2481d | close not a bug | 28 | 25 | 4 | Adding `base: core18` to Subiquity's snapcraft.yaml left the ISO's seed invalid, so snapd hung seeding with empty /snap/bin. snapd maintainers traced it to seed.yaml generation in the ISO builder, not snapcraft, and marked their task Invalid. |
|
snapcraft (launchpad) issue #1816524 |
snapcraft register-key fails | ~muthiahn | 2819d | needs triage | 28 | 42 | 8 | register-key fails on 2.43.1: `snap export-key` dies with GPG 'Operation cancelled' plus a raw CalledProcessError traceback. Peers traced it to ~/.gnupg and pinentry issues; untriaged, no fix. |
|
fetch-service issue #389 |
Update snapcraft test to stable in CI tests | cmatsuoka | 547d | needs triage | 28 | 50 | 11 | CI spread tests still install snapcraft from latest/edge; maintainer wants the stable channel used in tests once craft-test is published there. Still open, unlabelled, no discussion. |
|
snapcraft (launchpad) issue #1944982 |
Build warns when vim is the editor | ~knitzsche | 1870d | keep open | 28 | 74 | 18 | vim leaves .snapcraft.yaml.swp swap files in snap/, triggering the permanent 'snap directory is meant specifically for snapcraft' warning; asks for an exemption. Still open, check has no backup/swap-file allowance. |
|
craft-cli issue #371 |
Multi-line permanent progress doesn't overwrite temporary progress | jonathan-conder | 454d | close resolved | 28 | 90 | 19 | Bug in craft_cli printer: a permanent multi-line progress message did not fully overwrite a longer previous temporary progress line, leaving residual text ("bar foo foo"). Fixed by merged PR #445. |
|
snapcraft (launchpad) issue #1684091 |
snapcraft gives a confusing message when you lack permissions to administer snap | ~ev | 3490d | keep open | 28 | 76 | 17 | Acknowledged message-quality bug: status should distinguish a missing snap from insufficient collaborator access; the series-based wording is gone, but no explicit resolution is recorded. |
|
craft-providers issue #468 |
Check for a running process should be more fine-grained | mr-cal | 1074d | keep open | 28 | 82 | 18 | Enhancement: the LXD launcher's creator-PID liveness check only tests Path('/proc/<pid>').exists(); suggested fix is to also verify /proc/<pid>/cmdline is a python process so PID reuse triggers immediate cleanup instead of a 60s wait. Still unimplemented. |
|
snapcraft-rocks pr #116 |
ci: always discard spread workers in build-rock tests (core22-7) | lengau | 120d | needs review | 28 | 62 | 15 | Adds an always-run 'Discard spread workers' cleanup step to the spread-tests job in .github/workflows/build-rock.yaml (core22-7) so GCP VMs aren't leaked on cancellation (SNAPCRAFT-1368). +8/-0, spread-tests green, build-rock amd64/arm64 failing. |
|
craft-cli issue #243 |
Brief Emitter mode still appears to be verbose when plugins are called ? | flotter | 979d | needs triage | 28 | 30 | 4 | User asks whether BRIEF mode can suppress subprocess output passed through emit.open_stream(); maintainers confirmed subprocess output is intentionally echoed ephemerally in BRIEF and deferred the question of desired behaviour. |
|
craft-application pr #649 |
feat(ProviderService): deprecate work_dir on instance | lengau | 632d | needs review | 28 | 30 | 7 | Maintainer PR deprecating the redundant work_dir argument to ProviderService.instance() (emits a deprecation warning, keeps the arg for a future major release). Approved with no unresolved comments, but stale and CI is red. |
|
craft-providers issue #791 |
Move troubleshooting info on explanation index | bepri | 452d | keep open | 28 | 84 | 18 | Documentation cleanup remains open: network troubleshooting is still embedded in the explanation index, and NetworkError still links to that index. |
|
snapcraft (launchpad) issue #1996525 |
inaccurate error for a misformatted app name | ~ondrak | 1454d | needs triage | 28 | 76 | 14 | Snapcraft 7.2.7 reports the first app name when the later ccc_ccc app key is invalid; the report remains untriaged with no comments, labels, or confirmed fix. |
|
fetch-service issue #36 |
SNAP: Find a better way to handle perl dependencies | lengau | 1010d | keep open | 28 | 38 | 5 | Maintainer TODO from the fetch-service snap PR review: shrink/simplify the hardcoded PERLLIB env var in snap/snapcraft.yaml (still present at current HEAD, needed for the bundled licensecheck), no discussion or proposal yet. |
|
craft-cli issue #287 |
Document the pytest plugin | lengau | 760d | keep open | 28 | 72 | 15 | The pytest plugin has a basic how-to, but autodoc excludes it and its fixtures and assertion API remain incompletely documented; the enhancement is still open. |
|
craft-parts issue #1603 |
docs: for the autotools plugin relevant flags are not described, e.g.... | xypron | 163d | keep open | 28 | 82 | 21 | Docs gap: the Autotools plugin reference does not document the disable-parallel part property or its effect on make -j. Triaged; fix PR #1631 is open with unresolved review comments and failing CI. |
|
craft-cli issue #262 |
Always report error messages for incorrect usage | mattculler | 845d | keep open | 28 | 92 | 21 | No-command invocations still display general help instead of a specific “no command specified” error; the behavior remains in the current Dispatcher. |
|
craft-cli issue #114 |
Present long/short options separated in the options table for markdown formatted help | facundobatista | 1555d | keep open | 28 | 88 | 19 | Markdown help tables still combine short and long flags in one option cell; the maintainer’s requested separate short/long columns remains unimplemented. |
|
craft-cli issue #78 |
ArgumentParsingError for command not found should hint at the command that raised it | sergiusens | 1660d | needs triage | 28 | 52 | 12 | Feature request: ArgumentParsingError carries no attribute naming the offending command, forcing downstream apps to dig into err.__context__ to distinguish unknown-command errors. Still unimplemented at HEAD. |
|
snapcraft (launchpad) issue #2002980 |
Unpredictable "passthrough" behaviour | ~ondrak | 1391d | needs triage | 28 | 42 | 7 | Reports that a `passthrough:` key is flattened into meta/snap.yaml but left literal in a copied gadget.yaml, producing inconsistent output. Still reproduces in current code (snap_yaml.py vs setup_assets.py/package.py). No labels, no maintainer comments. |
|
snapcraft (launchpad) issue #1863961 |
completion /usr/lib/snapd/etelpmoc.sh error | ~casper-dcl | 2453d | needs triage | 28 | 62 | 13 | gh snap tab completion broken: etelpmoc.sh cannot source /usr/share/bash-completion/bash_completion inside the snap, so _get_comp_words_by_ref is missing. Clear reproducer, but untriaged since 2020; cause looks like the snap missing bash-completion. |
|
snapcraft (launchpad) issue #1892551 |
snapcraft fails to run if it is installed as a try snap | ~anonymouse67 | 2269d | close stale | 28 | 64 | 4 | Snapcraft 4.1.5 failed in LXD builds when launched via snap try because snapd cannot export a try-snap file; the affected legacy provider is absent from the current codebase. |
|
snapcraft (launchpad) issue #1996618 |
Snapcraft does not list keys reported from snapd via External Key Manager | ~bugraaydogar | 1453d | close resolved | 28 | 88 | 20 | Legacy `snapcraft list-keys` hid keys returned by snapd/External Key Manager when the account had no registered keys; superseded by the craft-app `keys` command and Snapcraft 9 removal of list-keys. |
|
snapcraft (launchpad) issue #1948597 |
TypeError: load() missing 1 required positional argument: 'Loader' | ~kenneth-loafman | 1840d | close resolved | 28 | 70 | 17 | Snapcraft 2.43.1 deb crashes with "TypeError: load() missing 1 required positional argument: 'Loader'" in states/_state.py; Loader-less yaml.load call since fixed, and the reporter confirmed their core18 CI image was the trigger. |
|
charmcraft issue #1809 |
--project-dir fails to find metadata.yaml when running in destructive mode | andersson1234 | 816d | close resolved | 28 | 90 | 16 | Destructive pack with --project-dir and split metadata.yaml was a path-resolution bug; later lifecycle fixes and the documented Charmcraft 4.2.1 fix for analogous #2493 resolve it. |
|
snapcraft (launchpad) issue #1851003 |
Error message displays name of first application when a secondary... | ~ec0 | 2563d | needs triage | 28 | 88 | 16 | App-name validation reports the first valid app instead of the offending secondary app; no fix or maintainer triage is evident. |
|
snapcraft (launchpad) issue #1803736 |
meson plugin: Allow duplicate items in meson-parameters | ~brlin | 2913d | close resolved | 28 | 94 | 24 | Legacy Snapcraft rejected duplicate meson-parameters entries; legacy was removed, and craft-parts now uses an unrestricted list that preserves duplicates. |
|
charmcraft pr #2789 |
test(spread): add core26 venv/bin/python reproducer for uv dispatch script bug | copilot-swe-agent | 115d | keep open | 28 | 32 | 7 | Test-only spread change adding a core26 reproducer: requires venv/bin/python in the uv charm payload and runs `venv/bin/python -c "import ops"` in the task. 2 slow-test jobs fail, 1 review comment unresolved, no reviewers. |
|
snapcraft (launchpad) issue #1723726 |
“snapcraft register” message is mysterious and inaccurate | ~mpt | 3311d | needs triage | 28 | 58 | 14 | Wants the 'snapcraft register' confirmation prompt rewritten: undefined 'we'/'our community', false claim that snaps get renamed, hedged wording, and a prompt users can't truthfully answer. Text still unchanged in snapcraft/commands/names.py |
|
snapcraft (launchpad) issue #1612741 |
Snapcraft go plugin install issues | ~josvaz | 3739d | close resolved | 28 | 94 | 18 | Go 1.6 godoc builds targeted read-only GOROOT; Go 1.7 fixed the special case, and Snapcraft now directs Go binaries into the part install directory. |
|
snapcraft (launchpad) issue #1723720 |
“snapcraft register” with invalid characters still blathers on about name ownership | ~mpt | 3311d | needs triage | 28 | 70 | 14 | `snapcraft register` shows the name-ownership blather and prompt before the store rejects invalid names. Still present at HEAD: names.py validates nothing client-side. Untriaged, only one self-comment from reporter. |
|
starflow pr #78 |
feat(test-python): Add Python 3.14 to the defaults | lengau | 446d | keep open | 28 | 22 | 6 | Draft re-application of merged-then-reverted PR #75: adds Python 3.14 to the default test-python matrix (2 lines). Blocked on PyO3 0.26; one CI job (Fast tests, noble) failing; no review activity in 409 days. |
|
starbase issue #357 |
`make docs-auto` should ignore editor temp files and stuff. | lengau | 624d | keep open | 28 | 74 | 17 | Enhance make docs-auto to exclude editor temp files such as Kate swap files; maintainers are still comparing patterns across several editors. |
|
starbase issue #34 |
codespell doesn't ignore files in `.gitignore` | mr-cal | 1360d | keep open | 28 | 52 | 7 | codespell scans gitignored paths (venv/pip) causing lint false positives; maintainers agreed to a manual `skip` workaround (venv already in [tool.codespell].skip) and left it open pending upstream gitignore support |
|
snapcraft (launchpad) issue #2090799 |
Not possible to spawn other instances of myappid | ~sblantipodi | 706d | close not a bug | 28 | 18 | 1 | Asks for a flatpak-spawn equivalent so a strictly confined snap can launch more instances of itself; this is snapd/AppArmor runtime confinement, not snapcraft — no relevant code and no maintainer response in 669 days. |
|
craft-parts issue #1247 |
python plugin: Support `disable-parallel` parameter | lengau | 431d | keep open | 28 | 34 | 3 | Python plugin support for compiled-wheel parallel control remains unimplemented; maintainers are awaiting a real-world case and resolution of tri-state semantics versus setting CRAFT_PARALLEL_BUILD_COUNT=1. |
|
craft-providers issue #792 |
Create an inner class for LXD variables | bepri | 452d | keep open | 28 | 58 | 8 | Maintainer-filed enhancement to group LXD launcher variables into an inner class/dataclass to shrink launch()'s long parameter lists; still open, approach under discussion. |
|
charmcraft pr #2772 |
Work/charmcraft 710 prototype e2e | lengau | 120d | close stale | 28 | 15 | 2 | An 11-file end-to-end prototype has been inactive for 84 days with five unresolved review comments; its craft-parts counterpart was closed after the design shifted to relative parent paths. |
|
snapcraft (launchpad) issue #1804957 |
Malicious namesquatting of snaps | ~buzz-- | 2905d | close not a bug | 28 | 15 | 1 | Complaint that an unverified publisher holding the 'bitcoin' snap name pushes outdated software, calling for stronger store name/publisher vetting; out of scope for the snapcraft build tool |
|
craft-parts issue #1531 |
docs: Add more explanation and/or examples to dump_plugin | marcusboden | 220d | close resolved | 28 | 85 | 22 | Doc request for examples on the dump plugin reference page; resolved by merged PR #1547 (fb57e5a3), which added a YAML example with local source and organize remapping. Issue still open in tracker. |
|
snapcraft (launchpad) issue #1604810 |
try to snapcraft release an unexisting revision shows the wrong error | ~elopio | 3762d | keep open | 28 | 66 | 11 | Maintainer-confirmed misleading error when releasing a nonexistent revision; store-specific behavior still needs clarification before implementation. |
|
craft-cli issue #9 |
Have a sub-char resolution in the progress bar | facundobatista | 1873d | keep open | 28 | 90 | 19 | Triaged enhancement for eighth-block progress rendering; the current printer still floors progress to whole full-block characters, leaving smoother sub-character resolution unimplemented. |
|
rockcraft issue #714 |
remove support for i386 | cjdcordeiro | 773d | needs triage | 28 | 84 | 18 | i386 remains exposed as supported by SUPPORTED_ARCHS, the generated schema, and two spread fixtures; removal is unimplemented and the unlabelled issue awaits triage. |
|
craft-parts pr #1391 |
Fix the use of go-use (Go Workspaces) when using dependencies that include... | atandrewlee | 366d | close superseded | 28 | 8 | 1 | go-use symlink-resolution fix for relative `replace` directives in dependency go.mod files; changes requested, 3 unresolved comments, test-other-plugins and title-policy CI failing, author moved the approach to PR #1466. |
|
craft-parts pr #1309 |
test: run tests in a random order | lengau | 417d | close stale | 28 | 14 | 3 | Adds pytest-randomly so craft-parts tests run in random order to surface order dependence. Maintainer-authored, 380 days old, zero review comments, no updates, and 11 CI jobs failing (most test-common/test-other slow+fast runs). |
|
craft-cli issue #31 |
Error message formatting | cmatsuoka | 1824d | keep open | 28 | 69 | 11 | Open feature request to customize Emitter.error output with a prefix and optional color; prefix support is absent, while warning output already accepts a prefix. |
|
craft-cli issue #135 |
logging handler is not using any formater | rgildein | 1381d | needs triage | 28 | 60 | 13 | Enhancement request: craft_cli _Handler.emit uses record.getMessage() and ignores self.formatter, so log format can't be customised. Confirmed still unfixed at current HEAD; no maintainer response or labels. |
|
snapcraft (launchpad) issue #1814729 |
Setting SNAPCRAFT_BUILD_ENVIRONMENT_MEMORY doesn't take effect | ~popey | 2832d | close not a bug | 28 | 32 | 4 | Feature request: SNAPCRAFT_BUILD_ENVIRONMENT_MEMORY/CPU are ignored when an existing Multipass VM is reused; maintainer confirmed the vars only apply at VM creation and advised purging the instance. Not implemented |
|
snapcraft (launchpad) issue #1599234 |
should not remove suid/guid from binaries when confinement is devmode | ~osomon | 3777d | close not a bug | 28 | 40 | 6 | Requests that snapcraft keep suid/sgid bits on extracted binaries when building devmode snaps (oxide/chrome-sandbox aborted). Maintainers say stripping is intentional; workarounds are userns sandbox, browser-support allow-sandbox:true, or OXIDE_NO_SANDBOX. |
|
rockcraft issue #512 |
Document `overlay-packages` | alnvdl-work | 964d | close resolved | 28 | 90 | 23 | `overlay-packages` is now included in the unified rockcraft.yaml reference, and the former part-properties URL redirects to the new reference. |
|
craft-parts issue #835 |
Document the creation and use of stage-packages filters | lengau | 793d | needs triage | 28 | 66 | 14 | Docs task from maintainer: write a how-to for registering stage-packages filters; still undocumented (docs/how-to/index.rst has no callbacks page) and the register_stage_packages_filter docstring still misleadingly says the mechanism "is now deprecated". |
|
snapcraft (launchpad) issue #2028303 |
snap build installing old pypi version of argparse | ~kenneth-loafman | 1206d | close stale | 28 | 42 | 6 | An obsolete PyPI argparse can shadow distro argparse in core20 Python-extension builds; the report is untriaged, has a reporter-side workaround, and core20 is now an unsupported ESM base. |
|
snapcraft (launchpad) issue #1995488 |
Cannot generate new credentials (snapcraft 7.2.2->4) | ~sfljami | 1466d | needs triage | 28 | 74 | 16 | Snapcraft 7.2 headless CI exports credentials successfully, then login rejects the documented environment-variable workflow; with no keyring or maintainer response, it needs triage. |
|
craft-parts pr #1697 |
ci: collect s390x JVM crash information and compiler replay data | lengau | 71d | keep open | 27 | 18 | 3 | Draft by maintainer lengau adds an s390x QA job to collect OpenJDK 21 HotSpot crash logs (hs_err_pid*.log), compiler replay data and env debug info; CLA passes, the new job check is still pending, and 6 review threads are unresolved. |
|
craft-store issue #265 |
Using token from `snapcraft export-login` as environment auth results in... | aywaldron | 647d | keep open | 27 | 74 | 16 | u1-macaroon tokens from `snapcraft export-login` fail with a generic CredentialsNotParseable when used via StoreClient; reporter misused StoreClient (needs UbuntuOneStoreClient). Maintainer converted it to a wishlist item for a clearer error message based on the 't' field. |
|
craft-parts issue #1248 |
poetry plugin: Support `disable-parallel` parameter | lengau | 431d | keep open | 27 | 40 | 5 | Poetry lacks disable-parallel support; the valid but low-priority enhancement awaits a failing real-world build and a general Python design decision in #1247. |