Issue & PR triage
Loading...
Showing 100 of 2040 issues
| Issue | Title | Author | Age | Action | Staleness ↑ | Confidence | Summary |
|---|---|---|---|---|---|---|---|
|
snapcraft (launchpad) issue #1995856 |
Get Desktop icon from snap instead of source tree | ~merlijn-sebrechts | 1404d | close not a bug | 100 | 70 | Feature request to allow icon field in snapcraft.yaml to reference files in the snap instead of source tree. Issue is 3.8 years old with no maintainer interaction. |
|
snapcraft (launchpad) issue #1826262 |
Error: The part has run through its entire lifecycle | ~saviq | 2697d | close stale | 100 | 72 | Snapcraft 1.x build error 'part has run through its entire lifecycle' reported in 2017 when modifying multipass snapcraft.yaml; zero comments, no labels, project since fully rearchitected into craft-* subprojects. |
|
snapcraft (launchpad) issue #1824077 |
IsADirectoryError occurred when migrating /usr/bin/X11 symlink in stage step | ~brlin | 2711d | close stale | 100 | 75 | snapcraft 3.3 (2019) crashes with IsADirectoryError in _migrate_files when staging a symlink (usr/bin/X11) that points to '.'. 2701 days old, 0 comments, no labels, no maintainer interaction; old internal staging code since rewritten. |
|
snapcraft (launchpad) issue #1666161 |
Can’t dry-run a build to check snapcraft.yaml | ~mpt | 3490d | close stale | 100 | 65 | Feature request (9.5 years old, no maintainer activity) for a dry-run build that validates snapcraft.yaml without performing the build. The core capability now exists via the snapcraft validate command, so the request is largely obsolete. |
|
snapcraft (launchpad) issue #1804957 |
Malicious namesquatting of snaps | ~buzz-- | 2848d | close not a bug | 100 | 75 | Complaint that a user squatted the 'bitcoin' snap name and is forcing outdated, incompatible software on users. No labels, no comments, no maintainer activity in ~7.8 years. A store policy/moderation concern, not a snapcraft tool defect. |
|
snapcraft (launchpad) issue #1619818 |
No explicit error message when trying to push the same snap twice | ~elopio | 3661d | close stale | 100 | 70 | Request to surface the store's 'already been uploaded' message instead of a generic error when pushing a duplicate snap. 10 years old, no activity; snapcraft push was later removed, so it is no longer applicable. |
|
snapcraft (launchpad) issue #1849582 |
Mumble Crashes | ~derekagraham78 | 2515d | close stale | 100 | 80 | Mumble snap crash reported via pastebin link only, no description or reproduction steps. 2504 days old with zero comments and no maintainer interaction. Pastebin link likely dead. |
|
snapcraft (launchpad) issue #1624854 |
"Developer has not signed agreement" when run snap push | ~psivaa | 3645d | close stale | 100 | 65 | User hit 403 'Developer has not signed agreement' (user-not-ready) on snapcraft push, resolved via IRC by signing at myapps.developer.ubuntu.com. Suggests adding that link to the error message. 10 years old, no maintainer activity. |
|
snapcraft (launchpad) issue #1682822 |
Snapcraft deb does not work on KDE Neon. snap does. | ~frecel | 3437d | close stale | 100 | 80 | Old snapcraft deb package crashes on KDE Neon with 'not supported on this operating system' at import. 9+ years old, no labels or comments; the failing code path no longer exists in the current codebase and the deb install method is superseded by the snap. |
|
snapcraft (launchpad) issue #1617002 |
LP build: "/usr/bin/ld: cannot find -llibrary" | ~eldar | 3669d | close stale | 100 | 80 | Reporter's kicad-dev-snap failed on Launchpad (Xenial) with linker error 'cannot find -lngspice' while building locally succeeded. 10 years old, zero comments, no maintainer response, Xenial base long EOL. |
|
snapcraft (launchpad) issue #1693451 |
Support CircleCI for building | ~popey | 3396d | close stale | 98 | 70 | Feature request to add CircleCI as a supported CI for building/pushing snaps, with encrypted store credentials comparable to the Travis workflow. Open ~9 years, labelled integrations, zero comments, no maintainer activity. |
|
snapcraft (launchpad) issue #1735004 |
Push issue with bad internet connection | ~hatari | 3209d | close stale | 98 | 72 | Snapcraft push fails with binary_sha3_384 duplicate error after interrupted upload on slow connection; requests server return upload_id for resume. 8+ years old, zero comments, no labels, push command since removed. |
|
snapcraft (launchpad) issue #1663051 |
Stage package cache is never cleaned | ~kyrofa | 3502d | close stale | 98 | 55 | Snapcraft's stage-package cache (keyed by source hash) is never cleaned and grows unbounded as new packages/sources are fetched. Self-filed by a maintainer ~9.5 years ago with no labels, comments, or follow-up; related Launchpad bug closed without resolution. |
|
snapcraft (launchpad) issue #1959851 |
gnome-3-38 extension not compatible with python plugin on core20 | ~goodsoftworx | 1682d | close stale | 98 | 60 | gnome-3-38 extension sets PYTHONPATH to its own interpreter, overriding the python plugin and causing build errors on core20. Affects PyGObject-based GTK 3 snaps. No maintainer activity in 4.5 years; core20 base is legacy. |
|
snapcraft (launchpad) issue #1869542 |
snapcraft unable to find snap/snapcraft.yaml file | ~keshavnrj | 2358d | close stale | 98 | 60 | snapcraft 3.11 (2019) loses snap/snapcraft.yaml after a few builds and drops to the VM shell; workaround is snapcraft clean. 6+ years old, no labels, no maintainer comments, tied to a long-superseded build environment. |
|
snapcraft (launchpad) issue #1675545 |
undefined symbol: _Py_RefTotal | ~evarlast | 3459d | close stale | 98 | 70 | Reports undefined symbol _Py_RefTotal when loading the Cheetah C extension built for python2 inside a snap, asking whether the python plugin supports python2 C modules. No labels, no comments, no maintainer response; ~9.4 years old and python2 is EOL. |
|
snapcraft (launchpad) issue #1670162 |
publish complains about desktop file un-necessarily | ~popey | 3477d | close stale | 96 | 55 | Snapcraft publish validation falsely requires a .desktop file when a snap uses the x11 plug, blocking a CLI utility from releasing to stable. Reported ~9.5 years ago with no maintainer response; the quoted error is from the old snapcraft 1.x publish flow. |
|
snapcraft (launchpad) issue #1709674 |
Catkin plugin: consumer snap still pulls in packages contained in producer snap | ~kyrofa | 3320d | close stale | 96 | 58 | Catkin (ROS1) plugin bug: a consumer snap still pulls in packages already contained in the producer snap, implying a flaw in the underlay logic. Filed by a maintainer in 2016 as an investigation note; no labels, comments, or activity since. |
|
snapcraft (launchpad) issue #1839399 |
snapcraft not pulling snap from lxd container | ~popey | 2592d | close stale | 95 | 70 | 2019 report that snapcraft 3.7.1 with --use-lxd built a snap inside the LXD container but never copied it back to the host. No labels, no maintainer interaction, 7 years old; the LXD provider has since been rewritten via craft-providers. |
|
snapcraft (launchpad) issue #2006076 |
panic when use socks proxy | ~mohammadv184 | 1314d | close stale | 95 | 60 | Reported crash when using SOCKS proxy with snapcraft login. No maintainer engagement, no labels, no comments, inactive for 1305 days. |
|
snapcraft (launchpad) issue #1751828 |
using executable from core snap fails sanity check | ~ondrak | 3119d | close stale | 95 | 55 | Snapcraft's sanity check fails when an application command references an executable provided by the core snap (e.g., ping). Workaround: install the binary on the build host. Unanswered since 2017. Old host-based check likely obsolete in modern snapcraft. |
|
snapcraft (launchpad) issue #1986533 |
Can snapcraft commands default to base in snapcraft.yaml from build subdirectories? | ~rpjday | 1488d | needs triage | 95 | 60 | Feature request to make snapcraft commands use base from snapcraft.yaml when run from subdirectories of the build directory. Untriaged, 4 years old, zero maintainer interaction. |
|
snapcraft (launchpad) issue #1768233 |
Chains of parts with python contents can fail with pkg_resources import error | ~jocave | 3055d | close stale | 95 | 75 | Python part wheel build fails with pkg_resources.py31compat ImportError for bitstring on xenial. 8+ years old, zero comments, no labels. Parts system since rewritten in craft-parts with modern pip/setuptools, making this error no longer reproducible. |
|
snapcraft (launchpad) issue #1999038 |
"snapcraft release" chokes given an invalid revision value | ~rpjday | 1374d | close stale | 95 | 70 | Issue about confusing error when 'snapcraft release' receives invalid revision. Stale for 1366 days with no maintainer response. The release command appears to have been removed or deprecated. |
|
snapcraft (launchpad) issue #2007479 |
speedx doesn't launch in ubuntu 22.04.1 | ~624wtl | 1304d | close not a bug | 95 | 80 | User reports speedx Qt application fails to launch on Ubuntu 22.04.1 due to missing wayland-egl plugin. Issue is 1295 days old with no maintainer response or comments. |
|
snapcraft (launchpad) issue #1619912 |
Autotools plugin should allow additional make targets | ~sabdfl | 3660d | close stale | 95 | 75 | Feature request to add a make-targets option to the autotools plugin so users can run custom targets (e.g. make dist) before make install. Open since 2016 with no maintainer interaction; the option is not present in the current craft-parts autotools plugin. |
|
snapcraft (launchpad) issue #1922140 |
unable to run on centos 7 VM | ~anonymouse67 | 1990d | close stale | 95 | 85 | snapcraft 4.6 fails on CentOS 7 VM due to missing C.UTF-8 locale, causing Click to abort with ASCII encoding error. No maintainer response in 5+ years; CentOS 7 is EOL and snapcraft 4.6 is long superseded. |
|
snapcraft (launchpad) issue #1846195 |
provide snapcraft docker image for core18 | ~pyro4hell | 2537d | close stale | 95 | 75 | Request for canonical-provided core18-based snapcraft docker images (official ones were xenial-based). 7 years old, no comments or labels; core18 is EOL and the project has moved to core20+, so the request is no longer applicable. |
|
snapcraft (launchpad) issue #1761097 |
Python setup.cfg wrongly applied to all python package dependencies | ~dwynen | 3082d | close stale | 95 | 70 | 2017 report that a setup.cfg in the build directory was applied to all pip installs. No comments, no labels, no maintainer response. The python plugin has since been fully rewritten, so the problem is almost certainly no longer reproducible. |
|
snapcraft (launchpad) issue #1831111 |
Snapcraft strips build ID | ~sophie-w | 2661d | needs triage | 95 | 55 | Snapcraft's patchelf step strips the build ID from binaries, crashing the i965_dri mesa driver that relies on build-id for caching. Workaround is build-attributes: [no-patchelf]. No maintainer activity in 7+ years. |
|
snapcraft (launchpad) issue #1803235 |
signup process does not send activation email | ~lhonda | 2859d | close stale | 95 | 75 | Report that forum.snapcraft.io signup did not send an activation email (Discourse forum infrastructure problem, not a snapcraft codebase bug). No labels, no comments, no maintainer activity in ~8 years. |
|
snapcraft (launchpad) issue #1807125 |
After snapcraft refresh, old multipass containers no longer work | ~igorljubuncic-deactivatedaccount | 2836d | needs triage | 95 | 70 | snapcraft reuses outdated multipass containers after snap refresh, causing 'Could not find snap/snapcraft.yaml' errors until snapcraft clean is run; untriaged, no maintainer activity for ~7.7 years |
|
snapcraft (launchpad) issue #1743587 |
snapcraft push returns non exit zero code if snap requires manual review | ~serge-borovkov | 3160d | needs triage | 95 | 65 | snapcraft push returns non-zero exit code when a snap requires manual review despite successful upload; reporter expects zero exit code. Unlabeled, zero comments, inactive for over eight years. |
|
snapcraft (launchpad) issue #1839885 |
cmake parts build without install target broken after plugin update | ~neasoon | 2587d | close stale | 95 | 65 | cmake plugin regression: commit 305304e coupled build/install lifecycle, breaking cmake parts without install targets that previously used make-plugin artifacts option. 7 years old, zero comments, no labels, no maintainer engagement. |
|
snapcraft (launchpad) issue #1735800 |
snapcraft close should complain early with one argument | ~adam-collard | 3206d | needs triage | 95 | 60 | Feature request for snapcraft close to validate arguments early, rejecting a single argument like 'edge/bump-20' and suggesting the correct command from snapcraft.yaml. Unlabeled, zero comments, inactive for nearly 8 years. |
|
snapcraft (launchpad) issue #1826748 |
python: Errors regarding to the missing `--single-version-externally-managed` option | ~brlin | 2693d | close stale | 95 | 60 | Python plugin build fails because it passes the deprecated --single-version-externally-managed flag to setup.py, which newer setuptools rejects. 7+ years old, unlabelled, no maintainer response; reporter used a custom plugin workaround. |
|
snapcraft (launchpad) issue #1646081 |
Gadget snap cannot be built twice | ~zyga | 3572d | needs triage | 95 | 55 | Building a gadget snap twice in the same directory fails with a 'gadget.yaml and prime/meta/gadget.yaml are the same file' error on snapcraft 2.22.1. Unlabelled, no comments, 3561 days old, references a deprecated version. |
|
snapcraft (launchpad) issue #1626766 |
Make snapcraft work with ccache | ~oparoz | 3641d | close stale | 95 | 55 | Request that snapcraft automatically pick up a host-configured ccache (via $PATH) when compiling parts. Very old (filed ~10 years ago, last activity ~7 years ago), no labels, no maintainer response, and the premise is outdated: modern snapcraft builds run in a confined core20/core22 base where the host PATH/ccache is not inherited. |
|
snapcraft (launchpad) issue #1841618 |
snapcraft should run apt-get update | ~abitrolly | 2572d | needs triage | 95 | 60 | Feature request (2019) for snapcraft to refresh stale apt-get caches in process containers to avoid build failures. Open ~7 years with zero comments, no labels, no maintainer response; no general cache-refresh logic found in the build path. |
|
snapcraft (launchpad) issue #1848038 |
HACKING.md does not explain how to run snapcraft from a source tree | ~racb | 2524d | close stale | 95 | 70 | Request for HACKING.md to document running snapcraft from a source tree so code changes take effect. ~7 years old, 0 comments, no labels; the root HACKING.md no longer exists - docs were restructured into docs/contribute/. |
|
snapcraft (launchpad) issue #1835556 |
No way to natively build for the non-host arch | ~laney | 2625d | close stale | 95 | 65 | 2018 feature request for snapcraft to build for non-host architectures (e.g. --arch=i386) by launching a matching VM/container. Zero comments, no labels, dormant 7+ years; modern snapcraft now supports cross-arch builds via --build-for, so the request is effectively fulfilled. |
|
snapcraft (launchpad) issue #1835638 |
inconsistent to arch behaviour | ~ondrak | 2624d | needs triage | 95 | 55 | Snapcraft 3.6 stage-packages with 'on <arch>'/'to <arch>' conditionals behave inconsistently: cross-compiling works but native builds fail to pull required packages, and adding 'else' under 'on amd64' mixes arch packages. No maintainer response in 7+ years. |
|
snapcraft (launchpad) issue #1836206 |
snapped app with qtwebengine fails to run | ~teoretyk | 2619d | close stale | 95 | 55 | 2018 report that a QtWebEngine snap crashes (missing QtWebEngineProcess, DenySetgroups permission denied) with no documented way to snap such apps. No labels, 0 comments, no maintainer response in ~7 years. |
|
snapcraft (launchpad) issue #1829819 |
Wrong package source list | ~holger-seelig | 2670d | close not a bug | 95 | 72 | User asks how to make snapcraft 3.4.1 use Disco (19.04) apt sources instead of Bionic; behavior is working as intended for a core18 base. 7+ years old, no labels, no maintainer response. |
|
snapcraft (launchpad) issue #1794727 |
node plugin doesn't run yarn install during build | ~lucyllewy | 2906d | close stale | 95 | 85 | Nodejs plugin yarn support bug from 8 years ago; the nodejs plugin has been removed and replaced by the npm plugin which only supports npm, so the reported yarn install issue is no longer applicable to the current codebase. |
|
snapcraft (launchpad) issue #1822375 |
SNAPCRAFT_PART_INSTALL doesn't expand in build-environment assignments | ~brlin | 2723d | needs triage | 95 | 55 | SNAPCRAFT_PART_INSTALL not expanded in build-environment assignments, resolving to /lib/python3.6. Open since 2018 with zero comments and no labels; no evidence the behavior changed in current craft-parts, which still emits user build-environment values verbatim. |
|
snapcraft (launchpad) issue #1830520 |
Sorry, an error occurred in Snapcraft: | ~linuxmanco | 2665d | close stale | 95 | 75 | Snapcraft 2.43.1 (2019) crashed with FileNotFoundError wrapping app command spx_service missing from the prime dir during a Launchpad build. No maintainer activity in 7+ years; the 2.x code path no longer exists and the root cause is user snapcraft.yaml config. |
|
snapcraft (launchpad) issue #1816858 |
Set snap name to a human readable name in store upload | ~sil | 2760d | close stale | 95 | 65 | Feature request to auto-derive a human-readable title (e.g. 'Adobe Photoshop') from the snap name during store upload. Open since 2018 with zero comments or maintainer engagement; the CLI no longer sets the store display name in modern snapcraft. |
|
snapcraft (launchpad) issue #1752580 |
tests.integration.general.test_parser.TestParserWikis fails | ~kalikiana | 3116d | close stale | 95 | 75 | 8.5-year-old report that TestParserWikis failed locally because the bin/snapcraft-parser binary was missing (Python 3.5 era). The old tests/integration/general suite no longer exists in the repo; no maintainer engagement. |
|
snapcraft (launchpad) issue #1813364 |
The `setup.py` parse-info method treats description/long_description keys wrongly | ~brlin | 2786d | needs triage | 95 | 55 | Snapcraft's setup.py parse-info maps description to snap description and ignores long_description, mismatching setuptools conventions; open since 2018 with no maintainer activity. |
|
snapcraft (launchpad) issue #1823512 |
`snapcraft --shell` shouldn't run the lifecycle steps | ~brlin | 2714d | close stale | 95 | 60 | Bug report claiming `snapcraft --shell` runs lifecycle steps instead of dropping into the build environment shell. 7+ years old, 0 comments, no labels; the `--shell` flag was removed in the modern CLI and `snapcraft shell` now provides the requested behavior. |
|
snapcraft (launchpad) issue #1830217 |
Unable to change dotnet-runtime-version to 2.2.3 | ~linusaker | 2668d | close stale | 95 | 65 | Snapcraft dotnet plugin fails to parse .NET runtime versions above 2.1.4 due to upstream releases.json format change. Filed against snapcraft 2.43.1 on Ubuntu 16.04; both EOL. No maintainer interaction in 7+ years. |
|
snapcraft (launchpad) issue #1795059 |
`after:` does not support `- on` selector | ~3v1n0 | 2905d | needs triage | 95 | 55 | Snapcraft part dependency 'after:' rejects arch-specific '- on <arch>:' selectors, failing schema validation. Reported ~8 years ago with no maintainer response, labels, or activity. |
|
snapcraft (launchpad) issue #1810738 |
Catkin plugin missing rosdep and stage packages source lists customization | ~benjamin.leclerc | 2804d | needs triage | 95 | 55 | Catkin plugin lacks customization for rosdep source lists and stage packages source lists (PLUGIN_STAGE_SOURCES already overridden), making it unusable with custom dependencies. Open since 2019, zero comments, no maintainer response, no labels beyond 'catkin'. |
|
snapcraft (launchpad) issue #1796802 |
PKG_CONFIG_PATH during build step should include multiarch paths | ~brlin | 2894d | needs triage | 95 | 60 | Snapcraft build step sets PKG_CONFIG_PATH to only $SNAPCRAFT_STAGE/lib/pkgconfig, missing multiarch lib/<triplet>/pkgconfig paths, so .pc files installed there are not found by later parts. Unlabelled, zero comments, ~8 years old. |
|
snapcraft (launchpad) issue #2014963 |
Snapcraft fails to build snap if Snapcraft itself is installed using `snap try` | ~brlin | 1259d | close stale | 95 | 60 | Snapcraft fails when using snap try due to snapd not allowing file downloads for try-mode snaps. Issue is 1251 days old with no maintainer engagement. |
|
snapcraft (launchpad) issue #1748324 |
python plugin fails on hashes in requirements.txt | ~ipmb | 3137d | close stale | 95 | 70 | Python plugin (snapcraft 2.35) fails when requirements.txt contains --hash entries, as pip's --require-hashes mode rejects the file:// directory requirement. Old plugin architecture removed; issue is 8.5 years old with no maintainer activity. |
|
snapcraft (launchpad) issue #1771218 |
Could not execute process 'rustc -vV' (never executed) | ~mmacedoeu | 3042d | close stale | 95 | 85 | Travis CI build failing to locate rustc after installation. Issue is 8+ years old with zero comments or maintainer activity. The project has since migrated to GitHub Actions, making the Travis integration referenced here obsolete. |
|
snapcraft (launchpad) issue #1798205 |
Underscores in app names not reported properly | ~roger.light | 2887d | needs triage | 95 | 60 | Snapcraft reports the wrong app name in validation errors when an app name contains an underscore: with apps 'one' and 'two_three', the error blames the valid app 'one' instead of 'two_three'. Open since 2014, no labels, comments, or maintainer activity. |
|
snapcraft (launchpad) issue #1826481 |
LXDInstanceProvider does not pass proxy information to lxc exec | ~bnevis | 2696d | close stale | 95 | 70 | Request to pass proxy env vars (http_proxy, https_proxy, no_proxy) to lxc exec in LXDInstanceProvider for builds behind firewalls. Class no longer exists in current codebase; LXD legacy support was removed. |
|
snapcraft (launchpad) issue #1837268 |
cannot build snap in Arch Linux | ~shackraseaslug | 2611d | close stale | 95 | 75 | Snapcraft 3.6 on Arch Linux segfaults during VM build, leaving a stale multipass instance that fails to remount. Reported July 2019; no labels, no comments, no maintainer activity in ~7 years; the core18 multipass build path is long obsolete. |
|
snapcraft (launchpad) issue #1763048 |
Snap names regexes are inconsistent or too permissive | ~adam-collard | 3075d | needs triage | 95 | 65 | Snap name regexes across the store, click-reviewers-tools, and snapd are inconsistent or too permissive (allowing one-char names, leading/trailing dashes, double dashes); snapcraft itself does not enforce a regex. No maintainer response in ~7 years. |
|
snapcraft (launchpad) issue #1958282 |
Pass proxy settings to override-pull | ~mr-cal | 1697d | close stale | 95 | 70 | Feature request to pass proxy settings into override-pull. Open for 4.6 years with zero comments, no labels, and no maintainer engagement. |
|
snapcraft (launchpad) issue #1838474 |
nodejs plugin assumes a version key in the package.json | ~robcresswell-deactivatedaccount | 2600d | close stale | 95 | 75 | Nodejs plugin crashed with KeyError when package.json lacked a version key, with no fallback to snapcraft.yaml version. Reported 2019, zero comments, no maintainer response. The nodejs plugin has since been removed and replaced by the npm plugin, so the referenced code no longer exists. |
|
snapcraft (launchpad) issue #1766101 |
Snapcraft not handling cmake nested builds, not including build script files... | ~anoncoward8348 | 3064d | close stale | 95 | 55 | Snapcraft 2.41 (classic) user reports three problems building FeedReader: cmake plugin fails on nested builds, build-override output not primed, meson build linking host glibc/gcc/zlib. No maintainer interaction; version superseded by core22 rewrite. |
|
snapcraft (launchpad) issue #1767077 |
Container names are inconsistent lxd vs multipass | ~popey | 3060d | needs triage | 95 | 55 | Request for consistent build container naming between LXD (snapcraft-<name>) and Multipass (random <name>) so snapcraft containers are easy to spot. No labels, no comments, no maintainer activity for ~7.5 years. |
|
snapcraft (launchpad) issue #1769519 |
Setting the snapcraft.yaml version field to 'git' produces undocumented and... | ~njmcphail | 3050d | close stale | 95 | 55 | Snapcraft 2.42 (2018): setting version: git in snapcraft.yaml substitutes a mangled git describe output; tags with invalid chars (e.g. underscore) yield an invalid version that snap refuses to install, with no error. No maintainer interaction in 8+ years. |
|
snapcraft (launchpad) issue #1770364 |
Using 2 remote parts, file not being copied from stage to prime | ~gerboland | 3046d | close stale | 95 | 55 | Snapcraft bug (2017): with two remote parts, a file staged by the xwayland-kiosk-helper remote part (lib/libxwayland-preload.so) is not copied into prime, while another file from the same part is. No maintainer response or activity in 8+ years. |
|
snapcraft (launchpad) issue #1834766 |
spread tests fail on non-interactive prompt in ruby/legacy-pull | ~techtonik | 2630d | close stale | 95 | 70 | 2019 CI timeout in ruby/legacy-pull spread test from interactive apt prompt during legacy snapcraft pull; zero maintainer interaction, legacy pull command and Travis CI no longer exist in current codebase. |
|
snapcraft (launchpad) issue #1655634 |
Unable to release classic snap to beta channel | ~stub | 3530d | close stale | 95 | 55 | snapcraft release prints only 'Package is not ready to be published' with no reason, blocking the user from releasing a classic snap to beta. No labels, no comments, no maintainer response; inactive for ~6 years. |
|
snapcraft (launchpad) issue #1774410 |
Having python3-netaddr as a stage package produces external symlink | ~bjornt | 3025d | needs triage | 95 | 55 | Specifying python3-netaddr as a stage-package in snapcraft 2.42 yields symlinks pointing outside the snap (to /var/lib/...), while build-packages give relative symlinks. Unlabelled, zero comments, no maintainer activity in ~8 years. |
|
snapcraft (launchpad) issue #1741131 |
python plugin ignores source-subdir | ~elopio | 3173d | close stale | 95 | 70 | Python plugin can't find setup.py when it lives in a source-subdir, so it finishes without installing anything. No comments; a fix to locate setup.py under source-subdir was merged in PR #1975 (earlier #771 superseded #751). |
|
snapcraft (launchpad) issue #1772885 |
dropping privs did not work: No data available | ~edo.red | 3033d | close stale | 95 | 75 | User reports 'dropping privs did not work: no data available' when running sudo lxd init while setting up snapcraft. It is a support question about LXD (an external tool), not a snapcraft bug. Open 8+ years with zero comments, labels, or maintainer interaction. |
|
snapcraft (launchpad) issue #1771778 |
Inconsistent parameter syntax | ~popey | 3039d | close stale | 95 | 60 | snapcraft release accepts comma-separated channels but snapcraft close does not, requiring space-separated args. 8+ years old, zero comments, no labels, project since completely rewritten. |
|
snapcraft (launchpad) issue #1749699 |
Delta error is shown on first push, can be avoided? | ~facundo | 3130d | close stale | 95 | 60 | User reports snapcraft push prints 'Error generating delta: delta saving is less than 10%' on a first push where no delta can exist. No labels, no comments, no maintainer activity in ~8.5 years; delta compression has since been removed from snapcraft. |
|
snapcraft (launchpad) issue #1795430 |
build-package "on amd64 to armhf" seems to be not working | ~mvo | 2902d | close stale | 95 | 70 | Cross-building with build-on/run-on architecture grammar does not install the specified build-packages (e.g. gcc-arm-linux-gnueabihf) unless an explicit --target-arch is passed. Reported in 2018, no maintainer interaction, zero comments. |
|
snapcraft (launchpad) issue #1750006 |
Revamp tests for using utilities in deb/snap/docker | ~kyrofa | 3129d | close stale | 95 | 70 | Maintainer task to revamp complex unit tests verifying which utilities are used when Snapcraft runs from a deb, snap, or docker. 8.5 years old, no labels, zero comments; near-identical issue snapcraft#1932 was closed without action. |
|
snapcraft (launchpad) issue #1827217 |
create-key without a passphrase is not possible using multipass | ~0-luke | 2690d | close stale | 95 | 55 | 2018 report that snapcraft create-key cannot be run without a passphrase in a multipass VM: pressing return loops back to the confirm-password prompt. Open ~7.3 years with zero comments, no labels, and no maintainer interaction. |
|
snapcraft (launchpad) issue #1858023 |
export-login is too big for env variable | ~abitrolly | 2445d | close stale | 95 | 55 | snapcraft export-login output (macaroon credentials) too large for Travis CI SNAP_TOKEN env variable. 6.7 years old, zero comments, no labels, no maintainer interaction. Travis CI for open source is defunct and snapcraft store integration has been rewritten since. |
|
snapcraft (launchpad) issue #1813634 |
not reliable way to detect target architecture | ~ondrak | 2783d | needs triage | 95 | 55 | Snapcraft 3.0.1: project.target_arch and SNAPCRAFT_ARCH_TRIPLET give inconsistent values for target arch across native, cross, and multi-arch (build-on/run-on) builds. No maintainer response, no labels, inactive ~7 years. |
|
snapcraft (launchpad) issue #1602799 |
Wrong error when trying to release a devmode snap to stable | ~elopio | 3712d | close stale | 95 | 55 | Snapcraft displays a technical error ('Revision 2 (devmode) cannot target a stable channel') instead of the UX-specified friendly message ('Cannot release a devmode snap in the stable channel. Try --beta or --edge') when a devmode snap is released to stable. No comments, no labels beyond store/ux, no maintainer response in ~9.5 years. |
|
snapcraft (launchpad) issue #1777659 |
Snapcraft version string doesn't allow certain characters | ~popey | 3006d | needs triage | 95 | 45 | Snapcraft rejects version strings containing underscores (e.g. '2018_931-01') even though the version field is described as 'just for humans'. No maintainer response, no labels, 0 comments, ~8 years old. |
|
snapcraft (launchpad) issue #1778530 |
rust plugin. failed build with RUST ver. 1.27 | ~general-beck | 3000d | close stale | 95 | 65 | Snapcraft rust plugin fails with Rust 1.27: 'could not execute process rustc -vV (never executed)'; 1.26.2 works. 8 years old, zero comments, no maintainer response. The plugin has since been substantially rewritten. |
|
snapcraft (launchpad) issue #1815358 |
python package not updating during snap creation | ~falko-o | 2770d | close stale | 95 | 60 | Snapcraft python plugin fails to rebuild a changed Python package on re-run, keeping the old version; user must flip source-type git/local to force a build. Legacy multipass-VM flow, no maintainer activity in ~7.5 years. |
|
snapcraft (launchpad) issue #1779154 |
BrokenPipeError when `| head`ing output | ~saviq | 2997d | needs triage | 95 | 60 | Piping snapcraft revisions output to head triggers a BrokenPipeError traceback. Reported 8+ years ago with zero maintainer interaction; no BrokenPipeError handling found in current codebase. |
|
snapcraft (launchpad) issue #1921950 |
Can't build simple snap, maybe because of missing kmod arp_tables | ~paddor | 1991d | close stale | 95 | 80 | User's snapcraft 4.6 build stalls after snapcraftctl build; host KVM kernel lacks the arp_tables module needed by multipass networking, plus unrelated store 403 and polkit errors. Untriaged, 0 comments, ~5.4 years old, on long-EOL versions. |
|
snapcraft (launchpad) issue #1830788 |
Electron apps won't cross-compile for armhf (raspberry pi) | ~zane470 | 2663d | close stale | 95 | 75 | Snapcraft 2.43.1 (Ubuntu 18.04) crashes with NotImplementedError when cross-compiling an Electron app using the desktop-gtk3 plugin for armv7l. No activity for 7+ years; the affected 2.x plugin system has been replaced by the modern parts/extension architecture. |
|
snapcraft (launchpad) issue #1807492 |
Snapcraft should print the path of the stack trace file even when the error... | ~brlin | 2834d | close stale | 95 | 70 | Feature request to always print the local stack trace file path when Snapcraft auto-sends error reports. Open since 2018 with zero comments, no labels, and no maintainer interaction. |
|
snapcraft (launchpad) issue #1825797 |
cmake: Shouldn't use sourcedir for building | ~brlin | 2699d | close stale | 95 | 85 | Request for cmake plugin to use out-of-source builds (build in SNAPCRAFT_PART_BUILD instead of SNAPCRAFT_PART_SRC). 2689 days old, no labels, no comments, no maintainer interaction. The current craft-parts cmake plugin already implements out-of-source builds via get_out_of_source_build() returning True. |
|
snapcraft (launchpad) issue #1786423 |
Cannot install snapd on OpenWrt | ~liteon-tonyyu | 2954d | close stale | 95 | 70 | Reported that the snapd source tarball URL (people.canonical.com/~teknoraver/snapd-2.0.10.tar.xz) referenced in the OpenWrt install docs is dead, breaking package compilation. No maintainer response, no labels, 8+ years old. |
|
snapcraft (launchpad) issue #1660614 |
snapcraft's nodejs plugin does not refresh the global, user cache before... | ~gvancuts | 3510d | close stale | 95 | 70 | Legacy snapcraft nodejs plugin used npm --cache-min=Infinity, so a stale npm cache could cause ETARGET build failures when a dependency version was newly published. No maintainer response in ~9.5 years; the legacy plugin no longer exists in current snapcraft. |
|
snapcraft (launchpad) issue #1790346 |
store review fails on "unknown keys in snap/manifest.yaml: snapcraft..." | ~saviq | 2931d | close stale | 95 | 60 | Store auto-review (lint-snap-v2) rejected core18/bionic snaps, flagging snapcraft-os-release-id, snapcraft-os-release-version-id, snapcraft-version as unknown manifest.yaml keys. No activity in ~8 years; base is EOL, store linting since updated. |
|
snapcraft (launchpad) issue #1663583 |
'prepare' and 'install' stanza are missing documentation | ~3v1n0 | 3500d | close stale | 95 | 65 | Missing docs for 'prepare:' and 'install:' part stanzas in snapcraft. Open since 2016 with zero interaction; these stanzas belonged to the old snapcraft 1.x parts system, completely rewritten in 2.x. |
|
snapcraft (launchpad) issue #1793748 |
Error pulling nodejs plugin v6.14.2-linux-x64.tar.gz | ~aleks.bogdanov | 2912d | close stale | 95 | 85 | snapcraft 2.43.1 nodejs plugin crashes with zlib 'invalid block type' error while extracting a corrupted node-v6.14.2-linux-x64.tar.gz. 8 years old, zero comments, and the legacy nodejs plugin has since been removed from snapcraft. |
|
snapcraft (launchpad) issue #1793471 |
snapcraft trggers unnecessary pulls from unrelated file modifications | ~aleks.bogdanov | 2913d | close stale | 95 | 60 | Feature request to add .snapignore support so IDE and .git changes stop marking snapcraft stages stale and triggering unnecessary re-pulls/rebuilds. Open since 2018 with label 18.10-build-caching, zero comments, no maintainer engagement for ~8 years. |
|
snapcraft (launchpad) issue #1625630 |
python3 plugin cannot create hard link | ~sinzui | 3643d | close stale | 95 | 85 | python3 plugin fails during parts phase on Xenial with tar hard link error (python3.5 vs python3.5m). Untriaged, no comments, ~9.7 years old. The python3 plugin has since been removed from snapcraft (commit 958b58615, PR #2325), making the issue obsolete. |
|
snapcraft (launchpad) issue #1868453 |
All interfaces are allowed to have a label | ~zyga | 2364d | close stale | 95 | 72 | Snap Store review pipeline rejects the 'label' interface attribute with 'unknown attribute' error, despite snapd supporting it. 6+ years old, zero comments, no labels, no maintainer engagement. Store-side validation issue outside snapcraft scope. |
|
snapcraft (launchpad) issue #1739473 |
Add support for pipenv/Pipfile | ~oddbloke | 3187d | close stale | 95 | 65 | Feature request to add pipenv/Pipfile support to snapcraft, filed ~8.7 years ago with no labels, comments, or maintainer activity. The premise that pipenv is Python.org's recommended tool is outdated, and requirements.txt export remains a workaround. |
|
snapcraft (launchpad) issue #1686442 |
Tab Completion Blocks Keyboard Input | ~ocdrichard | 3425d | close stale | 95 | 80 | Report that pressing TAB during 'sudo snap install --devmode' on snap 2.23.6 (Ubuntu 17.04, series 16) freezes the console and blocks all keyboard input. No labels, no comments, no activity for ~9 years; the affected release is long past EOL. |
|
snapcraft (launchpad) issue #1760583 |
Text not being displayed in PyQt app | ~subins2000 | 3084d | close stale | 95 | 65 | PyQt5 app (TorrentBro) packaged as a snap shows no text because the Sans-serif font is unavailable inside the confined snap. Author asks whether to bundle the font or if it is a bug. No maintainer response; ~8.4 years old. |