Re: [SOLVED] Re: Buster wget: The certificate of 'lists.debian.org' is not trusted

On Sat 02 Oct 2021 at 08:15:59 (+0200), to...@tuxteam.de wrote: > On Fri, Oct 01, 2021 at 03:18:22PM -0500, David Wright wrote: > > [...] > > > I have a buster system that was up-to-date from the last point-release > > and kernel (2021-09-10 18:22:47). > > > > The only certificate expiration pr

Re: [SOLVED] Jessie wget: certificate not trusted

Hi, i wrote: > > The proposal of mett finally got wget to download lists.debian.org with > > certificate check enabled. > > [...] > > Now i am puzzled why this operation is not necessary on Debian 10 from > > where the file /etc/ca-certificates.conf was copie

Re: [SOLVED] Jessie wget: certificate not trusted, was: Jessie iceweasel: This Connection is Untrusted

ficates --fresh) > > Indeed this brought success with wget on the Debian 8 machine. > > $ wget https://lists.debian.org > ... > 2021-10-04 11:48:12 (7.34 MB/s) - ‘index.html’ saved [7533/7533] > $ > > I copied > /usr/share/ca-certificates > /etc/ca-certi

[SOLVED] Jessie wget: certificate not trusted, was: Jessie iceweasel: This Connection is Untrusted

Hi, mett wrote: > the final solution is: > -disable the certs with an ! before the cert name > (vi /etc/ca-certificates.conf: !DST_Root_CA_X3.crt) > -then, rebuild the cert directory (update-ca-certificates --fresh) Indeed this brought success with wget on the Debian 8 machine.

Re: [SOLVED] Re: Buster wget: The certificate of 'lists.debian.org' is not trusted

e no surprise (provided I understood correctly > above, that is): firefox and lynx don't proxy through > apt-cacher-ng. No, but look at the top of this thread: "new certification problem, this time on buster. "While looking why wget on Debian 8 does not work with lists.debi

Re: [SOLVED] Re: Buster wget: The certificate of 'lists.debian.org' is not trusted

On Fri, Oct 01, 2021 at 03:18:22PM -0500, David Wright wrote: [...] > I have a buster system that was up-to-date from the last point-release > and kernel (2021-09-10 18:22:47). > > The only certificate expiration problem I have observed (and still > observe, having taken no action) is with apt-

Re: [SOLVED] Re: Buster wget: The certificate of 'lists.debian.org' is not trusted

On Fri 01 Oct 2021 at 20:31:54 (+0200), Thomas Schmitt wrote: > > So again, for the archives: > > apt-get update > apt-get dist-upgrade > > solved the wget certificate problem with the buster installation from > juli 2020. I have a buster system that was up-to-

Re: Buster wget: The certificate of 'lists.debian.org' is not trusted

2772 Jan 28 2021 ACCVRAIZ1.crt > > -rw-r--r-- 1 root root 1972 Jan 28 2021 AC_RAIZ_FNMT-RCM.crt > > Hm. The system is one year old. Time for > apt-get update > apt-get dist-upgrade > > Afterwards i have success with > wget https://lists.debian.org/debian-user/

[SOLVED] Re: Buster wget: The certificate of 'lists.debian.org' is not trusted

Hi, i forgot to add a [SOLVED] tag to the subject of my previous mail. So again, for the archives: apt-get update apt-get dist-upgrade solved the wget certificate problem with the buster installation from juli 2020. Have a nice day :) Thomas

Re: Buster wget: The certificate of 'lists.debian.org' is not trusted

Le vendredi 01 octobre 2021 à 19:09 +0200, Thomas Schmitt a écrit : > Hi, > > new certification problem, this time on buster. > > While looking why wget on Debian 8 does not work with > lists.debian.org > i learn that it does not work on Debian 10 either: &

Re: Buster wget: The certificate of 'lists.debian.org' is not trusted

The system is one year old. Time for apt-get update apt-get dist-upgrade Afterwards i have success with wget https://lists.debian.org/debian-user/ It reports Certificates loaded: 137 Indeed ls -t /etc/ssl/certs lists a few new certificate files: VeriSign_Universal_Root_Certifica

