Hello,

I have a problem with the 'curl' program.

transmission(bt), needs a more recent version of curl than the updated official slackware package.

the package for my 12.1 system is curl-7.16.2

for 12.2, its curl-7.19.6 (latest curl version).


Im guessing that something will break if I install a curl version above 7.16.2?

Hi,

(a possible possibility) At a Slackware mirror, locate and download the source files for curl for 12.1

For sometimes can then slightly modify the curl.slackbuild script then use it to build yourself a later curl. Run the script against a later (downloaded) curl source code file, a .bz2 or .tgz or .tar.gz

If you need a pkg rather than build your own -- you might browse/search the various pkgs sites on the internet.

Alan.

Many things will.
IMO you have two options.
a) Stick to an older version of transmission.
b) upgrade the whole system to 12.2.

bittorrent-curses

is the client I use on 12.2 (YMMV) (may not need later curl?).

But **Be sure to** take your ssl / openssh (security, the level of) needs into consideration too as don't want yourself without adequate security for whatever it is that you're doing.

Alan.

sahko, I would like to upgrade to 12.2, but unfortunately I've got too much tied up with my install, and too little time also.

Alan, I thought that all bt clients would need the same curl version, but after you mentioned bittorrent-curses, I went to rtorrent website and it seems that it only needs curl 7.12.x , I have thought about trying it for a while now, so I suppose this is a good opportunity.

Thanks

Eventually though, rtorrent probably will only build with a later version of curl. I don't see why you can't update to 12.2 over your existing install. Many of us do update to every new version with bo problems.

Just make sure to read the upgrade.txt, changes_and_hints.txt and changelog.

ftp://slackware.mirrors.tds.net/pub/...torrent/README

ftp://slackware.mirrors.tds.net/pub/...ra/bittorrent/

http://mirrors.tds.net

Recent versions of curl no longer ship with certificate (due said cert. became outdated).

The Links above (due that for 12.1 the bittorrent being in "extra") are pointing you to "what may be a version of curl that's with the mentioned outdated cert."

go to curl website to verify "which (recent) version of curl discontinued ship of outdated cert."

a curl security update happened very recently for Slack 12.2 and current -> check the Slackware changelogs. Did 12.1 get or need the same security update?

And/or (if keep with 12.1) create your own cert. given if there are no other security holes.

Are you sure you do not want 12.2?

Alan.

its an interesting option.

Yes there was a security updated curl package made available for slack 12.1 on the 14th of this month, at the same time as the updated 12.2 package.

I think I'll bite the bullet and upgrade to 2.2