Bzr Error No Such Tag Upstream
dailydeb it fails while the same recipe is working when building on launchpad. the recipe is: https://code.launchpad.net/~hannes-janetzek/+recipe/expedite-svn bzr: ERROR: unknown command "--verbose" jeff@rappelkiste:/opt/testing% bzr dailydeb --verbose expedite.recipe Building tree. Retrieving 'lp:~hannes-janetzek/enlightenment-svn/expedite' to put at '/tmp/bzr-builder-YY3tKV/expedite-201109191120-{revno}'. All changes applied successfully. Committing to: /tmp/bzr-builder-YY3tKV/expedite-201109191120-{revno}/ added debian added debian/changelog added debian/compat added debian/control added debian/copyright added debian/rules Committed revision 230. bzr: ERROR: No such tag: upstream-201109191120 - Stage 5/5 Question information Language: English Edit question Status: Solved For: bzr-builder Edit question Assignee: Jelmer Vernooij Edit question Solved by: hjanetzek Solved: 2011-09-20 Last query: 2011-09-20 Last reply: 2011-09-19 Related bugs Link existing bug Related FAQ: None Link to a FAQ Jelmer Vernooij (jelmer) said on 2011-09-19: #1 You are trying to build a non-native package but your branch doesn't contain a tag for the upstream tarball. bzr-builder needs this tag so it can create an .orig.tar.gz file. You should either: * create a tag for the upstream version named upstream-201109191120 * change the package to be a native package * allow bzr-builder to make the package a native package by building with --allow-fallback-to-native. hjanetzek (hannes-janetzek) said on 2011-09-20: #2 The third option worked. I'll check the other when needed :) Thank You! History Link existing bug Create bug report Link to a FAQ Create a new FAQ To post a message you must log in. Ask a question Edit question Subscribers Subscribe Subscribe someone else • Take the tour • Read the guide © 2004-2016 CanonicalLtd. • Terms of use • Contact Launchpad Support • Blog • Careers • System status • r18217 (Get the code!)
tags. -v, --verbose Display more information. -h, --help Show help message. -q, --quiet Only display errors and warnings. -d ARG, --directory=ARG Branch in which to place the tag. --usage Show usage message and options. -r ARG, --revision=ARG See "help revisionspec" for details. --delete Delete this tag rather than placing it. Description:Tags give human-meaningful names to revisions. Commands https://answers.launchpad.net/bzr-builder/+question/171624 that take a -r (-revision) option can be given -rtag:X, where X is any previously created tag. Tags are stored in the branch. Tags are copied from one branch to another along when you branch, push, pull or merge. It is an error to give http://doc.bazaar.canonical.com/beta/en/user-reference/tag-help.html a tag name that already exists unless you pass -force, in which case the tag is moved to point to the new revision. To rename a tag (change the name but keep it on the same revsion), run bzr tag new-name -r tag:old-name and then bzr tag --delete oldname. If no tag name is specified it will be determined through the ‘automatic_tag_name' hook. This can e.g. be used to automatically tag upstream releases by reading configure.ac. See bzr help hooks for details. See also:commit, tags Previous topic switch Next topic tags This Page Show Source Quick search Enter search terms or a module, class or function name. Navigation next previous | Home| Documentation| Table of Contents (2.8.0dev1) » Bazaar User Reference » © Copyright 2009-2011 Canonical Ltd. Created using Sphinx 1.1.3.
Global Options Revision Identifiers Standard Options Status Flags URL Identifiers Commands add annotate bind branch break-lock cat check checkout commit conflicts deleted diff export help ignore ignored info http://doc.bazaar.canonical.com/bzr.1.0/en/user-reference/bzr_man.html init init-repository log ls merge missing mkdir mv nick pack plugins http://wiki.bazaar.canonical.com/FAQ pull push reconcile reconfigure remerge remove remove-tree renames resolve revert revno root send serve sign-my-commits status switch tag tags testament unbind uncommit update upgrade version version-info whoami About This Manual This manual is generated from Bazaar's online help. To use the online help system, try bzr error the following commands. Introduction including a list of commonly used commands: bzr help List of topics and a summary of each: bzr help topics List of commands and a summary of each: bzr help commands More information about a particular topic or command: bzr help topic-or-command-name The following web sites provide further information on Bazaar: bzr error no Home page:http://www.bazaar-vcs.org/ Official docs:http://doc.bazaar-vcs.org/ Launchpad:https://launchpad.net/bzr/ Concepts Branches A branch consists of the state of a project, including all of its history. All branches have a repository associated (which is where the branch history is stored), but multiple branches may share the same repository (a shared repository). Branches can be copied and merged. Related commands: init Make a directory into a versioned branch. branch Create a new copy of a branch. merge Perform a three-way merge. Checkouts Checkouts are source trees that are connected to a branch, so that when you commit in the source tree, the commit goes into that branch. They allow you to use a simpler, more centralized workflow, ignoring some of Bazaar's decentralized features until you want them. Using checkouts with shared repositories is very similar to working with SVN or CVS, but doesn't have the same restrictions. And using checkouts still allows others working on the project to use whatever workflow they like. A checkout is created with the bzr checkout
Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow Search Bazaar Also see the "Questions for Bazaar" page on Launchpad for more answers to frequently asked questions. <