Do I surmise correctly that Bugzilla tickets are only to be created if
there is a packaging issue preventing python3 "compliance", and not if
upstream needs to be updated first to support? If so, is there a different
resource that is used to track any research done into upstream that
identified the need for changes? Or is the assumption that there would be
discussion on the upstream mailing list or an issue in their project
specific tracker and thus a Bugzilla entry would be redundant?
It doesn't look like the original maintainer has ever updated the package since it's original version in 2014 and it's very out of date. I need it updated in all supported Fedora releases (and EPEL if it exists) to at least 0.4.10 for mythtv at RPM Fusion.
The current release is 0.4.13...
Can someone from the python SIG with provenpackager rights help?
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, I cannot authenticate with my ssh key. There is no where to add
it within pagure, and my FAS key doesn't seem to be sufficient. So perhaps
this isn't they way? Then I was reading through
, but it seems a bit geared toward brand new packages, so I was not sure if
that was in fact the proper coarse.
I'd appreciate any pointers as to the proper direction to get this updated
package updated. In the meantime, I'll fix the rpmlint warnings I just
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
If I start working on a particular package, should I mention as such in the
associated porting bugtracker ticket? I could see it either way, either it
needless clutters the ticket comments, or it is helpful for the next guy to
pick a different package.
I already started looking at gpsd, since I've had some experience with it,
and it is bound to be challenging! I was proven right pretty quickly. It
is all perfectly workable, but I wanted to know the general expectation.
For changes to python modules/scripts themselves to support python 3, does
this need to flow through upstream in all cases? Most of my packaging
experience has been with the enterprise distros, and there are always loads
of patches carried along with the sources, but in this case do you require
an official release from the upstream project with the necessary changes?
I certainly plan on providing all the changes upstream, but the last
release was almost 2 years ago, so I'm not certain when a new one might be
expected (the project is still active though).