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

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,

Re: Package owner required for ImageMagick

2021-10-13 Thread Troy Curtis Jr
On Tue, Oct 12, 2021, 10:14 PM Luya Tshimbalanga wrote: > > On 2021-10-12 15:37, Michael Cronenworth wrote: > > Hi all, > > > > I would like to put out a public call for a new primary owner for > > ImageMagick[1]. > > > > I only picked it up a few years ago to prevent it from being orphaned, > >

Re: Package downgrades from F34 -> F35 (categorized list included)

2021-09-20 Thread Troy Curtis Jr
On Mon, Sep 20, 2021 at 8:44 AM Fabio Valentini wrote: > ... - ulauncher-0:5.13.0-1.fc34 > ulauncher-0:5.12.1-1.fc35 > ... I just submitted the new ulauncher 5.14 update https://bodhi.fedoraproject.org/updates/FEDORA-2021-894c62b141 (and similarly for F34) so it should be resolved shortly.

Re: orphaning rarian

2021-08-22 Thread Troy Curtis Jr
On Sun, Aug 22, 2021 at 10:16 AM Iago Rubio wrote: > On Sun, 2021-08-22 at 09:00 -0400, Troy Curtis Jr wrote: > > > > On Wed, Aug 11, 2021 at 6:25 PM Mukundan Ragavan < > > nonamed...@gmail.com> wrote: > > > I am orphaning rarian (https://src.fedoraproject.or

Re: orphaning rarian

2021-08-22 Thread Troy Curtis Jr
On Wed, Aug 11, 2021 at 6:25 PM Mukundan Ragavan wrote: > > I am orphaning rarian (https://src.fedoraproject.org/rpms/rarian). As > far as I can tell, nothing in Fedora depends on it anymore. > > # dnf repoquery --releasever rawhide --whatrequires librarian\* > Last metadata expiration check:

Re: Don't update to the latest f33!

2021-02-16 Thread Troy Curtis Jr
On Mon, Feb 15, 2021 at 10:02 PM Dominique Martinet wrote: > Michael Catanzaro wrote on Mon, Feb 15, 2021 at 08:46:57PM -0600: > > We removed the fallbacks due to complaints from users who didn't want DNS > > ever going to Cloudflare or Google. So the lack of fallback is expected > and > >

Re: Why are we shipping debug builds of pythons?

2018-08-04 Thread Troy Curtis Jr
On Sat, Aug 4, 2018 at 5:16 PM Miro Hrončok wrote: > Hi, > > an interesting discussion came up in the Python Maint team recently, > about not shipping python3-debug and python2-debug. > > On the Chesterton's fence principle [0], I'd would like to know why are > we building and shipping them

Re: Parselmouth Badge

2017-11-06 Thread Troy Curtis Jr
On Mon, Nov 6, 2017, 5:02 AM Petr Viktorin <pvikt...@redhat.com> wrote: > On 11/05/2017 08:39 PM, Troy Curtis Jr wrote: > > So, do upstream contributions count toward Parselmouth badges? ;) > > I'm afraid the way they're set up now, they're just for the Fedora > packages

Re: [HEADS-UP] unannounced libfastjson ABI change breaks rsyslog

2017-11-01 Thread Troy Curtis Jr
On Wed, Nov 1, 2017 at 5:49 PM Dominik 'Rathann' Mierzejewski < domi...@greysector.net> wrote: > Dear Fedora, > > ..snip.. > This breaks, for example, rsyslog-8.30.0-3, which was compiled against > libfastjson-0.99.7, but didn't go out together with it, so when I ran > dnf update, the set

Extension Build Question/Recommendation

2017-10-21 Thread Troy Curtis Jr
I'd like to know what everyone's take on the best way to build python extensions for both python2 and python3 when the upstream build system can only build for one at time. The path I took for the gpsd update I submitted was to use two independent source trees, then build one for python2 and

portingdb

2017-10-05 Thread Troy Curtis Jr
What is the story with the python3 portingdb instance ( http://fedora.portingdb.xyz/)? It's been down for quite a while now. Troy ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to

Re: Python 3 porting Bugzilla guidance

2017-09-27 Thread Troy Curtis Jr
On Mon, Sep 18, 2017 at 7:01 AM Petr Viktorin wrote: > It's only automatic for Bugzilla. If upstream is not using the Fedora/RH > bugzilla (which it shouldn't, really), a URL for the upstream discussion > needs to be added manually. And of course you can open a portingdb >

Re: Package submission question

2017-09-04 Thread Troy Curtis Jr
On Mon, Sep 4, 2017 at 3:54 AM Petr Viktorin <pvikt...@redhat.com> wrote: > On 09/04/2017 06:21 AM, Troy Curtis Jr wrote: > > I have a version of the gpsd package which I believe addresses this > > ticket https://bugzilla.redhat.com/show_bug.cgi?id=1390812. I've been >

Package submission question

2017-09-03 Thread Troy Curtis Jr
I have a version of the gpsd package which I believe addresses this ticket https://bugzilla.redhat.com/show_bug.cgi?id=1390812. I've been looking around about the right way to submit. I thought it would be by using a pull request from within the pagure instance at src.fedoraproject.org. However,

Re: Question about working with upstream vs patches

2017-09-02 Thread Troy Curtis Jr
On Sat, Sep 2, 2017 at 7:40 AM Miro Hrončok <mhron...@redhat.com> wrote: > On 2.9.2017 05:53, Troy Curtis Jr wrote: > > Howdy, > > Hi Troy, > > > I'd like to help work toward the Fedora move toward Python 3. There is > > lots of good information out there

Question about working with upstream vs patches

2017-09-01 Thread Troy Curtis Jr
Howdy, I'd like to help work toward the Fedora move toward Python 3. There is lots of good information out there about much of the process, but I did have a few questions about how you like to do things, and the proper work-flow. If I start working on a particular package, should I mention as