Re: [yocto] Git clone over http broken on git.yoctoproject.org
On Thu, 12 Dec 2013, michael_e_br...@dell.com wrote: HOWEVER, if I use "https" instead of "http", it all WORKS OK. NOTE: Some repos work over http, some don't. Working: meta-selinux, yocto-autobuilder, for example. You're using a HTTP proxy, right? I suspect the http vs https difference is then simply because git will use completely different ways to go through the proxies for the different protocols. git clone --mirror http://git.yoctoproject.org/git/poky.git Initialized empty Git repository in /home/michael_e_brown/yocto/poky.git/ error: RPC failed; result=52, HTTP code = 100 I think this means that git gets a HTTP 100 continue response back but then nothing else, which indicates a problem in your network or proxy. Can you use git fine over this http+proxy against other git repos out in the wild? Which git + libcurl versions are you using? -- / daniel.haxx.se ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Enabling SFTP on libcurl package
On Fri, 19 Jul 2013, Saddam Quirem wrote: Since you're the author and maintainer of cURL, I was wondering why SSH is not yet supported in the Yocto cURL package and if it will be? Sorry, I'm the maintainer of the actual *upstream* curl project, I don't have anything to do with the current recipe in Yocto. -- / daniel.haxx.se ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Enabling SFTP on libcurl package
On Thu, 18 Jul 2013, squirem wrote: Seems libssh2 is not included in oe-core and meta-oe, you should add recipe for libssh2 firstly. I've never personally written a bitbake recipe, but I guess it's worth trying. If I can't figure it out I may try to see if someone more knowledgeable might have interest in the library. libssh2 is a rather standard autotools-using library that itself depends on a crypto backend (OpenSSL or gcrypt). There should be plenty of recipes for similar libs to get inspiration from. -- / daniel.haxx.se (maintainer of libcurl and libssh2...) ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Upstream-Status finally @ 100%
On Wed, 8 Feb 2012, Saul Wold wrote: If you can fix those issues, since we can't address all of them initially or be experts in all upstreams, we would be very grateful to remove 1 or 2 more patches. Yes, I started looking into that. -- / daniel.haxx.se ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Upstream-Status finally @ 100%
On Wed, 8 Feb 2012, Saul Wold wrote: If the author of curl would like to review and/or implement modification for OE that would be awesome, feel free to share the patches with them. I am the maintainer of curl. The curl patches Björn mentioned are clearly not written in way intended to be "upstreamable" so they cannot be accepted by the curl project and nobody has tried to. This said, at least one of the patches fixes a problem that still exists upstream but the yocto patch [*] is made in such a hard-coded way it'd have to be seriously edited to get accepted. The flaw has not even been discussed with or mentioned to the curl project AFAICR... So, room for improvements! [*] = http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-support/curl/curl/noldlibpath.patch -- / daniel.haxx.se___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
