← Back to issue list

"version: git" can produce version strings too long for snapd

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1812633
Type
issue
State
closed
Author
~dholbach
Labels
Created
Updated
Closed

Current evaluation

The version: git feature was deprecated in favor of craftctl set version=... to prevent excessively long version strings exceeding snapd's 32-character limit. Users should use version-script: or the new control command instead.

Suggested action:

No scores available.

Issue body

The following snapcraft.yaml (to go into the github.com/weaveworks/flux tree): name: fluxctl version: git summary: fluxctl talks to Weave Flux and helps you deploy your code description: | fluxctl talks to your Weave Flux instance and exposes all its functionality to an easy to use command line interface. grade: devel # must be 'stable' to release into candidate/stable channels confinement: strict plugs: system-files: read: [/etc/kube/config] personal-files: read: - $HOME/.kube/config - $HOME/.minikube/client.key - $HOME/.minikube/client.crt - $HOME/.minikube/ca.crt parts: fluxctl: plugin: go go-importpath: github.com/weaveworks/flux prime: - bin/fluxctl apps: fluxctl: command: fluxctl plugs: [system-files, personal-files, network, network-bind] snapd gives: [daniel@reef flux ]$ snap install --dangerous fluxctl_chart-0.2.1+git664.3a0e5b88-dirty_amd64.snap Fehler: cannot read snap file: invalid snap version "chart-0.2.1+git664.3a0e5b88-dirty": cannot be longer than 32 characters (got: 33) [daniel@reef flux ]$

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b The version: git feature was deprecated in favor of craftctl set version=... to prevent excessively long version strings exceeding snapd's 32-character limit. Users should use version-script: or the new control command instead.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 15
Confidence: 85
Support Request: 5
close stale Using version: git in snapcraft.yaml generates strings exceeding snapd's 32-character limit, causing install failures. No maintainer response or updates in over 7 years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 15
Confidence: 90
Support Request: 10
close stale Reports that snapcraft version git generates version strings exceeding snapd 32-character limit, causing installation failures. Unaddressed for over seven years with no maintainer interaction.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 15
Confidence: 85
Support Request: 10
close stale Snapcraft version git generates version strings exceeding snapd's 32-character limit. Unlabeled, unassigned, and inactive for over 7 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 20
Confidence: 75
Support Request: 5
close stale Reports that snapcraft's "version: git" generates version strings exceeding snapd's 32-character limit. The issue is over seven years old with no maintainer response or comments.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1849935 Generated 'git describe' based version strings can exceed 32 character version limit snapcraft (launchpad) open 2018 bug report: version: git can generate git-describe strings exceeding snapcraft's 32-character limit (e.g. 38 chars). No maintainer activity in ~6.7 years. The version: git feature has since been deprecated in favor of version-script/craftctl set version.
82%
#1695251 'git' version not expanded in version-script snapcraft (launchpad) open Request to expand 'git' version before running version-script so SNAPCRAFT_PROJECT_VERSION holds the real version. version-script is deprecated/removed in current snapcraft (only docs reference remains), so the feature no longer exists.
77%
#1769519 Setting the snapcraft.yaml version field to 'git' produces undocumented and broken magic snapcraft (launchpad) open 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.
73%