Hi! On Sat, 2013-07-13 at 21:00:58 -0400, Braiam Peguero wrote: > Package: dpkg > Version: 1.16.10 > Severity: minor
I'll try to address some of the things you mentioned off-list. > * What led up to the situation? > Install a package with apt-get, aptitude or dpkg Being precise here is pretty important, because it helps when tracking down the specific cause of the error, and where to file the bug report (did it really happen too when calling «dpkg -i» manually for example?). Also being more verbose is of essence, because this is a so rare problem no one has reported it before, so saying that just installing a package will trigger this error will not really help others when trying to reproduce it (attaching possible sources.list entries, apt or dpkg configs, or a list of other installed apt-related packages that might be called during the invokation might have helped, for example). After having been able to perform a source code search on the entire Debian archive (which ironically has been timing out these past days too): <http://codesearch.debian.net/search?q=%22Timeout+was+reached%22> I see there's only two probable sources for this error message, glib and curl. Given this, my suspicion is that you might be using an https transport (from the apt-transport-https package) in your sources.list file? And some of the network operations timed out. If so I'd reopen and reassign to that package, to at lest improve the error message so that it's clear where it's coming from. Otherwise this might just be a network/server timeout. > * What was the outcome of this action? > Sometimes even when the package(s) install correctly, apt/dpkg ends > with a 'Error: Timeout was reached' message at the end. I concede that given the error message, it's not easy to infer from where it's coming from, but discarding possible culprits by elimination would have helped here too. Thanks, Guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
