pristine-lfs - store pristine tarballs in Git LFS

Author

       Andrej Shadura <andrew.shadura@collabora.co.uk>

20210222.0                                         2021-02-22                                    PRISTINE-LFS(1)

Commands

pristine-lfscommit[-bBRANCH][-mMESSAGE][--force-overwrite]tarball[upstream]pristine-lfscommit stores the specified tarball using Git LFS, and commits its metadata to
version control. The pristine-lfscheckout command can later be used to recreate the original
tarball based on the information stored in Git LFS. The data are not submitted to the server until
gitpush command is issued.

The upstream parameter is ignored and is supported for compatibility with pristine-tar.

If tarball with a different hash has already been committed, it will only be overwritten if
--force-overwrite is specified.

pristine-lfsimport-dsc[-bBRANCH][-mMESSAGE][--force-overwrite][--full]path-to-dsc
Import tarballs and their signatures from a .dsc file of a Debian source package.

If --full is specified, also imports the Debian packaging and the .dsc file itself.

If tarball with a different hash has already been committed, it will only be overwritten if
--force-overwrite is specified.

pristine-lfscheckout[-bBRANCH][-ooutdir][--full](--auto|tarball)
Regenerate a copy of the specified tarball using information previously saved in version control
by pristine-lfscommit.

By default, the tarball is placed in the current directory. If outdir is specified, the file is
created in that directory.

For compatibility with pristine-tar, tarball can include the path to the output directory; this
takes precedence over the outdir option.

If --auto is specified, pristine-lfs will consult a file named debian/changelog, and if it exists,
will check out all tarballs associated with the latest version the changelog mentions.

If --full is specified and a .dsc file is requested, also checks the Debian packaging and the .dsc
file itself.

pristine-lfslist[-bBRANCH]
List tarballs that pristine-lfs is able to checkout from version control.

pristine-lfsverify[-bBRANCH]tarball
Verify whether an existing tarball matches the one that has been committed to version control.

Description

       pristine-lfs  can  store  pristine  upstream  tarballs  in Git leveraging Git LFS. Instead of storing the
       potentially large tarballs within the Git repository as blobs, Git LFS  only  stores  specially  prepared
       metadata in the repository, while storing the actual file contents out of band on a Git LFS server.

       Using  pristine-lfs allows Debian packages to be built entirely using sources in version control, without
       the need to keep copies of upstream tarballs.

       pristine-lfs supports tarballs compressed with any compressor.

       Tarball signatures (any files ending with .asc) are committed as they are, without utilising the Git  LFS
       mechanisms.

Environment

TMPDIR Specifies a location to place temporary files, other than the default.

Name

       pristine-lfs - store pristine tarballs in Git LFS

Options

-mMESSAGE, --message=MESSAGE
              Use the given MESSAGE as the commit message for  the  metadate  commits.  Applies  to  commit  and
              import-dsc  commands.  %s  in  the  commit  message is replaced by a comma-separated list of files
              committed.

       -bBRANCH, --branchBRANCH
              Branch to store Git LFS metadata on.

       -v, --verbose
              Be more verbose.

       --debug
              Show all sorts of debugging information. Implies --verbose.

       -h     Show this help message and exit.

Synopsis

pristine-lfs [-h|--help]

       pristine-lfs [OPTIONS] commit [OPTIONS] (--auto | tarball)

       pristine-lfs [OPTIONS] import-dsc [OPTIONS] dscpristine-lfs [OPTIONS] checkout [-o outdir] tarballpristine-lfs [OPTIONS] listpristine-lfs [OPTIONS] verifytarball