← Back to issue list

autotools.configflags enforces uniqueness

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1694707
Type
issue
State
closed
Author
~saviq
Labels
bitesize plugin
Created
Updated
Closed

Current evaluation

Closed without resolution. The autotools plugin configflags property enforces uniqueness, blocking duplicate -skip arguments. No comments or fixes were provided, indicating abandonment.

Suggested action: —

No scores available.

Issue body

Trying out the 'qt58' part, snapcraft complains: $ snapcraft Issue while loading plugin: properties failed to load for qt58: The 'configflags' property does not match the required schema: [...] has non-unique elements The reason for this is that the part tries to pass multiple -skip arguments1, which should be followed by a module name. This is impossible today, as snapcraft seems to require the configlags property to have unique entries. Should snapcraft really impose that restriction? Coming from the forum: https://forum.snapcraft.io/t/configflags-has-non-unique-elements/726

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b — — Closed without resolution. The autotools plugin configflags property enforces uniqueness, blocking duplicate -skip arguments. No comments or fixes were provided, indicating abandonment.
qwen/qwen3.6-35b-a3b — — The uniqueness validation for configflags was removed to allow duplicate entries, resolving build failures for plugins requiring repeated flags.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1337 autotools: don't force uniqueness on configflags snapcraft merged Merged to stop forcing uniqueness on autotools configflags, resolving Launchpad bug #1694707. Approved by two reviewers, the change modifies two files with a net reduction of three lines.
82%
#3066 autotools v2 plugin: rename configflags to autotools-configure-parame… snapcraft merged Merged a maintainer change renaming configflags to autotools-configure-parameters in the autotools v2 plugin. This correctly namespaces the property to eliminate ambiguity. All checks passed and the code was integrated.
71%