On Mon, Sep 4, 2017 at 3:54 AM Petr Viktorin <pviktori(a)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
> looking around about the right way to submit. I thought it would be by
> using a pull request from within the pagure instance at
;. 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 found!
That shouldn't be happening.
What's your FAS username?
If you can push the changes to another public Git repository (e.g.
GitHub), that could be a workaround while we get Pagure access sorted out.
Ok so Pagure is the right way to go then. I tried importing my key again,
but I'm still getting denied. I can use the same key on a different linux
host as well as with gitlab.com
, so I'm fairly confident my local
configuration is correct. I assume this is unrelated, but I also can't
seem to tie my FAS account correctly to the
For the time being then, I've pushed my changes to
'python2-packaging' branch for review. Additionally, I used copr to build
for several releases, which you can find at