$summary
Any news on this? Now prey 0.5.10 is out!
sorry i have no interest in this package anymore so someone else should step up and maintain it. Also bug #443728 is pending as well
(In reply to Markos Chandras from comment #2) > sorry i have no interest in this package anymore so someone else should step > up and maintain it. Also bug #443728 is pending as well Ping @ Travis: Can you look at this package? Are you still interested?
I haven't looked at it in a while. What needs help?
(In reply to Travis Hansen from comment #4) > I haven't looked at it in a while. What needs help? Resolving this bug and bug #443728 which have been open for months; if you can one of these days, you're very welcome and we can push your fixes, if not and you want us to pick over the package or release to maintainer-needed@g.o then feel free to state so. You can see this as a check if you still want to proxy maintain this or not; we're trying to clean up the back end of the list, to ensure packages don't end up being not maintained. Thank you in advance for replying.
For the time being go ahead and release to maintainer-needed. Thanks!
+ 14 Aug 2013; Tom Wijsman <TomWij@gentoo.org> metadata.xml: + Dropped herds and maintainers, assigned to maintainer-needed; as per + confirmation from all maintainers, see bug #451882. This package has no maintainer so this bug may go unnoticed for a long time. Gentoo has a dedicated team[1] for assisting users in maintaining orphaned packages. If you are interested in maintaining this package, please contact proxy-maint@gentoo.org. [1]: http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml
Created attachment 371404 [details, diff] app-laptop/prey-0.6.2 ebuild diff against 0.5.4-r1 Update of 0.5.4-r1 ebuild to upstream version 0.6.2, should fix bug #443728 and possibly others. Requires updated patches, also attached.
Created attachment 371406 [details, diff] prey-0.6.2-cron-functions.patch Updates cron-functions patch to work for 0.6.2 ebuild.
Please also note that upstream is presently developing a node.js based client to replace the current bash one. While it would be nice to have an ebuild for the new client (currently version 1.0.5, I believe), installation is normally through npm (according to upstream) and I have no idea what I should do about that. Bypass npm or trust npm, etc.
removed
