Issue & PR triage
Loading...
Showing 100 of 698 issues
| Issue | Title | Author | Age | Action | Staleness ↑ | Confidence | Summary |
|---|---|---|---|---|---|---|---|
|
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 #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 #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 #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 #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 #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 #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 #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 #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 #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 #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 | 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 #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 #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 #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 #1673658 |
python package failed to install because of directories in the source | ~thomir-deactivatedaccount | 3466d | close stale | 95 | 70 | Snapcraft 2.27.1-era report that the python plugin fails to install packages when the source contains directories, leaving the executable unstaged. No comments, author account deactivated, and the affected version is long obsolete. |
|
snapcraft (launchpad) issue #1669471 |
problems on revoking a gpg key for signing assertions | ~elopio | 3480d | close stale | 95 | 75 | snapcraft revoke-key prints usage help instead of revoking a GPG key (snapcraft 2.27.1). No comments or maintainer response for ~9.5 years. Version is long deprecated and store commands were reorganized under the snapcraft store subcommand. |
|
snapcraft (launchpad) issue #1670388 |
classic snap are missing some env variables for reaching command name. (snap... | ~didrocks | 3476d | close stale | 95 | 65 | Classic-confinement snapcraft 2.27.1 app wrappers omit $SNAP/bin from PATH, so bare command names fail at runtime and shebangs resolve to system binaries instead of snap ones. Reported 2017, zero comments; later addressed in snapcraft via snapcraft-runner workaround (#2889). |
|
snapcraft (launchpad) issue #1586400 |
Snap type: change from "os" to "core" | ~kyrofa | 3759d | close stale | 95 | 70 | Request to rename snapd's 'os' snap type to 'core' to avoid ambiguity on classic systems. 10+ years old with zero comments; the rename has since been implemented in snapd (core snap is now type 'core'), so the issue is moot. |
|
snapcraft (launchpad) issue #1813942 |
`snapcraft clean <part>` doesn't ensure the project is mounted | ~saviq | 2781d | close stale | 95 | 75 | snapcraft clean <part> fails with 'Could not find snap/snapcraft.yaml' when the multipass project is manually unmounted. Reported in 2017 against v3.1; no maintainer response. Codebase since rewritten to craft_application, making the original code path obsolete. |
|
snapcraft (launchpad) issue #1683536 |
snapcraft uploaded snap and then told me same content had already been uploaded | ~brian-murray | 3434d | close stale | 95 | 70 | 2017 request to detect duplicate snap content before uploading, since `snapcraft push` only reports the store's 'already been uploaded' error after a full upload. No labels or comments. The push command was later removed from snapcraft. |
|
snapcraft (launchpad) issue #1884683 |
snapcraft fail app | ~alandecunto | 2272d | close stale | 95 | 75 | Snapcraft 2.43.1+18.4 crashes with FileNotFoundError when an app's command points to /bin/Sastreria, which is missing from the prime directory. No comments or labels; the affected 2.x version is long EOL and the code path no longer exists. |
|
snapcraft (launchpad) issue #1845276 |
snapcraft shouldn't complain about snap/README.md | ~anonymouse67 | 2544d | close not a bug | 95 | 62 | Request to stop snapcraft warning about snap/README.md as a non-snapcraft path so docs can live in the snap/ dir. 7 years old, zero comments, no labels or maintainer response; the warning is intentional and already documents the snap/local/ workaround. |
|
snapcraft (launchpad) issue #1886388 |
Parameterized builds are required for snapcraft build | ~muthiahn | 2258d | close stale | 95 | 65 | Feature request from 2018 to add parameterized builds to snapcraft so a git-source part can be built from different branches via a build parameter. No labels, no comments, no maintainer response in ~6 years; largely addressable today via environment variable substitution in snapcraft.yaml. |
|
snapcraft (launchpad) issue #1917639 |
--debug drops me into an unexpected directory | ~racb | 2018d | needs triage | 95 | 55 | Snapcraft 4.5.1 --debug drops the user into /root instead of the override-stage script's working directory. Reported ~5.5 years ago, zero comments, no labels, no maintainer interaction. Related Launchpad bugs 1848513 (env vars) and 1848732 (snapcraftctl) still open. |
|
snapcraft (launchpad) issue #1897098 |
Trigger font cache rebuild if new fonts added to the system | ~igorljubuncic-deactivatedaccount | 2178d | close stale | 95 | 70 | Placeholder request (2019) to rebuild the font cache when new system/user fonts appear after a snap install. No labels, comments, or maintainer activity for ~6 years; desktop extensions now rebuild the cache via a configure-fonts hook. |
|
snapcraft (launchpad) issue #1663002 |
organize and stage keywords together mess up file conflict checking | ~mrjogo | 3502d | close stale | 95 | 55 | Bug: combining organize and stage keywords makes snapcraft's file-conflict check inconsistent — a conflict error appears for staged paths but not pre-organize paths, so a duplicate file overwrites. Unlabelled, no maintainer response, inactive ~9.5 years. |
|
snapcraft (launchpad) issue #1875524 |
remote-build doesn't work with gadget snaps | ~anonymouse67 | 2328d | close stale | 95 | 70 | snapcraft remote-build fails to copy gadget.yaml to the generated Launchpad project, breaking gadget snap builds. Unlabelled, zero comments, inactive ~6 years. The remote-build command was removed in snapcraft 2.0, so the issue no longer applies. |
|
snapcraft (launchpad) issue #1883145 |
Incorrect Exec entry transformation in .desktop file | ~alan-griffiths | 2283d | needs triage | 95 | 40 | Snapcraft incorrectly transforms Exec=snap run <snap> in .desktop files to Exec=<snap> run <snap>, producing a broken command. 6+ years old, no labels, no comments, no maintainer interaction. |
|
snapcraft (launchpad) issue #1716054 |
It is not possible to install a build-snap with the default track | ~elopio | 3290d | needs triage | 95 | 55 | Snapcraft build-snaps fails with KeyError when a channel is given without a track (e.g. snap/edge), because the code looks up store channels by the bare channel name instead of track/risk. Old bug, no maintainer response, no labels. |
|
snapcraft (launchpad) issue #1856594 |
Snapcraft tutorial errors out on OSX with multipass error, "returned exit code 2" | ~dobsorg | 2461d | close stale | 95 | 70 | Dec 2019 report: snapcraft 3.9 on macOS fails via multipass (apt 404s, mount exit code 2) and crashes with AttributeError on os.sched_getaffinity. No maintainer activity; that code path no longer exists in current snapcraft, and macOS support was dropped. |
|
snapcraft (launchpad) issue #1886861 |
npm install network errors with build.snapcraft.io proxy configuration | ~benfrancis | 2256d | close stale | 95 | 75 | npm install fails with getaddrinfo ENOTFOUND github.com due to build.snapcraft.io proxy config; reporter has a workaround via proxy env vars. ~6 years old, zero comments, and the affected build service has since been decommissioned. |
|
snapcraft (launchpad) issue #1681861 |
classic snaps recurse | ~chris.macnaughton | 3440d | close stale | 95 | 72 | Classic snap command wrappers generated by snapcraft use bare command names instead of $SNAP/bin/command paths, causing failures since PATH is not reset in classic confinement. 3429 days old, no labels, no comments, no maintainer interaction. |
|
snapcraft (launchpad) issue #1636233 |
Add support for compiler flags in autotools plugin | ~ivan-lezhnjov-iv | 3609d | needs triage | 95 | 60 | Feature request to add compiler flag support (cflags) to the autotools plugin, similar to configflags, needed for packaging PostgreSQL with flags like -fPIC -pie and mit-krb5 paths. No maintainer response, no labels beyond 'plugin', and no activity in ~10 years. |
|
snapcraft (launchpad) issue #1684091 |
snapcraft gives a confusing message when you lack permissions to administer snap | ~ev | 3432d | needs triage | 95 | 70 | snapcraft status reports 'Snap X was not found in series 16' when the real cause is that the user lacks collaborator/admin permissions on the snap; reporter suggests a clearer message. No labels, no comments, no maintainer activity in ~9 years. |
|
snapcraft (launchpad) issue #1738265 |
cmake plugin should set CMAKE_BUILD_TYPE, CMAKE_INSTALL_PREFIX | ~saviq | 3193d | close stale | 95 | 70 | Feature request from 2016 asking the CMake plugin to default CMAKE_BUILD_TYPE=RelWithDebInfo and CMAKE_INSTALL_PREFIX=/ when configuring. No maintainer response, no labels, no activity in ~9 years. Modern craft-parts cmake plugin still does not set these defaults. |
|
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 #1918267 |
The warning for CVE-2020-27348 could include a reference to how to fix | ~seb128 | 2012d | close stale | 95 | 55 | Feature request to enhance the CVE-2020-27348 empty LD_LIBRARY_PATH warning in snapcraft build logs to include a hint on how to fix the issue or a link to relevant documentation. No maintainer response, no labels, inactive for ~5.5 years. |
|
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 #2099923 |
Snapcraft builds are failing: install of snap "snapcraft" failed | ~snawoot | 564d | close stale | 95 | 80 | Snapcraft builds failing due to outdated snapd (2.61) on build infrastructure unable to install core20 base. Issue is 556 days old with no maintainer response. |
|
snapcraft (launchpad) issue #1751773 |
Re-building "snapcraft" part after failure fails at intltool-update | ~kalikiana | 3119d | close stale | 95 | 70 | Rebuilding the snapcraft part with SNAPCRAFT_CONTAINER_BUILDS=1 fails on the second build: python-apt wheel build needs intltool-update, missing from the environment. No comments or labels; the self-build flow no longer exists in current snapcraft. |
|
snapcraft (launchpad) issue #1658765 |
[Godeps] Specifying source tag fails to stage | ~nskaggs | 3518d | close stale | 95 | 70 | Godeps plugin fails to stage when source-tag is specified: git pull of the tag ref errors with 'cannot update the ref HEAD: non-commit object'. Reported ~2016, no maintainer activity, no labels. |
|
snapcraft (launchpad) issue #2017688 |
staging lsb-release in python part make the part fail | ~gbeuzeboc | 1235d | needs triage | 95 | 70 | Untriaged bug report stating that staging lsb-release in a python part causes ensurepip to fail due to PATH pollution. No maintainer interaction in over 3 years. |
|
snapcraft (launchpad) issue #1735410 |
Localization support | ~mkljczk | 3207d | close stale | 95 | 70 | Request to implement localization (l10n) support in Snapcraft, filed by an external contributor who offered to take it on. Open ~8.7 years with zero comments, no maintainer response, and no evidence of any l10n work in the codebase. |
|
snapcraft (launchpad) issue #1662634 |
Please add snapcraft version key | ~ted | 3503d | needs triage | 95 | 45 | Feature request to add a snapcraft-version key to snapcraft.yaml so users on older snapcraft get a clear 'Snapcraft X required' message instead of a cryptic schema error. Open ~9.5 years with zero comments, no labels, and no maintainer engagement. |
|
snapcraft (launchpad) issue #1676684 |
Python plugin tries to chmod symlinks to system files | ~mrjogo | 3455d | close stale | 95 | 70 | Old snapcraft python plugin (pre-rewrite) crashed with PermissionError when _fix_permissions tried to chmod root-owned symlinks to system files after a prior part staged python-dev. The plugin has since been fully rewritten as a thin wrapper around craft-parts; the offending _fix_permissions/_replicate_owner_mode code no longer exists in the repo. |
|
snapcraft (launchpad) issue #2000890 |
Changed base from 20->22, crash report | ~williamcharltonengineering | 1348d | close stale | 95 | 85 | User reported crash when changing base from core20 to core22 in snapcraft 7.2.10. KeyError: 'core22' in legacy build provider code. Issue is 1339 days old with no activity. |
|
snapcraft (launchpad) issue #1681722 |
classic snaps cannot find stage packages in $PATH | ~stub | 3440d | close stale | 95 | 60 | Classic snaps with stage-packages cannot find dependent binaries because snap bin directories are missing from default PATH. 9+ years old, zero comments, no labels. A related workaround (PR #2889, snapcraft-runner) was merged to address classic snap PATH resolution. |
|
snapcraft (launchpad) issue #1820797 |
Snapcraft should allow prepending/appending additional text from description... | ~brlin | 2734d | needs triage | 95 | 65 | Feature request to let packagers prepend/append custom text (e.g. unofficial-snap disclaimers) to the description adopted via adopt-info. ~7.5 years old, no labels, no comments, no maintainer interaction; never triaged. |
|
snapcraft (launchpad) issue #1695081 |
autotools plugin should support explicit autogen or autoreconf | ~sabdfl | 3389d | close stale | 95 | 70 | Feature request (2015) for the autotools plugin to support explicit autogen/autoreconf steps. No comments or labels; core request since implemented in the autotools v2 plugin via autogen.sh and bootstrap support (PR #3398). |
|
snapcraft (launchpad) issue #1709060 |
Trouble allocating fonts in a Tcl/Tk (Python 3.5) based snap | ~kushalchauhan98 | 3322d | close stale | 95 | 75 | Tcl/Tk font allocation error when running a Python 3.5 tkinter snap built with snapcraft 2.33. No maintainer interaction; issue is 9 years old with zero comments. |
|
snapcraft (launchpad) issue #1663233 |
Confusing error message for "organize" when source refers to multiples items... | ~didrocks | 3501d | needs triage | 95 | 55 | Snapcraft 2.26 (2017) reports a misleading 'already exists' error when an organize glob matches multiple items and the destination lacks a trailing slash; reporter suggests auto-treating the destination as a directory. No maintainer response; code has since moved to craft-parts. |
|
snapcraft (launchpad) issue #1740500 |
"The name <foo> is already taken" is a poor experience | ~popey | 3178d | close stale | 95 | 80 | UX complaint that the 'The name <foo> is already taken' error from snapcraft register is off-putting and discourages new users from claiming a name they legitimately own. 8+ years old, no maintainer response, and the register command/prompt has since been removed from current snapcraft. |
|
snapcraft (launchpad) issue #1742585 |
snapcraft version number output inconsistent | ~popey | 3166d | needs triage | 95 | 55 | snapcraft 2.35 CLI displays version 3.10 as 3.1 in release/status output while push shows 3.10; unlabelled, no maintainer response, inactive 3155 days (snapcraft 2.35 era, now superseded by 8.x). |
|
snapcraft (launchpad) issue #1752576 |
tests.unit.test_lifecycle.CoreSetupTestCase.test_core_setup_if_docker_env fails | ~kalikiana | 3116d | close stale | 95 | 70 | 2017-era snapcraft unit test failure: test_lifecycle CoreSetupTestCase regex expected bare 'unsquashfs' but code emits full /snap/snapcraft path. No labels, no comments, no maintainer response in 8.5 years; referenced test no longer exists in the modern codebase. |
|
snapcraft (launchpad) issue #1800659 |
"Writing more data than expected" while snapping an ros project | ~ghost069 | 2873d | close stale | 95 | 75 | User on snapcraft 2.43.1 hit an apt FetchError ('Writing more data than expected') pulling catkin/ROS deps. No maintainer response in ~8 years; the error is an apt cache/mirror issue and the affected version is long EOL. |
|
snapcraft (launchpad) issue #1576289 |
image loaders (gdkpixbuf) not easy to integrate | ~seb128 | 3788d | close stale | 95 | 85 | Feature request to automate gdk-pixbuf loader integration in snaps. Now implemented via desktop extensions: desktop-exports sets GDK_PIXBUF_MODULE_FILE/MODULEDIR and regenerates the cache. 0 comments, no maintainer activity in ~9 years. |
|
snapcraft (launchpad) issue #1847321 |
Snap with python3 + tkinter crashes with SEGFAULT | ~eikekuehn42 | 2530d | close stale | 95 | 45 | Snap built with python3 + tkinter segfaults when creating a tkinter Label; minimal repro repo provided. No comments or maintainer activity for ~6.4 years; the original build stack is long out of support. |
|
snapcraft (launchpad) issue #1629978 |
create-key prints no progress | ~elopio | 3630d | needs triage | 95 | 70 | snapcraft create-key prints no progress output and can appear stuck while collecting entropy; issue is open, unlabelled, and has no maintainer response. |
|
snapcraft (launchpad) issue #1666739 |
Content interface parsing too lenient | ~michihenning | 3489d | close stale | 95 | 55 | Snapcraft silently accepts a string for the content interface read/write path instead of requiring a list, deferring the error to snapd install time. Reporter wants snapcraft to reject the invalid YAML. Unlabelled, no maintainer activity in ~9.5 years. |
|
snapcraft (launchpad) issue #2011634 |
New App Icon Not Shown in Ubuntu Software | ~arian73 | 1277d | close stale | 95 | 45 | Report that a changed app icon is not displaying in Ubuntu Software. Issue is 1269 days old with no maintainer engagement, labels, or comments, and lacks reproduction details. |
|
snapcraft (launchpad) issue #1669854 |
Hidden files are not staged after "dump" | ~joeborg | 3479d | close stale | 95 | 55 | Reports that hidden files/dirs from a tar.gz unpacked via the dump plugin are dropped during part staging and again from stage to prime, though they appear in the install dir. 9.5 years old, zero comments, no maintainer interaction. |
|
snapcraft (launchpad) issue #1661463 |
parser doesn't pull in dependent parts from the origin | ~joetalbott | 3508d | close stale | 95 | 55 | Snapcraft parser fails to include 'after' parts (e.g. libmbim, libqmi) referenced from a remote git origin, erroring 'not defined in the parts entry'. 9.5 years old, no labels or maintainer activity; the origin-based parts feature is likely gone in modern rewrites. |
|
snapcraft (launchpad) issue #1613779 |
go plugin ignores the source-subdir keyword | ~jgrimm | 3678d | close stale | 95 | 80 | Go plugin (snapcraft 1.x) ignored source-subdir, symlinking GOPATH to git root instead of the subdirectory. 10 years old, 0 comments, no maintainer interaction. The GOPATH-symlink approach and go-importpath key no longer exist in the modern go plugin. |
|
snapcraft (launchpad) issue #2052928 |
Pulling from private repository without known_hosts hangs forever | ~gbeuzeboc | 942d | needs triage | 95 | 50 | SSH pull from private repo hangs when known_hosts is missing; SSH authenticity prompt is hidden by snapcraft progress bar. Untriaged, 935 days old. |
|
snapcraft (launchpad) issue #1646546 |
snapcraft packages .so from /usr instead of from .deb | ~aacid | 3571d | close stale | 95 | 60 | 2016-era report that snapcraft picked up .so files from the host /usr instead of from .deb packages, so snap contents depended on the host system. No maintainer response or labels. Likely obsolete since snapcraft now builds inside a confined core base. |
|
snapcraft (launchpad) issue #1636979 |
snapcraft validate and sign-build are inconsistent when there are multiple keys | ~elopio | 3607d | needs triage | 95 | 55 | snapcraft validate uses the default signing key while sign-build shows a key-selection wizard when multiple keys exist; the two commands should behave consistently. Open since 2016, zero comments, no maintainer response. |
|
snapcraft (launchpad) issue #1663052 |
No Fish shell support | ~joeborg | 3502d | close stale | 95 | 55 | Feature request for Fish shell completion support, filed ~9.5 years ago. Body only says a PR was created on GitHub, with no link, no labels, and zero comments or maintainer interaction since. |
|
snapcraft (launchpad) issue #1599974 |
[parser] find a better solution than pulling the entire wiki contents into memory | ~joetalbott | 3718d | close stale | 95 | 70 | Performance suggestion to stream wiki contents via a generator instead of loading them all into memory, targeting the old snapcraft wiki-based parts parser. 10 years old, zero comments, and the wiki parser no longer exists in the modern craft-parts-based codebase. |
|
snapcraft (launchpad) issue #1666639 |
unusual mode 'rwxr-xr-x' for symlink ' | ~joeborg | 3489d | close stale | 95 | 75 | 2015 report that a click-app build on myapps.developer.ubuntu.com failed with 'unusual mode rwxr-xr-x for symlink' warnings. No labels, no comments, no maintainer response in ~9.5 years; the referenced build portal no longer exists. |
|
snapcraft (launchpad) issue #1903854 |
desktop file Icon: relative search for case where prefix is not /usr | ~cjp256 | 2130d | needs triage | 95 | 55 | Snapcraft desktop file Icon path resolution fails when Meson prefix is not /usr; suggests searching relative to the desktop file. Open since 2019, no comments, no labels, no maintainer response. |
|
snapcraft (launchpad) issue #1683823 |
snapstore returns multiple instances of the same publication (was snapcraft... | ~apw | 3433d | close stale | 95 | 78 | 2017 bug report: snapcraft list-revisions displayed duplicate channel entries (e.g. 'edge*, edge*, edge*') per revision. No maintainer activity in 7 years. The revisions command has since been rewritten to use a set for channels, structurally preventing duplicates. |
|
snapcraft (launchpad) issue #1988095 |
prefixing snapcraft with "time" makes it ignore --verbose | ~ogra | 1474d | close stale | 95 | 50 | Running `time snapcraft --verbose` suppresses verbose output, unlike running `snapcraft --verbose` directly. Reported 1465 days ago with no maintainer engagement or labels. |
|
snapcraft (launchpad) issue #1989139 |
Duplicated /root/stage in path | ~nteodosio | 1464d | close stale | 95 | 40 | Bug report about duplicated /root/stage in Snapcraft 7.1.3 causing build failures. Issue is 4 years old with no maintainer interaction or labels. |
|
snapcraft (launchpad) issue #1634803 |
snapcraft register-key doesn't use U1 SSO login credentials | ~vrruiz | 3614d | close stale | 95 | 60 | register-key re-prompts for U1 SSO credentials even after a successful snapcraft login, tested on snapcraft 2.19. ~10 years old, unlabelled, 0 comments, no maintainer activity; a near-identical Launchpad bug is also open. |
|
snapcraft (launchpad) issue #1986624 |
snapcraft points to wrong entry in apps as being invalid. | ~djacobs98 | 1487d | keep open | 95 | 70 | Snapcraft 6.1 validation error misreports the first app ('runtests') as invalid when the actual offending app name ('get_cache_info', with an underscore) is the real problem. No maintainer interaction; zero comments; ~4 years old. |
|
snapcraft (launchpad) issue #1992557 |
snapcraft remote-build snapcraft.yaml validation too strict | ~fnordahl | 1431d | close stale | 95 | 55 | snapcraft remote-build validation rejects empty LD_LIBRARY_PATH in environment, blocking some classic snaps. Issue is 4 years old with no maintainer engagement. |
|
snapcraft (launchpad) issue #1995159 |
"upload" command sends progress to stdErr unnecessarily | ~knocte | 1414d | needs triage | 95 | 65 | Report that snapcraft upload sends progress messages to stderr instead of stdout, breaking CI automation that relies on stderr for important warnings. Untriaged, 1405 days old, no maintainer response. |
|
snapcraft (launchpad) issue #1995293 |
no uid/gid mappings when building on core22 with multipass | ~andreitoterman | 1411d | close stale | 95 | 60 | Multipass build with core22 mounts project directory without uid/gid mappings, causing ownership issues |
|
snapcraft (launchpad) issue #1637563 |
Add ability to automatically fetch Recommends from (a subset of) stage packages | ~3v1n0 | 3605d | needs triage | 95 | 55 | Feature request for a stage-packages-with-recommends flag so snap Recommends are auto-fetched from stage packages instead of listed manually. Open ~10 years with no labels, comments, or maintainer interaction. |
|
snapcraft (launchpad) issue #1995857 |
upload-metadata not working | ~merlijn-sebrechts | 1404d | close not a bug | 95 | 75 | upload-metadata command fails with unrecognized arguments; push-metadata works. Issue stems from command renaming and documentation inconsistency. |
|
snapcraft (launchpad) issue #1998340 |
Local pytest/unit run test_get_extensions_data_dir() fails | ~giusebar18 | 1381d | close stale | 95 | 70 | Local pytest test_get_extensions_data_dir() fails due to missing extensions data directory; workaround found but no maintainer engagement in 1373 days |
|
snapcraft (launchpad) issue #1640721 |
Feature Request: Would be nice to have a way to refresh .deb files | ~aacid | 3592d | close stale | 95 | 70 | Feature request to refresh only changed .deb files in a snap build instead of re-downloading the full ~300MB set. Open since 2017 with no labels, comments, or maintainer activity. |
|
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. |
|
snapcraft (launchpad) issue #2011719 |
snapcraft expand-extensions is broken | ~scarlettmoore | 1276d | close stale | 95 | 85 | snapcraft expand-extensions command produces invalid YAML with parse-info field error. Issue is ~3.5 years old with no activity. |
|
snapcraft (launchpad) issue #1640897 |
snapcraft doesn't validate gadget.yaml | ~elopio | 3592d | close stale | 95 | 55 | Feature request from 2015 asking snapcraft to validate gadget.yaml metadata for gadget snaps instead of just copying it. Open for nearly 10 years with no labels, comments, or maintainer activity. |
|
snapcraft (launchpad) issue #1655832 |
App name in snapcraft.yaml must match case of .desktop file | ~chris.macnaughton | 3529d | needs triage | 95 | 55 | Snapcraft breaks the .desktop file Exec line when the app name case in snapcraft.yaml mismatches the .desktop filename. Reported 2016, untriaged, no maintainer response, inactive 9 years. |
|
snapcraft (launchpad) issue #1594794 |
Embedded version required in snapcraft.yaml | ~stub | 3734d | close stale | 95 | 55 | Feature request from 2014 to let snapcraft.yaml's version key reference a part name so the version is derived from the plugin (e.g. Python setup.py) for Launchpad auto-builds. 10 years old, zero comments, no labels, no maintainer engagement; targets obsolete snapcraft 1.x. |
|
snapcraft (launchpad) issue #1948597 |
TypeError: load() missing 1 required positional argument: 'Loader' | ~kenneth-loafman | 1783d | close stale | 95 | 80 | Snapcraft 2.43.1 crashes during snap build with PyYAML TypeError (load() missing Loader) in internal/states/_state.py. No maintainer interaction for ~4.5 years; the affected code path no longer exists in the current codebase. |
|
snapcraft (launchpad) issue #2018456 |
Lack of support for ssh agent | ~suligap | 1226d | needs triage | 95 | 55 | Untriaged issue from 1218 days ago about snapcraft pull --bind-ssh getting stuck during git clone via SSH. No maintainer response or labels. |
|
snapcraft (launchpad) issue #1634038 |
Snapcraft should verify namespace before uploading | ~joetalbott | 3616d | close stale | 95 | 60 | Feature request from 2016 asking snapcraft to verify the user's namespace before uploading, to avoid expensive post-upload failures. Open for ~10 years with zero comments, no labels, and no maintainer interaction. |
|
snapcraft (launchpad) issue #2020348 |
Snapcraft tries to run chisel and fails | ~itrue | 1208d | close stale | 95 | 55 | Typo in stage-packages (missing $ before CRAFT_TARGET_ARCH) causes snapcraft to try running chisel instead of giving a clear syntax error. Unlabelled, no maintainer response, 1200 days old. |
|
snapcraft (launchpad) issue #1662932 |
history command shows duplicate channels | ~joetalbott | 3502d | close stale | 95 | 75 | 2017 report that snapcraft history prints duplicate channel names in its output table. No labels, comments, or maintainer response in ~9.5 years. The CLI and channel tracking have since been fully rewritten, so the old code path is gone. |
|
snapcraft (launchpad) issue #1631311 |
Add env configuration to baseplugin | ~stub | 3626d | close stale | 95 | 75 | Request to add env configuration to base plugin so environment variables can be set in yaml. Feature is already available via the part-level build-environment key in craft-parts, making this obsolete. |
|
snapcraft (launchpad) issue #1668555 |
Using organize to move a folder to a child folder fails due to recursion | ~jamesh | 3482d | needs triage | 95 | 40 | Snapcraft organize directive causes infinite recursion when moving a folder into its own child path (e.g. '.': lib/python3.6/site-packages). Workaround via glob ('*') documented in issue. 9+ years old, zero comments, no labels, never triaged. |
|
snapcraft (launchpad) issue #1596777 |
trying to upload a snap without signing the agreement prints the error twice | ~elopio | 3728d | needs triage | 95 | 55 | Snapcraft upload command prints the 'Developer has not signed agreement' error twice (once in red, once in green) when a user has not signed the store agreement. Suggests cleaning up output so Reason/Text only show with -d flag. Open since 2016 with no comments or maintainer response. |