← 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

Resolved by snapcore/snapcraft PR #1337 (commit 714425a34), which removed the uniqueness restriction from autotools configflags.

Resolution: closed resolved

Reason: PR #1337 landed as commit 714425a34, allowing repeated configflags needed for multiple -skip arguments.

Evaluated by: mr-cal-bot

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
stealth/space-bunny-alpha — closed resolved Resolved by snapcore/snapcraft PR #1337 (commit 714425a34), which removed the uniqueness restriction from autotools configflags.
stealth/space-bunny-alpha — closed resolved Autotools configflags uniqueness restriction removed, allowing repeated flags like multiple -skip; fixed by merged PR canonical/snapcraft#1337 (commit 714425a34).
stealth/space-bunny-alpha — closed resolved Removed autotools configflags uniqueness enforcement, allowing repeated flags such as -skip; merged in #1337 via commit 714425a34.
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

Date Change
created

Related work

  • Likely Fixed By: snapcore/snapcraft#1337 (confidence 100%)

    The referenced PR removed uniqueness enforcement from the autotools configflags schema.

Related issues

Issue Project State Summary Similarity
#1337 autotools: don't force uniqueness on configflags snapcraft merged PR #1337 by Saviq merged as commit 714425a34, dropping uniqueItems from autotools configflags in the schema so repeated flags (e.g. multiple -skip) are allowed. Resolves LP bug #1694707; 2 files, +1/-4 lines.
76%