TITO(8)

πŸ“¦
version 0.6.28 Β· 3 versions
, in epel 9, fedora 43, fedora 44

πŸ’– TITO(8) β€” the tito girlies' guide πŸ’–

okay so bestie, welcome to the tito manual page (section 8, system administration, we're fancy like that ✨). this is the Tito User Manual and it's about to become your whole personality. grab a boba, we're doing this πŸ§‹


✨ NAME ✨

tito β€” manage RPM based projects using git πŸ’…


🌸 SYNOPSIS 🌸

tito init

tito tag [OPTIONS]

tito build --test --rpm

tito build [OPTIONS]

tito release [OPTIONS] TARGET

tito report

πŸ¦‹ DESCRIPTION πŸ¦‹

so first you set up a directory as a Git repo, and then you use tito to manage the tags and builds. no cap, that's the whole vibe. a simple workflow lowkey looks like this:

  1. Save user preferences as described in titorc(5)
  2. Initialize a .tito directory
  3. Test
    1. Make changes to source
    2. Use git to commit changes
    3. Build: tito build --rpm --test
  4. Finalize a release
    1. Tag: tito tag
    2. Push: git push && git push $ORIGIN $TAG
    3. Build: tito build [OPTIONS]

πŸ‘‘ OPTIONS πŸ‘‘

πŸŽ€ tito init πŸŽ€

this creates a top-level metadata directory called .tito/ and commits it to git. this directory stores tito's configuration and package metadata on a per branch basis. it gets filtered out when you're creating .tar.gz's, so it won't sneak into your tarballs like an uninvited ex πŸ™ˆ

Note πŸ“ your spec file should list the source as %{name}-%{version}.tar.gz

🧚 tito tag [options] 🧚

by default, tito will tag by bumping the rpm version (i.e. we bump the Z in X.Y.Z, iconic behavior honestly). if you'd prefer to bump the package release instead (which normally should just be used for changes to the spec file or patches applied within it), you can change the tagger class in .tito/tito.props to ReleaseTagger. this will affect all packages in this git branch β€” the way that it's a whole-branch decision, not a per-package one 😭. but if you'd prefer to do this on a per-package basis you can do so in a package specific tito.props.

if you work in a OBS style git with a separate .changes file for the changelog, change the tagger class to tito.susetagger.SUSETagger. the SUSETagger is based on the VersionTagger. slay 🫢

  • -h, --help β€” show this help message and exit
  • --debug β€” print debug messages (can be also set using DEBUG environment variable)
  • --offline β€” do not attempt any remote communication (avoid using this please πŸ™)
  • -o OUTPUTDIR, --output=OUTPUTDIR β€” Write temp files, tarballs, and RPMs to OUTPUTDIR. Create sub-directories as needed by rpmbuild(8). (default /tmp/tito)
  • --tag-release β€” Deprecated, no longer required. πŸ’€ she's retired, respect her legacy
  • --keep-version β€” Use spec file version/release exactly as specified in spec file to tag package.
  • --use-version=USE_VERSION β€” Update the spec file with the specified version.
  • --use-release=USE_RELEASE β€” Update the spec file with the specified release.
  • --no-auto-changelog β€” Don't automatically create a changelog entry for this tag if none is found
  • --accept-auto-changelog β€” Automatically accept the generated changelog.
  • --auto-changelog-message=MESSAGE β€” Use MESSAGE as the default changelog message for new packages
  • --changelog=MESSAGE β€” Use MESSAGE as the changelog when tagging, this can be specified every time a package is tagged. Useful when needing to generate custom changelogs. This will override the auto generated changelog.
  • -u, --undo β€” Undo the most recent (un-pushed) tag. take-backsies are valid ✨
Note πŸ“ Tito will create automatic changelog from git commits. Unless you specify one of auto options, tito will open text editor and allow you to edit the text. Editor is by default. This can be changes by environment variable EDITOR.

🌈 tito build [options] 🌈

  • -h, --help β€” show this help message and exit
  • --debug β€” print debug messages (can be also set using DEBUG environment variable)
  • --offline β€” do not attempt any remote communication. Avoid using this please. See OFFLINE section below.
  • -o OUTPUTDIR, --output=OUTPUTDIR β€” Write temp files, tarballs and RPMs to OUTPUTDIR. (default /tmp/tito)
  • --tgz β€” Build .tar.gz
  • --srpm β€” Build srpm
  • --rpm β€” Build srpm and rpm
  • -i, --install β€” Install any binary RPMs being built.
Warning 🚨 uses sudo rpm -Uvh --force
  • --no-sudo β€” Don't escalate privileges when installing. Use when running this command with required privileges.
  • --dist=DISTTAG β€” Apply DISTTAG to srpm and/or rpm. (e.g., ".el5")
  • --test β€” use current branch HEAD instead of latest package tag.
  • --no-cleanup β€” do not clean up temporary build directories/files
  • --rpmbuild-options=OPTIONS β€” Pass OPTIONS to rpmbuild.
  • --builder=BUILDER β€” Override the normal builder by specifying a full class path or one of the pre-configured shortcuts. Only useful if you need to override the default builder for some purpose, such as testing a build via mock.
  • --arg=BUILDER_ARGS β€” Custom arguments specific to a particular builder. (key=value)
  • --scl=COLLECTION β€” Build package for software collection. This is mostly useful for building src.rpm, because for rpm you want to define this option for specific tag in tito.props
  • --quiet β€” Suppress output from the build process.
  • --verbose β€” Expose more output from the build process.

πŸ’œ tito release [options] TARGETS πŸ’œ

runs the release targets defined in .tito/releasers.conf. let's goooo πŸ”₯

  • -h, --help β€” show this help message and exit
  • --debug β€” print debug messages (can be also set using DEBUG environment variable)
  • --offline β€” do not attempt any remote communication. Avoid using this please. See OFFLINE section below.
  • -o OUTPUTDIR, --output=OUTPUTDIR β€” Write temp files, tarballs and RPMs to OUTPUTDIR. (default /tmp/tito)
  • --tag=PKGTAG β€” build a specific tag instead of the latest version (e.g., spacewalk-java-0.4.0-1)
  • --dry-run β€” Do not actually commit/push anything during release. pretend mode, we love her πŸŽ€
  • --no-build β€” Do not perform a brew/koji build, only DistGit commit. (only for Koji/DistGit releasers)
  • --all β€” Run all release targets defined in .tito/releasers.conf.
  • --list β€” List all release targets defined in .tito/releasers.conf.
  • --all-starting-with=ALL_STARTING_WITH β€” Run all release targets starting with the given string. (i.e. if you have defined release targets yum-f15 and yum-f14 in releasers.conf, --all-starting-with=yum will run only these targets, and ignore any others.)
  • --scratch β€” Perform a scratch build in Koji. Can be specified using environment variable SCRATCH set to 1 as well.
  • --yes β€” Do not ask to confirm release commits or edit their messages.

⭐ tito report [options] ⭐

displays a report of all packages with differences between HEAD and their most recent tag, as well as a patch for that diff. used to determine which packages are in need of a rebuild. it's giving detective energy πŸ”

  • -h, --help β€” show this help message and exit
  • --debug β€” print debug messages (can be also set using DEBUG environment variable)
  • --offline β€” do not attempt any remote communication. Avoid using this please. See OFFLINE section below.
  • -o OUTPUTDIR, --output=OUTPUTDIR β€” Write temp files, tarballs and RPMs to OUTPUTDIR. (default /tmp/tito)
  • --untagged-diffs β€” Print out diffs for all packages with changes between their most recent tag and HEAD. Useful for determining which packages are in need of a re-tag.
  • --untagged-commits β€” Print out the list for all packages with changes between their most recent tag and HEAD. Useful for determining which packages are in need of a re-tag.

πŸ’€ OFFLINE πŸ’€

Offline lets you potentially do builds you can't reproduce β€” normally we check that the tag you're building exists in the remote repo. If it hasn't been pushed, it's quite easy to do a build that will result in a checksum that is no longer the same. This is something you should try to avoid.

fr fr, don't do the offline thing unless you have to. unreproducible builds are not the vibe 😭

πŸ“ EXAMPLES πŸ“

Build and install a test package from the latest code in current git HEAD

tito build --rpm --test -i

Overriding the default builder to build via mock instead

tito build --builder mock --arg mock=fedora-15-x86_64 --rpm

πŸ”₯ SEE ALSO πŸ”₯

titorc(5) releasers.conf(5) tito.props(5)

/usr/share/doc/tito-*/README.mkd


🌟 AUTHORS 🌟

these absolute legends πŸ‘‘

  • Devan Goodwin <dgoodwin@rm-rf.ca>
  • James Bowes <jbowes@repl.ca>
  • Jan Pazdziora
  • Jesus M Rodriguez <jesusr@redhat.com>
  • Pall Sigurdsson <palli@opensource.is>
  • Miroslav SuchΓ½ <msuchy@redhat.com>

and: Adam Miller, Alex Wood, Aron Parsons, Brenton Leanhardt, Ivan Nečas, John Eckersberg, Kenny MacDermid, LukÑő Zapletal, Luke Meyer, Marian Csontos, Martin Bačovský, Michael Stead, Mike McCune, mscherer, Paul Morgan, Sean P. Kane, Steve Ashcrow Milner


and that's the whole page bestie, we ate and left no crumbs πŸ’…βœ¨

<cute>this was tito, from the Tito User Manual, dated 08/26/2026, living in section TITO(8) β€” ok bye ily, go tag something πŸŽ€πŸ¦‹</cute>

πŸ“¦ where this page comes from