Showing 100 of 2042 issues
| Issue | Title | Author | Age | Action | Staleness ↑ | Confidence | Summary |
|---|---|---|---|---|---|---|---|
|
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 #1824077 |
IsADirectoryError occurred when migrating /usr/bin/X11 symlink in stage step | ~brlin | 2712d | 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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #1693451 |
Support CircleCI for building | ~popey | 3397d | 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 #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 #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 #1903046 |
Progressive release stops showing metrics when set to 100% target | ~noise | 2136d | close stale | 95 | 55 | snapcraft status stops showing progressive release metrics once target reaches 100%. Reported 5.8 years ago with zero maintainer interaction, no labels, and no comments. Progressive release feature has since evolved (PR #6189 merged). |
|
snapcraft (launchpad) issue #1962474 |
snapcraft remote-build login url is badly formatted | ~nymea | 1656d | close stale | 95 | 65 | Reports that the snapcraft remote-build login URL included a trailing closing parenthesis, breaking terminal URL detection. No maintainer response in ~4.4 years; the remote-build command was later removed from snapcraft, so the issue is obsolete. |
|
snapcraft (launchpad) issue #1638622 |
dump plugin cannot copy a single file | ~jamesj | 3600d | needs triage | 95 | 70 | Request for the dump plugin to support copying individual files (like the deprecated copy plugin's files property). No maintainer response in ~9.6 years; dump plugin still only accepts source, so the gap persists. |
|
craft-platforms pr #95 |
docs: how-to and explanation for filtering a build plan | lengau | 596d | close stale | 95 | 50 | Documentation PR adding how-to guide for filtering build plans in craft-platforms. PR is 589 days old with no activity, no reviewers, and no CI checks. |
|
snapcraft (launchpad) issue #1998341 |
Local pytest/unit run test_get_extensions_data_dir() fails | ~giusebar18 | 1381d | close stale | 95 | 55 | Local pytest test_get_extensions_data_dir() fails due to missing extensions data directory; resolved by running pip install .; no maintainer engagement in 1373 days |
|
snapcraft (launchpad) issue #1858785 |
go plugin doesn't strip binaries | ~ack | 2438d | close stale | 95 | 60 | Feature request to add an option to strip binaries built by the go plugin to reduce snap size. 6.6 years old with zero comments and no labels; the go plugin has since been removed from snapcraft, making the request moot. |
|
craft-platforms pr #117 |
DO NOT MERGE: tests: add some questionable but valid platform names | lengau | 529d | close stale | 95 | 85 | Discussion PR about platform name validation limits, marked DO NOT MERGE. No activity for 521 days. Platform name validation already implemented in project. |
|
snapcraft (launchpad) issue #1859424 |
Multipass/VMs by default discourages newcomers | ~lool | 2433d | needs triage | 95 | 55 | Snapcraft's default use of Multipass for builds frustrates newcomers (nested-VM failures on macOS/Windows, slow builds from silent LXD-to-Multipass switch); proposes warnings, KVM detection, docs, and release/debug defaults. Open 6.6 years, no labels, no comments, no maintainer response. |
|
snapcraft (launchpad) issue #1834207 |
removing parts should clean stage and prime… stages? | ~saviq | 2635d | close stale | 95 | 55 | Bug report from 2017: removing a part from snapcraft.yaml does not clean its contents from stage/prime, so the built snap still includes the removed part's files. No labels, no comments, no maintainer activity in ~7 years. |
|
snapcraft (launchpad) issue #1858994 |
snapcraft list-keys doesn't show the non-registered key when no key is registered | ~ethan.hsieh | 2438d | close stale | 95 | 70 | list-keys (snapcraft 3.8) fails to show a locally created key when no key is registered yet, printing 'No keys have been registered' instead. Unlabelled, zero comments, no activity for ~6.6 years; the command was later removed and replaced by snapcraft keys. |
|
snapcraft (launchpad) issue #1608932 |
multiple parts with same git repo makes build checkout out redundant repos | ~adam-stokes | 3692d | close stale | 95 | 60 | snapcraft 2.13.1: parts sharing the same git source each get their own checkout instead of a shared cache. No maintainer activity for ~9.5 years; the 2.x series is EOL and modern craft-parts-based snapcraft uses a shared source cache. |
|
snapcraft (launchpad) issue #1989030 |
snapcore/snapcraft image is outdated (again) | ~ianconsolata | 1465d | needs triage | 95 | 70 | Report that snapcore/snapcraft Docker images are outdated, claiming automation to keep them updated may be broken. Issue is 4 years old with no maintainer response or labels. |
|
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 #1990298 |
fatal: detected dubious ownership in repository at '/root/project' when ran... | ~saviq | 1452d | close stale | 95 | 75 | snapcraft --use-lxd fails with Git dubious ownership error when using version: git. Issue is 4 years old with no maintainer interaction. |
|
snapcraft (launchpad) issue #2031494 |
snapcraft login doens't work on fresh multipass or lxd | ~gbeuzeboc | 1123d | close not a bug | 95 | 75 | snapcraft login fails in fresh multipass/LXD containers due to missing keyring. No maintainer response. Workaround documented in error message. |
|
snapcraft (launchpad) issue #1946406 |
snapcraftcontent.com shows certificate error | ~steve010 | 1800d | close stale | 95 | 70 | Revoked SSL certificate on canonical-bos01.cdn.snapcraftcontent.com broke automated snap downloads. Open ~5 years with zero maintainer interaction; a similar CDN cert issue was resolved externally by Canonical renewing certificates. |
|
snapcraft (launchpad) issue #1617253 |
snapcraft syntax documentation is incomplete | ~rogpeppe | 3668d | close stale | 95 | 72 | 10-year-old report that snapcraft.yaml syntax docs omitted app-level plugs. Docs have since been fully restructured into docs/reference/ (58 files); the old URL paths no longer exist. No maintainer interaction, zero comments. |
|
snapcraft (launchpad) issue #1947914 |
concurrent snapcraft builds with multipass provider | ~geekorous | 1787d | close stale | 95 | 60 | Concurrent snapcraft builds with the multipass provider assign all instances the same IPv4, aborting builds with no debug info. No labels, comments, or maintainer activity in ~4.8 years; targets snapcraft 5.0 on EOL Ubuntu 18.04/20.04. |
|
snapcraft (launchpad) issue #2028686 |
snapcraft pack failure from git worktree | ~dbungert | 1144d | close stale | 95 | 60 | snapcraft pack fails when building from a git worktree. Issue is 1136 days old with no labels, no comments, and no maintainer engagement. |
|
snapcraft (launchpad) issue #1617346 |
Need richer autotools control | ~stub | 3668d | close stale | 95 | 60 | Feature request from 2015 asking the autotools plugin to support overriding make steps (e.g. make world, install-world) for a custom build pipeline. No maintainer response or labels; a similar Launchpad bug (1619912) requesting make-targets remains open. |
|
snapcraft (launchpad) issue #1860550 |
Defining base snap breaks snapping Subiquity | ~nwessels | 2424d | close stale | 95 | 80 | Subiquity snap build with base: core18 leaves /snap/bin empty and snapd stuck seeding in ISO; works without base keyword. Reported ~6.5 years ago with zero comments; core18 is EOL and snapcraft 8.x rewrote base handling, so it is no longer applicable. |
|
snapcraft (launchpad) issue #1627042 |
prime in nodejs plugin does work if used multiple times in one snapcraft.yaml | ~maarten-ectors | 3640d | close stale | 95 | 65 | nodejs plugin yields correct stage but wrong prime when two separate parts both use the plugin; a single part with multiple node-packages works. 10-year-old report, no labels, no maintainer activity. |
|
snapcraft (launchpad) issue #1698888 |
Snapcraft dpkg-query error on multiarch OS | ~pcercuei | 3371d | needs triage | 95 | 65 | Snapcraft fails on multiarch OS with both i686 and x86_64 libc6 installed, as dpkg -L libc6 returns an ambiguous package name error. 9-year-old issue with no maintainer interaction; the dpkg -L call still exists in craft-parts. |
|
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 #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 #1957766 |
plugin:meson is not installed during pull stage | ~xnox | 1702d | needs triage | 95 | 55 | snapcraft 6.0.1: plugin:meson parts are not cached during the pull stage, so the build stage must fetch meson over the network and the proxy times out. Reported by xnox, open ~4.6 years with no labels, comments, or maintainer response. |
|
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 #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 #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 #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 #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 #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 #1940830 |
snapcraft remote-build fails in Windows when using a \\wsl$ path | ~lucyllewy | 1845d | close stale | 95 | 70 | snapcraft remote-build on Windows crashes with a ValueError when the project lives on a \\wsl$ mount, because link_or_copy_tree calls ntpath.relpath across different mounts. Old snapcraft 7.x code path; no maintainer activity in ~5 years. |
|
snapcraft (launchpad) issue #1851905 |
Unable to build with lxd when using lxd with lvm pool. | ~extraymond | 2499d | close stale | 95 | 70 | Snapcraft 3.8/3.9.2 fails with --use-lxd when LXD uses a custom LVM pool, due to a hardcoded /var/snap/lxd/common path. 6+ years old, no labels, no maintainer interaction, no comments. |
|
snapcraft (launchpad) issue #1670146 |
QMake plugin should allow specifying custom Qt paths | ~tim-sueberkrueb | 3477d | close stale | 95 | 55 | Feature request to let the QMake plugin point at a custom Qt installation newer than Ubuntu's archives. Open ~9.5 years, zero comments, no labels, never triaged; the project later added the qbs plugin as the modern Qt build path. |
|
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 #1771778 |
Inconsistent parameter syntax | ~popey | 3040d | 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 #1852329 |
appstream parsing fails when comments exist | ~ken-vandine | 2495d | needs triage | 95 | 50 | Snapcraft fails to parse the appstream description when translator comments are present in the metainfo XML. Unlabelled, zero comments, no maintainer interaction, inactive for ~6.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 #1853540 |
Snap package shows as registered but unable to publish | ~gabeduke | 2486d | close not a bug | 95 | 70 | User reports snap name kubectl-iexec shows as registered but snapcraft push fails with 'not the publisher' error; a store account permission issue, not a snapcraft bug; 2475 days old with no maintainer response. |
|
snapcraft (launchpad) issue #1982420 |
libdevmapper-dev fails to install as build-package using snapcraft:core20 (Multipass) | ~nuccitheboss | 1514d | close stale | 95 | 55 | core20 snap build in Multipass fails installing libdevmapper-dev build-package because the build instance apt upgrade pulls from focal-backports, then sources revert to main, leaving unmet version dependencies. No maintainer activity in ~3.5 years. |
|
snapcraft (launchpad) issue #2017771 |
apt update failure during core22 destructive-mode pulls | ~suligap | 1234d | needs triage | 95 | 60 | apt update fails during core22 destructive-mode pulls for non-root users, reported as regression from core20. No maintainer response or labels after 1226 days. |
|
snapcraft (launchpad) issue #1852618 |
apt auto refresh sometimes interferes with my snap builds | ~pengale | 2493d | close stale | 95 | 60 | snapcraft build fails with dpkg lock error when background apt auto-refresh in multipass VM holds the lock; reporter suspects their own ppa/apt update in a part may be self-inflicted; open 2482 days, 0 comments, no labels, no maintainer interaction. |
|
snapcraft (launchpad) issue #1688703 |
Enable optimizations by default | ~eyelash | 3416d | needs triage | 95 | 70 | Request (2018) to make snapcraft plugins consistently enable optimizations by default, or at least document each plugin's default optimization behavior. No maintainer response; plugins have since been refactored into craft-parts. |
|
snapcraft (launchpad) issue #1956157 |
RuntimeWarning: compiletime version 3.8 of module 'msgpack._packer' does not... | ~kenneth-loafman | 1714d | close stale | 95 | 65 | duplicity status against dropbox backend emits RuntimeWarning about msgpack._packer compiled with Python 3.8 but running under Python 3.6. No maintainer interaction in 1703 days; Python 3.6 is long EOL and the snap ecosystem has moved past this version mismatch. |
|
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 #1716055 |
It is not possible to install a build-snap with a closed risk | ~elopio | 3290d | close stale | 95 | 55 | build-snaps with a closed channel (e.g. latest/candidate) crashes with KeyError instead of falling back to the next open risk level; filed by maintainer elopio 9 years ago, zero activity, old internal/repo code path no longer exists in current architecture |
|
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 #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 #1860526 |
source-type breaks remote-build | ~wallyworld | 2425d | close stale | 95 | 85 | snapcraft remote-build fails when source-type is git because the source directory differs from the working directory, causing go dep to fail. The remote-build command has since been removed from snapcraft, making this issue obsolete. |
|
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 |
|
craft-providers pr #881 |
ci: add Linux multipass weekly tests | lengau | 270d | close stale | 95 | 90 | PR to add Linux multipass weekly CI tests. Inactive for 263 days with failing CI checks. Feature already merged in commit bc946f0. |
|
snapcraft (launchpad) issue #1675479 |
python plugin doesn't work for namespace packages | ~corey.bryant | 3459d | close stale | 95 | 75 | Snapcraft's python plugin (python2.7 era) failed to install namespace packages like repoze.lru and paste without __init__.py, causing ImportErrors in the keystone snap. Open since 2016 with zero comments; the affected plugin and pip bug are long obsolete. |
|
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 #1809475 |
Feature Request: Snapcraft should ship gitignore when running `snapcraft init` | ~brlin | 2821d | close stale | 95 | 65 | Feature request from 7.7 years ago asking snapcraft init to auto-create a .gitignore file using the community Snap.gitignore template. Zero comments, no labels, no maintainer interaction. The init command still exists but the project has been fully restructured since filing. |
|
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 #1591565 |
go plugin is not striping the .git from the source | ~elopio | 3744d | close stale | 95 | 75 | 2015 bug report: the legacy go parts plugin does not strip the .git suffix from source URLs, so go get targets the wrong package path (e.g. ./cli.git/...). No labels, no comments, inactive ~9.5 years; the go plugin no longer exists in modern snapcraft. |
|
snapcraft (launchpad) issue #1947067 |
Getting error trying to release a snap | ~pcushman | 1794d | close not a bug | 95 | 75 | User reports 'You do not have permissions to modify this Snap' error when releasing a snap, despite having been granted permission. No labels, no comments, no activity for ~5 years. Store-side permission issue, not a snapcraft bug. |
|
snapcraft (launchpad) issue #1856242 |
Python plugin: ship pyc files only | ~om26er | 2465d | close stale | 95 | 70 | Feature request to make the Python plugin ship only .pyc files (removing .py) to reduce snap size. Open since 2019, unlabelled, zero comments, no maintainer activity. The current craft-parts python plugin v2 no longer bytecompiles, so the premise is outdated. |
|
snapcraft (launchpad) issue #1987853 |
snapcraft terminates override-build script prematurely without error | ~nicolasbock | 1477d | close stale | 95 | 85 | Snapcraft prematurely terminates override-build scripts after core18 to core20 upgrade, with no error output. Untriaged and inactive for over 4 years. |
|
snapcraft (launchpad) issue #1989248 |
Displaying plugins formats output differently for core20 v core22 | ~rpjday | 1462d | close stale | 95 | 75 | Inconsistent formatting of `snapcraft plugins` output across core18, core20, and core22 bases. Issue is 1454 days old with no maintainer engagement or labels. |
|
snapcraft (launchpad) issue #1606819 |
snapcraft doesn't tell me where to put the .py file for my custom plugin | ~zyga | 3699d | close stale | 95 | 65 | Request for a clearer error when a custom plugin's .py file is in the wrong location; author self-resolved in an edit (file goes in parts/plugins/x_foo.py, 'plugin: x-foo'). No maintainer activity for ~8.6 years. |
|
snapcraft (launchpad) issue #1744822 |
poor naming conventions for scripts prepare and install | ~bsutton | 3154d | close stale | 95 | 85 | Suggestion to rename snapcraft plugin scripts 'prepare' and 'install' to 'pre-build' and 'post-build' for clarity. Unlabeled, zero comments, inactive ~8.6 years; the plugin scriptlets were later removed in favor of the override-<step> model. |
|
snapcraft (launchpad) issue #1755524 |
Can not use NodeJS 8 | ~ark9719 | 3104d | close stale | 95 | 80 | snapcraft nodejs plugin build failures when pinning node-engine to 8.10.0 (missing bin, Text file busy on node). No comments or labels; closed without a fix. NodeJS 8 is long EOL and the plugin has since been 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 #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 #1798881 |
patchelf fails on i386 vscode | ~popey | 2884d | close stale | 95 | 60 | i386 vscode snap build fails because patchelf 0.9 cannot patch the 32-bit ELF (virtual address space underrun); no maintainer response, unlabelled, ~7.5 years old. |
|
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 #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. |
|
fetch-service issue #364 |
Inspectors contain valid URL placeholders | cmatsuoka | 543d | close stale | 95 | 70 | Inspectors contain valid URL placeholders that are being approved by the fetch service. Issue is stale with no maintainer engagement, labels, or assignee. |
|
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 #1761097 |
Python setup.cfg wrongly applied to all python package dependencies | ~dwynen | 3083d | 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 #1727787 |
segmentation fault | ~hawat-thufir | 3242d | close stale | 95 | 80 | Segfault when running ubuntu-make.umake android after installing the ubuntu-make classic snap. ~9 years old, no labels, no comments, no maintainer interaction; crash is in the external ubuntu-make app, not snapcraft. |
|
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. |
|
snapcraft (launchpad) issue #1737561 |
stage-packages do not honor --target-arch | ~lool | 3196d | close stale | 95 | 65 | Cross-building stage-packages pulls host architecture packages instead of target architecture. Issue is 8.7 years old with no maintainer interaction or comments. Old cross-build mode deprecated in favor of core24/craft-parts architecture. |
|
snapcraft (launchpad) issue #1767077 |
Container names are inconsistent lxd vs multipass | ~popey | 3061d | 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. |
|
fetch-service issue #96 |
Missing metadata attributes in certain file formats | cmatsuoka | 862d | close stale | 95 | 70 | Missing metadata fields (name, vendor, version, etc.) in ancillary file formats like apt Packages, git responses, snap API, pip index. No activity for 860 days. |
|
snapcraft (launchpad) issue #1741091 |
Installing snapcraft (and its dependencies) | ~tanesh | 3173d | close stale | 95 | 75 | Reports a missing 'cd snapcraft' step in the HACKING.md install guide. Open 8+ years with zero comments, no labels, and no maintainer interaction; the referenced HACKING.md no longer exists at the repo root (docs restructured into docs/contribute/). |
|
snapcraft (launchpad) issue #1599711 |
Writing snapcraft plugins is hard due to lack of API documentation | ~thomir-deactivatedaccount | 3719d | close stale | 95 | 80 | Request for snapcraft plugin author API docs (BasePlugin methods, attributes, call order). 10+ years old, 0 comments, author deactivated. The referenced BasePlugin API no longer exists in modern snapcraft. |
|
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 #1771767 |
File dispute not working | ~cprov | 3040d | close stale | 95 | 60 | 2017 report that filing a snap-name dispute via the register-name API returns an already_registered error instead of already_claimed. No labels, no comments, no maintainer activity for ~6 years; store integration has since been rewritten. |
|
snapcraft (launchpad) issue #1889082 |
snapcraft could be more helpful in figuring out prime/organize errs vs... | ~anonymouse67 | 2237d | close stale | 95 | 70 | Request to improve snapcraft error message for command-chain items to distinguish between missing file, wrong location, and non-executable script. No maintainer interaction in 6+ years. |