Re: libcurl problem.

2018-12-02 Thread David 
On Sun, 2 Dec 2018 at 23:17, Roberto C. Sánchez  wrote:
> On Sun, Dec 02, 2018 at 08:20:25PM +1100, David wrote:
> >
> > apt-cache policy $(dpkg -l | awk '/libcurl/ {print $2}')
> >
> > would be a nicer way to do that, FAWC.
>
> Thanks for the pointer.

You are welcome. I learn from your posts too.

Re: libcurl problem.

2018-12-02 Thread Roberto C . Sánchez 
On Sun, Dec 02, 2018 at 08:20:25PM +1100, David wrote:
> On Wed, 28 Nov 2018 at 06:41, Roberto C. Sánchez  wrote:
> >
> > apt-cache policy $(dpkg -l |grep libcurl | awk '{print $2}')
> 
> Just FAWC (for anyone who cares :]) that's a UUOG (useless
> use of grep), because regular expression support is fundamental
> to the design of awk.
> 
> apt-cache policy $(dpkg -l | awk '/libcurl/ {print $2}')
> 
> would be a nicer way to do that, FAWC.
> 

I suppose I should know that.  For the longest time I always did 'grep |
cut' but kept encountering instances where I needed something a bit more
flexible than cut.  I found awk to my liking but never properly learned
it, just always using it as a fancy cut replacement.

Thanks for the pointer.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: libcurl problem.

2018-12-02 Thread David 
On Wed, 28 Nov 2018 at 06:41, Roberto C. Sánchez  wrote:
>
> apt-cache policy $(dpkg -l |grep libcurl | awk '{print $2}')

Just FAWC (for anyone who cares :]) that's a UUOG (useless
use of grep), because regular expression support is fundamental
to the design of awk.

apt-cache policy $(dpkg -l | awk '/libcurl/ {print $2}')

would be a nicer way to do that, FAWC.

Re: libcurl problem.

2018-11-28 Thread Roberto C . Sánchez 
On Wed, Nov 28, 2018 at 09:28:39PM -0500, Gene Heskett wrote:
> 
> Trying to run opera from the cli returns exactly the same libcurl.so.4 
> error.
> 
> Must be time to update this thing... Gr!
> 
Looks like it.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: libcurl problem.

2018-11-28 Thread Gene Heskett 
On Wednesday 28 November 2018 06:56:26 Roberto C. Sánchez wrote:

> ls -l /etc/alternatives/x-www-browser
/etc/alternatives/x-www-browser -> /usr/bin/opera

Opera? I got tired of its inability to read a news site, and nuked it 
years ago

gene@coyote:/CoCo$ ldd /etc/alternatives/x-www-browser
linux-vdso.so.1 =>  (0x7fff0d7bc000)
libffmpeg.so => not found
libcurl.so.4 => not found
libdl.so.2 => /lib64/libdl.so.2 (0x7feaa46ba000)
librt.so.1 => /lib64/librt.so.1 (0x7feaa44b2000)
libgmodule-2.0.so.0 => not found
libgobject-2.0.so.0 => not found
libglib-2.0.so.0 => not found
libpangocairo-1.0.so.0 => not found
libpango-1.0.so.0 => not found
libcairo.so.2 => not found
libgio-2.0.so.0 => not found
libnss3.so => /home/gene/bin/firefox/libnss3.so 
(0x7feaa420b000)
libnssutil3.so => /home/gene/bin/firefox/libnssutil3.so 
(0x7feaa3fd7000)
libsmime3.so => /home/gene/bin/firefox/libsmime3.so 
(0x7feaa3dac000)
libnspr4.so => /home/gene/bin/firefox/libnspr4.so 
(0x7feaa3b6c000)
libexpat.so.1 => not found
libfontconfig.so.1 => not found
libfreetype.so.6 => not found
libX11.so.6 => not found
libXcomposite.so.1 => not found
libXcursor.so.1 => not found
libXdamage.so.1 => not found
libXext.so.6 => not found
libXfixes.so.3 => not found
libXi.so.6 => not found
libXrender.so.1 => not found
libXtst.so.6 => not found
libXss.so.1 => not found
libXrandr.so.2 => not found
libgconf-2.so.4 => not found
libasound.so.2 => not found
libdbus-1.so.3 => not found
libatk-1.0.so.0 => not found
libm.so.6 => /lib64/libm.so.6 (0x7feaa38ea000)
libcups.so.2 => not found
libpthread.so.0 => /lib64/libpthread.so.0 (0x7feaa36ce000)
libnotify.so.4 => not found
libgdk_pixbuf-2.0.so.0 => not found
libgtk-x11-2.0.so.0 => not found
libgdk-x11-2.0.so.0 => not found
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x7feaa33c7000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7feaa31b1000)
libc.so.6 => /lib64/libc.so.6 (0x7feaa2e24000)
/lib64/ld-linux-x86-64.so.2 (0x7feaa48be000)
libplc4.so => /home/gene/bin/firefox/libplc4.so 
(0x7feaa2c1e000)
libplds4.so => /home/gene/bin/firefox/libplds4.so 
(0x7feaa2a19000)
gene@coyote:/CoCo$

