From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: pcmanfm version update Date: Sat, 9 Apr 2016 21:06:19 -0400 Message-ID: <20160410010619.GB29029@jasmine> References: <87shyvrww4.fsf@gmail.com> <71ca60a5ce463ec85842355bdf5d86c6@openmailbox.org> <87bn5i4u2u.fsf@gmail.com> <20160409171958.GA25062@solar> <20160409195903.GC7587@debian-netbook> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40032) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ap3pK-0001Zr-1k for guix-devel@gnu.org; Sat, 09 Apr 2016 21:06:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ap3pG-00023T-Sk for guix-devel@gnu.org; Sat, 09 Apr 2016 21:06:09 -0400 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:58244) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ap3pG-00023P-PJ for guix-devel@gnu.org; Sat, 09 Apr 2016 21:06:06 -0400 Content-Disposition: inline In-Reply-To: <20160409195903.GC7587@debian-netbook> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Efraim Flashner Cc: guix-devel@gnu.org, Alex Kost , rain1@openmailbox.org On Sat, Apr 09, 2016 at 10:59:03PM +0300, Efraim Flashner wrote: > We do have some packages that have to be updated together, acme and > letsencrypt, python-cryptography and python-cryptography-vectors. But > those do have a commit message that they are updated together. If those packages were updated separately, the build would break after the first commit. Neither of those package pairs works if the versions are not in sync [0]. In my opinion, that is a valid reason for updating multiple packages in the same commit. [0] It's a little more complicated than that. Python-acme does not depend on letsencrypt, so it should still work if updated separately. But we should not break letsencrypt if we can help it. Letsencrypt and python-acme are developed in the same code base and are only separated for distribution, AFAICT.