Showing 100 of 1912 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
rockcraft issue #1385 |
`plugin: python` uses `$CRAFT_PART_INSTALL` in console-script polyglot... | himax16 | 26d | 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 #6526 |
snapcraft tiggers jammy/nobel/resolute backend tests on resolute GH runner | taurus-forever | 5d | needs triage | 60 | 80 | 24 | snapcraft triggers all backend tests (Jammy, Noble, Resolute) on Resolute GH runner instead of only Resolute backend. Issue is open, unlabelled, and awaiting maintainer triage. |
|
craft-parts pr #1599 |
fix(sources): detect local file source changes | gcomneno | 162d | needs review | 60 | 60 | 25 | Adds change detection for local file sources in FileSourceHandler, fixing issue #1364. Approved by 2 reviewers with 1 unresolved comment and 2 failing CI checks. |
|
fetch-service issue #354 |
Set up the proxy on a random port that's queryable from the control API | lengau | 605d | 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. |
|
craft-parts pr #1742 |
feat!: replace OsRelease with distro | lengau | 38d | keep open | 59 | 35 | 8 | Replaces the public OsRelease wrapper with distro across chroot checks, platform detection, Poetry, and tests. Open with lint/files and both minimum-dependency jobs failing; eight checks remain pending. |
|
snapcraft (launchpad) issue #2012504 |
PATH auto extended with stage paths | ~ondrak | 1321d | keep open | 58 | 76 | 25 | Cross-builds can prepend target-architecture staged binaries to a part's build PATH, executing tools such as Python from the wrong architecture. Maintainers acknowledged the defect, which remains open. |
|
imagecraft issue #258 |
Support using gadget.yaml volumes as a source for imagecraft.yaml volume definitions | alderic-coroir | 290d | keep open | 58 | 55 | 5 | Importing gadget.yaml volume layouts into imagecraft.yaml remains open under design discussion, with gadget/snapd consistency and import semantics unresolved. |
|
snapcraft issue #6076 |
Differentiate “need manual review” status in "snapcraft upload" from errors | Jehan | 244d | 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. |
|
snapcraft (launchpad) issue #2161192 |
python plugin not working at all with snapcraft 9+ | ~t-a-k | 107d | 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 #1836206 |
snapped app with qtwebengine fails to run | ~teoretyk | 2671d | 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. |
|
charmcraft issue #1042 |
add `charmcraft purge` or `charmcraft cleanall` command to clean all instances | sed-i | 1337d | 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. |
|
rockcraft issue #656 |
Properly support `build-snaps` with differing versions for independent parts. | aznashwan | 826d | 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 (launchpad) issue #1804845 |
Applications requiring UTF-8 fail | ~merlijn-sebrechts | 2901d | 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 (launchpad) issue #1576282 |
Snaps built from deb can't be gettext translated | ~seb128 | 3840d | 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 (launchpad) issue #1681861 |
classic snaps recurse | ~chris.macnaughton | 3492d | 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. |
|
fetch-service issue #364 |
Inspectors contain valid URL placeholders | cmatsuoka | 595d | 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. |
|
craft-providers issue #684 |
Create a generic craft LXD profile | dilyn-corner | 753d | 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. |
|
snapcraft (launchpad) issue #1999321 |
Snapcraft is stuck on "launching instance..." indefinitely | ~mjakeman | 1422d | 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. |
|
fetch-service issue #419 |
Missing inspectors for JARs (Maven) | Vyom-Yadav | 467d | 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. |
|
charmcraft issue #2707 |
Charmcraft confuses the current directory with the project directory when... | gycsaba96 | 160d | 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. |
|
charmcraft issue #2247 |
The charm build failed due to the recent release of wheel version 0.46.1. | adglkh | 572d | 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 | 1433d | 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 (launchpad) issue #1684225 |
retry store actions when it returns a 503 error | ~elopio | 3484d | keep open | 58 | 72 | 20 | Maintainer-requested resilience for temporary Store 503 responses remains open: all store commands should retry with backoff, but current request handling has no 503-specific retry path. |
|
craft-parts issue #1026 |
Part's source directory needs to be read-only | vpa1977 | 612d | 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 #1908061 |
gnome-3-34 extension is missing libraries | ~christianrauch | 2149d | keep open | 58 | 69 | 10 | GNOME 3.34 extension users can get startup crashes when staged HarfBuzz, GLib, or GIO libraries shadow the content snap; the cause and deletion workaround are known, but no general conflict detection fix is identified. |
|
imagecraft issue #381 |
[Feature] Support s390x bootloader installation using zipl | lengau | 104d | 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. |
|
craft-application issue #386 |
Explicitly separate public and private APIs | lengau | 839d | 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. |
|
craft-parts issue #817 |
Local file changes are not detected | mr-cal | 805d | keep open | 58 | 74 | 17 | Triaged enhancement to mark dump-plugin pull steps dirty when local sources change, including permission-only edits; a maintainer confirmed in 2026 that it remains unimplemented. |
|
snapcraft (launchpad) issue #2065801 |
Snapcraft hangs with no space left on device | ~nteodosio | 901d | 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 #1835638 |
inconsistent to arch behaviour | ~ondrak | 2675d | 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. |
|
rockcraft issue #433 |
isolate parts of a rockcraft build process from each other | ca-scribner | 1067d | 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 #770 |
NPM Plugin: wrong node version is used to build the package | dimaqq | 850d | 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. |
|
craft-parts issue #675 |
Python plugin is not idempotent on iterative builds due to faulty `PATH` set up | NucciTheBoss | 976d | 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. |
|
snapcraft issue #4587 |
Improvements to the PythonPlugin for core24 | tigarmo | 990d | 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. |
|
craft-providers issue #381 |
Improve integration tests | mr-cal | 1174d | keep open | 58 | 74 | 10 | Integration-test overhaul is partially implemented: weekly macOS fast/slow jobs and pytest timing exist, but base-instance behavior tests and full base/provider coverage remain absent. |
|
craft-application issue #821 |
5.5.0 changes pack semantics if the project file has different metadata | javierdelapuente | 466d | 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. |
|
snapcraft issue #4658 |
File permissions leak through to built snap | samuelallan72 | 964d | 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-rocks issue #37 |
Building snaps with `kde-neon` extension is not working | hhromic | 918d | keep open | 58 | 88 | 27 | Snapcraft Rocks images resolve extension sources to the wrong path, breaking kde-neon and GNOME extension builds; the issue remains unresolved. |
|
craft-parts issue #1174 |
Craft parts should rebuild all parts if the list of partitions changes | mr-cal | 475d | keep open | 58 | 89 | 30 | Partition-list changes are not tracked in lifecycle state, so stale builds can place files in incorrect stage or prime partitions; the bug remains open and triaged. |
|
craft-parts issue #1076 |
Give organize access to variables set during the build step #5241 | mr-cal | 560d | keep open | 58 | 67 | 14 | Enhancement to let organize reference variables populated during the build step, enabling paths known only at build time; triaged and still open with no implementation evidence. |
|
snapcraft (launchpad) issue #2015370 |
Undefined Symbol Error While trying to launch Application from a snap... | ~ameya-v-singh | 1307d | 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. |
|
snapcraft (launchpad) issue #1885074 |
stage-packages behaviour inconsistent | ~ondrak | 2321d | 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. |
|
craft-parts issue #1122 |
craft-parts doesn't track primed files when using `override-prime` | mr-cal | 510d | 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. |
|
debcraft issue #127 |
Run lintian automatically as a linter | steinbro | 203d | keep open | 58 | 68 | 22 | Triaged feature request to run Lintian on generated .deb files for parity with traditional Debian builds; override installation exists, but package validation is not implemented. |
|
snapcraft (launchpad) issue #1893262 |
pygtk apps fail with gnome-3-34 extension | ~ken-vandine | 2258d | keep open | 58 | 82 | 26 | Python GTK apps using GNOME extensions still fail in core20/core22 because runtime Python module paths remain incompatible; a minimal reproducer is provided despite an earlier PYTHONPATH fix attempt. |
|
craft-parts pr #721 |
fix(part_handler): fetch correct target stage packages | dilyn-corner | 920d | 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. |
|
snapcraft (launchpad) issue #1918999 |
stage-packages for classic snaps silently drop core20 snap debs | ~racb | 2060d | 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. |
|
craft-parts issue #561 |
Meson Plugin with python or gjs based app | soumyaDghosh | 1123d | 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 #1965814 |
snap contains python 3.8 and 3.9 libs | ~kenneth-loafman | 1687d | 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. |
|
snapcraft (launchpad) issue #1859046 |
Allow Custom Build Certificate Authority And Proxy Credentials | ~zicklag | 2489d | 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. |
|
snapcraft issue #4440 |
snapcraft configure hook fails: segmentation fault | barrettj12 | 1091d | 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 (launchpad) issue #1917919 |
snapcraft validate (and possibly other operations requiring gpg passphrases)... | ~roadmr | 2068d | 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 |
|
rockcraft issue #959 |
Allow Custom Build Contexts | clay-lake | 419d | close resolved | 58 | 84 | 17 | Opt-in monorepo support now mounts the enclosing Git repository, allowing subdirectory rockcraft.yaml files to use shared source elsewhere in the repository. |
|
craft-application issue #1119 |
Prepare instance environment in LP builds | cmatsuoka | 119d | keep open | 58 | 59 | 13 | Launchpad builds still need instance proxy configuration equivalent to local policy-enabled builds; the maintainer-authored requirement is triaged and open, with only an internal CRAFT-5255 sync comment. |
|
snapcraft (launchpad) issue #2073910 |
snapcraft cannot connect through a transparent SSL proxy | ~rudratrivedi | 832d | 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 issue #5485 |
Provide option to filter stage packages | kubiko | 539d | 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 #1759740 |
Library discovery for rpath patching needs to be deterministic | ~kyrofa | 3140d | keep open | 58 | 90 | 23 | RPATH patching still resolves duplicate SONAMEs with an unsorted os.walk, so Snapcraft may choose a library contrary to ld precedence; this maintainer-authored issue remains open. |
|
snapcraft issue #5214 |
Please add revisions of `stage-snaps` to `manifest.yaml` | jhenstridge | 649d | 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. |
|
craft-archives issue #176 |
Allow modifying existing default repositories | lengau | 487d | close resolved | 58 | 94 | 28 | Request to rewrite Ubuntu default repositories is implemented: PR #192 added defaults.use_old_releases to redirect EOL release sources to old-releases.ubuntu.com. |
|
debcraft issue #151 |
[Feature] Add support for makeshdeps symbols file | hector-cao | 189d | 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-parts issue #974 |
Python plugins install wheels for the host architecture, not the target architecture. | lengau | 656d | 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. |
|
snapcraft (launchpad) issue #1913599 |
remote-build always recovers, even when --recover is not specified | ~nymea | 2104d | 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. |
|
craft-parts issue #822 |
[Python plugin]: Consider including a rust compiler by default | lengau | 804d | 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 issue #5735 |
Modifying a part's `build-environment` doesn't trigger a rebuild | dilyn-corner | 431d | 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-rocks issue #109 |
Failed to pull source: unable to determine source type of... | jkbeg | 390d | 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. |
|
craft-archives issue #151 |
Update sources added by craft-archives | mr-cal | 636d | close resolved | 58 | 78 | 31 | Craft-generated deb822 sources now include explicit Architectures fields, including configured target architectures, so the requested cross-compilation behavior for craft-*.sources is already present. |
|
craft-parts issue #1390 |
Warn on outward relative path sources | bepri | 363d | keep open | 58 | 80 | 27 | Warn when parsed part sources are absolute or resolve above Path.cwd(), since managed builds can misread paths or copy the root; triaged and still open. |
|
craft-archives issue #217 |
craft-archives does not remove managed repositories that are no longer in... | lengau | 348d | keep open | 58 | 69 | 8 | Confirmed bug: repositories installed by craft-archives remain configured after removal from craft.yaml; the repro is clear, but safe package rollback and cleanup behavior remain unresolved. |
|
craft-parts issue #889 |
add "always run" plugin hook | flotter | 734d | 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. |
|
imagecraft issue #379 |
[Feature] Support non-EFI ARM and RISC-V booting via U-Boot (extlinux.conf /... | lengau | 104d | 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. |
|
snapcraft (launchpad) issue #1673186 |
the gox classic snap gets stuck consuming a lot of cpu | ~zyga | 3519d | close resolved | 58 | 92 | 28 | Classic snap wrappers could resolve their own /snap/bin launcher and spin in an exec/fork loop. Snapcraft later added a classic-PATH workaround in #2889, resolving the report. |
|
fetch-service issue #329 |
Is the support complete for `rock` images? (potentially new inspector required) | Vyom-Yadav | 644d | 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 #261 |
Commands cannot always load projects with advanced grammar | mr-cal | 966d | close resolved | 58 | 94 | 26 | Resolved by PR #279: commands now auto-select a build target and process advanced grammar even when build-for and platform are omitted. |
|
craft-cli issue #278 |
Support output formats | mr-cal | 763d | keep open | 58 | 48 | 8 | Maintainer-filed feature request (Aug 2023) for a craft-cli API to render data as tables or machine-readable JSON; still unimplemented, tracked as CRAFT-3513, and blocking snapcraft#5060. |
|
snapcraft (launchpad) issue #1921418 |
wrong architecture of stage-snaps when cross building | ~ondrak | 2048d | keep open | 58 | 87 | 26 | Cross-building downloads host-architecture stage-snaps instead of build-for artifacts; the acknowledged craft-415 bug appears unresolved in current craft-parts. |
|
snapcraft issue #5997 |
Stage package filtering doesn't deal with foreign arch packages (e.g. i386 on amd64) | Saviq | 276d | keep open | 58 | 82 | 15 | Foreign-architecture stage packages such as xz-utils:i386 are mishandled by Snapcraft's name-only base-package filter, duplicating i386 libraries in core24/core26 snaps; maintainers recognize it as a design-first craft-parts bug, still unresolved. |
|
snapcraft (launchpad) issue #1566331 |
snapcraft autotools plugin doesn't support building other architectures | ~cmiller | 3863d | close resolved | 58 | 88 | 27 | Autotools cross-compilation is now supported through target build-for selection, CRAFT_ARCH_TRIPLET_BUILD_FOR, and --host configuration; the historical request has been implemented. |
|
snapcraft (launchpad) issue #1921397 |
Cant build snaps with snapcraft when snap store is down | ~bugraaydogar | 2048d | keep open | 58 | 61 | 12 | Reported Snap Store outages can block builds; maintainers identified refresh, base, extension, injection, and default-provider paths, but no complete fix or current reproducer is documented. |
|
charmcraft issue #2461 |
uv plugin doesn't cache wheels to LXC host | carlcsaposs-canonical | 388d | keep open | 58 | 84 | 19 | uv with no-binary builds caches inside the LXC guest instead of CRAFT_SHARED_CACHE; the bug remains open and is blocked on craft-providers PR #900. |
|
craft-parts issue #1369 |
Chisel slices always cut for the host architecture | lengau | 384d | keep open | 58 | 76 | 23 | Confirmed bug: Chisel cuts stage and build slices without the target architecture, causing cross-compiles to receive host-architecture payloads. The issue remains open and needs implementation. |
|
rockcraft issue #683 |
File capabilities (xattrs) are not preserved in final ROCK image layers. | aznashwan | 797d | 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 |
|
craft-parts issue #766 |
The prime step uses the install dir when creating a list of migrateable filesets | mr-cal | 853d | keep open | 58 | 70 | 10 | Prime can fail after stage exclusions because its fileset is computed from install rather than staged content; the proposed fix is blocked by undefined overlay-cleaning semantics. |
|
charmcraft issue #2211 |
Kubernetes Resource Requests in charmcraft.yaml | alexdlukens | 606d | keep open | 57 | 43 | 4 | Valid feature request for charm-declared default container CPU and memory requests; maintainers acknowledge it but say Juju-side support and a cross-project design are required. |
|
craft-parts issue #806 |
sources module unaware of the environment | upils | 815d | 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. |
|
fetch-service issue #653 |
Force upstream cache revalidation for mutable repository metadata | lengau | 38d | keep open | 57 | 70 | 19 | Maintainer-filed: stale proxy-cached apt InRelease can predate a newly published Packages.gz, triggering validatePackagesFile checksum failures (HTTP 403). Proposed fix: inject Cache-Control: max-age=0, must-revalidate on upstream metadata requests; approach still under discussion. |
|
craft-parts issue #1001 |
npm plugin fails in the presence of `base-files` | tigarmo | 640d | keep open | 57 | 76 | 14 | Cross-part staging rejects directory-vs-symlink collisions such as npm's bin/lib and base-files' usrmerge links; the valid repro remains unresolved and affects more than the npm plugin. |
|
craft-providers issue #880 |
Support LXD backend on non-Linux hosts | lengau | 321d | keep open | 57 | 64 | 12 | Maintainer-authored enhancement to use the LXD provider on non-Linux hosts through a configured remote or VM. Remote arguments exist, but availability checks still require local LXD. |
|
rockcraft issue #432 |
improve the speed rockcraft's iterative design experience | ca-scribner | 1067d | 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 | 1529d | 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. |
|
snapcraft (launchpad) issue #1999385 |
Removing a `package-repositories:` entry does not affect existing containers | ~saviq | 1421d | 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. |
|
craft-parts issue #751 |
Silent failure on certain store issues | lengau | 878d | keep open | 56 | 92 | 37 | Transient snap-store HTTP 500s exhaust five retries in get_store_snap_info and return None, silently skipping required build-snaps; the triaged bug remains in current code. |
|
charmcraft issue #2273 |
charmcraft.yaml deleted while packing (working tree not clean) | carlcsaposs-canonical | 553d | 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 |
|
snapcraft (launchpad) issue #2031494 |
snapcraft login doens't work on fresh multipass or lxd | ~gbeuzeboc | 1174d | close resolved | 56 | 95 | 29 | Snapcraft 7.5.2 could not log in on fresh Multipass/LXD systems without a usable keyring; Snapcraft 8.0.0 added file-based credential fallback. |
|
charmcraft issue #2720 |
`organize` part expects distinct subdirectories since 4.2.1 | natalian98 | 147d | 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. |
|
imagecraft issue #300 |
Race condition when mounting loop devices | lengau | 224d | keep open | 56 | 70 | 13 | Loop partition nodes can disappear during asynchronous udev processing, intermittently breaking mounts. Although the code now waits for initial node creation, the race remains triaged and open. |
|
craft-providers issue #454 |
Using default compatibility tag can cause DNS name conflicts | mr-cal | 1088d | keep open | 56 | 89 | 28 | Missing compatibility tags still produce identical LXD base-instance names across projects, causing DNS conflicts and failed launches; the proposed warning and API redesign remain unimplemented. |
|
craft-archives issue #221 |
Support adding private repositories | lengau | 220d | keep open | 56 | 70 | 16 | Triaged enhancement remains open: add auth.conf.d credential support for private APT repositories and PPAs so Imagecraft can build images using them. |
|
snapcraft (launchpad) issue #2025447 |
Incorrect Downloads directory for LDAP user in snapped firefox & chromium | ~dgadomski | 1221d | keep open | 56 | 91 | 38 | LDAP/AD users' Firefox and Chromium snaps download into snap data instead of ~/Downloads; reproduced on 22.04, confirmed for multiple users, and a SNAP_REAL_HOME fix was validated. |
|
snapcraft (launchpad) issue #1889741 |
Snapcraft concurrent build | ~lawrencegripper | 2285d | keep open | 56 | 84 | 23 | Concurrent first-time builds can race during pyxdg cache-path creation; the flaw was still reported on Snapcraft 8.2.12 despite a 2022 upstream fix attempt. |
|
craft-application issue #676 |
Use a different instance name when using the fetch service | lengau | 605d | 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. |