Issue & PR triage
Loading...
Showing 100 of 1108 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
rockcraft issue #132 |
Rockcraft wipes working directory | jardon | 1469d | keep open | 84 | 78 | 34 | Maintainers agreed to prevent `organize` rules from wiping the working directory mounted at `/root/project`, but no safeguard or resolving fix is evident and the issue remains open. |
|
rockcraft issue #122 |
`rockcraft pack` uses all available memory | gruyaume | 1478d | keep open | 80 | 31 | 7 | Reported LXD-backed rockcraft pack host memory exhaustion remains unconfirmed; the 2022 0.0.1.dev1 repro used a disputed branch, and maintainers await current version and LXD profile details. |
|
rockcraft issue #857 |
Missing symlinks in bare-based images built with Noble | clay-lake | 568d | needs triage | 78 | 74 | 24 | Rockcraft 1.9.0 bare images built on Noble omit the /lib64 loader path, making staged dynamically linked executables fail with “no such file or directory”; the issue remains untriaged. |
|
craft-parts issue #1460 |
`organize` with mapping like `{app: app/app}` when `app` is a directory not... | javierdelapuente | 254d | keep open | 75 | 85 | 35 | Bug in `organize` mapping where moving a directory into itself (`app: app/app`) causes silent file deletion or crashes. A fix is being prepared and approved by maintainers. |
|
charmcraft issue #2685 |
`uv` plugin produces architecture-mislabeled charm on cross-build... | UtkarshBhatthere | 176d | needs triage | 75 | 80 | 27 | uv plugin silently produces architecture-mislabeled charms on cross-build (build-on amd64, build-for arm64) — host-arch wheels packaged under target-arch manifest. Unlabelled, no maintainer response. |
|
craft-parts pr #1757 |
perf(state): cache source outdated checks within planning | chris-bainbridge | 24d | keep open | 75 | 40 | 12 | Adds planning-scoped cache for source outdated checks in StateManager, keyed by part and pull-state serial, with defensive report copies. ~96% planning speedup on large SDK. CI failing lint/files and OSV-scanner; one unresolved review comment. |
|
snapcraft (launchpad) issue #1711333 |
snaps must have accompanying source available | ~jr | 3360d | keep open | 74 | 57 | 7 | Maintainer-acknowledged request to persist and publish snap source and build assets for license compliance remains open, with no implementation found. |
|
snapcraft issue #4533 |
Regression: Interacting with an on-prem store proxy fails indiscriminately | atomcult | 1011d | close resolved | 72 | 92 | 54 | Export-login credentials for on-prem proxies were rejected as malformed Candid credentials in Snapcraft 7/8; current code explicitly bypasses Candid validation for on-prem auth and has regression coverage. |
|
snapcraft (launchpad) issue #1933224 |
Recent changes completely break 32bit snaps | ~ogra | 1955d | keep open | 72 | 76 | 23 | Base-snap library filtering omits armhf runtime libraries from armhf/arm64 snaps, silently producing broken Raspberry Pi releases; maintainers acknowledge the bug, but no fix is recorded. |
|
rockcraft issue #1351 |
Changing from basefull to baseless silently produces an incomplete rock | lczyk | 62d | keep open | 72 | 83 | 25 | Rebuilding a project after switching `base: ubuntu@26.04` to `base: bare` reuses stale state, silently producing a rock missing ~520 base-provided files; pack exits 0 with no warning. Labeled as a bug, awaiting triage/fix. |
|
rockcraft issue #350 |
Support pinning of snap revisions for build-snaps and stage-snaps | shayancanonical | 1157d | keep open | 72 | 76 | 23 | Unresolved feature request to pin exact Snap Store revisions in build-snaps and stage-snaps for reproducible ROCK builds; current syntax accepts only a snap name and channel. |
|
snapcraft issue #6410 |
Bundled patchelf drops PT_NOTE coverage for .note.qt.metadata, making every... | desvaters | 57d | keep open | 70 | 80 | 25 | Vendored patchelf relocates .note.qt.metadata out of PT_NOTE coverage when growing .dynstr, making staged Qt 6 plugins unloadable. Triaged; maintainer confirms patchelf update is needed. |
|
rockcraft issue #655 |
Make ROCK base image registry configurable. | aznashwan | 822d | needs triage | 70 | 80 | 39 | Request to make the hardcoded ECR base image registry configurable to avoid rate-limit failures in CI builds. |
|
snapcraft (launchpad) issue #2099923 |
Snapcraft builds are failing: install of snap "snapcraft" failed | ~snawoot | 612d | needs triage | 68 | 76 | 19 | Reported Launchpad Bionic non-i386 builds cannot install Snapcraft 7.x/stable because core20 needs snapd 2.61; the issue remains open, untriaged, and unanswered. |
|
snapcraft (launchpad) issue #2015091 |
snapcraft download debian package from incorrect arch | ~aristochen | 1305d | needs triage | 68 | 85 | 21 | Cross-building for arm64 on amd64 resolved explicitly qualified bsdmainutils:arm64 to an amd64 package; the valid report remains untriaged and a similar bug is still open. |
|
craft-providers issue #508 |
LXD Provider requires a local installation of LXD on macOS | jat-canonical | 993d | keep open | 68 | 70 | 10 | Remote-LXD builds remain unavailable on macOS and Windows because provider checks still require a local LXD install, despite acknowledged demand and partial low-level remote support. |
|
craft-parts issue #786 |
Python plugin. Python is broken in core24 classic snaps if snap is used on... | NucciTheBoss | 834d | keep open | 68 | 87 | 20 | Core24 classic snaps using the Python plugin fail on older Ubuntu LTS hosts because staged Python cannot find its stdlib; Snapcraft 8.3.2's fix proved incomplete, with follow-up in snapcraft#5144. |
|
snapcraft (launchpad) issue #2041182 |
Desktop extension doesn't update GDK pixbuf module cache when reverting | ~gbeuzeboc | 1099d | keep open | 68 | 86 | 42 | Desktop extensions keep a revision-specific .last_revision while sharing its GDK pixbuf cache, so snap reverts can reuse loaders from another revision and crash; the maintainer-approved move is not implemented. |
|
charmcraft issue #2788 |
uv plugin fails on core26: dispatch script uses system Python instead of venv | zyga | 106d | keep open | 68 | 78 | 24 | uv plugin breaks core26 charm builds: craft-parts strips venv python symlinks, dispatch falls back to system Python lacking ops. Acknowledged by lengau, ownership moved into Charmcraft (CHARMCRAFT-714). |
|
snapcraft issue #6017 |
XKB_CONFIG_ROOT pointing to non-existent directory in kde-neon-6/kde-neon-qt6 | RealLucioCarreras | 266d | needs triage | 68 | 82 | 29 | Untriaged core24 KDE Neon extension bug: XKB paths resolve to absent runtime directories, causing an xkbcommon error and Sayonara segfault; current code retains the invalid exports. |
|
snapcraft (launchpad) issue #2036424 |
Mantic s390x install fails: grep-status: *** stack smashing detected ***: terminated | ~dbungert | 1137d | keep open | 66 | 72 | 17 | Snapcraft-built Subiquity on Mantic s390x had a missing ELF RPATH, mixing core22's loader with host glibc. Edge core22 worked, but stable core22 still failed on LPAR; the issue remains open. |
|
rockcraft issue #583 |
support project directory with remounted path | henrymao-zz | 870d | keep open | 65 | 70 | 20 | Bind-mounted paths in project directory are not accessible inside rockcraft's build environment (chroot/container). Issue open 863 days with no maintainer response. |
|
snapcraft issue #6491 |
Task: Wokr with LXQT to achieve their theme without integration into... | ScarlettGatelyMoore | 16d | keep open | 65 | 45 | 10 | Discussion about separating LXQt theme support from kf6-core integration to avoid snap crashes; active multi-party discussion ongoing with no resolution yet. |
|
snapcraft (launchpad) issue #1582469 |
clean behavior is confusing | ~niemeyer | 3818d | needs triage | 65 | 58 | 8 | The 2016 clean/redo UX proposal remains open; modern Snapcraft still exposes clean, while the requested un/re commands are absent from the current command set. |
|
snapcraft (launchpad) issue #1887096 |
not able to install MAAS from snap on ppc64le | ~jhusakowski | 2303d | keep open | 65 | 85 | 23 | MAAS snap installs segfault on ppc64le in older and stable releases because of libsnapcraft-preload; 3.3/edge installs successfully, but stable-channel resolution remains unconfirmed. |
|
charmcraft issue #2680 |
`name` field missing from packed charm's `metadata.yaml` when defined in... | javierdelapuente | 182d | needs triage | 65 | 85 | 30 | Packed charm metadata.yaml omits name when name is in charmcraft.yaml and separate metadata.yaml lacks it, making charm undeployable. Confirmed by second user; no maintainer triage yet. |
|
snapcraft issue #6297 |
Task: kde-neon-6 core26 support | ScarlettGatelyMoore | 133d | keep open | 65 | 75 | 22 | Triaged enhancement task for kde-neon-6 core26 support, actively being worked on by an assigned contributor with recent progress updates. |
|
rockcraft issue #181 |
Add testing framework? | sed-i | 1367d | close resolved | 65 | 72 | 22 | Rockcraft now exposes an upstream-backed rockcraft test command for built-rock testing; commit a6d1b77a added it, and downstream CI supports its implicit pack-and-test flow. |
|
snapcraft (launchpad) issue #1764100 |
pyqt5 cannot load xcb plugin | ~ihaywood3 | 3119d | needs triage | 65 | 62 | 15 | PyQt5 snap aborts because libQt5XcbQpa.so.5 has an undefined QPlatformTheme::fileIconPixmap symbol; the report has no labels or maintainer comments. |
|
snapcraft issue #5661 |
Snapcraft hangs forever if a GitHub repository doesn't exist | vandah | 454d | keep open | 65 | 90 | 46 | Snapcraft 8.10.2 hangs during part pulls when Git prompts for credentials; maintainers assigned the fix to craft-parts, where the equivalent issue remains open. |
|
snapcraft-rocks issue #112 |
Provide snapcraft-rocks based on core26 | brunvonlope | 178d | keep open | 65 | 82 | 37 | Requests a core26-based snapcraft-rocks image for CI use; maintainer mr-cal confirms it is on the roadmap (SNAPCRAFT-1387). README still lists only 7_core22/8_core22/8_core24; experimental PR #118 for Snapcraft 9/core26 is unmerged. |
|
snapcraft (launchpad) issue #1882535 |
[focal/core20][python3.7+] staging conflicts when multiple python parts have... | ~dmitriis | 2334d | keep open | 65 | 65 | 11 | Overlapping Python dependencies generate nondeterministic bytecode, RECORD, and venv artifacts that block staging; confirmed to affect multiple users, with workarounds but no complete fix. |
|
charmcraft issue #2243 |
Consider adding an optional cli argument for base (including the arch) for... | gabrielcocenza | 575d | needs triage | 65 | 82 | 19 | Request for an optional base and architecture selector on `charmcraft release` to prevent multi-base legacy charm promotions from changing unrelated architectures; the CLI still lacks this option. |
|
rockcraft issue #1261 |
stage-packages with deb packages create /etc/ssl/certs/ca-certificates.crt... | javierdelapuente | 133d | keep open | 65 | 55 | 11 | stage-packages deb pulls a host-generated /etc/ssl/certs/ca-certificates.crt that conflicts with the base/chisel copy, breaking 12-factor extensions on non-bare bases; root cause still under investigation |
|
craft-application pr #994 |
feat(RequestService): retry upon ChunkedEncodingError | zhijie-yang | 277d | needs review | 65 | 75 | 27 | Adds retry handling for ChunkedEncodingError in RequestService downloads; approved with 1 unresolved review comment, CI passing |
|
snapcraft (launchpad) issue #1670388 |
classic snap are missing some env variables for reaching command name. (snap... | ~didrocks | 3524d | needs triage | 65 | 75 | 32 | Classic snap wrappers omit snap-local PATH entries, so commands such as chuck-norris-cli can pass packaging but fail at runtime; the confirmed report remains open. |
|
craft-application issue #1205 |
remote build: stale git repositories on launchpad | enriqueesanchz | 28d | needs triage | 64 | 78 | 19 | New, unlabelled report documents several remote-build paths orphaning about 20,000 Launchpad git repositories and proposes a best-effort, bounded cleanup sweep; no maintainer response yet. |
|
craft-application issue #792 |
http auth token occasionally leaked | setharnold | 490d | keep open | 64 | 88 | 37 | Triaged security bug: short-lived Launchpad HTTP tokens can appear in remote-build git failure logs; current code still streams unsanitized git output. |
|
snapcraft (launchpad) issue #2012503 |
wrong arch of stage packages | ~ondrak | 1317d | keep open | 64 | 88 | 27 | Confirmed cross-build stage packages are fetched for amd64 instead of arm64; no fix or verification is recorded, so the valid cross-compilation bug remains open. |
|
snapcraft (launchpad) issue #1834207 |
removing parts should clean stage and prime… stages? | ~saviq | 2683d | keep open | 62 | 88 | 31 | Removing a part leaves its prior files in stage/prime and packages them; the report has a clear reproducer and maintainer confirmation, but no fix reference is recorded. |
|
snapcraft (launchpad) issue #1813634 |
not reliable way to detect target architecture | ~ondrak | 2831d | close resolved | 62 | 90 | 29 | Snapcraft 8.0.0 added explicit build-for architecture variables, superseding the ambiguous 3.0.1-era target_arch and SNAPCRAFT_ARCH_TRIPLET behavior. |
|
craft-parts issue #1641 |
uv plugin fails on core26: dispatch script uses system Python instead of venv | zyga | 106d | needs triage | 62 | 72 | 19 | core26 has no Python in the base snap, so uv-built parts find no interpreter in the payload and fall back to the system python, leaving venv/bin/python pointing at a bare interpreter that lacks ops. Fix options undecided. |
|
craft-parts pr #1652 |
fix(parts): run override build on working subdir | soumyaDghosh | 104d | needs review | 62 | 38 | 18 | Changes override-build to run in the configured source-subdir, but it remains unreviewed with unresolved compatibility concerns. Core tests pass; CLA and lint checks fail. |
|
snapcraft issue #5137 |
Fails to login when Kwallet is default keyring | eeickmeyer | 728d | keep open | 62 | 88 | 45 | KWallet-backed Snapcraft login fails with “python-dbus not installed”; maintainers agreed to add python3-dbus as a stage package, but the current snap manifest still omits it. |
|
snapcraft issue #4373 |
library linter fails on foreign archs and can't be disabled for core20 | alexclewontin | 1134d | keep open | 62 | 95 | 38 | Cross-arch core20 builds still lint foreign ELF files, causing missing-loader failures or QEMU segfaults and potentially 20+ GB core dumps; open PR #6249 proposes the fix. |
|
snapcraft (launchpad) issue #1750527 |
dashboard does not validate text fields | ~chipaca | 3173d | close resolved | 62 | 88 | 23 | Dashboard/store control-character validation was implemented in 2018, and the remaining snapd safe-display path was confirmed fixed in 2020; the Launchpad issue remains open. |
|
snapcraft (launchpad) issue #1824473 |
Changed stage-snaps property does not make pull step dirty | ~brlin | 2757d | needs triage | 62 | 78 | 35 | No response or triage is present. Current craft-parts still omits stage-snaps from PullState.properties_of_interest, matching the reported stale-step and build crash. |
|
rockcraft issue #902 |
Go plugin environment validation fails if toolchain downloads a new version | hk21702 | 498d | needs triage | 60 | 80 | 36 | Go plugin env validation fails when `go version` triggers toolchain auto-download; stderr download message is parsed as the version. Root cause is in craft-parts validator; duplicate craft-parts#1447 is open. |
|
snapcraft issue #5721 |
Failed to pull source: unable to determine source type of... | jkbeg | 433d | needs triage | 60 | 94 | 35 | Snapcraft's 8_core22 container resolves extension data under /usr/share while the image installs it in site-packages, breaking ROS 2 builds; the path mismatch remains in current code. |
|
snapcraft (launchpad) issue #1896820 |
Snapcraft can't be run against a local or remote LXD project | ~stgraber | 2227d | needs triage | 60 | 55 | 9 | Support user-selected local and remote LXD projects is still pending; Snapcraft hard-codes its own local LXD project, while remote-instance work is tracked separately. |
|
craft-parts issue #1364 |
File source handler ignores changes to the file | dmitry-lyfar | 381d | keep open | 60 | 90 | 28 | Confirmed triaged bug: source-type: file lacks pull-step change detection, so touched or edited files are not recopied; dump and Python plugin cases are affected. |
|
snapcraft issue #5146 |
Snap: Snapcraft currently relies on `libapt` during configure | Meulengracht | 710d | close resolved | 60 | 92 | 30 | Resolved in current code: snapcraft_legacy and its configure-time apt import chain were removed; the hook now loads SnapConfig without relying on libapt from the base. |
|
snapcraft (launchpad) issue #1995424 |
A way to get debug symbols | ~ilya-fedin | 1457d | keep open | 60 | 45 | 4 | Requests debug-symbol distribution for diagnosing snap crashes; maintainer reports active design work, while uploadable components offer a partial path but are documented as not production ready. |
|
rockcraft issue #905 |
rockcraft 1.12.0 fails but 1.11.0 works with django-framework extension | toabctl | 492d | needs triage | 60 | 60 | 22 | rockcraft 1.12.0 regression: django-framework extension prime fails with FileNotFoundError in craft_parts apply_permissions; 1.11.0 works. No maintainer triage yet. |
|
rockcraft issue #307 |
nodejs snap installed through stage-snaps is not usable in the final image | nrobinaubertin | 1220d | close resolved | 60 | 96 | 26 | Staged Node.js snaps lack their core20 dynamic loader in final Ubuntu OCI images. The lifecycle layer fix for usrmerge symlink collisions appears to resolve this. |
|
rockcraft issue #1385 |
`plugin: python` uses `$CRAFT_PART_INSTALL` in console-script polyglot... | himax16 | 22d | keep open | 60 | 80 | 24 | Python plugin console scripts embed build-time $CRAFT_PART_INSTALL shebangs; long paths trigger pip polyglot shebang not rewritten, causing runtime exit 127. Triaged, awaiting fix. |
|
snapcraft issue #5684 |
Support a `-f|--file` or `-C|--directory` flag | dilyn-corner | 448d | keep open | 60 | 68 | 13 | Enhancement request for lifecycle flags to select a snapcraft.yaml file or project directory, enabling monorepo and variant builds. Maintainers recognize the need and called it a possible Snapcraft 9 candidate; implementation is not present. |
|
rockcraft issue #582 |
allow adding customized label | henrymao-zz | 870d | needs triage | 60 | 80 | 34 | Feature request to allow users to specify custom OCI labels in rockcraft.yaml. Currently only standard labels (version, title, description, license) are set automatically. No maintainer response after 863 days. |
|
charmcraft issue #2631 |
Multiple `charmcraft pack` fail on mismatching platforms | simondeziel | 210d | needs triage | 60 | 70 | 19 | Consecutive charmcraft pack runs with different platform sets fail: second charm (24.04 only) launches a 22.04 instance and errors 'Platform not found'. Regression from 4.0.1, still present in 4.3.1, no maintainer response. |
|
snapcraft issue #6497 |
kernel plugin: /proc/version_signature is empty for kernels built from... | canonical-nicoharnois | 14d | needs triage | 60 | 80 | 34 | Kernel plugin leaves CONFIG_VERSION_SIGNATURE empty when building from Ubuntu kernel source with flavour config. Reporter has a patch ready. |
|
craft-parts pr #1750 |
perf: stage collision and cleanup performance optimizations | chris-bainbridge | 28d | needs review | 60 | 65 | 12 | Nine perf optimizations for stage-collision checks and lifecycle-state cleanup; +1061/-82 across 12 files. Pending review; most CI green, OSV-scanner and ppc64el fast tests failing. |
|
craft-application pr #1206 |
Issue 1205 remote clean build stale repos | enriqueesanchz | 28d | needs review | 60 | 60 | 16 | Adds best-effort cleanup of stale Launchpad git repositories during remote builds; under review, CI title check failing and tests pending. |
|
craft-parts issue #889 |
add "always run" plugin hook | flotter | 730d | needs triage | 58 | 57 | 10 | Requests an optional plugin hook that runs even when sources are unchanged, supporting build IDs and propagation of craft.yaml configuration; it remains untriaged. |
|
craft-parts issue #1026 |
Part's source directory needs to be read-only | vpa1977 | 609d | needs triage | 58 | 58 | 9 | Request to protect part source directories from build-step mutations so subsequent builds produce consistent output; the reproducibility concern remains unassessed. |
|
rockcraft issue #683 |
File capabilities (xattrs) are not preserved in final ROCK image layers. | aznashwan | 793d | keep open | 58 | 90 | 17 | Maintainer-acknowledged bug with a complete reproducer: security.capability xattrs on primed files are lost when ROCK image layers are packaged |
|
snapcraft issue #6076 |
Differentiate “need manual review” status in "snapcraft upload" from errors | Jehan | 240d | keep open | 58 | 79 | 22 | `snapcraft upload` needs a documented, distinct outcome for revisions awaiting manual review so CI can distinguish them from failures; maintainer linked open work in #6081. |
|
fetch-service issue #419 |
Missing inspectors for JARs (Maven) | Vyom-Yadav | 463d | close resolved | 58 | 72 | 26 | JAR downloads from repo1.maven.org were not recognized. JAR handling was fixed by commit ea913b3 (#535), but Java-archive MIME and noncanonical Maven host support remain unresolved concerns. |
|
snapcraft (launchpad) issue #1918999 |
stage-packages for classic snaps silently drop core20 snap debs | ~racb | 2057d | keep open | 58 | 78 | 25 | Classic snaps using stage-packages lose dependencies already present in core20 because base-package filtering silently omits them; a bare-base workaround exists, but the underlying filtering bug remains open. |
|
charmcraft issue #2247 |
The charm build failed due to the recent release of wheel version 0.46.1. | adglkh | 568d | needs triage | 58 | 87 | 33 | Wheel 0.46.1 broke Charmcraft source-dependency charm builds with a missing bdist_wheel command; pinning 0.45.1 works, but the issue remains untriaged. |
|
snapcraft (launchpad) issue #1998269 |
Gnome extension breaks fontconfig for some applications | ~zoopgoop | 1430d | needs triage | 58 | 64 | 14 | Untriaged GNOME-extension fontconfig failures block Wine initialization and Steam UI fonts; a minimal reproducer and FONTCONFIG_FILE workaround exist, but root cause and current impact remain unverified. |
|
snapcraft issue #5735 |
Modifying a part's `build-environment` doesn't trigger a rebuild | dilyn-corner | 427d | close resolved | 58 | 96 | 48 | Build-environment changes failed to invalidate cached part builds; craft-parts 2121e8ed fixed rebuild tracking, and current Snapcraft requires the fixed 2.37.1 release. |
|
snapcraft (launchpad) issue #1576282 |
Snaps built from deb can't be gettext translated | ~seb128 | 3836d | close resolved | 58 | 87 | 24 | Deb-built snap gettext localization was historically blocked by missing locale data and hard-coded /usr paths; current desktop integration sets LOCPATH and redirects bindtextdomain to snap locale directories. |
|
snapcraft issue #4440 |
snapcraft configure hook fails: segmentation fault | barrettj12 | 1087d | keep open | 58 | 55 | 10 | Snapcraft installation segfaults in the configure hook on an AWS aarch64 runner; the workflow is reproducible, but the requested hook-task logs are still missing. |
|
snapcraft issue #4658 |
File permissions leak through to built snap | samuelallan72 | 961d | needs triage | 58 | 87 | 24 | A restrictive host umask can preserve inaccessible source modes in built snaps, reproducing an OpenStack runtime PermissionError; the report remains untriaged and unresolved. |
|
snapcraft (launchpad) issue #1999321 |
Snapcraft is stuck on "launching instance..." indefinitely | ~mjakeman | 1418d | close resolved | 58 | 92 | 30 | Endless LXD startup on failed container DNS now times out via craft-providers; Snapcraft 7.5.4 is recorded as fixing the wait. Multipass arm64 and Docker diagnostics remain separately tracked. |
|
craft-providers issue #684 |
Create a generic craft LXD profile | dilyn-corner | 749d | needs triage | 58 | 50 | 13 | A dedicated craft LXD profile is proposed to isolate build containers from user-edited defaults; the open enhancement still needs a decision on shared versus per-user profiles. |
|
craft-parts issue #770 |
NPM Plugin: wrong node version is used to build the package | dimaqq | 847d | keep open | 58 | 72 | 19 | NPM node setup is skipped when override-build replaces built-in steps, so builds fall back to system Node 12.22.9; a manual-install workaround and future pre-build hook are proposed. |
|
snapcraft (launchpad) issue #1804845 |
Applications requiring UTF-8 fail | ~merlijn-sebrechts | 2897d | needs triage | 58 | 57 | 13 | UTF-8-dependent packaged apps can fail because host locales are unavailable; no generic fallback is visible, and the open report remains untriaged despite documented workarounds. |
|
charmcraft issue #2707 |
Charmcraft confuses the current directory with the project directory when... | gycsaba96 | 156d | close resolved | 58 | 84 | 23 | Charmcraft 4.2.1 mixed the CWD and -p project files when both had charmcraft.yaml, breaking nested pack builds and CI; targeted project-directory fixes are present in current code. |
|
snapcraft (launchpad) issue #1965814 |
snap contains python 3.8 and 3.9 libs | ~kenneth-loafman | 1683d | keep open | 58 | 45 | 8 | A core20 build staged Python 3.8 and 3.9 files; Duplicity added a packaging workaround, but the underlying Snapcraft conflict and potential side effects remain unresolved. |
|
rockcraft issue #433 |
isolate parts of a rockcraft build process from each other | ca-scribner | 1063d | needs triage | 58 | 47 | 2 | Requests per-part build isolation so build-packages and other environment side effects do not leak between parts. It remains open, unlabelled, and without maintainer discussion or a located implementation. |
|
snapcraft (launchpad) issue #1835638 |
inconsistent to arch behaviour | ~ondrak | 2672d | needs triage | 58 | 70 | 13 | Snapcraft 3.6 advanced grammar can omit stage-packages on native builds and mix host/target packages in nested on/to cases; the old report remains open and untriaged. |
|
snapcraft (launchpad) issue #1885074 |
stage-packages behaviour inconsistent | ~ondrak | 2317d | needs triage | 58 | 64 | 18 | Snapcraft 4.0.7 reportedly creates an empty core18 arm64 snap when stage-packages use :arm64 suffixes natively, while cross-compilation succeeds; no triage or resolution is recorded. |
|
snapcraft (launchpad) issue #2065801 |
Snapcraft hangs with no space left on device | ~nteodosio | 897d | needs triage | 58 | 48 | 10 | Reported in June 2024: an ENOSPC during a large Chromium build could leave the builder hanging instead of returning control; the cause remains untriaged. |
|
snapcraft (launchpad) issue #1859046 |
Allow Custom Build Certificate Authority And Proxy Credentials | ~zicklag | 2485d | close resolved | 58 | 96 | 31 | LXD build proxy and custom CA support was implemented through proxy CLI/provider plumbing and an option for installing custom CA certificates in build environments. |
|
rockcraft issue #656 |
Properly support `build-snaps` with differing versions for independent parts. | aznashwan | 822d | needs triage | 58 | 86 | 12 | Reproducible build-snaps conflict: parts requesting Go 1.18 and 1.21 both build with 1.18.10. The issue has no maintainer triage or activity. |
|
snapcraft issue #5214 |
Please add revisions of `stage-snaps` to `manifest.yaml` | jhenstridge | 645d | keep open | 58 | 80 | 15 | Record resolved stage-snaps revisions in manifest.yaml for reproducibility and debugging; maintainers recognize the gap and describe a craft-parts state/API approach, but no implementation is present. |
|
snapcraft-rocks issue #109 |
Failed to pull source: unable to determine source type of... | jkbeg | 386d | keep open | 58 | 86 | 35 | The :8_core22 image stages extensions under site-packages while Snapcraft expects them under /usr/share; the mismatch remains open, with a symlink workaround reported. |
|
snapcraft (launchpad) issue #2073910 |
snapcraft cannot connect through a transparent SSL proxy | ~rudratrivedi | 828d | needs triage | 58 | 78 | 22 | Snapcraft 7.5.5/8.3.1 rejects a system-trusted MITM proxy CA; setting REQUESTS_CA_BUNDLE works, but the report remains untriaged. |
|
craft-parts pr #721 |
fix(part_handler): fetch correct target stage packages | dilyn-corner | 916d | close stale | 58 | 28 | 9 | Targets architecture for stage-package fetches, but omits architecture:all handling; approved once with an unresolved regression-review thread and no CI after 889 days. |
|
fetch-service issue #329 |
Is the support complete for `rock` images? (potentially new inspector required) | Vyom-Yadav | 640d | keep open | 58 | 74 | 14 | Rockcraft's Ubuntu OCI base remains unsupported: gzip layer blobs are rejected as unknown; a maintainer says an OCI inspector is planned. |
|
craft-application issue #821 |
5.5.0 changes pack semantics if the project file has different metadata | javierdelapuente | 462d | close resolved | 58 | 98 | 31 | Metadata-only charmcraft.yaml edits were skipped as "Already packed," leaving stale .charm artifacts; Charmcraft PR #2890 is reported to fix repacking after the edit. |
|
craft-parts issue #561 |
Meson Plugin with python or gjs based app | soumyaDghosh | 1119d | needs triage | 58 | 67 | 15 | Meson-built Python/GJS apps retain invalid build-time shebangs and fail to launch; a reproducer is linked, but the unlabelled issue has no maintainer triage or fix. |
|
snapcraft (launchpad) issue #1917919 |
snapcraft validate (and possibly other operations requiring gpg passphrases)... | ~roadmr | 2064d | keep open | 58 | 76 | 26 | GPG-backed assertion signing can fail on headless systems because no terminal is passed to gpg-agent; exporting GPG_TTY=$(tty) is reported to fix it |
|
snapcraft issue #5485 |
Provide option to filter stage packages | kubiko | 535d | keep open | 58 | 79 | 18 | Enhancement to exclude unwanted dependency packages from stage-packages after base migrations; triaged and maintainer-endorsed, with reproducible core22/core24 examples showing major snap-size growth, but remains unimplemented. |
|
snapcraft (launchpad) issue #1681861 |
classic snaps recurse | ~chris.macnaughton | 3488d | close resolved | 58 | 86 | 38 | Classic PATH recursion was addressed by commit 343ac2862, which added the snapcraft-runner workaround; current metadata tests still expect that runner in command chains. |
|
snapcraft (launchpad) issue #2161192 |
python plugin not working at all with snapcraft 9+ | ~t-a-k | 103d | close resolved | 58 | 67 | 23 | Core26 Python plugin builds and module loading were fixed; packaging Python separately is now documented as required by the base. |
|
snapcraft (launchpad) issue #1913599 |
remote-build always recovers, even when --recover is not specified | ~nymea | 2100d | close resolved | 58 | 92 | 37 | remote-build recovery is now opt-in: interrupted builds are resumed only with --recover, addressing the reported automation and artifact-provenance risk. |
|
charmcraft issue #1042 |
add `charmcraft purge` or `charmcraft cleanall` command to clean all instances | sed-i | 1333d | keep open | 58 | 71 | 13 | Proposed `charmcraft purge` to reclaim disk space by clearing provider caches and build instances; the design is taking shape, but implementation is absent and the former blocker is resolved. |
|
debcraft issue #151 |
[Feature] Add support for makeshdeps symbols file | hector-cao | 185d | needs triage | 58 | 67 | 16 | Requested .symbols generation for native shared libraries remains unimplemented; debcraft generates shlibs and consumes symbols files but has no helper that writes them. Needs maintainer triage. |