#3 Update to 2.5.0, modernize
Merged 4 years ago by churchyard. Opened 4 years ago by churchyard.
rpms/ churchyard/python-munch 2.5.0  into  master

file modified
+4 -7
@@ -1,7 +1,4 @@ 

- /munch-2.0.2.tar.gz

- /munch-2.0.3.tar.gz

- /munch-2.0.4.tar.gz

- /munch-2.1.0.tar.gz

- /munch-2.1.1.tar.gz

- /munch-2.2.0.tar.gz

- /munch-2.3.2.tar.gz

+ /munch-*.tar.gz

+ /munch-*/

+ /results_python-munch/

+ *.rpm

file modified
+13 -14
@@ -1,8 +1,8 @@ 

  %global modname munch

  

  Name:               python-munch

- Version:            2.3.2

- Release:            7%{?dist}

+ Version:            2.5.0

+ Release:            1%{?dist}

  Summary:            A dot-accessible dictionary (a la JavaScript objects)

  

  License:            MIT
@@ -13,6 +13,7 @@ 

  

  BuildRequires:      python3-devel

  BuildRequires:      python3-setuptools

+ BuildRequires:      python3-pbr

  

  %global _description\

  munch is a fork of David Schoonover's **Bunch** package, providing similar\
@@ -26,16 +27,10 @@ 

  %description %_description

  

  %package -n python3-munch

- Summary:            A dot-accessible dictionary (a la JavaScript objects)

- 

- %description -n python3-munch

- munch is a fork of David Schoonover's **Bunch** package, providing similar

- functionality. 99% of the work was done by him, and the fork was made

- mainly for lack of responsiveness for fixes and maintenance on the original

- code.

+ Summary:            %{summary}

+ %{?python_provide:%python_provide python3-munch}

  

- Munch is a dictionary that supports attribute-style access, a la

- JavaScript.

+ %description -n python3-munch %_description

  

  %prep

  %setup -q -n %{modname}-%{version}
@@ -48,11 +43,11 @@ 

  

  

  %build

- %{__python3} setup.py build

+ %py3_build

  

  

  %install

- %{__python3} setup.py install -O1 --skip-build --root=%{buildroot}

+ %py3_install

  

  

  %files -n python3-munch
@@ -60,10 +55,14 @@ 

  %{!?_licensedir:%global license %doc}

  %license LICENSE.txt

  %{python3_sitelib}/%{modname}/

- %{python3_sitelib}/%{modname}-%{version}*

+ %{python3_sitelib}/%{modname}-%{version}*/

  

  

  %changelog

+ * Wed Mar 04 2020 Miro Hrončok <mhroncok@redhat.com> - 2.5.0-1

+ - Update to 2.5.0 (#1766566)

+ - Fixes build with Python 3.9 (#1789175)

+ 

  * Thu Jan 30 2020 Fedora Release Engineering <releng@fedoraproject.org> - 2.3.2-7

  - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild

  

file modified
+1 -1
@@ -1,1 +1,1 @@ 

- SHA512 (munch-2.3.2.tar.gz) = 7cbcd79b9506940f88a2090649e5ab6678164b468ed04feebeab8f85c9af861a1a8012aaafc869755c3c7957feefb231bc15426c382c014e82e9b806a879b8e7

+ SHA512 (munch-2.5.0.tar.gz) = 7eca31111f40782a19b49535322bc56d723022d52b0842c4beff512f32fa415a6c75851eb84950358cb6a11693095cafe56364028e48385b11135de414edca21

asv failure is unrelated:

E       selenium.common.exceptions.WebDriverException: Message: unknown error: Chrome failed to start: crashed.
E         (unknown error: DevToolsActivePort file doesn't exist)
E         (The process started from chrome location /usr/lib64/chromium-browser/chromium-browser is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
E         (Driver info: chromedriver=80.0.3987.122 (cf72c4c4f7db75bc3da689cd76513962d31c7b52-refs/branch-heads/3987@{#943}),platform=Linux 5.4.10-200.fc31.x86_64 x86_64)

https://koschei.fedoraproject.org/package/asv?collection=f33

python-osc-lib failure unrelated: https://bugzilla.redhat.com/show_bug.cgi?id=1809967
python-openstackclient failure unrelated: https://bugzilla.redhat.com/show_bug.cgi?id=1809969
python-openstacksdk failure unrelated: https://bugzilla.redhat.com/show_bug.cgi?id=1809970
python-tackerclient failure unrelated: https://bugzilla.redhat.com/show_bug.cgi?id=1809986

And that's it: Everything either builds or is broken for unrelated reason.

+1 to merge. Thanks for working on this!

Pull-Request has been merged by churchyard

4 years ago

Thanks for working on this!

I figured that you better spend your time on actual infra stuff.

That said, I am worried about that large amount of packages that have fedora-infra set as primary Bugzilla PoC: getting a response is very hard. What would it take to regularly triage the open bugzillas?

Yeah, I brought infra-sig bugzilla bugs up the other day... we are going to try and make sure we watch them as an input for our team.

We also want to probibly orphan / add / adjust our packages, as some aren't needed anymore for our applications.

Yeah, I brought infra-sig bugzilla bugs up the other day... we are going to try and make sure we watch them as an input for our team.

Thank You!

We also want to probably orphan / add / adjust our packages, as some aren't needed anymore for our applications.

That makes perfect sense.