D-Bus service for Apertium - Revision history

Tino Didriksen: Text replacement - "(chat|irc)\.freenode\.net" to "irc.oftc.net"

2021-05-27T06:27:55Z

Text replacement - "(chat|irc)\.freenode\.net" to "irc.oftc.net"

2018-04-13T19:36:28Z

svn link updated

2018-03-08T05:05:46Z

GitHub migration

2018-03-07T22:09:47Z

2013-10-29T11:01:33Z

Installing

2013-10-29T10:29:13Z

Installing

2013-10-29T10:26:29Z

Installing

2013-10-29T10:09:57Z

Installing

2013-10-29T09:40:25Z

Installing

2013-07-15T15:57:32Z

Upated bugzilla link

@@ Line 60: / Line 60: @@
 This neat utility shows you the activity on the D-Bus. Now try executing <code>dbus-send --print-reply --dest=org.apertium.info / org.apertium.Info.modes</code> again.
-If you have no luck, come and talk to us in <code>#apertium</code> at <code>irc.freenode.net</code>
+If you have no luck, come and talk to us in <code>#apertium</code> at <code>irc.oftc.net</code>
 ==Installing into a prefix==

@@ Line 21: / Line 21: @@
 <pre>
-$ svn co http://apertium.svn.sourceforge.net/svnroot/apertium/trunk/apertium-dbus
+$ svn co https://svn.code.sf.net/p/apertium/svn/trunk/apertium-dbus
 </pre>

@@ Line 1: / Line 1: @@
-{{Github-migration-check}}
 {{TOCD}}
 [http://dbus.freedesktop.org/ D-Bus] is a simple inter-process communication system. We are in the process of developing D-Bus services for Apertium which will make programmatic access to the Apertium tools easier.
@@ Line 16: / Line 15: @@
 ==Installing==
+'''Note:''' After Apertium's migration to GitHub, this tool is '''read-only''' on the SourceForge repository and does not exist on GitHub. If you are interested in migrating this tool to GitHub, see [[Migrating tools to GitHub]].
 The package is available from [[SVN]] in the <code>apertium-dbus</code> module. The process for installation is the standard:

@@ Line 1: / Line 1: @@
+{{Github-migration-check}}
 {{TOCD}}
 [http://dbus.freedesktop.org/ D-Bus] is a simple inter-process communication system. We are in the process of developing D-Bus services for Apertium which will make programmatic access to the Apertium tools easier.

@@ Line 28: / Line 28: @@
 </pre>
-The current package is in the process of being ported to Python3. Do "svn up -r25849" to get the last working Python2 version.
+The current package is in the process of being ported to Python3, but should work. Do "svn up -r25849" if you want to get the last working Python2 version instead.
 ===Check that it works===

@@ Line 28: / Line 28: @@
 </pre>
-'''Note''': The current svn tip is ported to Python3, but doesn't seem to work:
+The current package uses Python3. Do "svn up -r25849" to get the last working Python2 version.
-<pre>
-$ /usr/local/share/apertium/dbus-1/info.py -p /usr/local
-Traceback (most recent call last):
-  File "/usr/local/share/apertium/dbus-1/info.py", line 78, in <module>
-    service.run_as("org.apertium.info")
-  File "/usr/local/share/apertium/dbus-1/service.py", line 37, in run_as
-    mainloop = gi._gobject.MainLoop()
-AttributeError: 'module' object has no attribute 'MainLoop'
-</pre>
-Do "svn up -r25849" to get the working Python2 version.
 ===Check that it works===

@@ Line 24: / Line 24: @@
 <pre>
 $ ./autogen.sh
-$ ./configure
 $ make
 $ make install

@@ Line 51: / Line 51: @@
 If the above two commannds don't work, then it's quite possible that a Python error from our side snuck in. Try running info.py directly; that is
 :<code>python info.py -p /usr/local</code>
-where the prefix for Apertium in the above example is <code>/usr/local</code>. If you get a Python error, please post the error on this page or post a bug report in [http://xixona.dlsi.ua.es/bugzilla/ our bug tracker]. If the service starts up without errors, try executing
+where the prefix for Apertium in the above example is <code>/usr/local</code>. If you get a Python error, please post the error on this page or post a bug report in [http://bugs.apertium.org/cgi-bin/bugzilla/index.cgi our bug tracker]. If the service starts up without errors, try executing
 :<code>dbus-send --print-reply --dest=org.apertium.info / org.apertium.Info.modes</code>
 again. If there is no output, then open a new terminal and run