Description of problem:
Ref: upstream bug: https://bugs.launchpad.net/bugs/245634
The fix to upstream bug #230223 has an undesirable feature .. it breaks
launchpad-login because there is no CA Certificate on the Fedora 9 system for
launchpad-login does not fail on Fedora 8 because python-pycurl is not
installed. I can circumvent the problem by uninstalling (--nodeps)
python-pycurl on the Fedora 9 system but this is really a very temporary solution.
Lokk at my upstream bug report. Apparently, debia has a "ca-certificates"
package which contains certificates for common CAs. What is the solution for
Version-Release number of selected component (if applicable):
Fedora 9, bzr-1.5
Suggestion: Create a new Fedora rpm which has commonly used ca-certificates
like debian does: http://packages.debian.org/unstable/misc/ca-certificates
Given that debian has done all the work, this should be a simple solution to
I attempted to use the ca-certificates rpm from F10 development but it
conflicts with openssl on F9. This ca-certificates rpm needs to be re-done for F9.
This is a bazaar bug. Will add more information on the upstream bug. If you'd
like to have ca-certificates backported to F9, please open a new bug against
that package to see what the maintainer thinks.
I believe there is no need for the backport ... I beleive that openssl in Fedora
8/9 already provide the CA Certs in /etc/pki/tls/certs/ca-bundle.crt
The question is, how does whatever is checking the CA cert know to look there?
[debian has a different location]
more over at bzr
Q: When you added the requirement for pycurl to the bzr package, did you do any
testing to see if lp-login worked?
The message is from the curl (libcurl) package.
I believe that the problem is that launchpad's CA cert is missing but I am going
to close this report.
I am not sure if the fix is to backport the ca-certificates package or fix
openssl on Fedora 9.