Bug 1399536 - RFE: Update GitPython in epel7
Summary: RFE: Update GitPython in epel7
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: GitPython
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Carl George 🤠
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-29 09:32 UTC by Nacho Barrientos
Modified: 2022-04-28 05:56 UTC (History)
6 users (show)

Fixed In Version: GitPython-1.0.2-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-28 05:56:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Nacho Barrientos 2016-11-29 09:32:08 UTC
Hi,

Could GitPython be updated to a newer version on EPEL7? We're hitting a bug [0][1] that's present in 1.0.1-5 and that should be fixed in newer versions, like 1.0.2.

Thanks.

[0] https://github.com/gitpython-developers/GitPython/issues/301
[1] https://github.com/gitpython-developers/GitPython/commit/369e564174bfdd592d64a027bebc3f3f41ee8f11

Comment 1 Steve Traylen 2016-11-29 10:37:40 UTC
I checked and updating software with existing .spec file seems to build just fine.

Scratch build - http://koji.fedoraproject.org/koji/taskinfo?taskID=16667902

Comment 2 Nacho Barrientos 2016-11-30 07:03:19 UTC
It'd be cool if you could go for 2.1.0 instead (latest upstream) as 1.0.2 contains a very ugly regression [0]. Thanks.

[0] https://github.com/gitpython-developers/GitPython/issues/383

Comment 3 Nacho Barrientos 2016-12-02 09:10:15 UTC
Same about 2.1.0, seems to build fine.

Comment 4 Kevin Fenzi 2021-03-27 21:09:54 UTC
So, we can't go to 3.x as that's where there is no more python2 support. 

So, the latest 2.x is 2.1.15. It needs a patch to build against python3 (due to python3 requires changes), but thats easy enough:

Can you all look at this scratch build and see if it works for you?

https://koji.fedoraproject.org/koji/taskinfo?taskID=64699755

If so, I can push out an official update.

Comment 5 Carl George 🤠 2022-04-19 04:11:03 UTC
Updating from the current version 1.0.1 to version 2.x.x involves breaking changes [0].  That is normally not allowed by EPEL policy [1], unless someone wants to put in the work to go through the incompatible upgrade process [2].

In the meantime, I've opened a pull request [3] to update the epel7 package to version 1.0.2, including a patch to fix the regression Nacho mentioned.


[0] https://github.com/gitpython-developers/GitPython/blob/2.0.0/doc/source/changes.rst#200---features
[1] https://docs.fedoraproject.org/en-US/epel/epel-policy/#package_maintenance_and_update_policy
[2] https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/
[3] https://src.fedoraproject.org/rpms/GitPython/pull-request/6

Comment 6 Fedora Update System 2022-04-20 00:14:34 UTC
FEDORA-EPEL-2022-29dba5dac3 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-29dba5dac3

Comment 7 Fedora Update System 2022-04-20 19:44:31 UTC
FEDORA-EPEL-2022-29dba5dac3 has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-29dba5dac3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2022-04-28 05:56:08 UTC
FEDORA-EPEL-2022-29dba5dac3 has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.