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
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
>
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
>
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
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
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,
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
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
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,
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
10 matches
Mail list logo