Differential D639

Start versioning deps in resultsdb spec file
ClosedPublic
Actions

Authored by jskladan on Nov 4 2015, 11:29 AM.

Details

Reviewers
kparal
tflink
mkrizek
Maniphest Tasks
T621: Start versioning deps in resultsdb spec file
Commits
rRSDB73f95834caad: Start versioning deps in resultsdb spec file
Summary

Done in the same way as in D337

Test Plan

none

Diff Detail

Repository
rRSDB resultsdb
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
jskladan retitled this revision from to Start versioning deps in resultsdb spec file.Nov 4 2015, 11:29 AM
jskladan updated this object.
jskladan edited the test plan for this revision. (Show Details)
jskladan added reviewers: tflink, mkrizek, kparal.
mkrizek accepted this revision.Nov 4 2015, 11:56 AM

LGTM

This revision is now accepted and ready to land.Nov 4 2015, 11:56 AM
tflink accepted this revision.Nov 4 2015, 4:50 PM

The specfile is fine as is - my one point is that the deps are not in alphabetical order like the taskotron ones are.

Closed by commit rRSDB73f95834caad: Start versioning deps in resultsdb spec file (authored by Josef Skladanka <jskladan@redhat.com>). · Explain WhyNov 5 2015, 12:46 PM
This revision was automatically updated to reflect the committed changes.

Revision Contents

PathPackages
Mrequirements.txt (42 lines)
Mresultsdb.spec (25 lines)

Diff 1671

View Options

requirements.txt

1Flask>=0.9 1​# This is a list of pypi packages to be installed into virtualenv. Alternatively,
2Flask-SQLAlchemy>=0.16 2​# you can install these as RPMs instead of pypi packages. Use
3SQLAlchemy>= 0.7 3​# `rpmspec -q --requires resultsdb.spec`
4WTForms>1.0 4​
5Flask-WTF>=0.8 5​# A note for maintainers: Please keep this list in sync with resultsdb.spec.
6Flask-Login>=0.2.2 6​# You should require exact versions here (in order to define an exact working
7Flask-RESTful >= 0.2.5 7​# environment), and require a minimal version in the spec file (in order to allow
8​# the libraries to have some minor version bumps during the Fedora release
9​# lifecycle). If the Fedora libraries span multiple versions across releases,
10​# you can define a dependency range here instead of an exact version.
11​
12​# This list is in the same order as the requirements in the specfile.
13​
14​
15​fedmsg == 0.16.2
16​alembic == 0.8.3
17​Flask == 0.10.1
18​Flask-Login == 0.2.11
19​Flask-RESTful == 0.2.11
20​Flask-SQLAlchemy == 2.0
21​Flask-WTF == 0.10.0
22​iso8601 == 0.1.10
23​six == 1.9.0
24​SQLAlchemy == 0.9.10
25​WTForms == 2.0
26​
8pytest>=2.4.2 27​pytest >= 2.4.2
9pytest-cov>=1.6 28​pytest-cov >= 1.6
10alembic>=0.7.4 ​
11# although this is a Flask-Restful dependency, it was not installed, adding manualy ​
12six ​
13iso8601 >= 0.1.4 ​
14fedmsg>=0.11.1 ​
View Options

resultsdb.spec

