Hello, x11-misc/electricsheep is 2.6.8-r3, but the server used by the 2.6 is down, you must be in 2.7.x to run Electric Sheep, or the server doesn't answer
Yes, and as long as upstream refuses to provide tarballs it's a mess to create a snapshot of the 2.7betas. I'll see if I can cook up something that works ...
You can get a tarball of the svn here : http://electricsheep.svn.sourceforge.net/viewvc/electricsheep/trunk/client.tar.gz Good luck ;)
Now the videos (sheeps) tell people to go to http://electrisheep.org/upgrade, and then they say that by June 30th the old server will be shutdown and no more sheeps will be downloaded. Perhaps the old versions should be removed from portage after June 30th? I know that currently there is not a 2.7 version available for gentoo, but if a new user installs electricsheep after June 30th it won't be able to enjoy it.
Now the sheep are not dreaming at all anymore... As the current version does not seem to be working anymore and a new ebuild can apparently not be expected any time soon, why not mask the current version? I am giving up and will use SETI now...
Can't we just have an svn ebuild in the meantime? It's not like they're unusual.
(In reply to comment #5) > Can't we just have an svn ebuild in the meantime? It's not like they're > unusual. Since upstream refuses to package it sanely that's about the only option anyway. If you can manage to make an ebuild that compiles (which I still haven't) I wouldn't be opposed to adding it to the tree.
Created attachment 195999 [details] electricsheep-9999.ebuild Live ebuild for electricsheep (not supplied as a patch against the latest in the tree, as that would be almost twice as long). Activity seems to be low enough that it might be just as well to make a snapshot, but that's your call. It depends on a live version of flam3 - I'm not sure if that's strictly necessary, but the various build scripts at http://community.sheepserver.net/node/51 do that, so it seems safer to do it this way. KDE support is only tested against KDE 3.5 - bug 256338 probably still applies to this ebuild. GNOME support doesn't work and is commented out - someone who uses GNOME can fix it. ;-)
Created attachment 196001 [details, diff] electricsheep-9999-xdg-utils.patch Patch to use xdg-open instead of gnome-open - saves a GNOME dep.
Created attachment 196003 [details, diff] electricsheep-9999-gnome.patch Don't install the various GNOME things in the Makefile - they would be installed by the ebuild with USE=gnome, were that part not commented out (update-gconf-defaults and 16_electricsheep appear to be a Debianism, and I'm not sure if we have an equivalent in Gentoo).
Created attachment 196005 [details, diff] electricsheep-9999-external-ffmpeg.patch Patch to use the system FFmpeg instead of the bundled one.
Created attachment 196006 [details, diff] electricsheep-9999-valgrind.patch Patch (submitted upstream) to fix various valgrind complaints, including a big leak which I think was the reason for using a patched bundled FFmpeg in the first place.
Created attachment 196008 [details, diff] flam3-9999.ebuild.patch Live flam3 ebuild, in the form of a patch against 2.7.18
I've got an error with the electricsheep-9999-external-ffmpeg.patch: ***** electricsheep-9999-external-ffmpeg.patch ***** ==================================================== PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < /usr/local/portage/x11-misc/electricsheep/files/electricsheep-9999-external-ffmpeg.patch ==================================================== can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: client/configure.in |=================================================================== |--- client/configure.in (revision 1257) |+++ client/configure.in (working copy) -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 17 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: client/Makefile.am |=================================================================== |--- client/Makefile.am (revision 1257) |+++ client/Makefile.am (working copy) -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ==================================================== PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < /usr/local/portage/x11-misc/electricsheep/files/electricsheep-9999-external-ffmpeg.patch ==================================================== patching file configure.in Hunk #1 FAILED at 2. 1 out of 1 hunk FAILED -- saving rejects to file configure.in.rej patching file Makefile.am Hunk #1 FAILED at 1. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.am.rej ==================================================== PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < /usr/local/portage/x11-misc/electricsheep/files/electricsheep-9999-external-ffmpeg.patch ==================================================== missing header for unified diff at line 5 of patch can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: client/configure.in |=================================================================== |--- client/configure.in (revision 1257) |+++ client/configure.in (working copy) -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored missing header for unified diff at line 17 of patch can't find file to patch at input line 17 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: client/Makefile.am |=================================================================== |--- client/Makefile.am (revision 1257) |+++ client/Makefile.am (working copy) -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ==================================================== PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < /usr/local/portage/x11-misc/electricsheep/files/electricsheep-9999-external-ffmpeg.patch ==================================================== missing header for unified diff at line 5 of patch can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: client/configure.in |=================================================================== |--- client/configure.in (revision 1257) |+++ client/configure.in (working copy) -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored missing header for unified diff at line 17 of patch can't find file to patch at input line 17 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: client/Makefile.am |=================================================================== |--- client/Makefile.am (revision 1257) |+++ client/Makefile.am (working copy) -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ==================================================== PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < /usr/local/portage/x11-misc/electricsheep/files/electricsheep-9999-external-ffmpeg.patch ==================================================== missing header for unified diff at line 5 of patch can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: client/configure.in |=================================================================== |--- client/configure.in (revision 1257) |+++ client/configure.in (working copy) -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored missing header for unified diff at line 17 of patch can't find file to patch at input line 17 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: client/Makefile.am |=================================================================== |--- client/Makefile.am (revision 1257) |+++ client/Makefile.am (working copy) -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored
Created attachment 197411 [details] electricsheep-9999.ebuild Upstream applied the valgrind patch and removed the bundled ffmpeg.
Thanks for providing these ebuilds! Some problems I had (with workarounds): 1) When installing the flam3-9999 package, I got a couple weird errors. The first was "directory m4 does not exist" (the gcc command was specifying -Im4). After creating that directory, the build failed with: "Incompatible ltmain.sh", or somesuch. The oddest thing was how I worked around it... I found that by touching all build files to give them the same creation-date, the build worked fine. I have no idea why, but it worked (reproducibly), and so I moved on. 2) electricsheep complained about "undefined reference to av_free_packet". I upgraded my ffmpeg to the 9999-r1 version, and the problem went away. -Larry
Created attachment 197863 [details] fixes missing m4 dir and ltmain.sh error (In reply to comment #15) > Some problems I had (with workarounds): > > 1) When installing the flam3-9999 package, I got a couple weird errors. The > first was "directory m4 does not exist" (the gcc command was specifying -Im4). > After creating that directory, the build failed with: "Incompatible ltmain.sh", > or somesuch. Yeah, I ran into this. I altered the ebuild, adding a src_unpack function to create the m4 directory and run eautoreconf. I'm attaching it.
Oops, I forgot: I keyworded it for my own use, so ignore that part.
David, your ebuild did it. It compiles and now everythings works. thank you very much! :)
*** Bug 280991 has been marked as a duplicate of this bug. ***
Thanks for fixing the ebuild. Works good again (albeit without mp4 use flag)
(In reply to comment #20) > Thanks for fixing the ebuild. Works good again (albeit without mp4 use flag) > forget what i wrote... works fine! (dunno what i was thinking mentionin mp4 use flag... ffmpeg maybe)
+ 17 Sep 2009; Patrick Lauer <patrick@gentoo.org> + +electricsheep-2.7_beta11.ebuild, +files/electricsheep-gnome.patch, + +files/electricsheep-xdg-utils.patch: + Finally bump to 2.7_beta. Thanks to David Leverton for the autotools + patches. Fixes #272050
