GNU bug report logs - #22458
Collision between khal and vdirsyncer "bin/vdirsyncer"

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 22458 in the body.
You can then email your comments to 22458 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: bug-guix <at> gnu.org
Subject: Collision between khal and vdirsyncer "bin/vdirsyncer"
Date: Sun, 24 Jan 2016 18:24:39 -0500

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.

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.

Is this a common issue that we have a workaround for? I wonder if
we can fix this in our package, or if I should take it upstream?

I found this discussion on guix-devel relating to easy-install and path
collisions, although I'm not sure if it's relevant:
http://lists.gnu.org/archive/html/guix-devel/2014-12/msg00283.html

Collisions!
warning: collision encountered: /gnu/store/xxfyiwan4aidigk552i9pnm5z6myhk09-vdirsyncer-0.7.5/bin/vdirsyncer /gnu/store/8y78mn6ng28h0lihkfb8qasrlfydnnfy-khal-0.7.0/bin/vdirsyncer 
warning: arbitrarily choosing /gnu/store/xxfyiwan4aidigk552i9pnm5z6myhk09-vdirsyncer-0.7.5/bin/vdirsyncer

Here is the output of `tree -a bin` from within khal's store directory:
bin
├── easy_install -> /gnu/store/8y78mn6ng28h0lihkfb8qasrlfydnnfy-khal-0.7.0/bin/.easy_install-wrap-01
├── easy_install-3.4 -> /gnu/store/8y78mn6ng28h0lihkfb8qasrlfydnnfy-khal-0.7.0/bin/.easy_install-3.4-wrap-01
├── .easy_install-3.4-real
├── .easy_install-3.4-wrap-01
├── .easy_install-real
├── .easy_install-wrap-01
├── ikhal -> /gnu/store/8y78mn6ng28h0lihkfb8qasrlfydnnfy-khal-0.7.0/bin/.ikhal-wrap-01
├── .ikhal-real
├── .ikhal-wrap-01
├── khal -> /gnu/store/8y78mn6ng28h0lihkfb8qasrlfydnnfy-khal-0.7.0/bin/.khal-wrap-01
├── .khal-real
├── .khal-wrap-01
├── vdirsyncer -> /gnu/store/8y78mn6ng28h0lihkfb8qasrlfydnnfy-khal-0.7.0/bin/.vdirsyncer-wrap-01
├── .vdirsyncer-real
└── .vdirsyncer-wrap-01

Here are the contents of .vdirsyncer-real:
#!/gnu/store/jdjxwh49zwnl954yk5rz09i0p0pcx42k-python-wrapper-3.4.3/bin/python
# EASY-INSTALL-ENTRY-SCRIPT: 'vdirsyncer==0.7.5','console_scripts','vdirsyncer'
__requires__ = 'vdirsyncer==0.7.5'
import sys
from pkg_resources import load_entry_point

if __name__ == '__main__':
    sys.exit(
        load_entry_point('vdirsyncer==0.7.5', 'console_scripts', 'vdirsyncer')()
    )

Message #8 received at 22458 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Leo Famulari <leo <at> famulari.name>
Cc: 22458 <at> debbugs.gnu.org
Subject: Re: bug#22458: Collision between khal and vdirsyncer "bin/vdirsyncer"
Date: Wed, 03 Feb 2016 22:56:21 +0100

Leo Famulari <leo <at> famulari.name> 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?

Ludo’.

Message #11 received at 22458 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Leo Famulari <leo <at> famulari.name>
Cc: 22458 <at> debbugs.gnu.org
Subject: Re: bug#22458: Collision between khal and vdirsyncer "bin/vdirsyncer"
Date: Tue, 03 May 2016 22:24:37 +0200

ludo <at> gnu.org (Ludovic Courtès) skribis:

> Leo Famulari <leo <at> famulari.name> 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?  :-)

Ludo’.

Message #16 received at 22458 <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 22458 <at> debbugs.gnu.org
Subject: Re: bug#22458: Collision between khal and vdirsyncer "bin/vdirsyncer"
Date: Tue, 3 May 2016 17:48:26 -0400

On Tue, May 03, 2016 at 10:24:37PM +0200, Ludovic Courtès wrote:
> ludo <at> gnu.org (Ludovic Courtès) skribis:
> 
> > Leo Famulari <leo <at> famulari.name> 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.

Message #21 received at 22458-done <at> debbugs.gnu.org (full text, mbox):

From: Leo Famulari <leo <at> famulari.name>
To: 22458-done <at> debbugs.gnu.org
Cc: Hartmut Goebel <h.goebel <at> crazy-compilers.com>
Subject: Re: bug#22458: Collision between khal and vdirsyncer "bin/vdirsyncer"
Date: Fri, 2 Dec 2016 14:20:31 -0500

On Sun, Jan 24, 2016 at 06:24:39PM -0500, Leo Famulari wrote:
> warning: collision encountered: /gnu/store/xxfyiwan4aidigk552i9pnm5z6myhk09-vdirsyncer-0.7.5/bin/vdirsyncer /gnu/store/8y78mn6ng28h0lihkfb8qasrlfydnnfy-khal-0.7.0/bin/vdirsyncer 
> warning: arbitrarily choosing /gnu/store/xxfyiwan4aidigk552i9pnm5z6myhk09-vdirsyncer-0.7.5/bin/vdirsyncer

Hartmut's work on the python-build-system has fixed this bug. Thank you
Hartmut!

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.