Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: Iaca480434f5f59d9b3cc66e477a9ea9c5c08c276
|
|
2. Keep same code with latest release
Change-Id: I30588773b0a039c9f5002bf65b5c768a16fb7935
|
|
Change-Id: I02f5d8cc11a268c7dd075da6e0064d3fedf72721
|
|
Change-Id: I87f32c6b28b8835c09004530d7e6e429143dc4bf
|
|
This is a Tizen-specific tool for creating and pushing special submit
tags.
Change-Id: Id014ce2aeced75f6506cd8559adcd787f958e6b4
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
This is a new tool for helping to clone remote per-package Git
repositories when working in BitBake-based "full distro" build
environment. This is useful in the case that individual packages are
actually maintained in per-package Git repositories (like Tizen). That
is, the full distro repository that the developer operates in is
composed of the packaging meta data from the individual per-package
repositories. When willing to contribute to a package the developer
would use clone-bb to clone the correct per-package repository and make
his changes there.
NOTE: clone-bb uses GBP_PACKAGING_REPO variable to determine the remote
repository URI. This variable should be defined in the package recipes
in order to make clone-bb usable.
Change-Id: I95fb3aa907dc78c55e042f16282a139d5ff3ce2a
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Initial version of the tool for building BitBake packages from Git.
NOTE: The buildpackage-bb tool itself is able to operate even without an
initialized BitBake build environment although the build likely fails in
this case. However, this makes it possible to export the packaging meta
data, for example.
Change-Id: I86204e477308da51f71fab76150ede4bd90e4d6e
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
This is a tool for managing patch-queues for packages maintained in the
BitBake packaging format (.bb recipes).
Change-Id: I7c2815c05495deb731106fbfea911494ac4984ac
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
This is the first tool in an effort of enabling gbp in the BitBake build
environment. Gbp-import-bb is a tool for importing packages from a
BitBake-based "combined" distro repository into individual per-package
Git repositories.
Change-Id: I86e27d8a1817eae30c3f828cea70b06162543000
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Consider remote branches, too, while looking for the upstream branch
when trying to guess if a package is native or not.
Change-Id: I3dbbb49816d1d294d81209ea5ab5870e053fd66a
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Change-Id: Iaadc614e9ed5df2e943eed71511559d0b76e0227
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
We will never get here as parse_spec() always returns GbpError.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Gracefully handle invalid keys in the --git-orig-prefix format string.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
No need to mangle the export directory.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Can be used to explicitly configure a package as native or non-native.
Default behavior is still to guess based on the existence of upstream
branch.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
There should be no reason to catch general Exception here.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Replaces and deprecates --git-export-only. The new option name is way
better in line with the other option names.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
GitRepository.git_dir is not callable.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
And not from the current working copy.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
If the package is native, always (re-)create the source tarball, even if
--git-no-create-orig is used. Not creating the tarball does not make
much sense (and most probably just causes problems and confusion): for
native packages there is no place for external tarball and no patches so
we need to always have the correct sources (i.e. the exported revision)
in the tarball.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
This gives the user the possibility to define what meta tags (in git
commit message) git-rpm-ch recognizes as bug tracking system references.
Or, makes it possible to disable bts meta tag tracking altogether.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Add a new keyword '%(commitish)s' that can be used in the
--git-spec-vcs-tag option. This will be translated to the sha1 of the
commitish (i.e. tag or commit). That is, if you export a tag you will
get the sha1 of the tag object - not resolving to a commit object unlike
'%(commit)s' does.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Pq branch must be created with 'import'.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
With this option defined gbp tries to preserve the history when
converting. That is, for each commit in the old branch create one
corresponding commit in the new orphan packaging branch. This works by
dumping packaging files and updating patches for each commit. However,
empty commits are not generated - these are caused e.g. by changes in
files that are ignored by patch-generation.
NOTE! Only valid for the 'convert' action.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Used for setting the packaging directory to be used in the new orphan
packaging branch. Defaults to --packaging-dir so that the gbp.conf files
are more likely to work without modification.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
The new subcommand is intended to be a one-time-callable command for
converting a package to use the "orphan-packaging" development model and
git layout (where packaging files are maintained in a separate branch
and code development in another branch).
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Adds git-buildpackage-rpm --patch-export support for the 'orphan
packaging' development model (where packaging files and development sources are kept in separate
branches).
New functionality:
1. If patch-export is enabled and gbp detects that the current branch
has a development/patch-queue branch it exports the patches from there,
instead of the tip of the packaging branch.
2. If gbp detects that the current (or exported) branch is a
development/patch-queue branch it automatically enables patch-export
and exports packaging files from the base branch (instead of the
development/patch-queue branch.
Also, add a new '--git-patch-export-rev' command line option with which
the user can explicitly set the treeish from which patches are generated
(i.e. HEAD..<patch-export-rev>)
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Try to get archive path/filename from spec file if no file name is given
on the command line. This should make version bumps more
straightforward: just update version number in the spec file and run
'git-import-orig-rpm'.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Automatically try to download the archive if the archive filename points
to a remote location.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Create the upstream branch if it does not exist. Use the same option
name that import-srpm has.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
If defined, git-rpm-ch uses all commits in the Git history. Also,
'--since' option is omitted.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
For giving the text for new changelog entry/entries, skipping git commit
messages entirely.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Implement '--tag' command line option (and other related options for
signing) for creating and tagging a release. These correspond the
tagging options in git-buildpackage-rpm.
The git-buildpackage-rpm tool does not commit anything to git. However,
in rpm-ch the '--tag' option causes the changelog modifications (and,
all other staged changes) to be committed to git before creating the
tag. This makes it possible to create a release and document the
packaging/release tag name in the rpm changelog.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Initial version of the git-rpm-ch tool which is intended for maintaining
RPM changelogs. Supports both spec files and separate "OBS style"
changelog files.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
For defining the packaging file(s) that will be imported into the
development/patch-queue branch.
By default, the local gbp conf files are imported in order to try to
ensure that gbp sees the same settings on the development/pq branch as
on the packaging branch.
NOTE: This option does not affect the patch files that are imported. The
files defined with this option will appear as new files in one
monolithic commit in the development/patch-queue branch.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Support '%(upstreamversion)s' as a replacable string in the pq branch
name.
Eliminate some unneeded branch switches that were only needed for
finding/parsing the spec file. Now, spec file is directly searched from
the git repository (from the 'base' branch) if the command is run when
on the pq branch - except for the 'export' subcommand which always
switches to the base branch.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Before, merge commits broke patch generation, or, (most probably) caused
the generated patches to be unapplicable (similar to how
git-format-patch behaves).
Now, changes up to the last merge commit are squashed into one diff if
merge commits are found in the revision list from which patches are to
be generated. Individual patches (one per commit) are generated from the
last merge commit up to the exported revision.
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|
|
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
|