From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:470:142:3::10]:59459)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1iY9ZW-0007xD-PS
 for guix-patches@gnu.org; Fri, 22 Nov 2019 09:06:07 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1iY9ZU-0007pI-Jg
 for guix-patches@gnu.org; Fri, 22 Nov 2019 09:06:06 -0500
Received: from debbugs.gnu.org ([209.51.188.43]:45174)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1iY9ZU-0007pC-Fw
 for guix-patches@gnu.org; Fri, 22 Nov 2019 09:06:04 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1iY9ZU-0008Uq-2E
 for guix-patches@gnu.org; Fri, 22 Nov 2019 09:06:04 -0500
Subject: [bug#38272] [PATCH] gnu: Add emacs-openwith.
Resent-Message-ID: <handler.38272.B38272.157443155432645@debbugs.gnu.org>
MIME-Version: 1.0
References: <6928567c-cd7f-40d9-be83-64aae9cc9cac@www.fastmail.com>
 <875zjfaa8i.fsf@devup.no>
 <69ad356e-7f07-41df-b381-dfc90e71454d@www.fastmail.com>
 <87tv6x6pq6.fsf@devup.no>
In-Reply-To: <87tv6x6pq6.fsf@devup.no>
From: zimoun <zimon.toutoune@gmail.com>
Date: Fri, 22 Nov 2019 15:05:35 +0100
Message-ID: <CAJ3okZ1Cox-uY8CceqZRsSjB1XRR_ZHB1rCPbh2-NecXtC5PvQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
List-Id: <guix-patches.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-patches>,
 <mailto:guix-patches-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-patches>
List-Post: <mailto:guix-patches@gnu.org>
List-Help: <mailto:guix-patches-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-patches>,
 <mailto:guix-patches-request@gnu.org?subject=subscribe>
Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org
Sender: "Guix-patches" <guix-patches-bounces+kyle=kyleam.com@gnu.org>
To: 38272@debbugs.gnu.org, Marius Bakke <mbakke@fastmail.com>, David Wilson <david@daviwil.com>

Hi Marius,

On Thu, 21 Nov 2019 at 19:37, Marius Bakke <mbakke@fastmail.com> wrote:

> But, I read in another message that BitBucket is shutting down Mercurial
> support in 2020, so I'm not sure what to do about it.  Thoughts?

The timeline of the shutdown is here [1] so we have still some time. :-)

The best seems to first list all the packages offended via some scheme
code -- I have no idea how many packages will be impacted.
Then contact each upstream to know what is their plan, i.e., where the
new location of the source will be: git conversion and still on
BitBucket; still hg and move to elsewhere; etc.

I do not know if it is better to open only one bug report to track the
progress (maybe my preference), or to open one bug report per package.

What do you think?


All the best,
simon

[1] https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket