pombredanne/rebase-helper

This tool helps you to rebase your package to the latest version

rebase-helper

This tool helps you to rebase your package to the latest version.

Landscape scans

Landscape.io scans of rebase-helper

General workflow

• rebase-helper-results and rebase-helper-workspace directories are created
• original spec file is copied to rebase-helper-results directory and its Version tag is modified
• old and new sources are downloaded (if needed) and extracted to rebase-helper-workspace directory
• patches are rebased using git, modified patches (if any) are saved to rebase-helper-results directory
• old and new source RPMs are created
• the source RPMs are rebuilt with selected build tool
• rpmdiff, pkgdiff and abipkgdiff are run against both sets of packages and their output is stored in rebase-helper-results directory
• rebase-helper-workspace directory is removed

Patch rebasing workflow

• new git repository is initialized and the old sources are extracted and commited to it
• every patch is applied and the changes introduced by it are commited
• new sources are extracted and added as a remote branch to the repository
• git rebase is used to rebase the commits on top of the new sources
• original patches are modified/deleted accordingly
• changes are reflected in the spec file

Requirements

Packages which need to be installed before you execute rebase-helper for the first time:

• git
• rpm-build
• mock
• fedpkg
• rpmlint
• pkgdiff
• libabigail

Python dependencies are listed in requirements.txt and can be installed with pip:

pip install -r requirements.txt

How to execute rebase-helper from CLI

Execute rebase-helper from a directory containing spec file, sources and patches (usually cloned dist-git repository).

There are two ways how to specify the new version. You can pass it to rebase-helper directly, e.g.:

rebase-helper 3.1.10

or you can let rebase-helper determine it from the new version tarball, e.g.:

rebase-helper joe-4.2.tar.gz