mentions new substitution variables even when recipe format doesn't support them

Bug #891880 reported by Jelmer Vernooij
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
bzr-builder
Fix Released
Medium
Jelmer Vernooij

Bug Description

users who specify "0.3" as the recipe format in their recipe, get an error saying it is not available. ... and then the list of possible options *does* include it:

gwenhwyvar:/tmp% bzr dailydeb bzr-svn.recipe
bzr: ERROR: deb-version not fully expanded: {latest-tag}. Valid substitutions are: ['{time}', '{date}', '{revno:package}', '{revno}', '{svn-revno:package}', '{svn-revno}', '{git-commit:package}', '{git-commit}', '{latest-tag:package}', '{latest-tag}', '{debversion:package}', '{debversion}', '{debupstream-base:package}', '{debupstream-base}', '{debupstream:package}', '{debupstream}', '{revdate:package}', '{revdate}', '{revtime:package}', '{revtime}']

bzr-builder should mention if the user is not using the latest version, and should only list the subsitutions available in the *current* version.

Related branches

Jelmer Vernooij (jelmer)
Changed in bzr:
assignee: nobody → Jelmer Vernooij (jelmer)
Jelmer Vernooij (jelmer)
affects: bzr → bzr-builder
Jelmer Vernooij (jelmer)
Changed in bzr-builder:
status: Triaged → In Progress
Jelmer Vernooij (jelmer)
Changed in bzr-builder:
status: In Progress → Fix Committed
milestone: none → 0.8
Jelmer Vernooij (jelmer)
Changed in bzr-builder:
status: Fix Committed → Fix Released
milestone: 0.8 → 0.7.3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.