Snapcraft python build fails to run with `GLIBC_2.25' not found error message
Metadata
Current evaluation
Snapcraft python plugin build on Ubuntu 17.10 fails at runtime with GLIBC_2.25 not found, a base/host glibc mismatch. 8+ years inactive, zero comments, no labels; EOL OS and obsolete snapcraft 2.34.
Suggested action: close stale
Reason: The issue is 3221 days old with 0 comments and no maintainer interaction, and it targets Ubuntu 17.10 (EOL since 2018) with snapcraft 2.34 — a version no longer supported by any current snapcraft release. The GLIBC_2.25 error is an environment/base mismatch on an unsupported host, not a reproducible bug in current code, so it is both inactive and no longer applicable.
Impact:
10
Quick Win:
8.0
Staleness:
95
Complexity:
20
Confidence:
75
Support Request:
80
Issue body
While starting snap build using snapcraft python plugin, following error message is displayed.
/snap/gestimator/x1/usr/bin/python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /snap/gestimator/x1/usr/bin/python3)
App git: https://github.com/manuvarkey/GEstimator.git
Ubuntu Version: 17.10 (64 bit) (Fully updated)
Kernel: 4.13.0-16-generic
Snapcraft version: 2.34
Snap Version: 2.28.5+17.10
Contents of yaml file is as below:
name: gestimator
version: 1.1.0
summary: GEstimator is a simple civil estimation software written in Python and GTK+
description: |
GEstimator is a simple civil estimation software written in Python and GTK+. GEstimator can prepare estimates along with rate analysis and supports multiple databases.
grade: devel
confinement: devmode
parts:
gestimator:
source: .
plugin: python
python-version: python3
after: []
apps:
gestimator:
command: bin/GEstimator.py
desktop: usr/share/applications/GEstimator.desktop
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
10
Quick Win:
8.0
Staleness:
95
Complexity:
20
Confidence:
75
Support Request:
80
|
close stale | Snapcraft python plugin build on Ubuntu 17.10 fails at runtime with GLIBC_2.25 not found, a base/host glibc mismatch. 8+ years inactive, zero comments, no labels; EOL OS and obsolete snapcraft 2.34. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
95
Support Request:
85
|
close stale | Snapcraft python build fails with GLIBC_2.25 error on Ubuntu 17.10. Unaddressed for 8+ years, referencing an EOL OS and outdated tool version. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
100
Complexity:
10
Confidence:
95
Support Request:
20
|
close stale | Snapcraft python build fails with GLIBC_2.25 error on Ubuntu 17.10. Issue is 8+ years old, uses obsolete OS and snapcraft version, and is no longer reproducible. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
10
Confidence:
95
Support Request:
20
|
close stale | Snapcraft python plugin build fails due to missing GLIBC_2.25 on Ubuntu 17.10 with Snapcraft 2.34. Issue is over 8 years old with no maintainer interaction. | |
| qwen3.6-35b-moe-q4 |
Staleness:
99
Complexity:
15
Confidence:
95
Support Request:
40
|
close stale | Snapcraft python plugin build fails with GLIBC_2.25 missing on Ubuntu 17.10. Unaddressed for over 8 years on an EOL OS and outdated snapcraft version. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2085813 snapcraft not installable | snapcraft (launchpad) | closed | Abandoned and closed due to a GLIBC_2.38 runtime incompatibility during installation. No resolution or fix was provided. | |
| #2099923 Snapcraft builds are failing: install of snap "snapcraft" failed | snapcraft (launchpad) | open | 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. | |
| #1626236 snapcraft newly fails on ubuntu-image | snapcraft (launchpad) | open | snapcraft 2.17 on Ubuntu 16.10 (Yakkety) fails to copy the ubuntu-image CLI script to prime/usr/bin, causing a FileNotFoundError during build. No maintainer activity in ~10 years; affected versions are long EOL and the codebase has been fully restructured since. |