On Thu, 2008-06-05 at 13:36 +0200, Dr J A Gow wrote: > On Thu, 2008-06-05 at 11:46 +0930, Iain Buchanan wrote: > > Hi again, > > > > sorry I'm a bit slow at trying this out atm... > > > > No problem - many thanks for your comprehensive analysis. > > > > First thing: config/config.xml is still listed in setup.py - I think > > it's change to config/syncengine.conf.xml and where is it supposed to go > > now? /etc? I'm happy if you leave it out of setup.py, then the distro > > can do it. > > > > Mea culpa! Again :) > > Not being a packager I tend to forget setup.py. I'll change this in the > next bunch of commits I have planned. That is right - it should go > in /etc to form the systemwide config. > > > > There will be no change in functionality, but I have altered a debug > > > message to highlight the absolute path to the authorization tool. The > > > line 'auth: auth prog INTERNAL_GUI does not exist' should now read > > > 'auth: auth prog <filename> does not exist'. Can you check whether > > > <filename> is present on your system and let me know the result? > > > > It says: > > > > auth: auth prog > > /usr/lib/python2.5/site-packages/SyncEngine/../tools/authgui.py does not > > exist > > > > and there is no authgiu.py installed anywhere. Is this a packaging > > thing? > > > > It should be installed. It resides in 'tools'. Maybe this is not the > best place to put it as it is strictly called from sync-engine and not a > tool that can be called directly from the CLI, although it is a separate > program in its own right. > > > I added > > 'tools/authgui.py', > > to setup.py, which installed it into /usr/bin (not sure if this is the > > right way), then changed AuthMethod in /etc/syncengine.conf.xml to > > <AuthMethod>/usr/bin/authgui.py</AuthMethod> > > > > But I see this from sync-engine: > > 2008-06-05 11:36:14,699 INFO engine.config.Config : UpdateConfig - unable > > to open system config file - using defaults > > 2008-06-05 11:36:14,699 INFO engine.config.Config : UpdateConfig - unable > > to open system config file - using defaults > > 2008-06-05 11:36:14,701 INFO engine.syncengine.kernel : device IO2 > > connected > > 2008-06-05 11:36:14,702 INFO engine.syncengine.kernel : ProcessAuth : > > processing authorization for device 'IO2' > > auth: auth prog > > /usr/lib/python2.5/site-packages/SyncEngine/../tools/authgui.py does not > > exist > > > > I checked the permissions on /etc/syncengine.conf.xml, and its readable > > by everyone. I checked config.py and it seems to be building the > > path /etc/syncengine.conf.xml. > > > > Finally I copied authgui.py > > to /usr/lib/python2.5/site-packages/SyncEngine/../tools/authgui.py and > > ran sync-engine again. This time it worked - popping up the gui. > > > > So in summarising, these are the questions I'm left with: > > 1. Where should syncengine.conf.xml go > > The systemwide file in /etc and the user file in ~/.synce >
Or for the source package stick it in somewhere like /usr/share/sync-engine-doc, so it's available but not installed by default. Or not, doesn't really matter. > > 2. Where should the internal authgui.py go > > At the moment it sits in 'tools' and sync-engine expects it there. The > fact it is not installed sounds like a packaging problem combined with > the hardcoded relative path in sync-engine. > > Packagers: Can any of the packagers reading this tell me where you would > prefer to place it? I can then adapt sync-engine to be able to see it. > >From the point of view of the source tree I think I will move it from > tools as it does not fit into the category of 'tools' as such. > I'd say anywhere in the engine module tree. Although it's technically a separate program it's very much part of sync-engine. > > 3. Why did I see "unable to open system config file" > > Normally should be because you don't have syncengine.conf.xml in /etc. > But you do :) So I should be able to repeat this problem and fix it. > Permissions ? > > 4. Even without the internal auth gui, I was using synce-gnome to > > authenticate - why didn't sync-engine like this? > > I will have to investigate this. If sync-engine sees a pre-authenticated > device it should not try to re-authenticate. I am a kde user and do not > use gnome - could you elaborate on how synce-gnome authenticates (from a > user's perspective? I may pick up some clues from this. > Not much time to investigate, so I'll take a guess at this. Device is plugged in, sync-engine and synce-gnome see it needs a password. synce-gnome provides the password, and unlocks the device. Meanwhile, sync-engine fails to authenticate directly via _ProcessAuth, but does see the auth state changes, and some confusion results ? Mark
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php
_______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
