libc6_2.3.1-10_i386.deb
libgnome-pilot1-dev_0.1.71-3_i386.deb
libdb1-compat_2.1.3-7_i386.deb
libgnome-pilot1_0.1.71-3_i386.deb
and trying to compile pilot I couldn't solve this problem
gpilotd-WARNING **: Unable to bind to pilot
and I installed gpilot *** .deb + conduits
I didn't uninstall the higher version of libc6 and the rest of
the packeges
and now I can sync all of the conduits
I am very very glad about this!!!
Unfortunately I had to give up some applications that depend on those
packeges
mainly on libc6 :-)) I think all of you know what I mean
Do I have to update all the packeges that depend on libc6 or how could I get the opreability of my lost programs again?
The problem seems to come from dependencies of locales on glibc-2.2.5-14.3, that seems to be not avilable - I think debians foult as I read in some newsgroups
dpkg: dependency problems prevent configuration of locales:
locales depends on glibc-2.2.5-14.3; however:
Package glibc-2.2.5-14.3 is not installed.
Do I have to install gcc - g++ by myself ???
Please help!
-- + Emanoil Kotsev - - - - -+ | tel. 0043(1)9253175 | | cel. -------------- | + E-Mail: emanuel abc at +
--- Begin Message ---I tried to install
- From: Emanoil Kotsev <emanuel abc at>
- To: gnome-pilot-list gnome org
- Subject: [Fwd: Memo-File Conduit problem]
- Date: Sat, 25 Jan 2003 02:54:35 +0100
pilot-link-0.11.7.tar.gz
gnome-pilot-0.1.71.tar.gz
gnome-pilot-conduits_0.10.tar.gzNow MemoFile isn't crashing the conduit but
I have following message
emanoil bendida:~$ ps -A | grep pilot
1106 pts/1 00:00:00 gpilot-applet
1140 ? 00:00:00 gpilotd
emanoil bendida:~$ gpilotd-Message: Woke on Cradle
gpilotd-Message: setting PILOTRATE=57600gpilotd-WARNING **: Unable to bind to pilot
I did have to update
libc6_2.3.1-10_i386.deb
libgnome-pilot1-dev_0.1.71-3_i386.deb
libdb1-compat_2.1.3-7_i386.deb
libgnome-pilot1_0.1.71-3_i386.debI think I would be able to sync with my Palm as far as I fix this
any ideas?
I use Palm III
thanks
-- + Emanoil Kotsev - - - - -+ | tel. 0043(1)9253175 | | cel. -------------- | + E-Mail: emanuel abc at +--- Begin Message ---
- From: Michael Timmins <mat3q virginia edu>
- To: gnome-pilot-list gnome org
- Subject: Re: [Fwd: File Conduit problem]
- Date: 24 Jan 2003 09:05:51 -0500
My solution thus far has been to write a shell script that kills gpilotd, uses pilot-xfer to install the files I ask it to and then restarts gpilotd. This way I can use evolution to sync everything and file installation is a little easier which is fine since I don't install files all that often. Mike On Thu, 2003-01-23 at 18:47, Emanoil Kotsev wrote: > Unfortunately I am looking for a wize sollution too > > What I am doing right now as work arround is I am syncing all the > stuff with Evolution except File, what I am doing with the > pilot-manager. > > I tought I could sync everything with pilot-manager, though it is not > that functional as Evolution and above this I have other errors > comming from the perl modules, that I could fix easier if I had the > time - may be in feb. or march. > > Untill then I will hope, look for, and be glad for some fix or > sollution. > > Below my config dump > I don't see any Pilot ID and some other thing diff file hanging down > in this mail too produced by > > find .gnome/gnome-pilot.d/ -type f -printf '######## \n' -print -exec > cat {} \; > ./gnome-pilot.d_dump > > It could be problem of gnome-core too I am not quite sure. > > I will try to compile and fix it ASAP as said in feb, but it would be > fine if this reaches somebody responsible for this issue and able to > do something for us > > If you have any informatioin let me know > > regards > -- > + Emanoil Kotsev - - - - -+ > | tel. 0043(1)9253175 | > | cel. -------------- | > + E-Mail: emanuel abc at + > > > ______________________________________________________________________ > > From: Michael Timmins <mat3q virginia edu> > To: gnome-pilot-list gnome org > Subject: [Fwd: File Conduit problem] > Date: 23 Jan 2003 09:09:26 -0500 > > Hi again, > I though I should also post my config files (at least the ones i thought > might possibly be relevant). There doesn't seem to be a configuration > file for the file conduit. It is the only one which doesn't but i > haven't been able to find out whether there should be one or what should > be in it. > Thanks, Mike Timmins > > ******************************************************* > .gnome/.gnome-pilot.d/conduits(): > > [General] > conduits=gpbackup1 e_address_conduit e_calendar_conduit e_todo_conduit > gpmemo1 gptime1 gpsendmail1 malconduit1 gpfile1 > > [gpbackup1] > sync_type=custom > > [e_address_conduit] > sync_type=synchronize > > [e_calendar_conduit] > sync_type=synchronize > > [e_todo_conduit] > sync_type=synchronize > > [gpmemo1] > sync_type=synchronize > > [gptime1] > sync_type=custom > > [gpsendmail1] > sync_type=custom > > [malconduit1] > sync_type=custom > > [gpfile1] > sync_type=custom > > ******************************************************* > .gnome/.gnome-pilot.d/gpilotd: > > [General] > sync_PC_Id=-1195810239 > progress_stepping=1 > num_devices=1 > num_pilots=1 > > [Device0] > type=0 > name=Cradle > device=/dev/pilot > speed=115200 > timeout=2 > > [Pilot0] > name=MyPilot > pilotid=0 > creation=0 > romversion=0 > pilotusername=mat3q > default_sync_action=custom > basedir=/home/mat3q/MyPilot > ******************************************************* > .gnome/gnome-pilot.d/queue > > [system] > number-of-requests=0 > ******************************************************* > > -- > Michael Timmins <mat3q virginia edu> > University of Virginia > > ______________________________________________________________________ > > From: Michael Timmins <mat3q virginia edu> > To: gnome-pilot-list gnome org > Subject: File Conduit problem > Date: 22 Jan 2003 18:02:09 -0500 > > Hi, > I'm running gnome-pilot under redhat 7.2 using the latest ximian-built > rpms. All other conduits work fine except for the file conduit. Any > suggestions? More info below. > > Thanks in advance, > Mike Timmins > > I'm getting the following error message running gpilot-install-file: > > gpilotd-WARNING **: gnome-pilot-client.gob:781: Caught exception: > IDL:GNOME/Pilot/UnknownPilot:1.0 > > The output from gpilotd looks like: > gpilotd-Message: gnome-pilot 0.1.69 starting... > gpilotd-Message: compiled for pilot-link version 0.11.5 > gpilotd-Message: compiled with [VFS] [GOAD] [USB] [IrDA] [Network] > gpilotd-Message: Activating CORBA server > gpilotd-Message: Watching Cradle (/dev/pilot) > gpilotd-Message: gpilotd: corba: get_pilots(...) > gpilotd-Message: gpilotd: corba: request_install(pilot_name=MyPilot > (0),filename=/home/mat3q/.gpilotd/PDBMrmR2v,survival=1,tim > eout=0) > gpilotd-Message: Woke on Cradle > gpilotd-Message: setting PILOTRATE=115200 > gpilotd-Message: Cradle Cradle has 0 events > gpilotd-Message: Instantiating 9 conduits... > gpilotd-Message: Instantiated 1 backup conduits, 1 file conduits, 7 > other conduits > gpilotd-Message: HotSync button pressed, synchronizing pilot > gpilotd-Message: Pilot ID is 0, name is MyPilot, owner is @ .@ > @T! DQv@C > gpilotd-Message: Pilot has 0 entries in restore queue > gpilotd-Message: Pilot has 0 entries in conduit queue > gpilotd-Message: Using conduit settings for sync... > gpilotd-Message: Pilot has 0 entries in file install queue -- Michael Timmins <mat3q virginia edu> University of Virginia _______________________________________________ gnome-pilot-list mailing list gnome-pilot-list gnome org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
--- End Message ---
--- End Message ---