On Fri, May 11, 2018 at 5:35 PM, Tim Jackson <lists@xxxxxxxxxx> wrote: > As an infrequent contributor, I have unfortunately had to resign myself to > the fact that every time I try to make a change to a package, something has > broken/changed, and thus 95% of the time goes on fixing the environment and > 5% on the package in question. However, I do wonder whether, when > refactoring the tooling, some improvements could be made to error handling > and reporting. As an example, today's error is something to do with logging > into Koji when running "fedpkg build": For "fedpkg build", should just need "kinit [FAS username]@FEDORAPROJECT.ORG". > > Kerberos authentication fails: Could not find a suitable TLS CA certificate > bundle, invalid path: ~/.fedora-server-ca.cert > Could not execute build: Could not login to > http://koji.fedoraproject.org/kojihub > > Firstly, could the error message "invalid path: ~/.fedora-server-ca.cert" be > improved? There _is_ a CA certificate in that location, untouched since > August 2014. As far as I can tell it's still valid (at least it's not > expired according to "openssl x509 -text <~/.fedora-server-ca.cert"). What's > suddenly "invalid" about it now? ("-d" doesn't provide any additional > information). It would be really helpful, especially to us less-frequent > packagers, if the error message could give a clue what might be wrong or how > to solve it. > > Trying to be constructive, I thought maybe fedora-packager-setup or > fedora-cert might give me some more info. However... > > $ fedora-packager-setup > Setting up Fedora packager environment > Traceback (most recent call last): > File "/usr/bin/fedora-packager-setup", line 123, in <module> > main() > File "/usr/bin/fedora-packager-setup", line 103, in main > if fedora_cert.certificate_expired(): > File "/usr/lib/python2.7/site-packages/fedora_cert/__init__.py", line 83, > in certificate_expired > if my_cert.has_expired(): > AttributeError: 'NoneType' object has no attribute 'has_expired' > > $ fedora-cert > Traceback (most recent call last): > File "/usr/bin/fedora-cert", line 85, in <module> > main(opts) > File "/usr/bin/fedora-cert", line 52, in main > if fedora_cert.certificate_expired(): > File "/usr/lib/python2.7/site-packages/fedora_cert/__init__.py", line 83, > in certificate_expired > if my_cert.has_expired(): > AttributeError: 'NoneType' object has no attribute 'has_expired' > > > This seems to be a >1 year old bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1412260 > > If I remove ~/.fedora.upn (why?) and re-run fedora-packager-setup, I > apparently get a new ~/.fedora-server-ca.cert, but the mysterious "invalid > path" error remains. > > Any pointers? > > Thanks > > Tim > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx -- Regards, Chenxiong Qi _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
