Due to error in GemBuilder.tgz method generating the list of sources
there was problem with adding the sources into lookaside (the list of
sources contained all the files in the directory, even directories).
Thanks to 9feb9cf48d the tgz method in
NoTgzBuilder is generic enough to be able to extract the source files
even for GemBuilder.
addressing:
$ tito release git-sat
Will release to the following targets: git-sat
Checking for tag [katello-1.4.2-4-sat] in git repo [ssh://git.corp.redhat.com/srv/git/engineering/katello]
Releasing to target: git-sat
Working in: /tmp/tito/release-katello-6a0e027d9e284d65e3407e7060e98ccf9d48b2fdiD7jdk
Building upstream tgz for tag [katello-1.4.2-1]
Checking for tag [katello-1.4.2-1] in git repo [ssh://git.corp.redhat.com/srv/git/engineering/katello]
Creating katello-1.4.2.tar.gz from git tag: 507e03d5743fd2f7609d5bca80ed1e1b7d302fc4...
Traceback (most recent call last):
File "/usr/bin/tito", line 23, in <module>
CLI().main(sys.argv[1:])
File "/usr/lib/python2.6/site-packages/tito/cli.py", line 94, in main
return module.main(argv)
File "/usr/lib/python2.6/site-packages/tito/cli.py", line 638, in main
scratch=self.options.scratch)
File "/usr/lib/python2.6/site-packages/tito/release.py", line 490, in release
self._git_release()
File "/usr/lib/python2.6/site-packages/tito/release.py", line 507, in _git_release
self.builder.tgz()
File "/usr/lib/python2.6/site-packages/tito/builder.py", line 784, in tgz
self.patch_upstream()
File "/usr/lib/python2.6/site-packages/tito/distributionbuilder.py", line 37, in patch_upstream
error_out("You are doomed. Diff contains binary files. You can not use this builder")
NameError: global name 'error_out' is not defined
addressing:
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 638, in main
scratch=self.options.scratch)
File "/usr/lib/python2.7/site-packages/tito/release.py", line 490, in release
self._git_release()
File "/usr/lib/python2.7/site-packages/tito/release.py", line 507, in _git_release
self.builder.tgz()
File "/usr/lib/python2.7/site-packages/tito/builder.py", line 784, in tgz
self.patch_upstream()
File "/usr/lib/python2.7/site-packages/tito/distributionbuilder.py", line 34, in patch_upstream
(status, output) = commands.getstatusoutput(
NameError: global name 'commands' is not defined
addressing:
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 635, in main
auto_accept=self.options.auto_accept)
File "/usr/lib/python2.7/site-packages/tito/release.py", line 473, in __init__
overwrite_checkout = self.config.get(self.target, "remote_git_name")
File "/usr/lib64/python2.7/ConfigParser.py", line 607, in get
raise NoSectionError(section)
ConfigParser.NoSectionError: No section: 'git-sat'
if package reside in subdirectory, then in metadata file is written
1.0 foo/
but if the package reside in git-root, then in metadata file is written
1.0 /
which is not relative path and if it is evaluated by some tool, it is evaluated incorrectly
This patch will change this singularity to:
1.0 ./
I done s/spacewalk.releng./tito./ in spacewalk.git, but it may reside in some (private) branches.
So let keep it for little bit more releases, but print warnings.
because output of:
rpm -q --qf '%{name}' --eval '%undefine scl' --specfile rubygem-robotex.spec
is:
rubygem-robotex
(i.e. two empty lines, then the output)
* Store the --test flag on the releaser and pass it to the builder
* With --test in effect, have the builder update the spec file
* When the builder does so it also updates the build_version to include git hash
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.
