← Back to issue list

plugin:meson is not installed during pull stage

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1957766
Type
issue
State
open
Author
~xnox
Labels
—
Created
Updated
Closed
—

Current evaluation

Snapcraft 6.0.1 Meson-part builds reportedly fetch Meson during build after the proxy expires; the issue remains open with no labels, comments, or triage.

Suggested action: needs triage

Reason: The report identifies a concrete Snapcraft 6.0.1 build-for failure where Meson is accessed during build after a four-hour proxy timeout, but the issue has zero comments, labels, or maintainer response. Current craft-parts documentation says the Meson plugin does not install Meson by default and expects it through build-packages, build-snaps, or another part; the missing recipe and logs require triage to determine whether this is configuration usage or a requested plugin change.

Evaluated by: mr-cal-bot

Impact: 45 Quick Win: 13 Complexity: 45 Confidence: 78 Actionability: 52

Issue body

plugin:meson is not installed during pull stage using snapcraft 6.0.1 which does pull before build, i manage to complete the pull stage if i skip qemu pull However, the build then fails, because during build stage `plugin:meson` parts try to connect to the internet to install meson, which by that point proxy times out as it has been 4 hours. I would have hoped that meson for parts with plugin:meson would be cached during pull step.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 45
Quick Win: 13
Complexity: 45
Confidence: 78
Actionability: 52
needs triage Snapcraft 6.0.1 Meson-part builds reportedly fetch Meson during build after the proxy expires; the issue remains open with no labels, comments, or triage.
stealth/space-bunny-alpha
Impact: 48
Quick Win: 16
Complexity: 50
Confidence: 90
Actionability: 66
needs triage Snapcraft 6.0.1's Meson plugin reportedly downloads Meson during build instead of pull, breaking build-for workflows after the proxy expires. The issue is open, unlabeled and untriaged.
qwen/qwen3.8-27b
Impact: 40
Quick Win: 18
Staleness: 95
Complexity: 55
Confidence: 55
Support Request: 15
needs triage 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.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 35
Confidence: 85
Support Request: 10
close stale Bug report regarding meson plugin not being cached during the pull stage in snapcraft v6.0.1, causing build timeouts. Issue is over 4.5 years old with no maintainer engagement.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 45
Confidence: 85
Support Request: 10
close stale Report about meson plugin not being cached during pull stage in Snapcraft 6.0.1, causing build failures. Issue is over 4.5 years old with no activity or maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 30
Confidence: 85
Support Request: 20
close stale Unlabelled report from over four years ago stating plugin:meson is not cached during the pull stage in snapcraft 6.0.1, causing proxy timeouts during build. Zero maintainer comments or activity.

Update history

Date Change
created

Related issues

Issue Project State Summary Similarity
#1982761 Meson plugin fails in snapcraft version 7.1.0 snapcraft (launchpad) closed Meson was not auto-installed; no fix was merged, and the report was closed as expired after 60 days of inactivity.
77%
#1753250 meson version out of date snapcraft (launchpad) open Snapcraft 3.x meson plugin installed meson 0.29, lacking gettext/gschemas/resources support (mesonbuild.modules.i18n ImportError). Current craft-parts MesonPlugin no longer installs/pins meson.
73%
#1766101 Snapcraft not handling cmake nested builds, not including build script files in snap, and dependency issues with meson builds snapcraft (launchpad) open Old, untriaged report bundles three FeedReader failures: nested CMake, override-build staging, and Meson runtime ABI mismatches. No maintainer assessment or current reproducer exists.
70%