[packages/python3-git-filter-repo] - new, separated from git-filter-repo.spec (now with python metadata, required for e.g. b4)

Elan Ruusamäe glen at pld-linux.org
Mon Oct 17 20:14:27 CEST 2022


wth. how is this any good?

just add the -n python3-git-filter-repo to main git-filter-repo package!

with your package split and the require-line in old spec, you force us 
to keep two .spec files up todate with each release of git-filter-repo, 
additionally deal with sending to builders, and in proper order as well.

why?

On 08.10.2022 21:51, qboosh wrote:
> commit 61919f8f6ee682327311dfb153d2fb5474d1e622
> Author: Jakub Bogusz <qboosh at pld-linux.org>
> Date:   Sat Oct 8 20:51:52 2022 +0200
>
>      - new, separated from git-filter-repo.spec (now with python metadata, required for e.g. b4)
>
>   python3-git-filter-repo.spec | 53 ++++++++++++++++++++++++++++++++++++++++++++
>   1 file changed, 53 insertions(+)
> ---
> diff --git a/python3-git-filter-repo.spec b/python3-git-filter-repo.spec
> new file mode 100644
> index 0000000..b402d05
> --- /dev/null
> +++ b/python3-git-filter-repo.spec
> @@ -0,0 +1,53 @@
> +Summary:	Quickly rewrite git repository history
> +Summary(pl.UTF-8):	Szybkie przepisywanie historii repozytorium
> +Name:		python3-git-filter-repo
> +Version:	2.34.0
> +Release:	1
> +License:	MIT
> +Group:		Libraries/Python
> +#Source0Download: https://pypi.org/simple/git-filter-repo/
> +Source0:	https://files.pythonhosted.org/packages/source/g/git-filter-repo/git-filter-repo-%{version}.tar.gz
> +# Source0-md5:	14825e3c78de704a0244092600bf1fdc
> +URL:		https://pypi.org/project/git-filter-repo/
> +BuildRequires:	python3-modules >= 1:3.5
> +BuildRequires:	python3-setuptools
> +BuildRequires:	python3-setuptools_scm
> +BuildRequires:	rpm-pythonprov
> +BuildRequires:	rpmbuild(macros) >= 1.714
> +Requires:	git-core >= 2.24.0
> +Requires:	python3-modules >= 1:3.5
> +Conflicts:	git-filter-repo < 2.34.0-2
> +BuildArch:	noarch
> +BuildRoot:	%{tmpdir}/%{name}-%{version}-root-%(id -u -n)
> +
> +%description
> +git filter-repo is a versatile tool for rewriting history.
> +
> +%description -l pl.UTF-8
> +git filter-repo to wszechstronne narzędzie do przepisywania historii.
> +
> +%prep
> +%setup -q -n git-filter-repo-%{version}
> +
> +# fix #!/usr/bin/env python -> #!/usr/bin/python:
> +%{__sed} -i -e '1s,/usr/bin/env python3,%{__python3},' git_filter_repo.py
> +
> +%build
> +%py3_build
> +
> +%install
> +rm -rf $RPM_BUILD_ROOT
> +
> +%py3_install
> +
> +%{__rm} $RPM_BUILD_ROOT%{_bindir}/git-filter-repo
> +
> +%clean
> +rm -rf $RPM_BUILD_ROOT
> +
> +%files
> +%defattr(644,root,root,755)
> +%doc README.md
> +%{py3_sitescriptdir}/git_filter_repo.py
> +%{py3_sitescriptdir}/__pycache__/git_filter_repo.cpython-*.py[co]
> +%{py3_sitescriptdir}/git_filter_repo-%{version}-py*.egg-info
> ================================================================
>
> ---- gitweb:
>
> http://git.pld-linux.org/gitweb.cgi/packages/python3-git-filter-repo.git/commitdiff/61919f8f6ee682327311dfb153d2fb5474d1e622
>
> _______________________________________________
> pld-cvs-commit mailing list
> pld-cvs-commit at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit


More information about the pld-devel-en mailing list