Uploading new sources with fedpkg seems to make files read only after
uploaded in an attempt to maintain their checksum most likely.
tito already generates files with consistent checksums, and this is
breaking if you release to Fedora/RHEL and then try to release anywhere
else.
"git diff" can accept --binary, which will produce diff with binary content. But patch does not understood
such diff, so we are doomed. Diff with binary file will produce
Binary files /dev/null and b/app/assets/images/false.png differ
diff --git a/app/assets/images/foreman.png b/app/assets/images/foreman.png
new file mode 100644
index 0000000..8815824
And patch will accept such syntax but will not create the file. Not even empty one.
So this result in silently throwing away some changes.
The VersionTagger fails in the spec file contains a number followed
by and underscore. This patch fixes that issue.
increase_version also returned an emtpy vlaue when nothing matched,
which led to a broken spec file. It now returns the original,
unmodified value instead.
This is for supporting tagging software collections (SC), if you have
installed meta package of SC then then name of package is different.
I.e. if you are tagging rubygem-foo package and you have ruby193-build
installed then the name of package is ruby193-rubygem-foo.
We use suffix in relase number to indicate build in a branch. Builds from master have no suffix.
When we had package-1.2.3-4h built in branch and was trying to tag package-1.2.3-4 in master
the check failed as the new tag was substring of the other tag and grep matches that.
addressing:
Error running command: /usr/bin/spectool --list-files '/tmp/tito-build/rpmbuild-ruby193-d6e54d8c72c34196a4f51ac134c4172b44d9eccae0bLpW/SOURCES/ruby193-1/ruby193.spec' | awk '{print $2}' |xargs -l1 basename
Status code: 31488
Command output: basename: missing operand
Try 'basename --help' for more information.
Traceback (most recent call last):
File "/usr/bin/tito", line 23, in <module>
CLI().main(sys.argv[1:])
File "/usr/lib/python2.7/site-packages/tito/cli.py", line 94, in main
return module.main(argv)
File "/usr/lib/python2.7/site-packages/tito/cli.py", line 401, in main
return builder.run(self.options)
File "/usr/lib/python2.7/site-packages/tito/builder.py", line 194, in run
self.srpm()
File "/usr/lib/python2.7/site-packages/tito/builder.py", line 228, in srpm
self.tgz()
File "/usr/lib/python2.7/site-packages/tito/builder.py", line 479, in tgz
result = run_command(cmd)
File "/usr/lib/python2.7/site-packages/tito/common.py", line 217, in run_command
raise Exception("Error running command")
Exception: Error running command
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
Travis[1] runs continuous integration for Open Source projects. With
github, it will run the configured tests and tag pull requests as passing
or failing. This commit adds a Travis configuration.
Since Travis hosts run debian/ubuntu, and execute tests in virtualenv,
getting access to `rpm` and `python-rpm` is impossible, or nontrivial,
at least. For now, ignore the functional tests. To support running the
BuildTargetParser tests, pull that class out into its own module, and
away from release.py, which imports `rpm`.
To configure travis, go to the website, log in with your github account,
then sync your repos under the account tab below your name. Then just
switch the repo to 'on' and it should be all set up.
[1]: http://travis-ci.org
The refactoring of YumRepoReleaser into RsyncReleaser and
YumRepoReleaser caused a regression that didn't allow multiple rsync
locations to be defined and sync'd properly.
Moved a bunch of code around and adding of method variables to
allow multiple rsync and tempdirs to be used.
