I just upgraded from beagle 0.2.7 to 0.2.14 and noticed that the paths in /etc/cron.daily/beagle-crawl-system are incorrect. They now refer to /usr/local/etc instead of /etc. Included is the diff that dispatch-conf showed me: @@ -36,7 +36,7 @@ MONO_SHARED_DIR=`mktemp -d -p $TMPDIR .beagleindexwapi.XXXXXXXXXX`|| ( echo "Can't create wapi directory!" ; exit 1 ) chown $CRAWL_USER $MONO_SHARED_DIR -for crawl_file in /etc/beagle/crawl-*; do +for crawl_file in /usr/local/etc/beagle/crawl-*; do unset CRAWL_ENABLED CRAWL_DISABLE_FILTERING CRAWL_RECURSIVE CRAWL_CACHE_TEXT CRAWL_ALLOW_PATTERNS CRAWL_D ENY_PATTERNS CRAWL_PATHS CRAWL_INDEX_NAME if [ -f $crawl_file ] ; then @@ -64,7 +67,7 @@ IONICE="$IONICE -c 3" fi - eval nice -n 19 $IONICE su -s /bin/bash $CRAWL_USER -c \"MONO_SHARED_DIR=$MONO_SHARED_DIR /usr/sbi n/beagle-build-index --target /var/lib/cache/beagle/indexes/$CRAWL_INDEX_NAME $OPTIONS $CRAWL_PATHS\" > /dev/n ull 2>&1 + eval nice -n 19 $IONICE su -s /bin/bash $CRAWL_USER -c \"MONO_SHARED_DIR=$MONO_SHARED_DIR /usr/loc al/sbin/beagle-build-index --target /usr/local/var/cache/beagle/indexes/$CRAWL_INDEX_NAME $OPTIONS $CRAWL_PATH S\" > /dev/null 2>&1 fi fi done Reproducible: Always Steps to Reproduce: 1. install beagle 0.2.14 2. watch cron emit errors daily 3.
Delete the file, not used any more. *** This bug has been marked as a duplicate of bug 138119 ***
I'm sorry, but this is not a duplicate of bug 138119. That bug talks about issues with an old file that was not removed. This bug is about wrong paths in a file that beagle 0.2.14 installs. I've just confirmed with "ebuild beagle-0.2.14 install" that this version of beagle installs the file with the wrong path.
Shrug; as far as I can see it doesn't install any cronjob whatsoever. Won't compile the tons of dotnet cruft to verify this.
It's installed by the package itself (in tools/Makefile). The file is shipped by upstream with the /usr/local paths and not properly re-generated after running configure. Punting tools/beagle-crawl-system after unpacking seems to work for me, although it may be better to understand why it didn't get re-generated in the first place.
can confirm and agree its not a dup of bug #138119.
Filed upstream as http://bugzilla.gnome.org/show_bug.cgi?id=401504
Fixed upstream in SVN by not including the pre-built beagle-crawl-system file, so that it is always generated during the build process. So my work-around in comment #4 is actually the correct fix. :-)
i added the upstream fix to our ebuild. so we can close this bug. Thanks for your bug report!
ok this isn't really fixed now using a patched makefile from the upstream svn it appears for crawl_file in /home/joe/build/beagle/etc/beagle/crawl-*; Are you sure it's really fixed for you ?
I'm seeing the same thing with beagle-0.2.15.1. I think you only applied part of the patch: the Makefile changes are one part, but the other part is to remove the beagle-crawl-system file. The gnome svn viewer doesn't really show this, but that is what I infer from the log message for the revision: http://svn.gnome.org/viewcvs/beagle?view=rev&rev=3357 I think if you just punt the file the Makefile patch is not even needed.
fixed in 0.2.16 that is in cvs that why i didn't fixed this before. This release will it stable asap.
