Issue & PR triage
Loading...
Showing 100 of 502 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
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. |
|
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. |
|
starflow issue #185 |
lint-python.yaml: pull-requests permission from #184 causes startup_failure... | lengau | 37d | needs triage | 72 | 85 | 26 | PR #184's pull-requests: read in lint-python.yaml breaks every downstream QA caller with startup_failure, since reusable workflows can only narrow caller permissions. craft-parts/craft-application QA broken; untriaged. |
|
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 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 #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 #895 |
Add a LXD VM provider | lengau | 275d | needs triage | 66 | 58 | 13 | Add a VM-backed LXD provider for Imagecraft loop-device support; the requested capability remains open and is absent from the current provider tree. |
|
imagecraft issue #305 |
Generate sparse images | alderic-coroir | 217d | needs triage | 65 | 50 | 15 | Feature request to generate sparse images (via img2simg) for Ubuntu Core, arguing raw images undermine footprint and delta updates; no triage or comments 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. |
|
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 (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. |
|
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. |
|
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-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. |
|
snapcraft (launchpad) issue #1824473 |
Changed stage-snaps property does not make pull step dirty | ~brlin | 2758d | 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. |
|
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 (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 #1780 |
A part's install directory doesn't get cleaned if the prior build failed. | lengau | 7d | needs triage | 60 | 80 | 38 | Install directory not cleaned after failed build, causing subsequent builds to fail with unclear errors. New issue with no labels or maintainer response. |
|
rockcraft issue #905 |
rockcraft 1.12.0 fails but 1.11.0 works with django-framework extension | toabctl | 493d | 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. |
|
charmcraft issue #2132 |
Prototype integration of testing service | cmatsuoka | 636d | needs triage | 60 | 45 | 5 | Feature request to integrate craft-application's testing service into charmcraft, including a strategy for testing multi-platform artefacts. Still unimplemented; no labels or maintainer triage in GitHub, Jira ticket CRAFT-4073 created. |
|
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. |
|
fetch-service issue #354 |
Set up the proxy on a random port that's queryable from the control API | lengau | 602d | needs triage | 60 | 68 | 18 | Requests a runtime-selected proxy port exposed through the control API; it remains open and unlabeled, and current code still uses a fixed default proxy port. |
|
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. |
|
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. |
|
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 issue #822 |
[Python plugin]: Consider including a rust compiler by default | lengau | 800d | needs triage | 58 | 63 | 21 | Open, untriaged request to provision Rust by default for Python native-extension builds; the current Python v2 plugin requests neither build snaps nor build packages. |
|
snapcraft (launchpad) issue #2015370 |
Undefined Symbol Error While trying to launch Application from a snap... | ~ameya-v-singh | 1303d | needs triage | 58 | 44 | 7 | Snap-installed VS Code cannot launch host applications due to a core20 GLIBC_PRIVATE pthread-symbol mismatch; the report remains untriaged and lacks snap revision and host details. |
|
craft-parts issue #974 |
Python plugins install wheels for the host architecture, not the target architecture. | lengau | 652d | needs triage | 58 | 76 | 14 | Cross-compiled Python plugin parts can succeed while installing host-architecture wheels, leaving binary dependencies such as cryptography unusable; the report remains open and 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. |
|
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. |
|
imagecraft issue #381 |
[Feature] Support s390x bootloader installation using zipl | lengau | 100d | needs triage | 58 | 70 | 16 | Add s390x bootloader support via zipl, skipping GRUB and generating /etc/zipl.conf; the feature is open, unlabeled, and awaiting maintainer triage. |
|
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. |
|
craft-application issue #386 |
Explicitly separate public and private APIs | lengau | 835d | needs triage | 58 | 46 | 6 | API visibility remains undefined: launchpad and remote already expose __all__, but no policy classifies them as public or private and no implementation plan is provided. |
|
snapcraft (launchpad) issue #1885074 |
stage-packages behaviour inconsistent | ~ondrak | 2318d | 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 #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. |
|
snapcraft (launchpad) issue #1836206 |
snapped app with qtwebengine fails to run | ~teoretyk | 2667d | needs triage | 58 | 49 | 7 | QtWebEngine apps abort at startup: the helper and resources are initially missing, and after a bind-mount workaround Chromium still fails in DenySetgroups. The report remains untriaged. |
|
craft-parts issue #675 |
Python plugin is not idempotent on iterative builds due to faulty `PATH` set up | NucciTheBoss | 972d | needs triage | 58 | 88 | 27 | Python plugin iterative rebuilds can resolve python3 from the prior install venv, causing ensurepip to fail; the current legacy plugin still prepends install/bin to PATH and needs triage. |
|
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. |
|
fetch-service issue #364 |
Inspectors contain valid URL placeholders | cmatsuoka | 591d | needs triage | 58 | 64 | 15 | Hard-coded PyPI URL matchers remain in package inspectors; the requested repository-wide placeholder audit is still open, unlabeled and awaiting maintainer triage. |
|
snapcraft issue #4587 |
Improvements to the PythonPlugin for core24 | tigarmo | 986d | needs triage | 58 | 55 | 12 | Core24 Python-plugin support merged in #4666, but the proposed interpreter-symlink and default-shebang linters plus broader Python/GNOME integration work remain open and untriaged. |
|
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. |
|
craft-parts issue #1122 |
craft-parts doesn't track primed files when using `override-prime` | mr-cal | 506d | needs triage | 58 | 91 | 34 | override-prime stores empty file metadata instead of tracking scriptlet-created content, breaking primed-stage-package manifests and related Snapcraft workflows. |
|
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. |
|
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. |
|
charmcraft issue #2247 |
The charm build failed due to the recent release of wheel version 0.46.1. | adglkh | 569d | 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. |
|
imagecraft issue #379 |
[Feature] Support non-EFI ARM and RISC-V booting via U-Boot (extlinux.conf /... | lengau | 100d | needs triage | 58 | 58 | 7 | Maintainer request for non-EFI U-Boot configuration and raw SPL/U-Boot flashing on armhf, arm64, and riscv64; current code supports only EFI/BIOS and remains untriaged. |
|
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 #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. |
|
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. |
|
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 #1999385 |
Removing a `package-repositories:` entry does not affect existing containers | ~saviq | 1417d | needs triage | 57 | 69 | 17 | Removing a package-repositories entry leaves its APT source in reused build containers, risking unintended package resolution. The report remains open, untriaged, and uncommented; no resolving change was found. |
|
rockcraft issue #432 |
improve the speed rockcraft's iterative design experience | ca-scribner | 1063d | needs triage | 57 | 40 | 6 | Request to speed repeated rockcraft pack runs with smarter caching; remains open, unlabelled, and apparently untriaged despite a clear developer-productivity goal. |
|
snapcraft (launchpad) issue #1987853 |
snapcraft terminates override-build script prematurely without error | ~nicolasbock | 1525d | needs triage | 57 | 81 | 24 | override-build silently skips trailing commands when a build tool consumes stdin on core20+, but piping a separate stdin stream works around it; the underlying failure remains untriaged. |
|
craft-parts issue #806 |
sources module unaware of the environment | upils | 811d | needs triage | 57 | 82 | 24 | Source pulls reportedly ignore the consuming application's environment, so snap-packaged consumers can miss snap PATH tools and invoke incompatible binaries; the issue remains untriaged. |
|
charmcraft issue #2273 |
charmcraft.yaml deleted while packing (working tree not clean) | carlcsaposs-canonical | 549d | needs triage | 56 | 86 | 25 | Packing a Charmcraft 3.4.3 reproducer deletes tracked charmcraft.yaml before a dump part, making git describe --dirty tag release builds incompatible; untriaged and apparently unresolved |
|
charmcraft issue #2720 |
`organize` part expects distinct subdirectories since 4.2.1 | natalian98 | 143d | needs triage | 56 | 87 | 20 | Charmcraft 4.2.1 regressed dump-part organize: two glob mappings targeting schemas/ now fail; distinct subdirectories work around it, and the report remains untriaged. |
|
craft-application issue #676 |
Use a different instance name when using the fetch service | lengau | 602d | needs triage | 56 | 61 | 19 | A separate provider-instance name is requested for fetch-service runs so they do not destroy the normal build instance; the issue remains open, unlabelled, and without discussion. |
|
craft-store issue #208 |
Rewrite with `httpx` | lengau | 776d | needs triage | 55 | 55 | 8 | Maintainer-filed request to rewrite craft-store's HTTP layer with httpx. Migration is partially done (httpx auth classes, Ubuntu One login) but http_client.py/base_client.py still use requests. Open 748 days, no labels, no triage. |
|
rockcraft issue #30 |
redundant whiteouts cause a path error | cjdcordeiro | 1648d | needs triage | 55 | 66 | 14 | Same-layer OCI whiteouts from package installation trigger path errors in tools such as Dive; the report remains open and has not been retested against current dependencies. |
|
snapcraft issue #6064 |
Extend advanced grammer to all keys of snapcraft | soumyaDghosh | 248d | needs triage | 55 | 70 | 12 | Advanced grammar remains limited to selected keys, limiting clean architecture-specific apps, part omission, and plugin parameters. The feature is untriaged; plugin-parameter support is tracked in craft-application #985. |
|
craft-parts issue #1666 |
Source pull step doesn't retry on transient network failures | lengau | 78d | needs triage | 55 | 62 | 20 | SourceHandler.download() in craft_parts/sources/base.py and GitSource._run() issue single un-retried requests.get()/git clone, so transient network errors fail the whole pull step. Unlabelled, no maintainer comments. |
|
snapcraft issue #4935 |
snapcraft cannot connect through a transparent SSL proxy | ghost | 827d | needs triage | 55 | 76 | 22 | Snapcraft 7.5.5/8.3.1 was reported to reject a system-trusted MITM proxy CA for host commands such as whoami; it remains untriaged and unanswered. |
|
snapcraft (launchpad) issue #1842376 |
No standard way of specifying memory requirements for multipass build VMs | ~dmitriis | 2614d | needs triage | 55 | 74 | 15 | Open, unlabelled request for a project-level Multipass RAM setting: Go builds are OOM-killed at the documented 2 GiB default, while only an environment-variable override is available. |
|
craft-parts issue #1058 |
SCP formatted git source cause infinite loading when packing | alesancor1 | 575d | needs triage | 55 | 84 | 29 | SCP-style Git sources can wait indefinitely for SSH host-key input during pull instead of returning a clone failure; the issue remains open, unlabelled, and untriaged. |
|
imagecraft issue #380 |
[Feature] Support ppc64el bootloader installation via Open Firmware... | lengau | 100d | needs triage | 55 | 82 | 14 | Adds a scoped design for booting ppc64el images with GRUB Open Firmware and PReP partitions; code still lacks ppc64el GRUB/PReP support, and the issue has no triage. |
|
snapcraft-rocks issue #111 |
Failed to create rock (Failed to stage: parts list the same file or... | asilnov | 314d | needs triage | 55 | 62 | 14 | Rock creation on core22-8 fails during staging because the snapcraft part and its overlay disagree on Python 3.10 files; the unlabelled report has no maintainer response. |
|
craft-parts issue #962 |
CI: create test workflow to build application docs upon changing `docs/common` | lengau | 658d | needs triage | 55 | 72 | 14 | Open CI feature request to build all downstream application docs when a PR changes docs/common, preventing reusable-documentation integration failures before merge. |
|
snapcraft issue #4569 |
pkg-config based project don't work with kde-neon extension | chubinou | 995d | needs triage | 55 | 90 | 25 | An exact core22 reproducer shows kde-neon no longer exposes Qt5 .pc files to pkg-config; the unlabelled report remains untriaged, and current extension code still omits PKG_CONFIG_PATH. |
|
craft-parts issue #1217 |
cargo-use: support Rust workspaces better | Saviq | 430d | needs triage | 55 | 72 | 16 | Feature request: cargo-use plugin only supports a single crate (reads [package] from one Cargo.toml) and breaks on workspace crates that inherit metadata; proposal is a CARGO_PACKAGES key plus `cargo package --no-verify` build-override. Untriaged, no maintainer response. |
|
craft-parts issue #1291 |
BUILD step of a part organizing to the overlay should invalidate overlay... | upils | 413d | needs triage | 55 | 82 | 25 | A part BUILD that organizes files into the overlay can change lower overlay layers without invalidating dependent OVERLAY steps; the precise reproducer exists but the open issue remains untriaged |
|
snapcraft (launchpad) issue #1807125 |
After snapcraft refresh, old multipass containers no longer work | ~igorljubuncic-deactivatedaccount | 2884d | needs triage | 55 | 63 | 14 | Snapcraft 3.0.1 could reuse incompatible Multipass VMs after a 3.0.0 refresh, causing a misleading missing-project error until snapcraft clean; the report is untriaged. |
|
snapcraft (launchpad) issue #2147036 |
Lots of noise produced at the end of build | ~nteodosio | 211d | needs triage | 55 | 65 | 20 | A failed snapcraft --debug build prints a huge escaped duplicate of its output before opening a shell, obscuring the error; the issue remains open and untriaged. |
|
snapcraft (launchpad) issue #2158702 |
Snapcraft API not answering | ~t-a-k | 121d | needs triage | 55 | 45 | 10 | api.snapcraft.io v2/snaps/info intermittently returns HTTP 200 with no parsable version (~70% failures), breaking version detection in GitHub remote builds; unlabelled, no maintainer reply, awaiting triage on the store API side |
|
snapcraft (launchpad) issue #1823308 |
automatically inject dbus slot & use it | ~apachelogger | 2764d | needs triage | 55 | 68 | 17 | Requests automatic D-Bus slot injection from desktop metadata, including X-DBUS-ServiceName; it remains open and untriaged, with current common-id and explicit bus-name support not covering the requested inference. |
|
craft-parts issue #674 |
Symlink fixing logic doesn't consider relative location changes when using organize | dilyn-corner | 975d | needs triage | 55 | 87 | 19 | Package normalization rewrites absolute symlinks before organize moves their link or target, leaving relative links dangling; a detailed reproducer exists, but the issue has not been maintainer-triaged. |
|
craft-archives issue #141 |
No longer works on macOS | Saviq | 692d | needs triage | 55 | 64 | 19 | Snapcraft via Homebrew crashes at startup on macOS because craft-archives eagerly imports the omitted python-debian module; responsibility for the fix remains unresolved. |
|
imagecraft issue #366 |
Correctly restore resolv.conf | lengau | 127d | needs triage | 55 | 70 | 21 | Maintainer request to preserve edits to /etc/resolv.conf during mount teardown; it remains open, unlabelled, and lacks a reproducer or follow-up discussion. |
|
rockcraft issue #459 |
Add support for pinning the build and build-base images | arturo-seijas | 1010d | needs triage | 55 | 68 | 13 | Digest pinning for base and build-base images remains unsupported; current validation only accepts enumerated releases, limiting reproducibility and Renovate integration. |
|
snapcraft (launchpad) issue #1681152 |
snap may execute host, not wrapped, executables | ~cgull | 3491d | needs triage | 55 | 60 | 21 | Classic snap wrappers may execute host binaries instead of snap payloads; a concrete mosh reproducer exists, but no triage followed and later PATH-related work may apply. |
|
rockcraft issue #654 |
Allow for configurable `skopeo` credentials during pulling of the ROCK base image. | aznashwan | 822d | needs triage | 55 | 76 | 20 | Configurable skopeo source credentials for ECR base-image pulls remain unimplemented and untriaged; the current Image class exposes no credential option. |
|
snapcraft issue #6299 |
Snapcraft upload+release not capturing review error | farshidtz | 129d | needs triage | 55 | 68 | 17 | snapcraft upload --release prints "Revision N created ... and released to ..." even when store review failed ("Status: error while processing"), leaving the revision in no channel. Two examples given; no maintainer response yet. |
|
snapcraft (launchpad) issue #1996206 |
Linter is checking against host libs when using --build-for argument | ~dbruno74 | 1449d | needs triage | 55 | 70 | 13 | Cross-architecture builds may lint arm64 libraries against x86_64 core22 paths; the report remains open, unlabelled, and untriaged without a confirmed fix. |
|
charmcraft issue #2816 |
`charmcraft pack` fails on Resolute | jameinel | 83d | needs triage | 55 | 63 | 11 | charmcraft pack fails on Ubuntu Resolute 26.04 hosts when using a Jammy 20.04 build base: snapd inside the LXD build instance cannot reload snap-confine AppArmor profiles; no maintainer response yet. |
|
snapcraft (launchpad) issue #1862516 |
Missing items in LD_LIBRARY_PATH break numpy stage-packages | ~aglavic | 2454d | needs triage | 55 | 70 | 16 | Numpy staged via stage-packages fails at runtime because libblas.so.3 and liblapack.so.3 sit in nested blas/lapack directories outside the library search path; the old issue is untriaged. |
|
imagecraft issue #280 |
Support for SBOM generation | rthill91 | 245d | needs triage | 55 | 60 | 13 | Feature request to add a create_sbom option to imagecraft.yaml and emit an SBOM build artifact for CPC images; it is unlabelled, has no maintainer response, and no implementation is present. |
|
rockcraft issue #681 |
New OverlayUnmountError with 5.21 lxd | tigarmo | 794d | needs triage | 54 | 61 | 11 | Overlay-based spread tests fail to unmount under LXD 5.21 with exit status 32; the open, unlabelled report has only an automated Jira comment and no diagnosis. |
|
debcraft issue #93 |
Automatically use source package's architectures in non-native mode | lengau | 238d | needs triage | 54 | 84 | 20 | Non-native builds still default to every standard Debian architecture instead of deriving platforms from debian/control; the feature remains open, unlabeled, and without maintainer discussion. |
|
charmcraft issue #2336 |
Can't login in headless multipass VM with 24.04 | kimwnasptd | 500d | needs triage | 54 | 88 | 28 | Open Charmcraft login failure on headless Ubuntu 24.04 Multipass VMs: Python selects keyring.backends.null.Keyring, so credentials cannot be retrieved; only a backend override is known. |
|
snapcraft (launchpad) issue #1989012 |
package-repositories assumes architecture | ~ondrak | 1513d | needs triage | 52 | 82 | 26 | Snapcraft 7.1.3 injects Architectures: arm64 into an APT source when package-repositories omits architectures; the report is old, untriaged, and may be superseded by later craft-archives handling. |
|
fetch-service issue #156 |
Add inspector for images | jugmac00 | 833d | needs triage | 52 | 47 | 9 | Image inspection is missing, so base images appear as unrecognized artifacts in manifests even though builds succeed; requirements and technical scope remain untriaged. |
|
snapcraft issue #5128 |
KDE Neon 6 broken on arm64 | waveform80 | 741d | needs triage | 52 | 79 | 12 | Reported arm64 kde-neon-6 failure caused by an incomplete kf6-core22 content snap; the issue remains unlabelled and untriaged despite a later related upstream fix. |
|
craft-parts issue #899 |
Craft parts should close stdin when cloning git projects | mr-cal | 721d | needs triage | 52 | 78 | 27 | Git source commands still inherit stdin, so private-repository prompts can hang or produce unhelpful failures in local and remote builds; this request remains open and untriaged. |
|
snapcraft (launchpad) issue #1790004 |
Snapcraft should warn if it produces a snap that the store will reject | ~ej-finneran | 2982d | needs triage | 52 | 62 | 12 | Requests local warnings for Snap Store rejection conditions. The reported permission failure is concrete, but mode validation is absent from current linters and broader local store-check work remains open. |
|
craft-application issue #993 |
`request` should be able to retry upon broken connections | zhijie-yang | 277d | needs triage | 52 | 55 | 16 | remote-build crashes with unhandled ChunkedEncodingError when artifact download breaks mid-stream; request service has no retry support. Still open, no maintainer response, code path unchanged. |
|
debcraft issue #39 |
Validate maintainer names | lengau | 344d | needs triage | 52 | 72 | 21 | RFC822 validation for maintainer, original-maintainer, and uploaders is still absent; the current model leaves these fields unvalidated and the issue is untriaged. |
|
snapcraft (launchpad) issue #2013242 |
Do not allow two different apps to have the same autostart-desktop file | ~3v1n0 | 1310d | needs triage | 52 | 84 | 33 | Requests validation preventing different apps from sharing an autostart .desktop file; current Snapcraft only validates each filename's format, leaving the conflict undetected. |
|
snapcraft (launchpad) issue #2002538 |
override-prime ignore failure on rebuild | ~gbeuzeboc | 1387d | needs triage | 52 | 86 | 26 | A failed override-prime step is cached as complete, letting a second build skip priming and package the snap; an exact old-version reproducer is provided, but the report remains untriaged. |