hitchhiker(1) [debian man page]
hitchhiker(1) 2012-06-15 hitchhiker(1) NAME
hitchhiker - Access locations using Bazaar transports SYNOPSIS
hitchhiker [URL] [COMMAND] [ARGS] OPTIONS
None. DESCRIPTION
A client to access bzr transports, namely the Bazaar version control repositories. This utility can be used to log into the remote host and manipulate Bazaar repositoy content like it were a FTP, SFTP client. Command include cp, mv, rmtree etc. Use Case: command 'bzr upgrade <URL> <repository format options>' is run and after the process is over the backup.bzr needs to be removed. With this tool the task is easy. If no COMMAND is supplied, interactive mode is launched. If no URL is supplied, in interactive mode, the "open" command should be used to connect to a location. EXAMPLES
COMMAND LINE USE To run command, like help non-interactively, use URL, e.g. current directory: hitchhiker . help Without options, the command line client starts in interactive mode: hitchhiker (Cmd) <cursor here> Try command help for list of possibilities (Cmd) help at cd connect-and-wait edit exit get help info ls lsl mirror mkdir open put rename rm rmtree Further help is provided for each command: (Cmd) help open Usage: open LOCATION Open a new location. The location may be any URL supported by Bazaar. (Cmd) exit USE CASES Upgrade a remote Bazaar baranch at http://launchpad.net Bazaar and remove the backup bzr upgrade lp:~user/+brach/name --2a hitchhiker lp:~user/+brach/name rmtree backup.bzr ENVIRONMENT
None. FILES
None. SEE ALSO
bzr(1) sftp(1) AUTHORS
Program was written by Aaron Bentley <aaron.bentley@canonical.com>. This manual page was written by Jari Aalto <jari.aalto@cante.net>, for the Debian GNU system (but may be used by others). Updated by Jari Aalto <jari.aalto@cante.net>. Released under license GNU GPL v2 or (at your option) any later version. For more information about license, visit <http://www.gnu.org/copyleft/gpl.html>. hitchhiker 2012-06-15 hitchhiker(1)
Check Out this Related Man Page
Config::Model::models::Debian::Dpkg::Control::Source(3pmUser Contributed Perl DocumentatiConfig::Model::models::Debian::Dpkg::Control::Source(3pm) NAME
Config::Model::models::Debian::Dpkg::Control::Source - Configuration class Debian::Dpkg::Control::Source VERSION
version 2.021 DESCRIPTION
Configuration classes used by Config::Model Elements Source - source package name Mandatory. Type uniline. Maintainer - package maintainer's name and email address The package maintainer's name and email address. The name must come first, then the email address inside angle brackets <> (in RFC822 format). If the maintainer's name contains a full stop then the whole field will not work directly as an email address due to a misfeature in the syntax specified in RFC822; a program using this field as an address must check for this and correct the problem if necessary (for example by putting the name in round brackets and moving it to the end, and bringing the email address forward). Mandatory. Type uniline. Uploaders Optional. Type list of uniline. Section The packages in the archive areas main, contrib and non-free are grouped further into sections to simplify handling. The archive area and section for each package should be specified in the package's Section control record (see Section 5.6.5 <http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Section>). However, the maintainer of the Debian archive may override this selection to ensure the consistency of the Debian distribution. The Section field should be of the form: o section if the package is in the main archive area, o area/section if the package is in the contrib or non-free archive areas. Optional. Type uniline. Priority Optional. Type enum. choice: 'required', 'important', 'standard', 'optional', 'extra'. Here are some explanations on the possible values: 'extra' This contains all packages that conflict with others with required, important, standard or optional priorities, or are only likely to be useful if you already know what they are or have specialized requirements (such as packages containing only detached debugging symbols). 'important' Important programs, including those which one would expect to find on any Unix-like system. If the expectation is that an experienced Unix person who found it missing would say "What on earth is going on, where is foo?", it must be an important package.[5] Other packages without which the system will not run well or be usable must also have priority important. This does not include Emacs, the X Window System, TeX or any other large applications. The important packages are just a bare minimum of commonly-expected and necessary tools. 'optional' (In a sense everything that isn't required is optional, but that's not what is meant here.) This is all the software that you might reasonably want to install if you didn't know what it was and don't have specialized requirements. This is a much larger system and includes the X Window System, a full TeX distribution, and many applications. Note that optional packages should not conflict with each other. 'required' Packages which are necessary for the proper functioning of the system (usually, this means that dpkg functionality depends on these packages). Removing a required package may cause your system to become totally broken and you may not even be able to use dpkg to put things back, so only do so if you know what you are doing. Systems with only the required packages are probably unusable, but they do have enough functionality to allow the sysadmin to boot and install more software. 'standard' These packages provide a reasonably small but not too limited character-mode system. This is what will be installed by default if the user doesn't select anything else. It doesn't include many large applications. Build-Depends Optional. Type list of uniline. Build-Depends-Indep Optional. Type list of uniline. Build-Conflicts Optional. Type list of uniline. Standards-Version - Debian policy version number this package complies to This field indicates the debian policy version number this package complies to. Optional. Type uniline. default: '3.9.3'. Vcs-Browser - web-browsable URL of the VCS repository Value of this field should be a http:// URL pointing to a web-browsable copy of the Version Control System repository used to maintain the given package, if available. The information is meant to be useful for the final user, willing to browse the latest work done on the package (e.g. when looking for the patch fixing a bug tagged as pending in the bug tracking system). Optional. Type uniline. Vcs-Arch - URL of the VCS repository Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. Optional. Type uniline. Vcs-Bzr - URL of the VCS repository Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. Optional. Type uniline. Vcs-Cvs - URL of the VCS repository Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. Optional. Type uniline. Vcs-Darcs - URL of the VCS repository Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. Optional. Type uniline. Vcs-Git - URL of the VCS repository Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. Optional. Type uniline. Vcs-Hg - URL of the VCS repository Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. Optional. Type uniline. Vcs-Mtn - URL of the VCS repository Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. Optional. Type uniline. Vcs-Svn - URL of the VCS repository Value of this field should be a string identifying unequivocally the location of the Version Control System repository used to maintain the given package, if available. * identify the Version Control System; currently the following systems are supported by the package tracking system: arch, bzr (Bazaar), cvs, darcs, git, hg (Mercurial), mtn (Monotone), svn (Subversion). It is allowed to specify different VCS fields for the same package: they will all be shown in the PTS web interface. The information is meant to be useful for a user knowledgeable in the given Version Control System and willing to build the current version of a package from the VCS sources. Other uses of this information might include automatic building of the latest VCS version of the given package. To this end the location pointed to by the field should better be version agnostic and point to the main branch (for VCSs supporting such a concept). Also, the location pointed to should be accessible to the final user; fulfilling this requirement might imply pointing to an anonymous access of the repository instead of pointing to an SSH-accessible version of the same. Optional. Type uniline. DM-Upload-Allowed - The package may be uploaded by a Debian Maintainer If this field is present, then any Debian Maintainers listed in the Maintainer or Uploaders fields may upload the package directly to the Debian archive. For more information see the "Debian Maintainer" page at the Debian Wiki - http://wiki.debian.org/DebianMaintainer. Optional. Type uniline. Homepage Optional. Type uniline. XS-Python-Version Deprecated Optional. Type uniline. X-Python-Version - supported versions of Python This field specifies the versions of Python (not versions of Python 3) supported by the source package. When not specified, they default to all currently supported Python (or Python 3) versions. For more detail, See python policy <http://www.debian.org/doc/packaging- manuals/python-policy/ch-module_packages.html#s-specifying_versions>Optional. Type uniline. upstream_default: 'all'. Note: X-Python-Version is migrated with my $old = $xspython ; my $new ; if ($old =~ /,/) { # list of versions my @list = sort split /s*,s*/, $old ; $new = ">= ". (shift @list) . ", << " . (pop @list) ; } elsif ($old =~ /-/) { my @list = sort grep { $_ ;} split /s*-s*/, $old ; $new = ">= ". shift @list ; $new .= ", << ". pop @list if @list ; } else { $new = $old ; } $new ; and with $xspython => ""- XS-Python-Version"" X-Python3-Version - supported versions of Python3 This field specifies the versions of Python 3 supported by the package. For more detail, See python policy <http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-specifying_versions>Optional. Type uniline. SEE ALSO
o cme AUTHOR
Dominique Dumont COPYRIGHT
2010,2011 Dominique Dumont LICENSE
LGPL2 perl v5.14.2 2012-11-09 Config::Model::models::Debian::Dpkg::Control::Source(3pm)