SUSE-style RPM packaging generally prefers having the RPM changelog
detached from the main RPM spec file as a changes file. This file is
typically named <pkg>.changes (corresponding to <pkg>.spec).
At package build time in the Open Build Service, the content of the
changes file is reformatted to the RPM changelog structure and
appended to the spec file by the build system before rpmbuild
processes it.
This change adds support for this particular workflow, which is
common in communities using an instance of the Open Build Service,
such as (open)SUSE.
This was originally authored by Michael Calmer. The code was ported
to work on Python 3 and adapted for the current tito codebase
by Neal Gompa.
Co-authored-by: Michael Calmer <mc@suse.de>
Co-authored-by: Neal Gompa <ngompa13@gmail.com>
The current output levels from `tito build` are both very verbose in the
case that nothing goes wrong and often missing full context when some-
thing does go wrong. By exposing `--quiet` and `--verbose`, the build
process should be able to modulate the amount of output coming from the
internal process and from `rpmbuild`.
Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
When using `tito build --install` on a system without `sudo`, such as
inside of a Linux container build, the current implementation fails.
Furthermore, if the user is running `tito build --install` with the
correct level of privilege, it is not necessary to escalate privileges
further for the installation step.
This patch adds the `--dont-escalate-privileges` flag to `tito build`
and defaults it to `True`, which keeps the behavior backwards compat-
ible. Users will want to use this flag when building RPMs inside of a
container or when running `tito build` with the requisite permissions
for installing in the first place.
Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
Add a command-line option of --scratch to perform a scratch
build in Koji. This is easier to use than always setting
the environment variable of SCRATCH=1.
scripted DistGit commits and koji/brew chain-builds
Needs testing.
pep8 cleanup from my changes
switch --no_build to --no-build for consistency
scope matters ... should pay attention to that
this should get plain list. One tag per each line. Eg.:
dist-5E-sw-1.3-candidate
dist-f13-sw-1.3-candidate
if run --list-tags --debug, it should list all tags with explanation
why it is included or not listed. E.g:
dist-5E-sw-1.3-candidate
dist-f13-sw-1.3-candidate whitelisted
dist-f14-sw-1.3-candidate blacklisted
