From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: bug#27795: Issues with upstream source for guile-emacs Date: Sun, 23 Jul 2017 16:22:06 +0200 Message-ID: <877eyz8c8h.fsf@elephly.net> References: <20170722231904.GA7314@jasmine.lan> <87d18r8hbb.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36782) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dZHmk-0004py-35 for bug-guix@gnu.org; Sun, 23 Jul 2017 10:23:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dZHmg-0001Tq-Vg for bug-guix@gnu.org; Sun, 23 Jul 2017 10:23:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:50873) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dZHmg-0001Tc-Rm for bug-guix@gnu.org; Sun, 23 Jul 2017 10:23:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dZHmg-0004xc-Cd for bug-guix@gnu.org; Sun, 23 Jul 2017 10:23:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87d18r8hbb.fsf@elephly.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Leo Famulari Cc: 27795@debbugs.gnu.org Ricardo Wurmus writes: > Leo Famulari writes: > >> While working on the bug 'Changing package source URLs from git:// to >> https://' [0], I noticed an issue with the sources for guile-emacs. >> >> We currently fetch this source code over the unauthenticated GIT >> protocol. It is also available over HTTPS. However, these two protocols >> are returning different Git repos for some reason. > > The clone times out for me: > > --8<---------------cut here---------------start------------->8--- > git clone https://git.hcoop.net/git/bpt/emacs.git guile-emacs-over-https > Cloning into 'guile-emacs-over-https'... > ^C > --8<---------------cut here---------------end--------------->8--- > > But the clone from git:// works fine. > > Is the repository actually served over HTTPS? Don’t mind me. It eventually worked. The repositories have different histories, and the https-repo looks like it is two commits behind. Looks like an older rebase. I’d say we should leave it with the current git:// URL. -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net