Issue & PR triage
Loading...
Showing 100 of 237 issues
| Issue | Title | Author | Age | Action | Impact ↓ | Actionability | Quick Win | Summary |
|---|---|---|---|---|---|---|---|---|
|
rockcraft issue #137 |
Priming files into /lib breaks system binaries in the final image | tigarmo | 1456d | close resolved | 74 | 92 | 24 | Priming files under Ubuntu usrmerge paths could replace base symlinks and break binaries; layer packing now rewrites those paths, but issue #137 remains open. |
|
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 issue #6185 |
Add core26 support for the gnome extension | mr-cal | 197d | close resolved | 65 | 95 | 46 | GNOME extension core26 support is implemented: merged PR #6278 added core26 to the supported bases and SDK mapping. The placeholder issue remains open and should be closed. |
|
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. |
|
craft-providers issue #665 |
Add a callback hook to allow users to configure a base on warmup before... | lengau | 764d | close resolved | 65 | 91 | 34 | Merged PR #788 adds a prepare_instance callback before base setup, enabling early apt and proxy configuration; the callback is not literally inside warmup, but the requested capability is implemented. |
|
craft-providers issue #259 |
Cannot launch lxd instance with high uids | mr-cal | 1282d | close resolved | 65 | 95 | 40 | LXD launches failed for host UIDs above 65,535; commit 5717e2c and PR #780 now configure separate UID and GID raw.idmap entries, resolving the reported failure. |
|
fetch-service issue #209 |
Implement configurable request authentication | cmatsuoka | 780d | close resolved | 65 | 95 | 22 | Configurable per-session URL-matched authentication is implemented, including basic, macaroon, and Keystone credentials injected into matching proxied requests. |
|
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. |
|
snapcraft (launchpad) issue #1750527 |
dashboard does not validate text fields | ~chipaca | 3174d | 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. |
|
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. |
|
snapcraft issue #5146 |
Snap: Snapcraft currently relies on `libapt` during configure | Meulengracht | 711d | 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. |
|
craft-application issue #821 |
5.5.0 changes pack semantics if the project file has different metadata | javierdelapuente | 463d | 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 (launchpad) issue #1673186 |
the gox classic snap gets stuck consuming a lot of cpu | ~zyga | 3515d | 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 #419 |
Missing inspectors for JARs (Maven) | Vyom-Yadav | 464d | 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. |
|
craft-archives issue #176 |
Allow modifying existing default repositories | lengau | 483d | 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. |
|
craft-application issue #261 |
Commands cannot always load projects with advanced grammar | mr-cal | 962d | 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. |
|
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 #1566331 |
snapcraft autotools plugin doesn't support building other architectures | ~cmiller | 3859d | 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. |
|
rockcraft issue #959 |
Allow Custom Build Contexts | clay-lake | 416d | 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-archives issue #151 |
Update sources added by craft-archives | mr-cal | 632d | 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. |
|
snapcraft (launchpad) issue #1999321 |
Snapcraft is stuck on "launching instance..." indefinitely | ~mjakeman | 1419d | 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. |
|
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. |
|
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 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 #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. |
|
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 #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. |
|
snapcraft (launchpad) issue #2031494 |
snapcraft login doens't work on fresh multipass or lxd | ~gbeuzeboc | 1171d | 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. |
|
snapcraft (launchpad) issue #1670323 |
binary entry (and lib) for python projects not installed in final snap | ~didrocks | 3525d | close resolved | 55 | 88 | 28 | A 2017 Python-plugin wheel regression omitted setup.py scripts and libraries when the project name matched a requirement; later wheel/install-ordering work appears to fix it. |
|
snapcraft (launchpad) issue #1774410 |
Having python3-netaddr as a stage package produces external symlink | ~bjornt | 3073d | close resolved | 55 | 72 | 27 | Snapcraft 2.42 could leave python3-netaddr stage-package symlinks pointing outside the snap; later normalization and regression fixes now rewrite them internally. |
|
charmcraft issue #1816 |
Reactive charm built with charmcraft 3.x is missing options from the... | lgp171188 | 806d | close resolved | 55 | 90 | 31 | Reactive layer options were lost because Charmcraft 3.x overwrote charm-tools' config.yaml; commit aa28f0dc and PR #2245 now preserve the generated configuration. |
|
snapcraft issue #4723 |
Please always test against Fedora | zyga | 932d | close resolved | 55 | 98 | 44 | Fedora Spread testing was enabled by commit 7189d7901, implementing the requested removal of the manual test gate. |
|
snapcraft issue #5879 |
Base images store out-of-date apt package caches | lengau | 344d | close resolved | 55 | 92 | 35 | Stale APT metadata in cached LXD base images made newly published build-packages appear missing; craft-parts PR #1468 has since added a cache refresh before package marking. |
|
snapcraft (launchpad) issue #1795827 |
Snapcraft doesn't install snapcraft inside the lxd container | ~saviq | 2949d | close resolved | 55 | 84 | 22 | Historical LXD builds failed because Snapcraft was not injected into the container; the modern Craft Providers LXD path injects Snapcraft and resolves the legacy failure. |
|
debcraft issue #149 |
[Feature] Add support for dpkg-buildflags for C/C++/Rust | hector-cao | 185d | close resolved | 55 | 90 | 35 | Feature request to inject dpkg-buildflags (C/C++/Rust) automatically into part builds. Implemented and merged via commit a0afaae (PR #170), which passes dpkg-buildflags output as build_environment to the parts lifecycle; unit-tested. |
|
craft-providers issue #391 |
LXD issue when build multiple charms in parallel | beliaev-maksim | 1154d | close resolved | 55 | 78 | 33 | Parallel LXD charm builds failed with a snapd 'daemon is stopping' error during `snap watch`. Fixed by retrying snap watch in commit e0f6bc7 (PR #899), released in 3.3.0; issue still open awaiting closure. |
|
snapcraft issue #6325 |
Skip repacking if artifact contents are unchanged | cmatsuoka | 115d | close resolved | 55 | 96 | 34 | Conditional repacking is implemented through craft-application PR #1111, integrated and documented in Snapcraft 9.1, but this issue remains open. |
|
snapcraft (launchpad) issue #1964329 |
meson plugin uses internet access during build, instead of pull | ~xnox | 1696d | close resolved | 55 | 58 | 22 | Legacy Meson plugin installed its build dependency with pip during build, blocking offline riscv builds; the legacy plugin is now absent and the active plugin only runs meson and ninja. |
|
snapcraft issue #5003 |
Building snap with `core20` failed with non-informative error message | chanchiwai-ray | 794d | close resolved | 55 | 95 | 39 | The misleading core20 snapcraft-pack error was fixed by merged PR #5616 (commit b511004af), which ran the lifecycle for legacy core20 snaps. |
|
snapcraft (launchpad) issue #1712808 |
udev interface fails in privileged containers | ~saviq | 3353d | close resolved | 55 | 70 | 23 | Long-standing bug: snap installs in privileged LXD/LXC containers fail with "cannot reload udev rules". Fixed upstream by snapd PR 14930 and SRU'd as snapd 2.68.5 to jammy/noble/plucky; jammy verification still pending. |
|
craft-application issue #313 |
Support local key assets for package-repositories | tigarmo | 924d | close resolved | 55 | 85 | 30 | Feature request to support local key assets (e.g. snap/keys) in package-repositories instead of hardcoding /dev/null. Resolved by merged PR #317 (071ad272), which added a local_keys_path parameter and an overridable _get_local_keys_path() hook. |
|
snapcraft (launchpad) issue #2012074 |
snapcraft cannot build snap by default on aarch64 | ~gbeuzeboc | 1322d | close resolved | 55 | 92 | 30 | ARM64 default builds failed on Snapcraft 7.3.1 because core20 selected amd64-only Multipass images; later defaults use core22/LXD on Linux, addressing the reported path. |
|
rockcraft issue #866 |
The image entry point should be configurable, making Pebble optional | petrutlucian94 | 555d | close resolved | 55 | 85 | 30 | Configurable OCI entrypoints are now available through entrypoint-command, bypassing Pebble; the feature shipped in Rockcraft 1.14 after this open request. |
|
charmcraft issue #1919 |
Charm venv shadows system python dependencies | silverdrake11 | 765d | close resolved | 55 | 90 | 27 | Reported: charm plugin's PYTHONPATH=lib:venv let Juju charm venv shadow system Python packages (pydantic ImportError). lengau confirmed and pointed to new dispatch-based plugins; dispatch now sets PYTHONPATH=lib:src, so the fix has landed. |
|
snapcraft (launchpad) issue #1790346 |
store review fails on "unknown keys in snap/manifest.yaml: snapcraft..." | ~saviq | 2980d | close resolved | 52 | 87 | 34 | Core18 snap uploads were rejected because generated manifest.yaml contained unsupported snapcraft-* keys; later review-tools compatibility coverage indicates the problem was addressed. |
|
snapcraft issue #5384 |
remote build: snapcraft incorrectly follows symlinks | andrewphelpsj | 569d | close resolved | 52 | 94 | 40 | remote-build previously failed while copying dangling symlinks; craft-application 7.1.1 fixed this via PR #1104, and Snapcraft now requires craft-application >=7.4.1. |
|
snapcraft (launchpad) issue #1861026 |
python3 ctypes can't find libs on due to ld cache | ~jdstrand | 2467d | close resolved | 52 | 82 | 11 | UC strict snaps let ctypes resolve bundled libraries through the host ldconfig cache; commit 786d0b8eab91c3be850f07195b4cd2c52dbdfbf7 is recorded as a workaround. |
|
craft-providers issue #765 |
Set up weekly tests for tests that don't need to run on each PR | lengau | 486d | close resolved | 52 | 90 | 29 | Weekly Linux LXD integration coverage now exists, but the issue remains open despite its implementation in PR #857. |
|
snapcraft (launchpad) issue #1654304 |
Allow pinning a source archive | ~mterry | 3584d | close resolved | 52 | 86 | 23 | APT pinning for the Ubuntu Touch overlay is now implemented via package-repositories priority, with craft-archives writing preferences and spread tests covering a PPA; this old request is resolved. |
|
charmcraft issue #1530 |
Changing charmcraft.yaml doesn't update the resulting charm's metadata.yaml | lengau | 983d | close resolved | 52 | 67 | 20 | The original stale metadata.yaml bug was fixed by merged PR #2874; a later Charmcraft 5.5.0 stale-repack variant remains tracked in craft-application#821. |
|
rockcraft issue #1005 |
rockcraft needs to update apt sources before installing build-packages | vpa1977 | 381d | close resolved | 52 | 96 | 43 | Rockcraft 1.15.0 could fail build-package resolution with a stale apt cache; craft-parts PR #1468 now refreshes apt metadata before marking packages. |
|
snapcraft (launchpad) issue #1668555 |
Using organize to move a folder to a child folder fails due to recursion | ~jamesh | 3531d | close resolved | 50 | 94 | 29 | The historical organize recursion is addressed by self-move protection; organize now runs during build, resolving both reported behaviors in current code. |
|
snapcraft issue #6190 |
Add core26 support for the colcon plugin and extensions | mr-cal | 196d | close resolved | 50 | 62 | 17 | Core26 support for colcon-based ROS extensions is implemented, including the ROS 2 Lyrical extension and subsequent ROS 2 compatibility fixes; the placeholder can be closed. |
|
debcraft issue #146 |
[Feature] Add support for debconf config script | hector-cao | 185d | close resolved | 50 | 78 | 28 | Feature request to support debconf config scripts. The requested first step (deploying config/templates into the package control dir) shipped as the installdebconf helper in PR #156, with token substitution added in #162. |
|
craft-application issue #301 |
Smarter docs URL handling | lengau | 937d | close resolved | 50 | 98 | 32 | Automatic documentation URL composition from an error's doc_slug and the application's versioned docs base is implemented in the current code, despite #301 remaining open. |
|
snapcraft (launchpad) issue #1652441 |
unity7: LauncherEntry API does not work due to snapd not respecting the... | ~mvo | 3596d | close resolved | 48 | 90 | 30 | Unity7 LauncherEntry progress-bar lookup failed because snapd exposed renamed desktop IDs; Snapcraft’s merged desktop-renaming fix addressed the mismatch, but the Launchpad issue remains open. |
|
snapcraft (launchpad) issue #1846068 |
Specifying `/var/lib` in layout breaks snapd because of `/var/lib/snapd` | ~zyga | 2586d | close resolved | 48 | 92 | 36 | A /var/lib layout could produce a snap rejected by snapd for masking /var/lib/snapd; merged pack-time skeleton validation now catches this invalid layout. |
|
charmcraft issue #2494 |
charmcraft pack wont produce a proper charm | erik78se | 334d | close resolved | 48 | 88 | 26 | Machine-profile init used Ubuntu 22.04 and lacked clear uv-lock guidance. The current implementation defaults machine to 24.04 and supplies uv/migration instructions, so the reported template concerns appear addressed. |
|
snapcraft (launchpad) issue #1663002 |
organize and stage keywords together mess up file conflict checking | ~mrjogo | 3550d | close resolved | 48 | 95 | 26 | The organize/stage collision bypass is resolved: organization now occurs during build, so stage filtering and collision detection see organized paths. |
|
snapcraft (launchpad) issue #1928756 |
export-login --expires silently ignores dates given in ISO 8601 format | ~bjornt | 1991d | close resolved | 48 | 94 | 38 | export-login now accepts the reported date-only expiry, retains timestamp support, and rejects unparseable values; the Launchpad issue remains open despite the resolved implementation. |
|
snapcraft (launchpad) issue #1600035 |
no way to differentiate between build-time and run-time env vars in plugins | ~thomir-deactivatedaccount | 3766d | close resolved | 48 | 96 | 25 | Legacy plugin env() conflated build and runtime variables; separate plugin build-environment support and part-level build-environment handling were later implemented. |
|
rockcraft issue #1153 |
Feature request: support dynamically setting top-level `version` during build | srbouffard | 223d | close resolved | 48 | 84 | 34 | Dynamic version updates are already supported: rockcraft exposes the top-level version as a craft-parts project variable that craftctl can update during the build. |
|
snapcraft (launchpad) issue #1754010 |
Dump follows symlink and fails | ~r4co0n | 3159d | close resolved | 48 | 76 | 20 | Snapcraft 2.39.3's dump plugin dereferenced an in-tree directory symlink during staging and crashed. Later symlink-preservation fixes and current no-dereference behavior resolve the defect, but the tracker remains open. |
|
craft-archives issue #118 |
Make Pydantic models more idiomatic | lengau | 876d | close resolved | 48 | 82 | 23 | Pydantic 2 modernization and schema-enabling model metadata now appear implemented through later cleanup and model-documentation changes, despite the issue remaining open. |
|
snapcraft (launchpad) issue #1741131 |
python plugin ignores source-subdir | ~elopio | 3221d | close resolved | 48 | 96 | 41 | Python plugin setup.py discovery now honors source-subdir; snapcraft PR #1975 fixed the bug in commit 0dbc20658, but this Launchpad report remains open. |
|
rockcraft issue #660 |
Rockcraft parts `permissions` field follows symlinks when changing ownership. | weiiwang01 | 819d | close resolved | 48 | 94 | 32 | Upstream craft-parts#1059 is recorded as merged and fixes symlink-following during permission application; rockcraft#660 remains open but is resolved by that upstream fix. |
|
craft-application issue #1059 |
Packing with CRAFT_BUILD_ON can fail when installing registered snaps | tigarmo | 202d | close resolved | 48 | 98 | 31 | Cross-architecture packing with registered snaps could inject incompatible host snaps; commit 16bd7ac3 now skips host snap injection when architectures differ. |
|
snapcraft (launchpad) issue #1608432 |
snaps with type: os should allow publishing of .manifest files | ~ogra | 3742d | close resolved | 48 | 90 | 25 | Launchpad support for publishing .manifest files alongside snaps was reported fixed in stable revision 18187; the issue remains open administratively. |
|
snapcraft (launchpad) issue #1869030 |
Running several instances of snapcraft in parallel for a given snap name... | ~osomon | 2409d | close resolved | 46 | 86 | 25 | Same-name builds from separate directories shared a provider instance and contended for APT locks; current code includes the project path inode in the instance name, resolving the collision. |
|
snapcraft (launchpad) issue #1597075 |
ant plugin only looks for jar files in directory named "target" | ~jenny-murphy | 3775d | close resolved | 46 | 93 | 33 | Ant now discovers JARs recursively across the part build directory, so the reported `lib` output layout no longer needs to be renamed to `target`; the issue is resolved. |
|
snapcraft (launchpad) issue #1796802 |
PKG_CONFIG_PATH during build step should include multiarch paths | ~brlin | 2943d | close resolved | 46 | 84 | 26 | Build-time pkg-config lookup historically omitted staged multiarch .pc files; current craft-parts includes both generic and architecture-triplet pkgconfig directories. |
|
fetch-service issue #202 |
Add snapcraft tests | cmatsuoka | 794d | close resolved | 45 | 68 | 14 | Snap package integration tests were added and CI now runs the Spread suite through snapcraft test, although the tracking issue remains open. |
|
snapcraft (launchpad) issue #1890046 |
Handle SOURCE_DATE_EPOCH for SquashFS | ~abitrolly | 2279d | close resolved | 45 | 90 | 32 | SOURCE_DATE_EPOCH-based SquashFS reproducibility was requested; a 2025 report says snap pack v2.72 now produces identical snaps, indicating resolution upstream |
|
craft-parts issue #647 |
apt package cache marks packages that don't exist | mr-cal | 1000d | close resolved | 45 | 76 | 23 | Apt stage-package marking could falsely report a valid architecture-qualified package as missing. Fixes from PRs #1446 and #1468 are now in the codebase. |
|
snapcraft issue #4972 |
Cannot create a snap with base:bare in destructive mode | nhathaway | 805d | close resolved | 45 | 90 | 23 | Snapcraft 8.3.2 mishandled bare-base projects without build-base, producing architecture/platform errors; current models require build-base and fail early during validation. |
|
snapcraft issue #6412 |
edit-validation-sets refuses to create a new validation set at sequence 1... | bugraaydogar | 56d | close resolved | 45 | 88 | 30 | edit-validation-sets rejects creating a brand-new validation set at sequence 1 because the sequence-increment check runs even when no existing set exists; confirmed by maintainer, tracked as SNAPCRAFT-1379. |
|
snapcraft issue #5102 |
Unable to set components version using craftctl set version | stephensp | 752d | close resolved | 45 | 90 | 30 | Current main supports `craftctl set components.<name>.version`, with per-component project variables and spread-test coverage; the enhancement appears implemented, but its resolving PR is unconfirmed. |
|
rockcraft issue #1198 |
docs: Rockcraft 1.18.0 documentation claims Ubuntu 26.04 support but it... | GregCasbolt | 189d | close resolved | 45 | 80 | 25 | Rockcraft 1.18.0 docs claim ubuntu@26.04 support but build-base ubuntu@26.04 raises KeyError; maintainer clarified devel workaround and stabilization planned. Now resolved in main via PR #1200. |
|
snapcraft (launchpad) issue #1676684 |
Python plugin tries to chmod symlinks to system files | ~mrjogo | 3503d | close resolved | 45 | 82 | 30 | Python permission-fix logic followed absolute system-file symlinks and broke builds with development stage packages; the affected legacy implementation has since been removed. |
|
charmcraft issue #2396 |
Tutorial spread tests are failing | lengau | 458d | close resolved | 45 | 85 | 29 | Tutorial spread tests fail because charms lose the 'greeting' config option after repeated packing without clean. Root cause traced to craft-application #821; fix merged in craft-application #829 and charmcraft now depends on craft-application 7.2. |
|
snapcraft (launchpad) issue #1615242 |
etcd tree drives snapcraft dump plugin insane | ~sabdfl | 3722d | close resolved | 45 | 90 | 28 | Historical dump-plugin recursion on etcd's directory symlinks was fixed; source copying now preserves links, and the current dump plugin uses cp --no-dereference. |
|
rockcraft issue #102 |
Allow customization/removal of automatic "go generate" step | tigarmo | 1492d | close resolved | 45 | 98 | 39 | Automatic Go generation is now opt-in: craft-parts added go-generate, which defaults to no generation, and Rockcraft exposes the option in its schema. |
|
snapcraft (launchpad) issue #1831135 |
prime error: unable to set version: it was already set in the 'build' step | ~saviq | 2709d | close resolved | 45 | 95 | 22 | A reproducible core22 lifecycle-ordering failure could set the snap version twice; it is covered by a regression test and addressed by the craft-parts 1.19.7 update. |
|
craft-parts issue #1513 |
Make Java plugins work on Ubuntu 26.04 | lengau | 220d | close resolved | 45 | 80 | 22 | Triaged: make Java plugin version-sensitive tests pass on Ubuntu 26.04 (Resolute, default OpenJDK 25). Tracked as CRAFT-5065 and fixed by merged PR #1530 (commit da6b596e), which enabled the Java plugin tests on resolute. |
|
charmcraft issue #1962 |
Spread test the documentation examples | lengau | 743d | close resolved | 45 | 95 | 27 | Documentation examples are now covered by dedicated Spread tests and CI through merged PR #2126; the still-open issue should be closed. |
|
charmcraft issue #1054 |
Charmcraft fails to launch LXD instance with high uid (`raw.idmap=both 595156457 0`) | jamesbeedy | 1314d | close resolved | 45 | 80 | 23 | High host UID causes LXD launch failure via raw.idmap=both; diagnosed as craft-providers idmap issue, fixed upstream by separate uid/gid maps and charmcraft now depends on fixed version. |
|
charmcraft issue #2507 |
Cannot build charm when base is Questing and build-base is devel | lmlg | 328d | close resolved | 45 | 75 | 29 | Build with base ubuntu@25.10 and build-base ubuntu@devel fails with 'Couldn't get EOL data for devel' in charmcraft 4.0.1; fixed in craft-providers 3.2.0 by skipping EOL checks for devel. |
|
charmcraft issue #1844 |
Add appropriate ignored packages for stage-packages | lengau | 794d | close resolved | 45 | 95 | 28 | Add per-base ignored-package lists so stage-packages excludes packages preinstalled in Jammy and Noble and does not descend to glibc. Implemented by merged PR #1875, but the issue remains open. |
|
craft-application issue #479 |
Application: treat CraftError-like exceptions as CraftErrors | lengau | 770d | close resolved | 45 | 70 | 24 | CraftError-like exceptions bubbling to Application were reported as internal errors; PR #695 added a craft_platforms.CraftError branch in handle_runtime_error, so this appears resolved but the issue remains open. |
|
snapcraft issue #5115 |
component does not take snap version when no version provided | stephensp | 746d | close resolved | 45 | 92 | 19 | Component version inheritance was triaged as an enhancement; maintainers adopted component-level adopt-info, and follow-up #5240 was closed after implementation merged in canonical/snapcraft#5753. |
|
charmcraft issue #1917 |
Charmcraft cannot parse a dev version build for multipass | jat-canonical | 765d | close resolved | 45 | 90 | 34 | Charmcraft pack fails on dev multipass versions like 1.15.0-dev.2929.pr661 due to invalid version parsing in craft-providers; fixed upstream and current charmcraft dependency includes the fix. |
|
snapcraft (launchpad) issue #1670162 |
publish complains about desktop file un-necessarily | ~popey | 3525d | close resolved | 44 | 85 | 16 | Store review incorrectly demanded a .desktop file for an x11-enabled CLI snap; maintainers reported the review-tools correction released on 2017-03-20, but the issue remains open. |
|
craft-application issue #698 |
Some valid `spread.yaml` files don't get parsed correctly. | lengau | 583d | close resolved | 44 | 94 | 34 | Valid spread backends with bare system-name strings are now accepted; this report was resolved by merged PR #737, commit 2f11fe33. |
|
snapcraft (launchpad) issue #1824077 |
IsADirectoryError occurred when migrating /usr/bin/X11 symlink in stage step | ~brlin | 2760d | close resolved | 43 | 89 | 24 | Snapcraft 3.3 staging aborted on IsADirectoryError for the usr/bin/X11 symlink to '.'; later commits fixed directory-targeted symlink handling. |
|
snapcraft (launchpad) issue #2004544 |
Rebuilding a Go project results in error "error obtaining VCS status" in... | ~saviq | 1366d | close resolved | 43 | 92 | 20 | Go rebuilds in privileged LXD fail with Git dubious-ownership errors from mixed host/container ownership; this duplicates #1990298 and is addressed by craft-providers 1.7.2. |
|
snapcraft (launchpad) issue #1958282 |
Pass proxy settings to override-pull | ~mr-cal | 1745d | close resolved | 43 | 76 | 25 | Proxy variables are now forwarded from Launchpad into Snapcraft's provider environment, resolving override-pull's reported lack of proxy access. |
|
snapcraft (launchpad) issue #1575188 |
Fix for bug #1572664 had broken my snap package build | ~townsend | 3838d | close resolved | 43 | 82 | 23 | The 2016 chroot build failure involved dangling symlinks; later commit 221a43803 stopped hard-linking symlinks, so the reported build path appears resolved. |
|
snapcraft (launchpad) issue #1617253 |
snapcraft syntax documentation is incomplete | ~rogpeppe | 3717d | close resolved | 43 | 88 | 25 | The former syntax page omitted app-level plugs; the current source-backed snapcraft.yaml reference documents App plugs and other project fields. |
|
charmcraft issue #1154 |
Use craft-application's store service | lengau | 1204d | close resolved | 42 | 98 | 19 | Store interactions now use a craft-application AppService, and all store commands inherit AppCommand; completed by commit 5dcad2af and related craft-application migration work. |
|
snapcraft (launchpad) issue #1849935 |
Generated 'git describe' based version strings can exceed 32 character version limit | ~ec0 | 2561d | close resolved | 42 | 90 | 27 | Historical version: git builds could generate a 38-character string rejected by snapd; snapcraft#3779 addressed the handling, and legacy support was later removed. |