Hi Francesco, On 2017-07-20 23:45:54 +0200, Francesco Poli wrote: > While it's true that the man page states what you quoted, it also goes > on stating: > > | The notable configuration options are > > followed by a list of the options that are read and used by apt-listbugs. > And Acquire::http::TimeOut is _not_ included in the list...
If you meant that these are the only supported options, then "notable" is not the right word (as I understood "notable configuration options", I thought these were the most important options in practice, in the context of apt-listbugs). > As far as the feature request itself is concerned, it seems to me > that apt.conf(5) man page says: > > | The option timeout sets the timeout timer used by the method; this > | value applies to the connection as well as the data timeout. > > It's not too clear to me whether the value is in seconds or in some > other unit of measurement. Where is this documented? I was wondering the same thing (since I had to use this option for "apt"), and assumed that this was in seconds, as this is the standard time unit (and the man page also mentions "seconds" for other time options). And indeed, this corresponds to the observed behavior. > Anyway, I'll try and take a look at some method to set the timeout > for ruby-httpclient. Let's hope it's not too difficult to do. That would be strange that standard modules wouldn't allow a configurable timeout. Actually this seems possible: https://stackoverflow.com/questions/20399534/whats-the-default-time-out-limitation-of-ruby-httpclient Otherwise, wouldn't the right solution to use libapt-pkg (just guessing), if there's a Ruby interface? -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
