From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#22458: Collision between khal and vdirsyncer "bin/vdirsyncer" Date: Tue, 3 May 2016 17:48:26 -0400 Message-ID: <20160503214826.GA14028@jasmine> References: <20160124232439.GA8199@jasmine> <871t8t5ugq.fsf@gnu.org> <8737pykhyy.fsf@gnu.org> 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]:35687) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1axiBz-0005yQ-Oh for bug-guix@gnu.org; Tue, 03 May 2016 17:49:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1axiBo-0000B2-3z for bug-guix@gnu.org; Tue, 03 May 2016 17:49:14 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:51832) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1axiBl-00009Y-ST for bug-guix@gnu.org; Tue, 03 May 2016 17:49:08 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1axiBi-0008Eu-Gi for bug-guix@gnu.org; Tue, 03 May 2016 17:49:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <8737pykhyy.fsf@gnu.org> 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 22458@debbugs.gnu.org On Tue, May 03, 2016 at 10:24:37PM +0200, Ludovic Courtès wrote: > ludo@gnu.org (Ludovic Courtès) skribis: > > > Leo Famulari skribis: > > > >> The packages khal and vdirsyncer are meant to be used together. Khal is > >> a console calendar program and vdirsyncer synchronizes CalDAV data from > >> a remote server to the local filesystem so that khal can use it. > > > > Then why do they both provide the same file? :-) > > > >> For some reason, the khal package is creating an > >> "EASY-INSTALL-ENTRY-SCRIPT" (as "bin/.vdirsyncer-real") that wraps the > >> propagated vdirsyncer executable. This means that both the khal and > >> vdirsyncer packages contain the path "bin/vdirsyncer", which is > >> annoying. Thankfully, they both end up executing the real vdirsyncer. > > > > I’m not sure I follow. Does upstream khal explicitly intend to install > > its own bin/vdirsyncer? > > Ping? :-) Since I filed the bug, I might have learned enough to debug it. I'll take a look in the next day or so.