It worked for me: Naitaka:~ mathuaerknedam$ hg clone https://hg.adium.im/adium scr/adium-new
warning: connecting to hg.adium.im using legacy security technology (TLS 1.0); see https://mercurial-scm.org/wiki/SecureConnections for more info warning: connecting to hg.adium.im using legacy security technology (TLS 1.0); see https://mercurial-scm.org/wiki/SecureConnections for more info warning: connecting to hg.adium.im using legacy security technology (TLS 1.0); see https://mercurial-scm.org/wiki/SecureConnections for more info requesting all changes warning: connecting to hg.adium.im using legacy security technology (TLS 1.0); see https://mercurial-scm.org/wiki/SecureConnections for more info adding changesets adding manifests adding file changes added 5951 changesets with 69292 changes to 34410 files (+10 heads) warning: connecting to hg.adium.im using legacy security technology (TLS 1.0); see https://mercurial-scm.org/wiki/SecureConnections for more info updating to branch default 6538 files updated, 0 files merged, 0 files removed, 0 files unresolved On Sat, Sep 17, 2016 at 6:16 AM, Robert Vehse <robertve...@fastmail.fm> wrote: > Hi everyone, > > Recently, I twice tried to download Adium source from our repo and each time > the download timed out. Yesterday, a user reported cloning didn’t work for > them either > (https://www.facebook.com/permalink.php?story_fbid=10153957981491819&id=6521951818&comment_id=10153987753641819&reply_comment_id=10153987939626819&comment_tracking=%7B%22tn%22%3A%22R5%22%7D). > > For now, should we perhaps only point to Bitbucket at > https://trac.adium.im/wiki/GettingNewestAdiumSource (and possibly other > places)? > > Regards, > Robbie -- Matthew