1%if ! (0%{?fedora} > 12 || 0%{?rhel} > 5) 1​%if ! (0%{?fedora} > 12 || 0%{?rhel} > 5)
2%{!?python_sitelib: %global python_sitelib %(%{__python} -c "from distutils.sysconfig import get_python_lib; print(get_python_lib())")} 2​%{!?python_sitelib: %global python_sitelib %(%{__python} -c "from distutils.sysconfig import get_python_lib; print(get_python_lib())")}
3%{!?python_sitearch: %global python_sitearch %(%{__python} -c "from distutils.sysconfig import get_python_lib; print(get_python_lib(1))")} 3​%{!?python_sitearch: %global python_sitearch %(%{__python} -c "from distutils.sysconfig import get_python_lib; print(get_python_lib(1))")}
4%endif 4​%endif
5 5​
6Name: resultsdb 6​Name: resultsdb
7Version: 1.1.13 7​Version: 1.1.13
8Release: 1%{?dist} 8​Release: 2%{?dist}
9Summary: Results store for automated tasks 9​Summary: Results store for automated tasks
10 10​
11License: GPLv2+ 11​License: GPLv2+
12URL: https://bitbucket.org/fedoraqa/resultsdb 12​URL: https://bitbucket.org/fedoraqa/resultsdb
13Source0: https://qadevel.cloud.fedoraproject.org/releases/%{name}/%{name}-%{version}.tar.gz 13​Source0: https://qadevel.cloud.fedoraproject.org/releases/%{name}/%{name}-%{version}.tar.gz
14 14​
15BuildArch: noarch 15​BuildArch: noarch
16 16​
17Requires: python-flask 17​Requires: fedmsg >= 0.16.2
18Requires: python-flask-sqlalchemy 18​Requires: python-alembic >= 0.8.3
19Requires: python-flask-wtf 19​Requires: python-flask >= 0.10.1
20Requires: python-flask-login 20​Requires: python-flask-login >= 0.2.11
21Requires: python-flask-restful 21​Requires: python-flask-restful >= 0.2.11
22Requires: python-six 22​Requires: python-flask-sqlalchemy >= 2.0
23Requires: python-iso8601 23​Requires: python-flask-wtf >= 0.10.0
24Requires: python-alembic 24​Requires: python-iso8601 >= 0.1.10
25Requires: fedmsg 25​Requires: python-six >= 1.9.0
26​Requires: python-sqlalchemy >= 0.9.10
27​Requires: python-wtforms >= 2.0
26BuildRequires: python2-devel python-setuptools 28​BuildRequires: python2-devel python-setuptools
27 29​
28%description 30​%description
29ResultsDB is a results store engine for (not only) FedoraQA tools. 31​ResultsDB is a results store engine for (not only) FedoraQA tools.
30Repositories 32​Repositories
31 33​
32%prep 34​%prep
33%setup -q 35​%setup -q
Show All 24 Lines
58 60​
59%attr(755,root,root) %{_bindir}/resultsdb 61​%attr(755,root,root) %{_bindir}/resultsdb
60%dir %{_sysconfdir}/resultsdb 62​%dir %{_sysconfdir}/resultsdb
61%{_sysconfdir}/resultsdb/* 63​%{_sysconfdir}/resultsdb/*
62%dir %{_datadir}/resultsdb 64​%dir %{_datadir}/resultsdb
63%{_datadir}/resultsdb/* 65​%{_datadir}/resultsdb/*
64 66​
65%changelog 67​%changelog
68​* Wed Nov 4 2015 Josef Skladanka <jskladan@redhat.com> - 1.1.13-2
69​- synchronize package versions between spec file and requirements.txt
70​
66* Wed Oct 7 2015 Martin Krizek <mkrizek@redhat.com> - 1.1.13-1 71​* Wed Oct 7 2015 Martin Krizek <mkrizek@redhat.com> - 1.1.13-1
67- Emit fedmsg with whatever result is being stored 72​- Emit fedmsg with whatever result is being stored
68 73​
69* Tue Aug 18 2015 Tim Flink <tflink@fedoraproject.org> - 1.1.12-1 74​* Tue Aug 18 2015 Tim Flink <tflink@fedoraproject.org> - 1.1.12-1
70- Use HTTP_X_FORWARDED_SCHEME (D264) 75​- Use HTTP_X_FORWARDED_SCHEME (D264)
71- Improve pagination metadata for JSON queries (D264) 76​- Improve pagination metadata for JSON queries (D264)
72- Add fedmenu to resultsdb (D364) 77​- Add fedmenu to resultsdb (D364)
73- Several dev and backend fixes 78​- Several dev and backend fixes
▲ Show 20 Lines • Show All 50 Lines • Show Last 20 Lines