Autokey is a programm for automating task. See : autokey.googlecode.com Reproducible: Always Actual Results: no maintainer Expected Results: A maintainer
Hello, What I ment is can this bug assigned to maintainer-wanted or maintainer-needed so I can put my ebuild in Sunrise overlay. Roelof (In reply to comment #0) > Autokey is a programm for automating task. > See : autokey.googlecode.com > > Reproducible: Always > > Actual Results: > no maintainer > > Expected Results: > A maintainer >
Created attachment 208314 [details] The ebuild for autokey
(In reply to comment #2) > Created an attachment (id=208314) [details] > The ebuild for autokey > I cannot get your ebuild to work. The following line in your ebuild: SRC_URI="http://autokey.googlecode.com/files/${PN}_${PV}.tar.gz" parses as: SRC_URI="http://autokey.googlecode.com/files/autokey-gtk_${PV}.tar.gz" However I believe it should be: SRC_URI="http://autokey.googlecode.com/files/autokey_${PV}.tar.gz" So I edited the ebuild and hardcoded the line as I've shown above. ----------------- Second problem: As autokey_0.71.0.tar.gz is now in the repository, I renamed your ebuild to autokey-gtk-0.71.0 in my local overlay. Then I created the manifest: # ebuild autokey-gtk-0.71.0.ebuild manifest >>> Creating Manifest for /usr/local/portage/app-misc/autokey-gtk # But the merge fails. Here's the end of the merge output: running install_data creating /var/tmp/portage/app-misc/autokey-gtk-0.71.0/image/usr/share creating /var/tmp/portage/app-misc/autokey-gtk-0.71.0/image/usr/share/pixmaps copying config/akicon.png -> /var/tmp/portage/app-misc/autokey-gtk-0.71.0/image/usr/share/pixmaps copying config/akicon-status.png -> /var/tmp/portage/app-misc/autokey-gtk-0.71.0/image/usr/share/pixmaps creating /var/tmp/portage/app-misc/autokey-gtk-0.71.0/image/usr/share/applications copying config/autokey-qt.desktop -> /var/tmp/portage/app-misc/autokey-gtk-0.71.0/image/usr/share/applications copying config/autokey-gtk.desktop -> /var/tmp/portage/app-misc/autokey-gtk-0.71.0/image/usr/share/applications creating /var/tmp/portage/app-misc/autokey-gtk-0.71.0/image/usr/share/man creating /var/tmp/portage/app-misc/autokey-gtk-0.71.0/image/usr/share/man/man1 copying doc/man/autokey-qt.1 -> /var/tmp/portage/app-misc/autokey-gtk-0.71.0/image/usr/share/man/man1/ copying doc/man/autokey-gtk.1 -> /var/tmp/portage/app-misc/autokey-gtk-0.71.0/image/usr/share/man/man1/ running install_egg_info Writing /var/tmp/portage/app-misc/autokey-gtk-0.71.0/image/usr/lib64/python2.6/site-packages/autokey-0.71.0-py2.6.egg-info !!! newinitd: /var/tmp/portage/app-misc/autokey-gtk-0.71.0/work/build/debian/autokey-gtk.init does not exist * ERROR: app-misc/autokey-gtk-0.71.0 failed: * (no error message) * * Call stack: * ebuild.sh, line 56: Called src_install * environment, line 3372: Called die * The specific snippet of code: * newinitd "${S}"/debian/autokey-gtk.init autokey || die * * If you need support, post the output of 'emerge --info =app-misc/autokey-gtk-0.71.0', * the complete build log and the output of 'emerge -pqv =app-misc/autokey-gtk-0.71.0'. * This ebuild is from an overlay named 'local_overlay': '/usr/local/portage/' * The complete build log is located at '/var/lib/portage/logs/app-misc:autokey-gtk-0.71.0:20100911-205446.log'. * The ebuild environment file is located at '/var/tmp/portage/app-misc/autokey-gtk-0.71.0/temp/environment'. * S: '/var/tmp/portage/app-misc/autokey-gtk-0.71.0/work/build' * QA Notice: file does not exist: * * newinitd: /var/tmp/portage/app-misc/autokey-gtk-0.71.0/work/build/debian/autokey-gtk.init does not exist >>> Failed to emerge app-misc/autokey-gtk-0.71.0, Log file: >>> '/var/lib/portage/logs/app-misc:autokey-gtk-0.71.0:20100911-205446.log' Any ideas?
After further investigation, I think the problem is the following line in the ebuild: newinitd "${S}"/debian/autokey-gtk.init autokey || die I believe it should be: newinitd "${S}"/debian/autokey-common.init autokey || die However, the merge then fails with the following error message: The init.d file has syntax errors: /var/tmp/portage/app-misc/autokey-gtk-0.71.0/image///etc/init.d/autokey Having looked inside the file /var/tmp/portage/app-misc/autokey-gtk-0.71.0/work/build/debian/autokey-common.init, it contains a reference to DPM § 9.3.2 (Debian Policy Manual), so I wonder -- with my limited knowledge of this stuff - whether init script syntax in Debian is different to init script syntax in Gentoo.
Created attachment 278065 [details] ebuild for latest release 0.71.3 of Autokey (builds both gtk and qt versions)
(In reply to comment #5) > Created attachment 278065 [details] > ebuild for latest release 0.71.3 of Autokey (builds both gtk and qt versions) My hunch in Comment #4 was correct. The problem is the initscript syntax. However, I found Issue #106 in the Autokey Issues: http://code.google.com/p/autokey/issues/detail?id=106 that states that the autokey daemon is not needed for X.Org 1.7.6 and above, so I have removed it from the ebuild, renamed the ebuild to autokey-gtk-0.71.3.ebuild to reflect the latest version of Autokey, and it merges. Merging autokey-gtk-0.71.3 resulted in both autokey-gtk and autokey-qt being built. I then tried to launch autokey in KDE 4.6.2 by entering the command: $ /usr/bin/autokey-qt and it resulted in a few lines of error messages, the last line being "ImportError: cannot import name Qsci". Autokey Issue #76: http://code.google.com/p/autokey/issues/detail?id=76 shows that the solution is to install qscintilla and python-qscintilla, so I added those as dependencies in the ebuild. It now builds and, when I issue the command /usr/bin/autokey-qt, the Autokey GUI pops up and works in my cursory tests so far. So I'm posting the modified ebuild in this bug report, hoping that someone can clean it up as I have zero expertise as far as ebuilds are concerned.
Created attachment 303115 [details] autokey-gtk-0.81.4.ebuild Seems that the latest source code (0.81.4) has dropped Qt support. Anyway, here's a new ebuild for autokey-gtk-0.81.4
Created attachment 311505 [details] autokey-gtk-0.81.4.ebuild, revised An improved ebuild * added lacking DPEDNDS and RDEPENDS elements. (dbus-python, pygtksourceview, and wmctrl) * fixed postinst message (dbus reload -> restart) * added dohtml. API doc is now installed Regards.
Created attachment 311863 [details] autokey-gtk-0.90.3.ebuild In 0.90.3, autokey-qt is resurrected, but I don't know how to build it. autokey-qt is installed in /usr/bin, but it's not good. Many dev-python dependencies may be in fact RDEPEND, not DEPEND, but I'm not sure. autokey-0.81.4 doesn't work any more. It uses attach_to_status_icon(), but it's removed from dev-python/notify-python-0.1.1-r2, which is the only available version now. notify-python is a dead project, and autokey-0.90.3 doesn't rely on notify-python any more. I'm still having trouble using it. Search the Gentoo Forum for my report.
Created attachment 312323 [details] autokey-gtk-0.90.4.ebuild autokey-gtk-0.90.4.ebuild.
Created attachment 313009 [details] autokey-0.90.4.ebuild Let me post a new ebuild which supports qt version. The developer has decided to develop only in qt, and doesn't add new features to gtk version: http://groups.google.com/group/autokey-users/browse_thread/thread/4db35ccc592069c9# I changed the filename to autokey-0.90.4.ebuild, dropping "-gtk". I think the category should be x11-misc. The USE flag for qt is not tested. It requires heavy kde dependencies, which I don't like. As I said before, I can't use the gtk version. Since I don't know how to use it without GUI, I can't use autokey at all, but I hope this will help.
(In reply to comment #11) > Created attachment 313009 [details] > autokey-0.90.4.ebuild > The USE flag for qt is not tested. It requires heavy kde dependencies Works for me. Thanks. It is a great application. I used +qt4 -gtk which took me 15Mb, instead of more than 100Mb with +gtk -qt4. I am under xfce, but I have already many both qt and gtk applications installed. Unfortunatly, the file menu is not complete as it should be, but the keystrokes work, so it is alright. Moreover, it is not stable. It freezes after a short time and does not work anymore, though I could make it work once.
When I run it, I have : $ Exception in thread KeypressHandler-thread: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 530, in __bootstrap_inner self.run() File "/usr/lib64/python2.7/site-packages/autokey/iomediator.py", line 204, in run target.handle_keypress(rawKey, modifiers, key, windowName, windowClass) File "/usr/lib64/python2.7/site-packages/autokey/service.py", line 179, in handle_keypress currentInput, windowInfo, True) File "/usr/lib64/python2.7/site-packages/autokey/service.py", line 304, in __checkTextMatches if item.check_input(buffer, windowInfo): File "/usr/lib64/python2.7/site-packages/autokey/model.py", line 735, in check_input abbr = self._should_trigger_abbreviation(buffer) File "/usr/lib64/python2.7/site-packages/autokey/model.py", line 134, in _should_trigger_abbreviation if self.__checkInput(buffer, abbr): File "/usr/lib64/python2.7/site-packages/autokey/model.py", line 147, in __checkInput stringBefore, typedAbbr, stringAfter = self._partition_input(buffer, abbr) File "/usr/lib64/python2.7/site-packages/autokey/model.py", line 194, in _partition_input stringBefore, typedAbbr, stringAfter = currentString.rpartition(abbr) ValueError: empty separator
After having suppressed ~/.config/autokey, it works. I think their GUI is fragile.
Created attachment 317282 [details] autokey-0.90.4.ebuild, revised. This version incorporates the Sabayon overaly ebuild. * It supports gnome. * Some gtk dependencies are more accurate. Not tested, but at least emerge succeeded.
Created attachment 424266 [details] KDE crash dump I can get this to build fine, and I have to tweak the python/distutils values in the ebuild to install for python2.7 not 3 (work to do there!) but I perpetually get a crash trying to run it, as per attachment.
Hello, everyone. It seems that at least one ebuild related to this bug exists in the Sunrise overlay at the moment. However, I have to regretfully announce that after a long inactivity period the Sunrise project has been discontinued and the related overlay will be eventually removed. For this reason, I'd like to ask you to reevaluate the ebuilds and consider moving them. If you'd like to maintain a package from Sunrise in Gentoo, please take a look at our Proxy Maintainers [1] project. Please make sure to take ebuilds from the unreviewed developer Sunrise repository [2] rather than the -reviewed one, since the latter has not been updated for over a year. While at it, please note that: 1. Adding a package to Gentoo requires declaring yourself as an active maintainer for it. All bugs regarding the package will be assigned to you, and you will be expected to maintain it. 2. Some packages may not be suitable for addition anymore. While there's no strong rules that would prevent you from adding a package, it may be a bad idea to add old-unmaintained packages that will shortly result in a large number of bugs reported with no solution. If that is the case, please close the bug as RESOLVED/OBSOLETE to make it easier to find packages worth adding. 3. Some of the bugs were already closed as WONTFIX/OBSOLETE/... while the relevant ebuild was kept in Sunrise. If you disagree with the original decision, you still can add the ebuild via proxy-maint. 4. Pleaes note that many of the Sunrise ebuilds are old and may be buggy. If you decide to move them, please make sure to update/clean them up. The proxy-maint team will also review your ebuilds, therefore making sure they land in Gentoo in good quality. Once again, thank you for your contribution. We hope that you will still want to contribute to Gentoo, through proxy-maint or otherwise. [1]:https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers [2]:https://gitweb.gentoo.org/proj/sunrise.git/
