Re: [Bug-wget] wget alpha release 1.14.96-38327
Hello, Am Dienstag, den 24.12.2013, 18:06 +0100 schrieb Giuseppe Scrivano: I could drop 3 documentation patches. The Debian bugtracker does not have additional patches. I don't track which wget upstream patch fixed which Debian bug if this is your request. would you mind to send the patches to the ML, either by git send-email or attaching the output git format-patch? It helps to get more eyes on them. Get these patches upstream will make things easier for you as well, you will have less stuff to rebase when a new version is out. Sure, but the 3 additional patches are included in 1.14.96-38327. wget release 1.14 in Debian is carrying the following patches: http://patch-tracker.debian.org/package/wget/1.14-5 and the 1.14.96-38327 reduces them by 3: http://patch-tracker.debian.org/package/wget/1.14.96.38327-2 They are only documentation patches. I hope I didn't misunderstand your request again. Maybe only a small documentation fix but its minor. https://savannah.gnu.org/bugs/index.php?33826 As a friend of release early and release often: Go for it;) and the wget user will get a lot of fixes from the 16 month of development. we definitely need a better model than let's release when we think it is ok :-) Should we move to a release every 3/6 months? 12 month would be fine too but I don't have a strong option on this. I don't think that doing it more often would make any sense, given the activity that usually wget has. ACK. -- Noël Köthe noel debian.org Debian GNU/Linux, www.debian.org signature.asc Description: This is a digitally signed message part
[Bug-wget] Debian wget bug #701032 and #709637 [was: Re: wget alpha release 1.14.96-38327]
Hello, Am Mittwoch, den 25.12.2013, 01:13 +0530 schrieb Darshit Shah: I tried going through the Debian bugtracker just now. Didn't see any patches available which haven't already been applied. However there are a couple of bug reports on it that we must look into. I'll try and reproduce them if possible. Specifically, I'm looking at bug reports #701032 and #709637. :) Good. @nok: It would be very nice of you if you could report these as bugs in the upstream bug tracker. I know they're both marked as non-reproducible in your system. While I'll attempt to reproduce #701032, there seems to be a definite bug in wget based on the extensive logs provided in #709637. Sure. http://bugs.debian.org/709637 wget: Credentials in URL not supported (server depended) is now here: https://savannah.gnu.org/bugs/index.php?41002 and http://bugs.debian.org/701032 wget tries to reuse connection despite http/1.0 and no connection: keep-alive you find here: https://savannah.gnu.org/bugs/index.php?41003 Have a nice day Noël signature.asc Description: This is a digitally signed message part
[Bug-wget] wget-1.14 not compatible with ppc64le architecture
Hi, IBM is introducing a new architecture - ppc64le (powerpc 64-bit Little Endian) and I was looking at building wget-1.14 on our ppc64le environment and I found that wget-1.14 would require a patch to either config.guess or needs to pick up the latest automake (1.13.4 or above) version from upstream. The latest config.guess which has the ppc64le changes can be found at : http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD. Can you please spin a new version which would support ppc64le ? Please do let me know if you will be picking up the patches from upstream or you would require local patches to be provided. Thanks, Madhu Pavan Kothapally.
[Bug-wget] [PATCH] Re: ping (Re: I am seeing problems with wget-1.14.96-38327 doing gnutls secure sessions.)
Am Donnerstag, 26. Dezember 2013, 01:26:00 schrieb SciFi:
ping
I guess I need to remind about this bug,
I haven't opened a real bugzilla report, tho.
Shall I?
FWIW, I've changed to the timeout=0 setting,
which did let the httpS code work.
I'll need to have a non-infinite setting
for some projects I have that use wget.
And I've hand-applied the patch below.
No ill effects there.
Happy Holidays!
The regression has been introduced by this change:
2013-05-05 mancha manc...@hush.com (tiny change)
* gnutls.c (ssl_connect_wget): Don't abort on non-fatal alerts
received during handshake. For example, when connecting to servers
using TSL-SNI that send warning-level unrecognized_name alerts.
You could trigger it by compiling/linking with GnuTLS and using --connect-
timeout=x or -- timeout=x (x 0).
I attached a fix.
Tim
From 41f9db4f5d309d605d90613c1dd5c208be8024aa Mon Sep 17 00:00:00 2001
From: Tim Ruehsen tim.rueh...@gmx.de
Date: Thu, 26 Dec 2013 21:17:07 +0100
Subject: [PATCH] fix GnuTLS connect timeout
---
src/ChangeLog | 4
src/gnutls.c | 5 ++---
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/src/ChangeLog b/src/ChangeLog
index fe4c321..22d036c 100644
--- a/src/ChangeLog
+++ b/src/ChangeLog
@@ -1,3 +1,7 @@
+2013-12-26 Tim Ruehsen tim.rueh...@gmx.de
+
+ * gnutls.c (ssl_connect_wget): Fix connect timeout failure
+
2013-11-10 Giuseppe Scrivano gscri...@redhat.com
* options.h (struct options) [!ENABLE_THREADS]: Define jobs.
diff --git a/src/gnutls.c b/src/gnutls.c
index 9b4b1ec..4f0fa96 100644
--- a/src/gnutls.c
+++ b/src/gnutls.c
@@ -526,8 +526,7 @@ ssl_connect_wget (int fd, const char *hostname)
break;
}
- if (err = 0)
-break;
+ err = GNUTLS_E_AGAIN;
}
else if (err 0)
{
@@ -543,7 +542,7 @@ ssl_connect_wget (int fd, const char *hostname)
}
}
}
- while (err == GNUTLS_E_WARNING_ALERT_RECEIVED gnutls_error_is_fatal (err) == 0);
+ while (err gnutls_error_is_fatal (err) == 0);
if (opt.connect_timeout)
{
--
1.8.5.2
signature.asc
Description: This is a digitally signed message part.
Re: [Bug-wget] wget-1.14 not compatible with ppc64le architecture
On Thursday 26 December 2013 01:39:16 Madhu Pavan wrote:
IBM is introducing a new architecture - ppc64le (powerpc 64-bit Little
Endian) and I was looking at building wget-1.14 on our ppc64le
environment and I found that wget-1.14 would require a patch to either
config.guess or needs to pick up the latest automake (1.13.4 or above)
version from upstream. The latest config.guess which has the ppc64le
changes can be found at :
once again, you're going about this wrong. you need to fix your distro to
automatically update config.{sub,guess}. having every open source package
distro on the planet do a re-release simply to update those files is
unreasonable (and impossible).
-mike
signature.asc
Description: This is a digitally signed message part.
