Re: git fetch fails because of gnutls_handshake
On Sat, 29 Oct 2016, Chris Jones wrote: > On 29 Oct 2016, at 4:27 pm, Lawrence Velázquezwrote: [...] > > Our Trac has never automatically subscribed anyone except ticket > > reporters. Owners and Cc need to be set explicitly. I don't know if > > other projects do things differently. > > I have fallen foul of this a few times, as pretty much all other issue > tracking systems i have used indeed automatically adds anyone who sends > a reply, to receive any future comments. Trac is a bit odd i would say > in this regard to not do this. > > But its true trac has never done this, so its not a recent change. Though if the new "Cc me" button were any smaller, it would be considered a web bug. :-) Fred Wright ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] #52645: qt5-qtbase build problem
On Sun, Oct 30, 2016 at 2:07 AM, CeDeROMwrote: > On Sun, Oct 30, 2016 at 2:04 AM, MacPorts wrote: >> Comment (by MarcusCalhoun-Lopez): >> Are you by chance using libressl?[[BR]] > Yes! LibreSSL in use. Will replace with OpenSSL and report back :-) I can confirm this is the LibreSSL + QT issue! Thanks!! -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] #52645: qt5-qtbase build problem
On Sun, Oct 30, 2016 at 2:04 AM, MacPortswrote: > Comment (by MarcusCalhoun-Lopez): > Are you by chance using libressl?[[BR]] Yes! LibreSSL in use. Will replace with OpenSSL and report back :-) Why QT does not support LibreSSL? Is it QT or MacPorts? -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git fetch fails because of gnutls_handshake
On Saturday October 29 2016 17:58:25 Chris Jones wrote: >But its true trac has never done this, so its not a recent change. Probably one of those things you start noticing again when enough other things change (another bug tracker I frequent also had a big overhaul). ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git fetch fails because of gnutls_handshake
On 29 Oct 2016, at 4:27 pm, Lawrence Velázquezwrote: >> On Oct 29, 2016, at 11:17 AM, René J.V. Bertin wrote: >> >> Does trac no longer auto-subscribe new participants? > > Our Trac has never automatically subscribed anyone except ticket > reporters. Owners and Cc need to be set explicitly. I don't know if > other projects do things differently. I have fallen foul of this a few times, as pretty much all other issue tracking systems i have used indeed automatically adds anyone who sends a reply, to receive any future comments. Trac is a bit odd i would say in this regard to not do this. But its true trac has never done this, so its not a recent change. Chris > > vq > ___ > macports-dev mailing list > macports-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git fetch fails because of gnutls_handshake
> On Oct 29, 2016, at 11:17 AM, René J.V. Bertinwrote: > > Does trac no longer auto-subscribe new participants? Our Trac has never automatically subscribed anyone except ticket reporters. Owners and Cc need to be set explicitly. I don't know if other projects do things differently. vq ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git fetch fails because of gnutls_handshake
On Saturday October 29 2016 16:44:29 Clemens Lang wrote: > I will veto this code for the reasons outlined in Trac. What made you think I was even considering wasting my own time to propose such a change? Does trac no longer auto-subscribe new participants? ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git fetch fails because of gnutls_handshake
On Saturday October 29 2016 09:57:35 Lawrence Velázquez wrote: >> I haven't yet found any indication that the port process might be using the >> OpenSLL library from port:openssl, or indeed any other related library. > >What OS are you running? Have you set DYLD_LIBRARY_PATH or something else? No, no such things either. OK, I must admit this is on Linux; I omitted that to avoid too quick "we don't support that replies" O:-) But my base build is pretty much stock and apart from this example (git) which apparently bit some users on OS X too I have no issues at all with fetching (or indeed most other functions). Now that's out: %> /usr/bin/curl --version curl 7.35.0 (x86_64-pc-linux-gnu) libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smtp smtps telnet tftp Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP %> /opt/local/bin/curl --version curl 7.45.0 (x86_64-pc-linux-gnu) libcurl/7.45.0 OpenSSL/1.0.2j zlib/1.2.8 Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp Features: IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP UnixSockets My system gnutls is kind of old though: %> /usr/bin/gnutls-cli -version /usr/bin/gnutls-cli (GnuTLS) 2.12.23 Packaged by Debian (2.12.23-12ubuntu2.5) but from what I understand gnutls itself isn't the likely culprit? I may investigate the workaround I proposed on trac, falling back to using an external curl command. R. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git fetch fails because of gnutls_handshake
> On Oct 29, 2016, at 9:54 AM, René J.V. Bertinwrote: > > On Saturday October 29 2016 15:32:19 Clemens Lang wrote: > > hi, > >> That's https://trac.macports.org/ticket/51516. > > Ah, thanks. > >>> What could this be due to? >> >> Your system libcurl is too old to talk modern SSL, or you have modified >> your system libcurl to use a different library, or you have built >> MacPorts against a custom copy of libcurl that uses a SSL library that >> cannot talk to kernel.org. > > Erm, I don't think so (3x if I count correctly). Pextlib is linked to the > system libcurl (and libssl) which I haven't modified, and the system curl > command (which uses that same library) works correctly. That's why I asked, I > have no clue how this can happen. > > I haven't yet found any indication that the port process might be using the > OpenSLL library from port:openssl, or indeed any other related library. What OS are you running? Have you set DYLD_LIBRARY_PATH or something else? vq ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git fetch fails because of gnutls_handshake
On Saturday October 29 2016 15:32:19 Clemens Lang wrote: hi, >That's https://trac.macports.org/ticket/51516. Ah, thanks. >> What could this be due to? > >Your system libcurl is too old to talk modern SSL, or you have modified >your system libcurl to use a different library, or you have built >MacPorts against a custom copy of libcurl that uses a SSL library that >cannot talk to kernel.org. Erm, I don't think so (3x if I count correctly). Pextlib is linked to the system libcurl (and libssl) which I haven't modified, and the system curl command (which uses that same library) works correctly. That's why I asked, I have no clue how this can happen. I haven't yet found any indication that the port process might be using the OpenSLL library from port:openssl, or indeed any other related library. R. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: git fetch fails because of gnutls_handshake
Hi, On Sat, Oct 29, 2016 at 02:48:32PM +0200, René J.V. Bertin wrote: > Hi, > > I'm seeing this on one of my systems (haven't been able to try others yet): > > {{{ > DEBUG: Executing org.macports.fetch (git) > ---> git-2.10.1.tar.gz doesn't seem to exist in > /opt/local/var/macports/distfiles/git > ---> Attempting to fetch git-2.10.1.tar.gz from > https://www.kernel.org/pub/software/scm/git/ > % Total% Received % Xferd Average Speed TimeTime Time > Current > Dload Upload Total SpentLeft Speed > 100 178 100 1780 0419 0 --:--:-- --:--:-- --:--:-- 418 > 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 > DEBUG: Fetching distfile failed: gnutls_handshake() failed: Handshake failed > }}} > > As far as I can tell the fetch procedure uses a curl function provided > by Pextlib, which in turn uses the host's gnutls libraries. This might > suggest that those are outdated w.r.t. www.kernel.org, but when I use > the system curl command the fetch completes without problems. That's https://trac.macports.org/ticket/51516. > What could this be due to? Your system libcurl is too old to talk modern SSL, or you have modified your system libcurl to use a different library, or you have built MacPorts against a custom copy of libcurl that uses a SSL library that cannot talk to kernel.org. -- Clemens ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
git fetch fails because of gnutls_handshake
Hi, I'm seeing this on one of my systems (haven't been able to try others yet): {{{ DEBUG: Executing org.macports.fetch (git) ---> git-2.10.1.tar.gz doesn't seem to exist in /opt/local/var/macports/distfiles/git ---> Attempting to fetch git-2.10.1.tar.gz from https://www.kernel.org/pub/software/scm/git/ % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 178 100 1780 0419 0 --:--:-- --:--:-- --:--:-- 418 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 DEBUG: Fetching distfile failed: gnutls_handshake() failed: Handshake failed }}} As far as I can tell the fetch procedure uses a curl function provided by Pextlib, which in turn uses the host's gnutls libraries. This might suggest that those are outdated w.r.t. www.kernel.org, but when I use the system curl command the fetch completes without problems. For now I have fortunately only seen this error with kernel.org . What could this be due to? Thanks, René ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev