This was using 'python_sitelib' in a non-standard way (it got
defined to either python2_sitelib or python3_sitelib depending
on whether we're doing a python2 or python3 build). Igor saw
the uses of 'python_sitelib' and assumed it was just using the
old name for 'the python 2 sitelib' and changed them all to
'python2_sitelib'...which broke all Fedora builds.
This fixes that problem and renames the package's confusing
'python_sitelib' and 'pythonbin' so hopefully no-one will make
the same mistake in future.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
None of currently supported distributions need that.
Last one was EL5 which is EOL for a while.
Signed-off-by: Igor Gnatenko <ignatenkobrain@fedoraproject.org>
createrepo_c is a faster and more correct implementation of
generating rpm repositories, used by Fedora, openSUSE, and Mageia
for creating official distro repositories. It is also used by COPR
for creating repositories for packages built through its system.
This was added in commit 9ce9442642 and is not actually neede.
Just because we print
Failed build dependencies
Please run 'yum-builddep %s' as root.
So it should be rather replaced by:
Suggest: yum-utils
But that cannot be parsed on el6 and is in fact not needed on F23+ at all.
So it should be rather described by rich deps like
Suggest: (yum-utils if yum) and (dnf-plugins-core if dnf)
But rich deps should not be used for now.
So lets remove it for now. So yum-utils can be safely retired in rawhide.
Tito can now build a project with Maven, expose the Maven artifacts to
a Cheetah template, and then build the SRPM (and RPM) using the
rendered template and the Maven artifacts.
Tito passes "git archive" a tree ID. The "git archive" man page states:
git archive behaves differently when given a tree ID versus when
given a commit ID or tag ID. In the first case the current time
is used as the modification time of each file in the archive.
Using the current time means that every time we build the source
tarball, the file fingerprint will change since the metadata in the
tarball changes. We don't want that since build systems track the
fingerprint to see if the actual source has changed.
This process was previously handled in an enigmatic Perl script that
lacked any comments whatsoever. Converting it to well-commented Python
makes the process less mysterious and speedier since Tito doesn't need
to shell out to Perl.
Here's an initial go at getting some bash-completion for the tito
command-line. Module options are a union of those culled from both
"tito MODULE --help" and "man tito" -- there are discrepancies. Some
options were deliberately omitted such as those documented as deprecated
or "avoid using this please". All short options are also omitted as
their completion would not save any typing but would hinder the
accessibility of the longer options.
Use unversioned macros for EL6, don't reset python_sitelib on F22+ and
always use the Python binary determined for the OS, not python3 for the
shebang line.
Fixes#167, #168
Ensure build deps are consistent across the spec file and test harness.
Note: http://fedoraproject.org/wiki/HOWTOFindMissingBuildRequires
says that some packages should not be BuildRequires because
"they would occur too often" and "are considered the minimum build
environment." However, Docker changes the scope of that assumption
to keep docker images small.
* asciidoc indirectly requires docbook-style-xsl on el6 and f20,
but not on el5. Resolve failure to build tito with tito on el5:
"I/O error : Attempt to load network entity"
* Resolve "egg missing file" on el5 due to busted symlinks
from 20c4f1b7c0.
* Add functional test to build tito with itself in order to
catch problems like the ones above.
Closes https://github.com/dgoodwin/tito/issues/133
