I'm new to prey, so bear with me a bit :)
When running the first time initialization for prey, I get the following output:
yuki etc # prey
/usr/bin/prey: line 18: /usr/share/prey/lang/en: No such file or directory
## Linux yuki 3.6.6-gentoo-yuki-v2.2 #3 SMP Sat Nov 17 19:54:26 EST 2012 x86_64 Intel(R) Core(TM) i5-2467M CPU @ 1.60GHz GenuineIntel GNU/Linux
## Sun Nov 18 00:17:30 EST 2012
-- Looking for connection...
-- Got network connection!
== Verifying status...
-- Got status code 200!
== Reading configuration...
-- Setting delay to regular interval.
== Reading module configuration...
-- Got instructions for system module.
!! Module system not found!
-- Trying to fetch system module from repository...
-- Couldn't grab module package. The repository may be temporarily down.
!! Couldn't install system module from repository.
-- Cleaning up!
find: `/etc/rc3.d/': No such file or directory
-- Setting up network detection trigger init script...
!! Couldn't copy init script into /etc/init.d!
The System module I believe may be related to prey itself, not so much prey itself. The rc3.d may be as well, however when I probed into init.d, I noticed the following:
yuki init.d # ls -lh prey-trigger
lrwxrwxrwx 1 root root 59 Nov 18 00:10 prey-trigger -> /usr/share/prey//usr/share/prey/platform/linux/prey-trigger
Which is improperly calling the trigger script.
As an aside, I'm converting the openrc script over to a systemd unit file, I can post the results here if desired.
Let me know if anything else is needed :)
The rc3.d is from prey itself:
Line 92: find /etc/rc3.d/ | grep 'prey-trigger' > /dev/null && echo 1
After much fiddling, I think this is mostly upstream, and I'm going to submit the changes I've made to the project as well, but I'm attaching the modified files here as well. Never quite figured out how to do diffing to make patch files :(
Created attachment 329784 [details]
Patched functions file
Created attachment 329786 [details]
Patched Services File with gentoo openrc configuration added
Created attachment 329788 [details]
Services needed a few more tweaks.
Created attachment 329790 [details]
Functions patched again to locate files in init.d directory
Had to patch the find commands, not the best patch either, otherwise it keeps attempting to load the init script
/etc/cron.d/prey.cron calls /usr/bin/prey.sh, should be altered over to /usr/bin/prey
Additionally, the ebuild may want to flag imagemagick as a dependency with the webcam useflag, otherwise the image is uploaded in ppm, not jpg, and will not render in the control panel.
This package is more broken than I expected.
(In reply to comment #8)
> This package is more broken than I expected.
I've submitted the relevant code to upstream. The problem right now is that with the functions/services patches, it won't allow registration of the device in the control panel because there isn't a "Gentoo" distribution (For Shame!)
Apparently they're planning to rewrite the entire client in node.js, but hopefully at least this will get taken care of. I just got up so in a bit i'm going to open up the files and do a rather nasty hack to get the services file to run properly.
I'm also getting syntax errors all over the place in the various python scripts. This may want to be remarked as unstable for a bit. It runs, but it's not happy about it, and all the problems are upstream.
Created attachment 329876 [details, diff]
Patch file for functions
Hijack Arch's script to work for gentoo until upstream adds a gentoo distribution, confirmed to work when both functions/services is patched.
Created attachment 329878 [details, diff]
Patch file for Services
Hijack arch's service setup for gentoo.
Apparently some merges to upstream should have removed the dependency on sudo, but this particular version requires it for lock/alert/alarm, etc. So sudo may want to be pulled in.
I'm new to ebuild patching, but it seems like scrot should be dropped in favor of imagemagick (as screenshot/webcam both depend on it) and sudo needs to be pulled in.
Additionally the python syntax errors are due to eselect python being set to 3.2, prey wants 2.7
If I manage to figure out what I'm doing with the ebuilds I'll dump everything here, haha.
please stop changing the fields of this bug
(In reply to Markos Chandras from bug #451882 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?
+ 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 for assisting users in maintaining orphaned
packages. If you are interested in maintaining this package, please contact
Hi! I maintain the most recent versions of prey on my overlay. Please, at masking, specify the version you want to unmask. Meanwhile, I unmasked mine.