Re: Guidance for a python package update

2023-05-30 Thread Miro Hrončok
On 30. 05. 23 15:13, Troy Curtis Jr wrote: Please, attempt to change the dependents. Since the requires generally come from the package metadata itself, does this mean changing upstream for each dependency? Or just patch for our Fedora packages? Presumably they could be patched and then

Re: Guidance for a python package update

2023-05-30 Thread Troy Curtis Jr
On Tue, May 30, 2023, 3:13 AM Miro Hrončok wrote: > Hi Troy. > > On 29. 05. 23 18:01, Troy Curtis Jr wrote: > > I'm currently working on the update for python-Levenshtein [1] and I > have a > > question about the best way to proceed. > > > > In the intervening time since the last release we have

Re: Guidance for a python package update

2023-05-30 Thread Miro Hrončok
Hi Troy. On 29. 05. 23 18:01, Troy Curtis Jr wrote: I'm currently working on the update for python-Levenshtein [1] and I have a question about the best way to proceed. In the intervening time since the last release we have packaged, a new maintainer has taken over maintenance, and built the u

Guidance for a python package update

2023-05-29 Thread Troy Curtis Jr
I'm currently working on the update for python-Levenshtein [1] and I have a question about the best way to proceed. In the intervening time since the last release we have packaged, a new maintainer has taken over maintenance, and built the updates around a stack of other packages (rapidfuzz-cpp, p