Trying to run opera from the cli returns exactly the same libcurl.so.4 
error.

Must be time to update this thing... Gr!

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: libcurl problem.

2018-11-28 Thread Roberto C . Sánchez 
On Tue, Nov 27, 2018 at 10:30:15PM -0500, Gene Heskett wrote:
> /usr/bin/x-www-browser: error while loading shared libraries: libcurl.so.4: 
> cannot open shared object file: No such file or 
> directory

OK.  The problem is not your application, directly, but rather the
system browser.  What is the output of these two commands?

ls -l /etc/alternatives/x-www-browser

ldd /etc/alternatives/x-www-browser

Regards,

-Roberto
-- 
Roberto C. Sánchez

Re: libcurl problem.

2018-11-27 Thread Gene Heskett 
On Tuesday 27 November 2018 21:20:16 Roberto C. Sánchez wrote:

> On Tue, Nov 27, 2018 at 03:51:47PM -0500, Gene Heskett wrote:
> > curl (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
> > libcurl3 (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
> > libcurl3-gnutls (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
> > libcurl4-gnutls-dev (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
> >
> > I knew I'd been looking at the error, but I didn't think it was THAT
> > far back up the log.  But an app I hadn't used in a coupler years,
> > refused to go get the docs for a new version, which made me back it
> > up to the previous version I was familiar with, also refused, I
> > thought I'd dig a little deeper.
> >
> > Abd the fix is?
>
> Can you try to launch the offending application from the terminal and
> post the complete error output?
>
> Regards,
>
Ton't take long, its name is DriveWire, writtem in java. It sets up a 
very high baud rate serial connection to an old TRS-80 Color Computer3 
over a usb2 to a 7 port usb hub in the basement, which has a custom 
built adapter cable plugged into the coco's bit banger port, giving 
the coco 32 additional channels of i/o that can be used as virtual 
disk drives, virtual terminal screens into the coco from a pc's screen.
a midi player, and access in text modes, to any printer attached to 
the pc.  All at speeds of about half that of a floppy controller.

I fired it up, and sent it to show me the documentation from the 
drivewire wiki pages.  And this is the trace:

==
ene@coyote:/CoCo$ ./dwstart
/CoCo/dw4directory
gene@coyote:/CoCo$ deleting old lockfile /var/lock/LCK..ttyUSB1
total 0
drwxr-xr-x 2 www-data root 40 Nov 19 20:20 apache2
-rw-rw-rw- 1 root root  0 Nov 19 20:20 tdekbdledsync-:0.lock
total 0
drwxr-xr-x 2 www-data root 40 Nov 19 20:20 apache2
-rw-rw-rw- 1 root root  0 Nov 19 20:20 tdekbdledsync-:0.lock
27 Nov 2018 22:00:34 INFO  [dwserver-9] DriveWire Server v4.3.3o starting
Warning: NineServer port already in use.  Is another DW4UI running?
/usr/bin/x-www-browser: error while loading shared libraries: libcurl.so.4: 
cannot open shared object file: No such file or 
directory
===
At that point I exited the app. The NineServer port message has been 
there for years, thru at least a dozen new versions and has never 
been a problem. At that point it had not yet drawn its gui, taking 
another 3 or 4 secs to complete that.  At that point I opened the help
pulldown and ask to see the docs from te wiki.

And thats is the complete trace, showing the libcurl.so.4 as not being loadable.

But its there:
 ls -l /usr/lib/i386-linux-gnu/libcurl*
lrwxrwxrwx 1 root root 16 May 16  2018 /usr/lib/i386-linux-gnu/libcurl.a -> 
libcurl-gnutls.a
-rw-r--r-- 1 root root 596234 May 16  2018 
/usr/lib/i386-linux-gnu/libcurl-gnutls.a
-rw-r--r-- 1 root root990 May 16  2018 
/usr/lib/i386-linux-gnu/libcurl-gnutls.la
lrwxrwxrwx 1 root root 23 May 16  2018 
/usr/lib/i386-linux-gnu/libcurl-gnutls.so -> libcurl-gnutls.so.4.2.0
lrwxrwxrwx 1 root root 19 May 16  2018 
/usr/lib/i386-linux-gnu/libcurl-gnutls.so.3 -> libcurl-gnutls.so.4
lrwxrwxrwx 1 root root 23 May 16  2018 
/usr/lib/i386-linux-gnu/libcurl-gnutls.so.4 -> libcurl-gnutls.so.4.2.0
-rw-r--r-- 1 root root 412384 May 16  2018 
/usr/lib/i386-linux-gnu/libcurl-gnutls.so.4.2.0
lrwxrwxrwx 1 root root 17 May 16  2018 /usr/lib/i386-linux-gnu/libcurl.la 
-> libcurl-gnutls.la
lrwxrwxrwx 1 root root 17 May 16  2018 /usr/lib/i386-linux-gnu/libcurl.so 
-> libcurl-gnutls.so
lrwxrwxrwx 1 root root 12 May 16  2018 /usr/lib/i386-linux-gnu/libcurl.so.3 
-> libcurl.so.4
lrwxrwxrwx 1 root root 16 May 16  2018 /usr/lib/i386-linux-gnu/libcurl.so.4 
-> libcurl.so.4.2.0
-rw-r--r-- 1 root root 433152 May 16  2018 
/usr/lib/i386-linux-gnu/libcurl.so.4.2.0

Me not java expert except for drinking it. :-)

Doing a new ldconfig makes no difference.

Thanks Roberto C. Sánchez.

> -Roberto

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: libcurl problem.

2018-11-27 Thread Roberto C . Sánchez 
On Tue, Nov 27, 2018 at 03:51:47PM -0500, Gene Heskett wrote:
> 
> curl (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
> libcurl3 (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
> libcurl3-gnutls (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
> libcurl4-gnutls-dev (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
> 
> I knew I'd been looking at the error, but I didn't think it was THAT far 
> back up the log.  But an app I hadn't used in a coupler years, refused 
> to go get the docs for a new version, which made me back it up to the 
> previous version I was familiar with, also refused, I thought I'd dig a 
> little deeper.
> 
> Abd the fix is? 
> 
Can you try to launch the offending application from the terminal and
post the complete error output?

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: libcurl problem.

2018-11-27 Thread Gene Heskett 
On Tuesday 27 November 2018 17:20:29 Brian wrote:

> On Tue 27 Nov 2018 at 16:26:19 -0500, Gene Heskett wrote:
> > On Tuesday 27 November 2018 15:55:18 Brian wrote:
> > > On Tue 27 Nov 2018 at 15:51:47 -0500, Gene Heskett wrote:
> > > > On Tuesday 27 November 2018 15:11:55 Roberto C. Sánchez wrote:
> > > > > Did you just recently update curl?
> > > >
> > > > About the first of october, it came from security.debian.org
> > > > IIRC, but
> > >
> > > You do not recall IIRC.
> >
> > Obviously but I'm rubbing it in bad enough w/o help ;)
>
> Knowing which package was installed would be useful. It should be in
> you logs.

I already posted that list. Up-thread.



-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: libcurl problem.

2018-11-27 Thread Brian 
On Tue 27 Nov 2018 at 16:26:19 -0500, Gene Heskett wrote:

> On Tuesday 27 November 2018 15:55:18 Brian wrote:
> 
> > On Tue 27 Nov 2018 at 15:51:47 -0500, Gene Heskett wrote:
> > > On Tuesday 27 November 2018 15:11:55 Roberto C. Sánchez wrote:
> > > > Did you just recently update curl?
> > >
> > > About the first of october, it came from security.debian.org IIRC,
> > > but
> >
> > You do not recall IIRC.
> 
> Obviously but I'm rubbing it in bad enough w/o help ;)

Knowing which package was installed would be useful. It should be in
you logs.

-- 
Brian.

Re: libcurl problem.

2018-11-27 Thread Gene Heskett 
On Tuesday 27 November 2018 15:55:18 Brian wrote:

> On Tue 27 Nov 2018 at 15:51:47 -0500, Gene Heskett wrote:
> > On Tuesday 27 November 2018 15:11:55 Roberto C. Sánchez wrote:
> > > Did you just recently update curl?
> >
> > About the first of october, it came from security.debian.org IIRC,
> > but
>
> You do not recall IIRC.

Obviously but I'm rubbing it in bad enough w/o help ;)


-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: libcurl problem.

2018-11-27 Thread Brian 
On Tue 27 Nov 2018 at 15:51:47 -0500, Gene Heskett wrote:

> On Tuesday 27 November 2018 15:11:55 Roberto C. Sánchez wrote:
> 
> > Did you just recently update curl?
> >
> About the first of october, it came from security.debian.org IIRC, but 

You do not recall IIRC.

-- 
Brian.

Re: libcurl problem.

2018-11-27 Thread Gene Heskett 
On Tuesday 27 November 2018 15:11:55 Roberto C. Sánchez wrote:

> On Tue, Nov 27, 2018 at 02:58:17PM -0500, Gene Heskett wrote:
> > On Tuesday 27 November 2018 14:40:40 Roberto C. Sánchez wrote:
> > > apt-cache policy $(dpkg -l |grep libcurl | awk '{print $2}')
> >
> > gene@coyote:/CoCo$ sudo apt-cache policy $(dpkg -l |grep libcurl |
> > awk '{print $2}')
> > [sudo] password for gene:
> > libcurl3:
> >   Installed: 7.26.0-1+wheezy25+deb7u1
> >   Candidate: 7.26.0-1+wheezy25+deb7u1
> >   Version table:
> >  *** 7.26.0-1+wheezy25+deb7u1 0
> > 100 /var/lib/dpkg/status
> >  7.26.0-1+wheezy13 0
> > 500 http://deb.debian.org/debian/ wheezy/main i386 Packages
> > libcurl3-gnutls:
> >   Installed: 7.26.0-1+wheezy25+deb7u1
> >   Candidate: 7.26.0-1+wheezy25+deb7u1
> >   Version table:
> >  *** 7.26.0-1+wheezy25+deb7u1 0
> > 100 /var/lib/dpkg/status
> >  7.26.0-1+wheezy13 0
> > 500 http://deb.debian.org/debian/ wheezy/main i386 Packages
> > libcurl4-gnutls-dev:
> >   Installed: 7.26.0-1+wheezy25+deb7u1
> >   Candidate: 7.26.0-1+wheezy25+deb7u1
> >   Version table:
> >  *** 7.26.0-1+wheezy25+deb7u1 0
> > 100 /var/lib/dpkg/status
> >  7.26.0-1+wheezy13 0
> > 500 http://deb.debian.org/debian/ wheezy/main i386 Packages
> > python-pycurl:
> >   Installed: 7.19.0-5
> >   Candidate: 7.19.0-5
> >   Version table:
> >  *** 7.19.0-5 0
> > 500 http://deb.debian.org/debian/ wheezy/main i386 Packages
> > 100 /var/lib/dpkg/status
> >
> > Is this helpfull?
> >
> > Rhanks Roberto C. Sánchez
>
> The version you have installed first appeared 6 months ago:
>
> http://snapshot.debian.org/package/curl/7.26.0-1%2Bwheezy25%2Bdeb7u1/
>
> Here is the related Debian LTS Advisory:
>
> https://lists.debian.org/debian-lts-announce/2018/05/msg00010.html
>
> Did you just recently update curl?
>
About the first of october, it came from security.debian.org IIRC, but 
let me see if I can find it in Synaptics history to be exact & sure of 
the date . Damn, clear back in May 17 2018, I see this:

curl (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
libcurl3 (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
libcurl3-gnutls (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1
libcurl4-gnutls-dev (7.26.0-1+wheezy25) to 7.26.0-1+wheezy25+deb7u1

I knew I'd been looking at the error, but I didn't think it was THAT far 
back up the log.  But an app I hadn't used in a coupler years, refused 
to go get the docs for a new version, which made me back it up to the 
previous version I was familiar with, also refused, I thought I'd dig a 
little deeper.

Abd the fix is? 

> Regards,
>
> -Roberto

Thanks Roberto C. Sánchez

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: libcurl problem.

2018-11-27 Thread Roberto C . Sánchez 
On Tue, Nov 27, 2018 at 02:58:17PM -0500, Gene Heskett wrote:
> On Tuesday 27 November 2018 14:40:40 Roberto C. Sánchez wrote:
> 
> > apt-cache policy $(dpkg -l |grep libcurl | awk '{print $2}')
> 
> gene@coyote:/CoCo$ sudo apt-cache policy $(dpkg -l |grep libcurl | 
> awk '{print $2}')
> [sudo] password for gene:
> libcurl3:
>   Installed: 7.26.0-1+wheezy25+deb7u1
>   Candidate: 7.26.0-1+wheezy25+deb7u1
>   Version table:
>  *** 7.26.0-1+wheezy25+deb7u1 0
> 100 /var/lib/dpkg/status
>  7.26.0-1+wheezy13 0
> 500 http://deb.debian.org/debian/ wheezy/main i386 Packages
> libcurl3-gnutls:
>   Installed: 7.26.0-1+wheezy25+deb7u1
>   Candidate: 7.26.0-1+wheezy25+deb7u1
>   Version table:
>  *** 7.26.0-1+wheezy25+deb7u1 0
> 100 /var/lib/dpkg/status
>  7.26.0-1+wheezy13 0
> 500 http://deb.debian.org/debian/ wheezy/main i386 Packages
> libcurl4-gnutls-dev:
>   Installed: 7.26.0-1+wheezy25+deb7u1
>   Candidate: 7.26.0-1+wheezy25+deb7u1
>   Version table:
>  *** 7.26.0-1+wheezy25+deb7u1 0
> 100 /var/lib/dpkg/status
>  7.26.0-1+wheezy13 0
> 500 http://deb.debian.org/debian/ wheezy/main i386 Packages
> python-pycurl:
>   Installed: 7.19.0-5
>   Candidate: 7.19.0-5
>   Version table:
>  *** 7.19.0-5 0
> 500 http://deb.debian.org/debian/ wheezy/main i386 Packages
> 100 /var/lib/dpkg/status
> 
> Is this helpfull?
> 
> Rhanks Roberto C. Sánchez
> 
The version you have installed first appeared 6 months ago:

http://snapshot.debian.org/package/curl/7.26.0-1%2Bwheezy25%2Bdeb7u1/

Here is the related Debian LTS Advisory:

https://lists.debian.org/debian-lts-announce/2018/05/msg00010.html

Did you just recently update curl?

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: libcurl problem.

2018-11-27 Thread Brian 
On Tue 27 Nov 2018 at 14:25:55 -0500, Gene Heskett wrote:

> Greetings all;
> 
> One of the last updates to wheezy was libcurl, from security.debian.org,

No, it wasn't from security.debian.org.

> to libcurl.so.4.2.0 which was installed by symlinking it to 
> libcurl.so.4, which is what the erroir.
> 
> Normally when you folks do that, the symlink says it is 100% compatible 
> with the older version.
> 
> But everything on my system that needs libcurl.so.4 is yelling about it 
> can't be found.
> 
> How to fix this if possible?

Look at what you had before and what you have now.

-- 
Brian.

Re: libcurl problem.

2018-11-27 Thread Gene Heskett 
On Tuesday 27 November 2018 14:40:40 Roberto C. Sánchez wrote:

> apt-cache policy $(dpkg -l |grep libcurl | awk '{print $2}')

gene@coyote:/CoCo$ sudo apt-cache policy $(dpkg -l |grep libcurl | 
awk '{print $2}')
[sudo] password for gene:
libcurl3:
  Installed: 7.26.0-1+wheezy25+deb7u1
  Candidate: 7.26.0-1+wheezy25+deb7u1
  Version table:
 *** 7.26.0-1+wheezy25+deb7u1 0
100 /var/lib/dpkg/status
 7.26.0-1+wheezy13 0
500 http://deb.debian.org/debian/ wheezy/main i386 Packages
libcurl3-gnutls:
  Installed: 7.26.0-1+wheezy25+deb7u1
  Candidate: 7.26.0-1+wheezy25+deb7u1
  Version table:
 *** 7.26.0-1+wheezy25+deb7u1 0
100 /var/lib/dpkg/status
 7.26.0-1+wheezy13 0
500 http://deb.debian.org/debian/ wheezy/main i386 Packages
libcurl4-gnutls-dev:
  Installed: 7.26.0-1+wheezy25+deb7u1
  Candidate: 7.26.0-1+wheezy25+deb7u1
  Version table:
 *** 7.26.0-1+wheezy25+deb7u1 0
100 /var/lib/dpkg/status
 7.26.0-1+wheezy13 0
500 http://deb.debian.org/debian/ wheezy/main i386 Packages
python-pycurl:
  Installed: 7.19.0-5
  Candidate: 7.19.0-5
  Version table:
 *** 7.19.0-5 0
500 http://deb.debian.org/debian/ wheezy/main i386 Packages
100 /var/lib/dpkg/status

Is this helpfull?

Rhanks Roberto C. Sánchez

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

Re: libcurl problem.

2018-11-27 Thread Roberto C . Sánchez 
On Tue, Nov 27, 2018 at 02:25:55PM -0500, Gene Heskett wrote:
> Greetings all;
> 
> One of the last updates to wheezy was libcurl, from security.debian.org, 
> to libcurl.so.4.2.0 which was installed by symlinking it to 
> libcurl.so.4, which is what the erroir.
> 
> Normally when you folks do that, the symlink says it is 100% compatible 
> with the older version.
> 
> But everything on my system that needs libcurl.so.4 is yelling about it 
> can't be found.
> 
> How to fix this if possible?
> 
What is the output of this command:

apt-cache policy $(dpkg -l |grep libcurl | awk '{print $2}')


-- 
Roberto C. Sánchez

libcurl problem.

2018-11-27 Thread Gene Heskett 
Greetings all;

One of the last updates to wheezy was libcurl, from security.debian.org, 
to libcurl.so.4.2.0 which was installed by symlinking it to 
libcurl.so.4, which is what the erroir.

Normally when you folks do that, the symlink says it is 100% compatible 
with the older version.

But everything on my system that needs libcurl.so.4 is yelling about it 
can't be found.

How to fix this if possible?

Thank you all.

-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page