Bug 1167025

Thanks for the report. Disclaimer: I haven't came in contact with SOCKS.

Ladislav, could setting the proxy in conf file [1] instead of using tsocks help to your use case?

Tomas, do you have any ideas why it doesn't work?

[1] http://dnf.readthedocs.org/en/latest/api_conf.html?#dnf.conf.Conf.proxy

Hi Ladislav,

I dig into this [1] and it seems to me more like a problem in Tsocks than Librepo.

Frankly, I wasn't able to use tsocks with curl or wget, let alone the librepo. Also, I found out that I'm not alone and that applications based on LibCURL may have troubles with Tsocks in general [2].

As Jan remarked, for dnf there are much better and convenient options how to set a proxy server:

1) The mentioned "proxy" option in dnf configuration
2) Standard "http_proxy" environment variable

Especially the last one can be considered as a typical way how to temporary set a proxy server to an application (or at least more typical than the tsocks):

$ sudo http_proxy=socks5h://proxyurl:proxyport dnf update

Should work like a charm (Instead of "socks5h" use the appropriate value - socks4://, socks4a://, socks5:// or socks5h://)


[1] https://github.com/Tojaj/librepo/wiki/HOWTO:-SOCKS-Proxy-setup
[2] http://curl.haxx.se/mail/lib-2010-01/index.html#258

Suggestion "http_proxy=socks5h://proxyurl:proxyport dnf update" solves my problem perfectly.
Guys, thanks a lot for perfect support.

Unfortunately I must correct my previous post. The trick with the environment variable "http_proxy" does not work at all. Sorry for false confirmation. Dnf's proxy option does not work too (definitely not for my aim - ssh socks tunneling).
I succeeded with "proxychains" application - http://proxychains.sourceforge.net/

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.