Bug 121268

Summary: gpilot conduits unable to instantuate on x86_64
Product: [Fedora] Fedora Reporter: Justin M. Forbes <64bit_fedora>
Component: gnome-pilot-conduitsAssignee: Matthew Barnes <mbarnes>
Status: CLOSED CANTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-10-29 21:54:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
gnome-pilot-2.0.10-lib64.patch
none
updated spec for gnome-pilot
none
gnome-pilot-2.0.10-lib64.patch
none
Updated spec for gnome-pilot-conduits
none
evolution-1.4.6-lib64conduit.patch
none
updated spec for evolution none

Description Justin M. Forbes 2004-04-19 21:00:52 UTC
gpilot gives "Unable to instantiate (insert Conduit name here)
conduit" for all conduits tested so far (Calendar, Todo, Memo, Backup,
and Contacts) on x86_64 systems.  Adding a new device was able to pull
the userid from the treo 600, so it seems to be isolated to conduit.

Comment 1 Justin M. Forbes 2004-06-02 04:23:31 UTC
Okay, got it all fixed.  The issue lies in the way
/usr/share/gnome-pilot/conduits/*.conduit are created.  The fix
requires a patch against each conduit's .conduit.in file and Makefile.
 Attached are updated specs and patches for gnome-pilot,
gnome-pilot-conduit, and evolution.  This gets all of them it seems,
and will build and function appropriately on lib and lib64 systems. 
Please push when you can, as gnome-pilot is essentially useless on
x86_64 until these are applied.

Comment 2 Justin M. Forbes 2004-06-02 04:25:14 UTC
Created attachment 100780 [details]
gnome-pilot-2.0.10-lib64.patch

This fixes the default .conduits paths in /usr/share/gnome-pilot/conduits/

Comment 3 Justin M. Forbes 2004-06-02 04:26:25 UTC
Created attachment 100781 [details]
updated spec for gnome-pilot

Comment 4 Justin M. Forbes 2004-06-02 04:27:32 UTC
Created attachment 100782 [details]
gnome-pilot-2.0.10-lib64.patch

Patch to fix paths in /usr/share/gnome-pilot/conduits/*.conduit

Comment 5 Justin M. Forbes 2004-06-02 04:27:57 UTC
Created attachment 100783 [details]
Updated spec for gnome-pilot-conduits

Comment 6 Justin M. Forbes 2004-06-02 04:28:51 UTC
Created attachment 100784 [details]
evolution-1.4.6-lib64conduit.patch

patch to fix the paths in /usr/share/gnome-pilot/conduits/*.conduit

Comment 7 Justin M. Forbes 2004-06-02 04:29:14 UTC
Created attachment 100785 [details]
updated spec for evolution

Comment 8 Justin M. Forbes 2004-06-02 04:33:17 UTC
Added patch in the evolution.spec is patch12


Comment 9 Justin M. Forbes 2004-07-08 22:17:32 UTC
Any chance of getting these patches pushed? FC3 release cycle is
kicking up now, and it is easy to forget about these things.  Until
this is patched, current x86_64 users cannot use any conduits.

Comment 10 Dave Malcolm 2004-08-20 03:04:34 UTC
Sorry it's taken so long for me to comment on this bug.

Attachment id=100780 has been in gnome-pilot since 2.0.10-8
Attachment id=100781 appears to simply add that patch; this was taken
care of at that time.

I've now applied attachments id=100782 and 100783 to
gnome-pilot-conduits and rebuilt into Rawhide as version 2.0.10-4

Attachment ids 100784 and 100785 remain to be applied to the 1.4
branch.  Looking at the latest Evolution package (1.5.93), the
conduits appear to use @privconduitdir@ which is generated from
${libdir}, so I believe that we don't need to apply these to fix the
1.5 branch of Evolution.

Does this functionality work in Evolution 1.5.93 on x86_64 with the
latest rawhide packages?





Comment 12 John Thacker 2006-10-29 21:54:13 UTC
Closing per lack of response to previous request for information.  Note that FC3
and FC4 are supported by Fedora Legacy for security fixes only.  Please test
this on FC5 or FC6.  If it still occurs there, please reopen and change the
version to fc5 or fc6.  Otherwise, if this is a security issue, please reassign
the bug to Fedora Legacy.  Thanks, and we apologize for not getting to this bug
earlier.