Bug#623167: cupt: unable to set download client socket timeout: Protocol not available

2011-04-25 Thread Eugene V. Lyubimkin
Hi Jonathan, Cupt 2.0.1 has landed to unstable, can you confirm that downloading, aside of some number of warnings, works on hurd now? -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- To UNSUBSCRIBE, email to

Bug#623167: cupt: unable to set download client socket timeout: Protocol not available

2011-04-19 Thread Jonathan Nieder
Hi again, Eugene V. Lyubimkin wrote: Yes, the functionality is not critical, it's an additional check against download methods (which could be also be written by third parties). I just committed a one-line fix to turn this into a warning. Depending on the view of porters/bug reporter, this

Bug#623167: cupt: unable to set download client socket timeout: Protocol not available

2011-04-18 Thread Eugene V. Lyubimkin
Hi, On 2011-04-17 19:29, Jonathan Nieder wrote: The cause: cupt calls setsockopt(sock, SOL_SOCKET, SO_RCVTIMEO, tv, sizeof(tv)) for an AF_UNIX socket and expects it to succeed rather than returning ENOPROTOOPT. hurd (even upstream master as of today) has a stub implementation

Bug#623167: cupt: unable to set download client socket timeout: Protocol not available

2011-04-17 Thread Jonathan Nieder
Package: cupt Version: 2.0.0~rc2 Severity: normal Justification: cupt update broken on hurd Hi cupt hackers and hurd porters, On hurd: | # cupt update | W: an attempt to set wrong list option 'Acquire::gpgv::Options' | E: unable to set download client socket timeout: Protocol not available | E: