From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:58931) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZDMb-0007Hq-Ee for guix-patches@gnu.org; Mon, 25 Nov 2019 07:21:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iZDDr-0004Nh-Sm for guix-patches@gnu.org; Mon, 25 Nov 2019 07:12:09 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:41745) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iZDDq-0004Mm-P9 for guix-patches@gnu.org; Mon, 25 Nov 2019 07:12:07 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iZDDl-0002Pr-MB for guix-patches@gnu.org; Mon, 25 Nov 2019 07:12:01 -0500 Subject: [bug#38272] [PATCH] gnu: Add emacs-openwith. Resent-Message-ID: From: Marius Bakke In-Reply-To: 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> Date: Sun, 24 Nov 2019 23:28:07 +0100 Message-ID: <87y2w47vuw.fsf@devup.no> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: zimoun , 38272@debbugs.gnu.org, David Wilson --=-=-= Content-Type: text/plain zimoun writes: > Hi Marius, > > On Thu, 21 Nov 2019 at 19:37, Marius Bakke 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. :-) > > [1] https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket Thanks for the link. I hope the affected archives will be available through the Software Heritage API for the time travellers among us. > 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. For this package in particular, I think it's okay to go with the original emacsmirror source David used, as the code had not changed since 2012. :-) More active packages probably already have a migration plan, so I suppose we'll have to deal with it on a case by case basis. > 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? I think one bug to track it is sufficient, but no strong opinion. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl3bA/cACgkQoqBt8qM6 VPpgbgf+IbeUkG4VKqCX8GivwMaqVkatlL/HnkaTzsHh7ZZVoFMUaqo2z4DjCzzh ag8x+Upp/iohSkXIFgHcCFR+JCQhfEO5IuRWkK3O1k+s5UVbFzn+GVw/UfTJ6lp0 A8Rrqcrc70O3HZ/Mv/N4F6R87CFZ3n3LTN//hPd4hJTz2STDnKo/TlOkDYwVw3zG G8bxOZiN0gSOl+gQLBLB9brKO1iYBH+8eHDTMZWVfdoQSjYWp1Jt+DMNf/KI1Gb1 3b6FoA1lFzZUVAOQVxR51XstRkF/dc2bAAPjcf7X7CaUUGjKJno87n00rz1RJa4W 1HEwh8ZWTW6sbeMOFyGLSFfc92hL/g== =R33U -----END PGP SIGNATURE----- --=-=-=--