On an i386-architecture chroot running under an amd64 vm running under
a MacBook Pro ( :D ), the following command reproduced at least half
the time I ran it:
$ w3m -T text/html -dump libX11-keys.proc >/dev/null
The GC would attempt to complain about allocating large-sized blocks,
and this would
Package: w3m
Version: 0.5.3-16
Severity: important
Tags: patch
Debian has a patch to w3m, 080_gc72.patch, which appears to attempt to
fix w3m's behavior for wrapping the warning handler in versions >= 7.2
of the garbage collector, but instead breaks it very severely.
Specifically, the wrapping fu
On Mon, Jul 29, 2013 at 5:46 AM, Vladislav Kurz
wrote:
> Is ther any particular reason why gnuTLS is used by default, and why
gnuTLS does not support NTLM?
The reason is that the code written to support NTLM comes from when wget
only supported OpenSSL,
and hadn't been updated. Further, GnuTLS didn
On Thu, Jun 13, 2013 at 8:20 AM, Christopher Huhn, GSI wrote:
> So the documentation is completely wrong here: '-O file' has the same
> timestamp of the last change of the web
> page as the naked wget and behaves clearly different from '-O - > file' here.
While it's true that -O file gets the t
On 12/19/2012 02:50 PM, David Starner wrote:
> It's been six years, and wget still can't read the locale to know that
> UTF-8 filenames shouldn't be mangled? An 8-year old document,
> http://hektor.umcs.lublin.pl/~mikosmul/computing/articles/linux-unicode.html
> , notes that "some GNOME application
I'm not sure how frequently Giuseppe, Wget's current maintainer, checks
the bug list, and I don't know whether he's CC'd on it, so he's probably
just unaware. I'd say, ping the bug-w...@gnu.org mailing list
(subscribing first would be a good idea).
-mjc
On 09/27/2012 08:05 PM, Frank Heckenbach wr
Can you confirm the problem is actually related to wget, as opposed to
gnutls? Your first post seems to indicate that some versions of gnutls
are having the same problem. Wget from stable used openssl exclusively,
IIRC. I believe curl uses openssl, too.
You said you played with different versions
On 07/18/2012 11:23 PM, Russell Stuart wrote:
> Package: wget
> Version: 1.12-2.1
Wget 1.12 doesn't support HTTP/1.1. It's inappropriate for the server to
send chunked content in response to an HTTP/1.0 request.
For HTTP/1.1 and chunked support, try a newer version of Wget, such as
1.13.4 (availa
(2011年12月30日 12:56), Jacob Burckhardt wrote:
> % /usr/bin/wget --output-document=- debian.org
> -k can be used together with -O only if outputting to a regular file.
>
> Since I did not use -k, please make wget not imply that I used -k.
Wget will also print that message if you have the equivalent
(07/12/2011 05:07 PM), jida...@jidanni.org wrote:
> X-debbugs-Cc: bug-w...@gnu.org
> Package: wget
> Version: 1.12-3.1
> Severity: wishlist
>
> Have you checked out the man page lately?
> The simple conversion from Info leaves some atrocious junk. Have a slice:
>
>server response, save: s
On 03/23/2011 01:18 PM, Ekin Akoglu wrote:
> This is the command I used:
>
> wget http://slax.speedymirror.com/iso/slax-6.1.2.iso
>
> Then the computer hangs. The file is about 192 MB. Maybe it might be
> related to that bug but I remember once I encountered this when getting
> a pdf file which i
On 03/23/2011 08:21 AM, Ekin Akoglu wrote:
> I managed to reproduce the situation with debugging options. It turned
> out that wget did not print any output either to stdout or to the log
> file. Whenever I turn on my computer and run wget this seems to happen.
> I managed to use "top" in terminal
I've just submitted bug 614714, which might be of interest to followers
of this bug. I mention it here because it seems likely to affect some of
the same people that this bug affects (though this bug probably masks
that one), provided that they tend to use bash and/or readline with
vi-mode bindings
Package: bash
Version: 4.1-2ubuntu4
Severity: normal
Tags: patch
(Forwarded from my bug report against Ubuntu 10.10 (bash 4.1-2ubuntu4,
copy/pasted here)
Binary package hint: bash
This is on Ubuntu 10.10. It very likely still remains in Natty.
I use bash with a prompt that is derived from the c
I can't reproduce this problem on Ubuntu using wget_1.12-2.1.
However, try adding the option --trust-server-name to see if that makes
a difference. A change went into wget to prevent it from letting the
server take too much control over how files are named, though
--content-disposition overrides t
Michael S Gilbert wrote:
> package: wget
> version: 1.12-1
> severity: important
> tags: security
>
> hi,
>
> wget implements a forked version of libntlm. in order to provide
> timely security support (and to reduce some of the burden on the
> security team), it would be very desirable (if possi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giuseppe Iuculano wrote:
> Package: wget
> Version: 1.11.4-4
> Severity: grave
> Tags: security
>
>
> Hi,
> the following CVE (Common Vulnerabilities & Exposures) id was
> published for wget.
>
> CVE-2009-3490[0]:
> | GNU Wget before 1.12 does not p
Hamish wrote:
> Yes, I'm just downloading a single file. I'm not interested in the
> recursive nature of -r, I'm only interested in the overwriting nature
> of it. I want to download the latest version of the file in place and
> have it immediately go live.
> So I guess I'd use ` --output-docume
Hamish wrote:
> Package: wget
> Version: 1.11.4-2
> Severity: minor
>
> Hi,
>
> when using wget with the -r and -O options you get a warning message:
> """
> WARNING: combining -O with -r or -p will mean that all downloaded content
> will be placed in the single file you specified.
> """
>
> (in
jida...@jidanni.org wrote:
> Package: wget
> Version: 1.11.4-4
> Severity: wishlist
> X-Debbugs-cc: bug-w...@gnu.org, w...@sunsite.dk
>
> man/info page says
>
>The time-stamping in GNU Wget is turned on using `--timestamping'
> (`-N') option, or through `timestamping = on'
>direc
Nigel Horne wrote:
> Update: FYI curl, using http://curl.haxx.se/programs/curlmirror.txt,
> works correctly.
Curl works exactly the same way as wget in downloading those files, and
any program that parses the link out of its results, but does not
understand JavaScript, would act like Wget does, fo
Nigel Horne wrote:
> Use your favourite browser to visit the page
> http://web.archive.org/web/20080207072124/http://barry-white.members.beeb.net/
> and look at its source and you'll find URLs such as
> http://web.archive.org/web/20080207072124/http://barry-white.members.beeb.net/registers/pr_birch
jida...@jidanni.org wrote:
>> "A" == Andrew M Bishop writes:
> A> Hi,
>
>>> $ wwwoffle http://www.中時健康.tw/
>>> Requesting: http://www./
>>> Only firefox gets it right:
>>> http://www.xn--fiqx7ci2wwkh.tw/
>
> A> How do you do that? I can't type multi-byte chars in xterm.
>
> with package sc
It would help us to determine the importance of this feature, if you
could supply a concrete usage scenario. Presumably you're actually in a
situation where this would be helpful, so perhaps you can describe a
little more about what you're currently doing?
--
Micah J. Cowan
Programmer, musician,
Michael Gebetsroither wrote:
> Screen does not start, but just returns and does nothing, if started
> from an xterm which is itself started from another screen.
That is the expected behavior. Consider adding -m to ignore $STY, which
is there specifically to let screen communicate with the
currentl
Nicolas Duillier wrote:
> Nico Golde [Sat, 17 Jan 2009 19:28:15 +0100]:
>> * Dmitry Baryshev [2009-01-17 18:41]:
>>> $ LC_ALL=C wget
>>> [32]ftp://ftp.apnic.net/apnic/whois-data/APNIC/apnic.RPSL.db.gz
>>> --2009-01-17 19:34:45--
>>> [33]ftp://ftp.apnic.net/apnic/whois-data/APNIC/apnic.RPSL.db.gz
I had been experiencing similar issues with less at one point. It turned
out to be an interoperation between a defect in less and a defect in
screen. We have a fix for that one upstream; it's possible that emacs
could have a similar issue:
http://git.savannah.gnu.org/gitweb/?p=screen.git;a=commitdi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Dickinson wrote:
> Screen does not necessarily honour backspace from the terminal it is in.
> Backspace works fine without screen in all these cases (e.g. running in a
> serial console, in lxterminal, a few other cases I don't remember). Thi
Tracking upstream at https://savannah.gnu.org/bugs/index.php?25377
--
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
GNU Maintainer: wget, screen, teseq
http://micah.cowan.name/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsub
https://savannah.gnu.org/bugs/index.php?24203
--
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
GNU Maintainer: wget, screen, teseq
http://micah.cowan.name/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tags: upstream
Tracking upstream at https://savannah.gnu.org/bugs/index.php?24152
- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
GNU Maintainer: wget, screen, teseq
http://micah.cowan.name/
-BEGIN PGP SIGNATURE-
Vers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nigel Horne wrote:
> Please add an option to pass the file through ClamAV. If the file is
> infected it isn't saved.
That's not very general, and isn't a particularly useful feature anyway,
since one can very easily run the files through ClamAV _after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nico Golde wrote:
> Hi,
> sometimes it would be nice to ignore robots.txt. What about adding an option
> to ignore this file?
It has one. :) Check the info manual (the manpage is not the complete
documntation). You want -e robots=off
- --
Micah J. Co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micah Cowan wrote:
> Nico Golde wrote:
>> sometimes it would be nice to ignore robots.txt. What about adding an option
>> to ignore this file?
>
> It has one. :) Check the info manual (the manpage is not the complete
> do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fernando Mitio Yamada wrote:
> Resolving ardownload.adobe.com... 204.2.241.154, 204.2.241.155
> Connecting to ardownload.adobe.com|204.2.241.154|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 49404752 (47M) [applicatoin/x-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trent W. Buck wrote:
> I've been (ab)using the :idle handler to lock my screen, similar to
> X's xscreensaver or xautolock + xlockmore:
>
> idle 1800 lockscreen# "screensaver" lockout
>
> I'd like to set this timeout to be much shorter (s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tags: upstream
Ryan Niebur wrote:
> I want to be able to have the session name in my caption.
> And I'm not the only person who wants to be able to do that.
> But there's no way to do it, so I made a patch.
Tracking upstream at https://savannah.gnu.o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tags: upstream
It looks to me as if the fault is in the terminfo description for screen.
Screen does in fact understand ^N/^O, and processes them according to
ISO-2022. It does not simply pass them through, but rather processes
them itself, to invoke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This behavior has been addressed in the current development sources, but
apparently didn't go in for 1.11.
Tracked upstream at https://savannah.gnu.org/bugs/index.php?23238. The
fix was http://hg.addictivecode.org/wget/mainline/rev/85298083bf02/
- --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Knoth wrote:
> On Tue, May 13, 2008 at 10:16:38AM -0700, Micah Cowan wrote:
> Good news. Is there already a planned release date? I see the bug is
> still open, so I guess the corresponding changes haven't hit the RCS
> yet.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adrian Knoth wrote:
> Hello,
>
> wget currently prefers IPv4 over IPv6 (see the manpage, command line
> switch --prefer-family).
>
> Though IPv4 might practically solve some issues with broken IPv6
> configurations, an IPv4 precedence would artific
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Goerzen wrote:
> 1) If starting a recursive download, I may have a local page giving
> the URLs to download, rather than a remote one
Note that this one can be solved with the use of --force-html
- --input-file=<...>
- --
Micah J. Cowan
Programm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tags: wontfix
The new version downgrades -r or -p with -O to a warning, but keeps -N
as an error. The reason is that it has never worked (that is, -N has
never properly timestamped the target of -O, since -O always alters the
timestamp (by clobbering
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raphael Geissert wrote:
>> Because -O doesn't mean "use this filename", it means "redirect output
>> to this file", rather like the shell does (see the manpage).
>
> The thing is that it can be interpreted in different ways, maybe it could be
> more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raphael Geissert wrote:
> Package: wget
> Version: 1.11.1-1
> Severity: important
>
> A few days ago I updated to the latest version of the package and it silently
> broke some data updating scripts.
>
> wget is executed like this:
>> wget -N -O foo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Wise wrote:
> On Fri, 2008-04-04 at 21:02 -0700, Micah Cowan wrote:
>
>>> It looks like it is finally fixed! Thanks for the followup, closing :)
>> Maybe not. This bug sounds a lot like one we're tracking upstream:
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> From:
> Paul Wise <[EMAIL PROTECTED]>
> On Fri, 2008-03-28 at 20:55 +0100, Noèl Köthe wrote:
>
>> I'm not able to reproduce this (old:() problem report since some hours
>> with wget 1.11.1-1 and this commandline:
>>
>> wget -r -np -c
>> http://meeti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Noèl Köthe wrote:
>> what I did was capture a HTTP response using netcat and then feed it to wget
>> using netcat
>>
>> cat capture | nc -lp 8083 &
>> wget http://localhost:8083/foo
>>
>> netcat didn't successfuly see the end of the file. - I think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mathieu Malaterre wrote:
> Thanks. You can close the bug.
>
> Sorry for the noise.
No worries. :)
- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http://micah.cowan.name/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mathieu Malaterre wrote:
> I still do not believe this has anything to do with the server, if you
> have a couple of seconds please try this file instead:
>
> http://www.medical.philips.com/us/company/connectivity/assets/docs/dicomcs/ENsphere%2520DICO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mathieu Malaterre wrote:
> $ wget -N --force-html -i dummy.txt
>
> --20:03:04--
> http://www.medical.philips.com/us/company/connectivity/assets/docs/dicomcs/ENsphere%20DICOM%203%20Conformance%20Statement.pdf
>=> `ENsphere DICOM 3 Confor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Antonio Messina wrote:
> wget manpage documents the "--ignore-case" option which in version
> 1.10.2-3 of wget does not exists (btw, version 1.20.2+1.11.beta1-1 in
> experimental does have support for the --ignore-case option).
>
> Please, correct the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nico Golde wrote:
> Then the manual of wget really sucks, searching for robots
> returns three matches and none these is related to this
> option.
Only if you're searching the man page (which, as I already mentioned, is
not the full manual). Use the
Paul Wise wrote:
> On Thu, 2007-11-22 at 22:36 -0800, Micah Cowan wrote:
>
>>> It would be nice if wget -O just accepted directories.
>> It'd be nice if you specified what -O should do if you handed it a
>> directory... or maybe you're looking for the -P
Paul Wise wrote:
> It would be nice if wget -O just accepted directories.
It'd be nice if you specified what -O should do if you handed it a
directory... or maybe you're looking for the -P option (possibly with -nd)?
--
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http:/
The patch is not an appropriate fix. The reason this behavior was chosen
by default, is that printing control characters from the C1 control set
commonly used by the ISO character sets is known to corrupt terminal
output; whereas producing invalid UTF-8 will not do so. Of the two
evils, the current
Vincent Danjean wrote:
> I fully understand this. Debian can have some /bin/sh (such as posh)
> that does not have 'type' (nor command -v) and debian has /bin/bash
> installed on all systems, so will keep this patch (in the Debian package).
>
> But I've no problem at all if you close this bug with
Micah Cowan <[EMAIL PROTECTED]> added the comment:
Vincent Danjean wrote:
> This is the Debian bug #447094 ( http://bugs.debian.org/447094 )
> The short story is that 'type' is not allowed (by POSIX) in
> #!/bin/sh scripts (in particular hgmerge)
It's a bit misle
Tags: moreinfo
> I don't know whether this behaviour is intended or not: during recursive
> retrieval, when wget has to decide whether to enqueue or not a discovered
> url, it scans accept/reject lists with u->file, instead of u->url.
> as a result, it is often wrong about what is to be crawled.
Debian Bug Tracking System wrote:
>> This operation fails on Ubuntu:
>>
>> $ /bin/sh -c 'if false; then d="${foo/bar}"; fi'
>> /bin/sh: Syntax error: Bad substitution
>>
>> When used with other POSIX shells it succeeds. While semantically the
>> variable reference ${foo/bar} is not valid,
Package: wget
Version: 1.10.2-3
The --ignore-case feature is documented in Debian's wget.texi (and the
generated manpage), but this feature is not actually present in wget.
This probably got slurped in by accident when the GFDL invariant changes
got pulled in.
--
To UNSUBSCRIBE, email to [EMAI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Trent W. Buck wrote:
> I notice that when you prematurely close wget's output stream when
> writing to stdout, wget gives a misleading error message:
I've confirmed that this occurs for 1.10.2, and not for the current
version of wget in the reposito
tags 162283 + upstream
forwarded 162283 https://savannah.gnu.org/bugs/index.php?20522
thanks
I have not attempted to reproduce this bug; however, if the behavior is
still present in wget, I would wish to address it. Therefore, to make
sure I don't forget about it, I've added it to our upstream bug
Noèl Köthe wrote:
> Am Freitag, den 25.07.2003, 21:26 -0400 schrieb Joey Hess:
>> It seems that if the filename is changed, wget's -N timestamp and size
>> checking does not work. Or rather, it looks for a local file with
>> whatever name wget would have saved the file as without the -O, and if
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick Shaforostoff wrote:
> On Среда 11 июля 2007, Noèl Köthe wrote:
>> afaik there are no manpage translation of wget.
>>
>> I will ask the upstream author how they would like to get
>> translations.
>
> Already tried to do that. It seems they requ
ssed to strace, this does not occur.
This was discovered by a debug hook in bzr. There are reports this
problem doesn't happen in dapper.
--
Micah Cowan comments:
This doesn't seem to be a bug. From strace(1), -f option:
If the parent process
Migration to GNU install-info in Lenny was announced on debian-dpkg, by
Nicolas François:
http://lists.debian.org/debian-dpkg/2007/04/msg00031.html
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0704.2/0549.html
Follows a trivial patch to check for RLIMIT_CPU to 0 in the right place.
diff -urN linux-2.6.20.3.orig/kernel/sys.c linux-2.6.20.3/kernel/sys.c
--- linux-2.6.20.3.orig/kernel/sys.c 2007-03-13 20:27:08.0 +0200
+++ linux-2.6
Package: kernel
This is in 2.6.20-3 and (Ubuntu) 2.6.20-15.
Full details may be found on the zsh-workers thread, here:
http://www.zsh.org/mla/workers/2007/msg00200.html
A bug for Ubuntu on launchpad is at
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/107209
The following be
current CVS, to resolve an issue with multiple frees (closes Malone
+bug #58256).
+
+ -- Micah Cowan <[EMAIL PROTECTED]> Fri, 6 Apr 2007 11:33:50 -0700
+
gawk (1:3.1.5.dfsg-4) unstable; urgency=low
* doc/gawk.info, doc/gawk.texi, doc/gawkinet.info, doc/gawkinet.texi:
only in patch2:
unch
igit or
when parameter is followed by a character that could be interpreted as
part of the name. The matching closing brace shall be determined by
counting brace levels, skipping over enclosed quoted strings, and
command substitutions.
---
In addition to bash I've checked Solaris /bin/sh
On Thu, 1 Dec 2005 07:48:47 +1100 Herbert Xu wrote:
> I agree with David's interpretation. The standard has been changed to
> explicitly state that $((x ...) needs to be supported. I will be
> implementing this soon.
Any progress in this department? I'm accustomed to relying on constructs
such a
> Job control is now mandatory in POSIX... perhaps it should be enabled by
> default?
Er, yeah. /Support/ for job control is mandatory, and -m is a standard
option. Sorry about that. ...still, it seems to be affecting things in
an unintuitive way, and one that still doesn't occur.
Note that using
> $ dash -c 'dash; read arg'
> dash$ exit
> [1] + 683 suspended (tty input) dash -c 'dash; read arg'
> $ kill %1
> [1] + 820 terminated dash -c 'dash; read arg'
> $
This behavior looks like what happens when a non-foreground process
tries to read from the terminal. Compare the result of '( re
> # non-interactive shell
> $ dash -c 'dash; read arg'
> dash$ exit
> [1] + 683 suspended (tty input) dash -c 'dash; read arg'
> $ kill %1
> [1] + 820 terminated dash -c 'dash; read arg'
> $
>
> # interactive shell
> $ dash -i -c 'dash; read arg'
> dash$ exit
> read this!
> $
adding the '-m'
75 matches
Mail list logo