Re: Buster wget: The certificate of 'lists.debian.org' is not trusted

On Fri, Oct 01, 2021 at 07:09:45PM +0200, Thomas Schmitt wrote: > Hi, > > new certification problem, this time on buster. > > While looking why wget on Debian 8 does not work with lists.debian.org > i learn that it does not work on Debian 10 either: > > $ wget -d

Buster wget: The certificate of 'lists.debian.org' is not trusted

Hi, new certification problem, this time on buster. While looking why wget on Debian 8 does not work with lists.debian.org i learn that it does not work on Debian 10 either: $ wget -d https://lists.debian.org/debian-user/ DEBUG output created by Wget 1.20.1 on linux-gnu. Reading HSTS

[solved] `wget' web site

>> On Sun, Sep 26, 2021 at 5:18 AM Rodolfo Medina >> wrote: >> > >> > Hi all. >> > >> > I manage to download an entire website, say www.mysite.com, with simply >> > >> > $ wget -r -l 0 www.mysite.com >> > >> > Af

Re: `wget' web site

>> On Sun, Sep 26, 2021 at 5:18 AM Rodolfo Medina >> wrote: >> > >> > Hi all. >> > >> > I manage to download an entire website, say www.mysite.com, with simply >> > >> > $ wget -r -l 0 www.mysite.com >> > >> > Af

Re: `wget' web site

I wonder, could the file pursuit pro app help here if installed on that tablet? On Sun, 26 Sep 2021, Karthik wrote: > On Sun, Sep 26, 2021 at 5:18 AM Rodolfo Medina > wrote: > > > > Hi all. > > > > I manage to download an entire website, say www.mysite.com, with

Re: `wget' web site

On Sun, Sep 26, 2021 at 5:18 AM Rodolfo Medina wrote: > > Hi all. > > I manage to download an entire website, say www.mysite.com, with simply > > $ wget -r -l 0 www.mysite.com > > After that, I can surf that web site offline with all its internal links. > Perfect. >

`wget' web site

Hi all. I manage to download an entire website, say www.mysite.com, with simply $ wget -r -l 0 www.mysite.com After that, I can surf that web site offline with all its internal links. Perfect. Now the problem comes when I want to copy that stuff into my Android tablet and read it offline too

Re: problem with wget -O

On Friday, January 29, 2021 12:20:21 PM David Wright wrote: > On Thu 28 Jan 2021 at 15:02:47 (-0500), Gene Heskett wrote: > > for a change, I am 100% with Greg W., in fact, if the file already > > exists, wget should assume a bad copy was previously obtained, and > > should

Re: problem with wget -O

merely to avoid overwriting http://master.zip with the > > > second instance of wget. The manpage expressly advises against doing > > > that: "Use of -O is not intended to mean simply "use the name file > > > instead of the one in the URL". They should jus

Re: problem with wget -O

On Thu 28 Jan 2021 at 11:10:48 (-0500), Greg Wooledge wrote: > On Thu, Jan 28, 2021 at 10:06:25AM -0600, David Wright wrote: > > Perhaps file a bug against that page. It appears that they were using > > -O merely to avoid overwriting http://master.zip with the second instance o

Re: problem with wget -O

On Thu 28 Jan 2021 at 15:02:47 -0500, Gene Heskett wrote: > Until then, lets put this thread to rest. wget was fixed by blowing away > my /home/me/.wgetrc wget wasn't fixed, but your setup was. Now we can all live happily ever after. :) > Cheers, Gene Heskett > -- > &quo

Re: problem with wget -O

On Thursday 28 January 2021 11:10:48 Greg Wooledge wrote: > On Thu, Jan 28, 2021 at 10:06:25AM -0600, David Wright wrote: > > Perhaps file a bug against that page. It appears that they were > > using -O merely to avoid overwriting http://master.zip with the > > second

Re: problem with wget -O

On Thu, Jan 28, 2021 at 10:06:25AM -0600, David Wright wrote: > Perhaps file a bug against that page. It appears that they were using > -O merely to avoid overwriting http://master.zip with the second instance of > wget. The manpage expressly advises against doing that: "Use

Re: problem with wget -O

1 17:04:23 Greg Wooledge wrote: > > > > > On Mon, Jan 25, 2021 at 04:07:33PM -0500, Gene Heskett wrote: > > > > > > gene@coyote:~/src/build$ cd .. && wget -O opencv.zip > > > > > > https://github.com/opencv/opencv/archive/master.zip Cannot &

Re: problem with wget -O

gt; to put the blame for this on the writers of documentation that involves > > downloading files. > > Having non-default options in a .wgetrc file is the point of a > .wgetrc file. :-) > > But perhaps wget should not read a config by default. This is Or alternatively, build s

Re: problem with wget -O

non-default options in a .wgetrc file is the point of a .wgetrc file. :-) But perhaps wget should not read a config by default. This is what GNU grep did by no longer supporting GREP_OPTIONS: if a user wants default options, he can create an alias (with a name different from any common utility).

Re: problem with wget -O

On Tue, Jan 26, 2021 at 01:35:09PM +0100, l0f...@tuta.io wrote: > Hi, > > 26 janv. 2021 à 10:44 de to...@tuxteam.de: > > > And thank Greg (I hope I'm not mis-assigning) for mentioning > > /etc/wgetrc and .wgetrc! > > > Let's not forget Darac Marjal who was the first (by a few minutes) actually ;)

Re: problem with wget -O

On 2021-01-26 06:27:40 -0500, Gene Heskett wrote: > The thing I don't get was that is the direct command from their > buildit page. If they did not specify a --no-config option, their buildit page is buggy. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML -

Re: problem with wget -O

On Tue, Jan 26, 2021 at 06:27:40AM -0500, Gene Heskett wrote: > The thing I don't get was that is the direct command from their buildit > page. You would think that would lead to such a common failure that it > would be documented. Nobody should have to guess that the reader has a custom ~/.wget

Re: problem with wget -O

Hi, 26 janv. 2021 à 10:44 de to...@tuxteam.de: > And thank Greg (I hope I'm not mis-assigning) for mentioning > /etc/wgetrc and .wgetrc! > Let's not forget Darac Marjal who was the first (by a few minutes) actually ;) Best regards, l0f4r0

Re: problem with wget -O

On Tue, Jan 26, 2021 at 12:30:39PM +0100, Nicolas George wrote: > Greg Wooledge (12021-01-25): > > Gene, you've been here a while, so you should know better than this. > > Where's the incentive at knowing better when one gets more help by > making no efforts? I think this is a bit unfair. I humbl

Re: problem with wget -O

Greg Wooledge (12021-01-25): > Gene, you've been here a while, so you should know better than this. Where's the incentive at knowing better when one gets more help by making no efforts? Regards, -- Nicolas George signature.asc Description: PGP signature

Re: problem with wget -O

04:07:33PM -0500, Gene Heskett wrote: > > > > > gene@coyote:~/src/build$ cd .. && wget -O opencv.zip > > > > > https://github.com/opencv/opencv/archive/master.zip Cannot > > > > > specify both -k or --convert-file-only and -O if multiple URLs >

Re: problem with wget -O

On 2021-01-26 10:40:01 +0100, Vincent Lefevre wrote: > On 2021-01-25 17:42:51 -0500, Gene Heskett wrote: > > On Monday 25 January 2021 17:04:23 Greg Wooledge wrote: > > > > > On Mon, Jan 25, 2021 at 04:07:33PM -0500, Gene Heskett wrote: > > > > gene@coyote:~/sr

Re: problem with wget -O

On Mon, Jan 25, 2021 at 05:38:04PM -0500, Gene Heskett wrote: [...] > > > posted at least once today: > > > gene@coyote:~/src/build$ cd .. && wget -O opencv.zip > > > https://github.com/opencv/opencv/archive/master.zip Cannot specify > > > both -k or

Re: problem with wget -O

On 2021-01-25 17:42:51 -0500, Gene Heskett wrote: > On Monday 25 January 2021 17:04:23 Greg Wooledge wrote: > > > On Mon, Jan 25, 2021 at 04:07:33PM -0500, Gene Heskett wrote: > > > gene@coyote:~/src/build$ cd .. && wget -O opencv.zip > > > https://githu

Re: problem with wget -O

Gene Heskett wrote: > Because synaptic says what is it the debian repo's is 10 years old? Well, at some point of time you stop repairing the car, you just drive it to the grave yard, no? It would be cheaper to upgrade because if you upgrade at the end you will have up to date system.

Re: problem with wget -O

ooledge wrote: > > > >> On Mon, Jan 25, 2021 at 03:47:03PM -0500, Gene Heskett wrote: > > > >>>> 1) You have a shell function or alias that overrides the wget > > > >>>> command. Diagnose this by running "type wget". > > >

Re: problem with wget -O

03PM -0500, Gene Heskett wrote: > > >>>> 1) You have a shell function or alias that overrides the wget > > >>>> command. Diagnose this by running "type wget". > > >>> > > >>> Interesting: > > >>> gene@coyote:~/src/bu

Re: problem with wget -O

On Monday 25 January 2021 17:04:23 Greg Wooledge wrote: > On Mon, Jan 25, 2021 at 04:07:33PM -0500, Gene Heskett wrote: > > gene@coyote:~/src/build$ cd .. && wget -O opencv.zip > > https://github.com/opencv/opencv/archive/master.zip Cannot specify > > both -k or

Re: problem with wget -O

On Monday 25 January 2021 16:48:52 Darac Marjal wrote: > On 25/01/2021 21:07, Gene Heskett wrote: > > On Monday 25 January 2021 15:55:31 Greg Wooledge wrote: > >> On Mon, Jan 25, 2021 at 03:47:03PM -0500, Gene Heskett wrote: > >>>> 1) You have a shell function

Re: problem with wget -O

On Monday 25 January 2021 16:48:52 Darac Marjal wrote: > On 25/01/2021 21:07, Gene Heskett wrote: > > On Monday 25 January 2021 15:55:31 Greg Wooledge wrote: > >> On Mon, Jan 25, 2021 at 03:47:03PM -0500, Gene Heskett wrote: > >>>> 1) You have a shell function

Re: problem with wget -O

On Mon, Jan 25, 2021 at 04:07:33PM -0500, Gene Heskett wrote: > gene@coyote:~/src/build$ cd .. && wget -O opencv.zip > https://github.com/opencv/opencv/archive/master.zip > Cannot specify both -k or --convert-file-only and -O if multiple URLs are > given, or in combination

Re: problem with wget -O

On 25/01/2021 21:07, Gene Heskett wrote: > On Monday 25 January 2021 15:55:31 Greg Wooledge wrote: > >> On Mon, Jan 25, 2021 at 03:47:03PM -0500, Gene Heskett wrote: >>>> 1) You have a shell function or alias that overrides the wget >>>> command.

Re: problem with wget -O

On Monday 25 January 2021 15:55:31 Greg Wooledge wrote: > On Mon, Jan 25, 2021 at 03:47:03PM -0500, Gene Heskett wrote: > > > 1) You have a shell function or alias that overrides the wget > > > command. Diagnose this by running "type wget". > > > > Int

Re: problem with wget -O

On Mon, Jan 25, 2021 at 03:47:03PM -0500, Gene Heskett wrote: > > 1) You have a shell function or alias that overrides the wget command. > >Diagnose this by running "type wget". > > > Interesting: > gene@coyote:~/src/build$ type wget > wget is hashed (/us

Re: problem with wget -O

-remembered piece of it. > > > direct copy/paste from the opencv build instructions html page: > > > > wget -O opencv.zip > > https://github.com/opencv/opencv/archive/master.zip wget -O > > opencv_contrib.zip > > https://github.com/opencv/opencv_contrib/archive/mas

Re: problem with wget -O

s html page: > wget -O opencv.zip https://github.com/opencv/opencv/archive/master.zip > wget -O opencv_contrib.zip > https://github.com/opencv/opencv_contrib/archive/master.zip Those look safe enough to rule out the URL quoting issue. It would be nice if you would show us the terminal session

Re: problem with wget -O

; > > > Greetings all; > > > > > > > > I don't know if this has been hashed out already, but the > > > > stretch version of wget is broken, does not accept the -O > > > > filename syntax. > > > > > > Are you sure you have the right wg

Re: problem with wget -O

t; > In file included > > from > > /home/gene/src/build/modules/python_bindings_generator/pyopencv_cust > >om_headers.h:7:0, > > Let me guess, you complained of wget trying to download the package > and now you complain, being not able to build the package :) > > Thi

Re: problem with wget -O

On Monday 25 January 2021 13:53:48 Greg Wooledge wrote: > On Mon, Jan 25, 2021 at 01:45:34PM -0500, Roberto C. Sánchez wrote: > > On Mon, Jan 25, 2021 at 01:40:19PM -0500, Gene Heskett wrote: > > > I don't know if this has been hashed out already, but the stretch > >

Re: problem with wget -O

has been hashed out already, but the stretch > > > version of wget is broken, does not accept the -O filename syntax. > > > > Are you sure you have the right wget? It works for me: > > > > root@debian:~# cat /etc/debian_version > > 9.13 > > root@debian:~# apt-

Re: problem with wget -O

on_bindings_generator/pyopencv_custom_headers.h:7:0, Let me guess, you complained of wget trying to download the package and now you complain, being not able to build the package :) This python stuff is tricky, Gene, why are you doing this to yourself?

Re: problem with wget -O

On Monday 25 January 2021 13:45:34 Roberto C. Sánchez wrote: > On Mon, Jan 25, 2021 at 01:40:19PM -0500, Gene Heskett wrote: > > Greetings all; > > > > I don't know if this has been hashed out already, but the stretch > > version of wget is broken, does not accept

Re: problem with wget -O

On Mon, Jan 25, 2021 at 01:45:34PM -0500, Roberto C. Sánchez wrote: > On Mon, Jan 25, 2021 at 01:40:19PM -0500, Gene Heskett wrote: > > I don't know if this has been hashed out already, but the stretch version > > of wget is broken, does not accept the -O filename syntax. Ge

Re: problem with wget -O

On Mon, Jan 25, 2021 at 01:40:19PM -0500, Gene Heskett wrote: > Greetings all; > > I don't know if this has been hashed out already, but the stretch version > of wget is broken, does not accept the -O filename syntax. > Are you sure you have the right wget? It works for me:

problem with wget -O

Greetings all; I don't know if this has been hashed out already, but the stretch version of wget is broken, does not accept the -O filename syntax. If there is a backport fix, what to I put in my sources.list to get it? Thanks. Cheers, Gene Heskett -- "There are four boxes to

Re: Problems with wget

complete, convert the links in > >the document to make them suitable for local viewing... > > > However, that usage causes wget to complain saying: > >Cannot specify both -k or --convert-file-only and -O if multiple URLs are > >given, or in combination > >with -p or -

Re: Problems with wget

://example.com/pageN.html> I wish my local file to have appropriate internal references. There are references of form http://some_where_else.com/pagex.html which I do not wish to download. I tried wget -l 2 -O owl.html ‐‐no-parent http://example.com/index.html It *almost* worked as intended. I did

Re: Problems with wget

ample.com/pageN.html> I wish my local file to have > appropriate internal references. > There are references of form >http://some_where_else.com/pagex.html > which I do not wish to download. > > > > I tried > wget -l 2 -O owl.html ‐‐no-parent http://example.com/i

Problems with wget

I do not wish to download. I tried wget -l 2 -O owl.html ‐‐no-parent http://example.com/index.html It *almost* worked as intended. I did get all the text of the site. HOWEVER: 1. I also got the text of <http://some_where_else.com/pagex.html> 2. Where <http://example.com/index.h

Re: using curl/wget to call logout

ookie /Login.jsp?message=logout but no success. How can I use curl/wget to logout through CLI ? It would be helpful if instead of 'no success' you provided precisely what did happen and what output/return code you got. The problem here, or really the behaviour you are asking questions abo

Re: using curl/wget to call logout

>From Chromium's Development Tools (press F12) you can right-click a request in the Network tab and "Copy as cURL" Might help with handling cookies and other such things using curl -- Justin

Re: using curl/wget to call logout

gt; > but no success. How can I use curl/wget to logout through CLI ? It would be helpful if instead of 'no success' you provided precisely what did happen and what output/return code you got. The problem here, or really the behaviour you are asking questions about, is specifi

using curl/wget to call logout

n.jsp?message=logout but no success. How can I use curl/wget to logout through CLI ? thanks & regards, Bob

Re: wget log from Jigdo

I have a sneaky suspicion it's a writing-style thing. I'll make 'em shorter next time. On Thu, 7 Jan 2016 12:51:53 +, you wrote: >On Thursday 07 January 2016 12:36:25 Steve Matzura wrote: >> Lisi, >> >> On Thu, 7 Jan 2016 11:04:33 +, you wrote: >> >I don't know how difficult it would be

Re: wget log from Jigdo

Richard: On Mon, 04 Jan 2016 05:53:15 -0600, you wrote: >On 1/4/2016 5:07 AM, Chris Bannister wrote: >> On Sun, Jan 03, 2016 at 09:32:36AM -0600, Richard Owlett wrote: >>> >>> A side question to Steve, "Is this post screen reader friendly?" >> >> That reminds me of the lecturers who say 'Hands up

Re: wget log from Jigdo

On 1/4/2016 8:10 AM, Lisi Reisz wrote: On Monday 04 January 2016 11:53:15 Richard Owlett wrote: On 1/4/2016 5:07 AM, Chris Bannister wrote: On Sun, Jan 03, 2016 at 09:32:36AM -0600, Richard Owlett wrote: A side question to Steve, "Is this post screen reader friendly?" That reminds me of the

Re: wget log from Jigdo

On Monday 04 January 2016 11:53:15 Richard Owlett wrote: > On 1/4/2016 5:07 AM, Chris Bannister wrote: > > On Sun, Jan 03, 2016 at 09:32:36AM -0600, Richard Owlett wrote: > >> A side question to Steve, "Is this post screen reader friendly?" > > > > That reminds me of the lecturers who say 'Hands up

Re: wget log from Jigdo

On 1/4/2016 5:07 AM, Chris Bannister wrote: On Sun, Jan 03, 2016 at 09:32:36AM -0600, Richard Owlett wrote: A side question to Steve, "Is this post screen reader friendly?" That reminds me of the lecturers who say 'Hands up if you can't hear me at the back.' I thought it was a logical ques

Re: wget log from Jigdo

On Tue, 5 Jan 2016 00:07:21 +1300 Chris Bannister wrote: > > A side question to Steve, "Is this post screen reader friendly?" > That reminds me of the lecturers who say 'Hands up if you can't hear me > at the back.' "Smith ! I did not see you at the camouflage class !" "Sir ! Thank you, Sir !

Re: wget log from Jigdo

On Sun, Jan 03, 2016 at 09:32:36AM -0600, Richard Owlett wrote: > > A side question to Steve, "Is this post screen reader friendly?" That reminds me of the lecturers who say 'Hands up if you can't hear me at the back.' -- "If you're not careful, the newspapers will have you hating the people wh

Re: wget log from Jigdo

On 1/2/2016 5:06 PM, Lisi Reisz wrote: [snip] My blind friend with his screen reader seems to have much less trouble with messy HTML than I (partially sighted) do. His screen reader just reads it to him. I stare at the mess of "pretty" colours and fancy writing, with blotches and swirls everyw

Re: wget log from Jigdo

On Sat, 2 Jan 2016 23:06:29 +, Lisi wrote: >My blind friend with his screen reader seems to have much less trouble with >messy HTML than I (partially sighted) do. His screen reader just reads it to >him. I stare at the mess of "pretty" colours and fancy writing, with >blotches and swirls

Re: wget log from Jigdo

On Saturday 02 January 2016 17:22:11 Chris Bannister wrote: > On Fri, Jan 01, 2016 at 03:45:40PM +, Brian wrote: > > On Sat 02 Jan 2016 at 03:54:38 +1300, Chris Bannister wrote: > > > (BTW, top-posting makes it difficult to reply, and I couldn't be > > > bothered copying and pasting to correct

Re: wget log from Jigdo

On Sun, 3 Jan 2016 06:22:11 +1300, Chris Bannister wrote: >> You would do well to read *all* of Steve Matzura's posts before >> bemoaning your lot. You'll come across "speech synthesis" and >> "screen reader". > >In that case, mails in html must be almost impossible to comprehend. :) >I'm guessin

Re: wget log from Jigdo

On Fri, Jan 01, 2016 at 03:45:40PM +, Brian wrote: > On Sat 02 Jan 2016 at 03:54:38 +1300, Chris Bannister wrote: > > > (BTW, top-posting makes it difficult to reply, and I couldn't be bothered > > copying and pasting to correct it.) > > You would do well to read *all* of Steve Matzura's post

Re: wget log from Jigdo

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/01/16 05:10, Steve Matzura wrote: >>> Glad that you got it going. That default of sound being set to >>> 0 or muted by default is annoying even if one has some sight. >>> It must be maddening and incomprehensible if you haven't! The >>> ratio

Re: wget log from Jigdo

On Friday 01 January 2016 14:54:38 Chris Bannister wrote: > On Wed, Dec 30, 2015 at 02:34:55PM -0500, Steve Matzura wrote: > > (BTW, top-posting makes it difficult to reply, and I couldn't be bothered > copying and pasting to correct it.) And harder still to follow. But I gather from elsewhere t

Re: wget log from Jigdo

On Sat 02 Jan 2016 at 03:54:38 +1300, Chris Bannister wrote: > (BTW, top-posting makes it difficult to reply, and I couldn't be bothered > copying and pasting to correct it.) You would do well to read *all* of Steve Matzura's posts before bemoaning your lot. You'll come across "speech synthesis"

Re: wget log from Jigdo

On Wed, Dec 30, 2015 at 02:34:55PM -0500, Steve Matzura wrote: > True, but who knew that? I go with what I know most of the time, and > what I know about Jigdo can be summed up in one word: nothing. So when > I see a URL that purports to be the one to use, I use it. This is what > makes me crazy ab

Re: wget log from Jigdo

On Thu, 31 Dec 2015 15:57:38 +, Lisi wrote: >Some years ago a friend complained to me that I ignored his advice and never >listened. I said, not at all. I always listen avidly to advice. I always >think about advice. I just don't always follow advice. ;-) LOL. I always find something in

Re: wget log from Jigdo

On Thursday 31 December 2015 15:45:23 Steve Matzura wrote: > Now everything's fixed, up, running, etc., it's quite time to thank > everyone who made suggestions, at least 99% of which were helpful in > some way, if not directly, then indirectly by putting my mind onto a > different thinking path.

Re: wget log from Jigdo

Now everything's fixed, up, running, etc., it's quite time to thank everyone who made suggestions, at least 99% of which were helpful in some way, if not directly, then indirectly by putting my mind onto a different thinking path.

Re: wget log from Jigdo

It doesn't help, but it *does* make sense. If that were documented in the Jigdo quick-start, that would be helpful. I'll write in and see about having it added as a cautionary note. On Wed, 30 Dec 2015 17:58:20 -0800, you wrote: > >> On Dec 30, 2015, at 1:13 PM, Steve Matzura wrote: >> >> I sti

Re: wget log from Jigdo

> On Dec 30, 2015, at 1:13 PM, Steve Matzura wrote: > > I still don't > understand why adding 'debian/' worked for the Pittsburgh URL but not, > say, for the Stevens Institute one. No matter, it's working now, I can’t say why any particular mirror does what it does, but the general rule is: mi

Re: wget log from Jigdo

On Wednesday 30 December 2015 15:55:02 Rick Thomas wrote: > On Dec 30, 2015, at 11:34 AM, Steve Matzura wrote: > > This is what > > makes me crazy about anything Linux--secret knowledge that some > > people just seem to have or know, that would never occur to anyone > > else. > > Yeah, it’s a pro

Re: wget log from Jigdo

Yes, and there's a lot of "do what it says, not what you might think it wants you to do" operating in the Windows sphere. I still don't understand why adding 'debian/' worked for the Pittsburgh URL but not, say, for the Stevens Institute one. No matter, it's working now, downloading and hopefully c

Re: wget log from Jigdo

That's true to a certain extent, but in the thirty years I've been working with Linux, back to SCO Xenix and System V Unix, I've found there's more unpublished knowledge and tips and tricks therein than ever I've found in twenty-five years of working with Windows. But what gets me is when people sa

Re: wget log from Jigdo

On Dec 30, 2015, at 11:34 AM, Steve Matzura wrote: > This is what > makes me crazy about anything Linux--secret knowledge that some people > just seem to have or know, that would never occur to anyone else. Yeah, it’s a problem; but fortunately there are mailing lists like this one, and wikis

Re: wget log from Jigdo

On Wednesday 30 December 2015 19:34:55 Steve Matzura wrote: > True, but who knew that? I go with what I know most of the time, and > what I know about Jigdo can be summed up in one word: nothing. So when > I see a URL that purports to be the one to use, I use it. This is what > makes me crazy about

Re: wget log from Jigdo

have or know, that would never occur to anyone else. On Thu, 31 Dec 2015 04:49:17 +1300, you wrote: >On Wed, Dec 30, 2015 at 10:36:33AM -0500, Steve Matzura wrote: >> This is what I could get from the wget portion of the Jigdo process >> running on a Windows 7 SP1 machine. I used

Re: wget log from Jigdo

On Wed 30 Dec 2015 at 13:22:03 -0500, Steve Matzura wrote: I'm not exactly sure what is happening with your Adventures with Jigdo in Windows tale. But if you do not want the bother of thinking about the best mirror to use you could have http://httpredir.debian.org/ Highly recommended. > ??

Re: wget log from Jigdo

How's that? The URL shown in the results of a search for "Pittsburgh" is: http://debian.mirrors.pair.com/ How did you know to add "debian/" to the end of it? Do I do that for any of those URL's? If that's true, I'd prefer to use a different mirror, slightly closer, listed as: ftp://ftp.

Re: wget log from Jigdo

On Wed, Dec 30, 2015 at 10:36:33AM -0500, Steve Matzura wrote: > This is what I could get from the wget portion of the Jigdo process > running on a Windows 7 SP1 machine. I used a pair of files called > debian-8.2.0-amd64-BD-1 (.jigdo and .template) downloaded yesterday, > and t

wget log from Jigdo

This is what I could get from the wget portion of the Jigdo process running on a Windows 7 SP1 machine. I used a pair of files called debian-8.2.0-amd64-BD-1 (.jigdo and .template) downloaded yesterday, and the mirror at debian.mirrors.pair.com, but that doesn't matter much, as I get the

Re: Progress bar of "wget" broken (some terminal bug?)

Brandon Vincent [2015-12-26 10:04:50-07] wrote: > I believe this problem was corrected by the GNU developers upstream > and should be fixed in wget (1.16-2). I don't see this version or a > newer package in proposed-updates, so you'll want to try the package > fro

Re: Progress bar of "wget" broken (some terminal bug?)

On Sat, Dec 26, 2015 at 4:46 AM, Teemu Likonen wrote: > I think I have seen similar problem with other programs' progress bars > too so I guess this is a terminal control problem not a wget bug. The > problem appeared after upgrading to Debian 8. Can it be fixed easily? Hi Teemu,

Progress bar of "wget" broken (some terminal bug?)

The download progress bar of "wget" is broken because it prints almost every progress stage in separate line. It's not a bar that updates in a single line. Here's an example: 10%[=> ] 20%[===> ] 30%[

  1   2   3   4   5   >