Nabble - Gnome - Dashboard - Dev

Re: beagle indexes and cache

2009-10-27T08:49:00Z

>>>> does beagle cleans up its indexes and textcaches now and then?
>>>> I mean it looks like old documents (now removed) still come up when
>>>> searching...
>>>> is there a way to clean indexes and textcache, or should I simply remove
>>>> these directories in the .beagle folder now and then?
...
>
> I was worried, though, about files being indexed that are in a directory
> which is later marked as ignored with beagle-settings: will those files well
> be removed from the beagle database?

They would definitely not show up in search results - the search
results are filtered based on current availability and beagle-settings
ignore list.
As far as actually removing them from the database is concerned, I
don't remember off the top of my head how it is dealt with. Ideally,
the entries should be removed since the index (and esp. the textcache)
might retain information that the user doesnt want it to contain ...
but ignoring a directory involves traversing all files and directories
beneath it which soon creates a nightmare. I remember seeing some code
on dropping the contents of the ignored directories but I am can't
remember if it is complete or what exactly it does.

- dBera

--
-----------------------------------------------------
Debajyoti Bera @ http://dtecht.blogspot.com
beagle / KDE fan
Mandriva / Inspiron-1100 user
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: beagle indexes and cache

2009-10-27T04:31:25Z

D Bera wrote:

>>> does beagle cleans up its indexes and textcaches now and then?
>>> I mean it looks like old documents (now removed) still come up when
>>> searching...
>>> is there a way to clean indexes and textcache, or should I simply remove
>>> these directories in the .beagle folder now and then?
>> It should, but I have had the indexes get stale, especially if I worked
>> for awhile with the beagle service turned off.
>
> That is right. If beagle service is running, it will monitor new files
> that are created and existing files that are removed almost
> immediately. If it is turned off, and then turned on again, then the
> changes while it was turned off are handled later:
> - new files are reported only during the next re-crawl
> - deleted files are not reported but they are removed from the beagle
> database much later and only when such a file comes up a search result
>
> In short, deleted files should not come up as a search result (I dont
> remember, but there was a bug in 0.3.7 or 0.3.8 which can cause
> something like that).
>
> Removing textcache and indexes manually should not be necessary,
> assuming there is no bug (and even less reason if beagle is running
> continuously). Note that the indexes are separated into backends and
> can be easier to remove but the textcache is not, so removing the
> textcache directory will wipe out all of textcache.
>

thanks for your answers!

I was worried, though, about files being indexed that are in a directory
which is later marked as ignored with beagle-settings: will those files
well be removed from the beagle database?

thanks again
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: beagle indexes and cache

2009-10-27T01:47:16Z

>> does beagle cleans up its indexes and textcaches now and then?
>> I mean it looks like old documents (now removed) still come up when
>> searching...
>> is there a way to clean indexes and textcache, or should I simply remove
>> these directories in the .beagle folder now and then?
>
> It should, but I have had the indexes get stale, especially if I worked
> for awhile with the beagle service turned off.

That is right. If beagle service is running, it will monitor new files
that are created and existing files that are removed almost
immediately. If it is turned off, and then turned on again, then the
changes while it was turned off are handled later:
- new files are reported only during the next re-crawl
- deleted files are not reported but they are removed from the beagle
database much later and only when such a file comes up a search result

In short, deleted files should not come up as a search result (I dont
remember, but there was a bug in 0.3.7 or 0.3.8 which can cause
something like that).

Removing textcache and indexes manually should not be necessary,
assuming there is no bug (and even less reason if beagle is running
continuously). Note that the indexes are separated into backends and
can be easier to remove but the textcache is not, so removing the
textcache directory will wipe out all of textcache.

- dBera
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: beagle indexes and cache

2009-10-23T03:38:34Z

> does beagle cleans up its indexes and textcaches now and then?
> I mean it looks like old documents (now removed) still come up when
> searching...
> is there a way to clean indexes and textcache, or should I simply remove
> these directories in the .beagle folder now and then?

It should, but I have had the indexes get stale, especially if I worked
for awhile with the beagle service turned off.

It helps to occasionally stop the Beagle service, open a shell, "export
BEAGLE_EXERCISE_THE_DOG=1", run "beagle-search" (yes - from the shell!),
then start the service. This will make the service index aggressively
as fast as it can; bringing the index up to date. I do this on my
laptop when I go to bed - then in the morning stop the service, close
the shell, run beagle-search from the GUI (GNOME-Do!) and restart the
service [now running in an environment without BEAGLE_EXERCISE_THE_DOG
set] so it is back to running as a low-priority background service.

You can also stop the service, "rm -R ~/.beagle", "export
BEAGLE_EXERCISE_THE_DOG=1", beagle-search, start the service - to
rebuild all your indexes from scratch as fast as it can.
--
openSUSE <http://www.opensuse.org/en/>
Linux for human beings who need to get things done.

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

signature.asc (204 bytes) Download Attachment

beagle indexes and cache

2009-10-22T03:23:23Z

Hi

does beagle cleans up its indexes and textcaches now and then?
I mean it looks like old documents (now removed) still come up when
searching...

is there a way to clean indexes and textcache, or should I simply remove
these directories in the .beagle folder now and then?

thanks
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134 (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: Beagle maintenance

2009-10-20T13:49:26Z

On Tue, 2009-10-20 at 13:32 -0700, Gabriel Burt wrote:
> Hi all,
> I was just catching up on the thread from a month ago about Beagle's
> maintenance status[1]. There were several comments inquiring about
> Novell's involvement in the project. Part of my responsibilities at
> Novell include doing bug fixing and limited feature development work
> on Beagle. I know it's nothing compared to two employees working on
> it full-time, or having DBera maintaining the project. But I just
> wanted you to know that Novell is still putting some resources behind
> supporting Beagle.

Good to hear.

- Will Beagle be updated to work with the latest [sqlite based]
Evolution? That is kind of a killer.

- Are there thoughts about Tracker vs. Beagle? Sadly they chose to
write Tracker in C [WHY?? Ugh.] but it seems to have an active community
and the attention of the GNOME overloads (something Beagle seems to have
lost some time ago). For example, it is likely to be supported by
Zeitgiest in GNOME 3.

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Beagle maintenance

2009-10-20T13:32:09Z

Hi all,

I was just catching up on the thread from a month ago about Beagle's
maintenance status[1]. There were several comments inquiring about
Novell's involvement in the project. Part of my responsibilities at
Novell include doing bug fixing and limited feature development work
on Beagle. I know it's nothing compared to two employees working on
it full-time, or having DBera maintaining the project. But I just
wanted you to know that Novell is still putting some resources behind
supporting Beagle.

Thanks,

Gabriel

[1] http://mail.gnome.org/archives/dashboard-hackers/2009-September/msg00005.html
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

unable to connect to daemon

2009-10-14T07:28:18Z

Beagle starts and runs, and I can search from gui, but each time a beagle-index-info, or beagle-status is run from cli, "Could not connect to the daemon." Asking gui to get index info vvia "Service Options -> Index Information" brings up a " Search service not running" with a button "Start search service". Which, incidentally, clicking the button will not start a stopped beagle.

this is running in gentoo x86_64 2.6.27-gentoo-r8

and beagle version:
[I] app-misc/beagle
Installed versions: 0.3.9-r1(22:33:37 14/10/09)(avahi chm eds firefox galago google gtk inotify ole pdf thunderbird xscreensaver -debug -doc -epiphany)
[I] dev-libs/libbeagle
Installed versions: 0.3.9(21:29:11 14/10/09)(python -debug -doc)

I have re-emerged all beagle and prerequisites as set on beagle http://beagle-project.org/Getting_Started
emerge -vaD `qlist -I beagle taglib mono sharp dbus sqlite gmine xlibs zip wv poppler gnumeric libgsf`

some output from debug
$ beagled --foreground --debug
Always: Starting Beagle Daemon (version 0.3.9)
Always: Running on Mono 2.4.2.3
Always: Command Line: /usr/lib64/beagle/BeagleDaemon.exe --foreground --debug
Warn: Extended attributes are not supported on this filesystem. Performance will suffer as a result.
Debug: Established a connection to the X server
Debug: Reniced process to 7
Debug: Starting signal handler thread
Debug: Starting messaging server
Debug: Using utf8 encoding for filenames
Debug: Starting QueryDriver
Always: HTTP Server: Listening on http://localhost:4000/
Debug: Found index helper at /usr/lib64/beagle/beagled-index-helper
Debug: Found 2 backends in /usr/lib64/beagle/Backends/EvolutionBackends.dll
Debug: Found 1 backends in /usr/lib64/beagle/Backends/GoogleBackends.dll
Debug: Found 1 backends in /usr/lib64/beagle/Backends/ThunderbirdBackends.dll
Debug: Starting Inotify FSQ file event backend
Debug: Loaded 154390 records from /home/rd/.beagle/Indexes/FileSystemIndex/FileAttributesStore.db in 2.765s
Debug: Checking if /home/rd/Mail is kmail local mail directory ?
Warn: KMail backend: No index file for /home/rd/Mail/Mail.Ignoring /home/rd/Mail, probably not a kmail directory.
Debug: KMail folders not found. Will keep trying
Debug: KonqCacheDir: /var/tmp/kdecache-rd/http
Debug: Found 19 backends in /usr/lib64/beagle/BeagleDaemonLib.dll
Debug: Loading system static indexes.
Debug: Initializing static queryable: /var/lib/cache/beagle/indexes/applications
Debug: Checking for dangling locks...
Debug: Initializing static queryable: /var/lib/cache/beagle/indexes/documentation
Debug: Initializing static queryable: /var/lib/cache/beagle/indexes/manpages
Debug: Initializing static queryable: /var/lib/cache/beagle/indexes/monodoc
Debug: Initializing static queryable: /var/lib/cache/beagle/indexes/windows
Debug: Found 5 system-wide indexes.
Debug: Loading user-configured static indexes.
Debug: Found 0 user-configured static indexes..
Debug: Waiting 60 seconds before starting queryables
Debug: Starting Scheduler thread
Debug: Starting Inotify threads
Debug: Zeroconf: Service started...
Debug: Daemon initialization finished after 4.18s
Debug: Memory usage: VmSize=218.0 MB, VmRSS=29.1 MB, GC.GetTotalMemory=7233536 (154 colls)
Warn: Caught exception trying to execute Beagle.Daemon.DaemonInformationExecutor. Sending error response
System.IO.IOException: read past EOF
at Lucene.Net.Store.BufferedIndexInput.Refill () [0x00000]
at Lucene.Net.Store.BufferedIndexInput.ReadByte () [0x00000]
at Lucene.Net.Store.IndexInput.ReadChars (System.Char[] buffer, Int32 start, Int32 length) [0x00000]
at Lucene.Net.Store.IndexInput.ReadString () [0x00000]
at Lucene.Net.Index.SegmentInfo..ctor (Lucene.Net.Store.Directory dir, Int32 format, Lucene.Net.Store.IndexInput input) [0x00000]
at Lucene.Net.Index.SegmentInfos.Read (Lucene.Net.Store.Directory directory, System.String segmentFileName) [0x00000]
at Lucene.Net.Index.SegmentInfos+AnonymousClassFindSegmentsFile1.DoBody (System.String segmentFileName) [0x00000]
at Lucene.Net.Index.SegmentInfos+FindSegmentsFile.run () [0x00000]
Warn: (Repeated) Caught exception trying to execute Beagle.Daemon.DaemonInformationExecutor. Sending error response
Warn: (Repeated) Caught exception trying to execute Beagle.Daemon.DaemonInformationExecutor. Sending error response

Get more done like never before with Yahoo!7 Mail. Learn more.
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: Beagle webinterface

2009-10-09T16:33:59Z

Has anybody tried the interface?

On Domingo 20 Septiembre 2009 21:53:14 Hugo Sarti escribió:
> Hi everybody,
> I was trying to share the new webinterface that I made when noticed the
> decision about moving to Unmanteined State.
> I'm really sorry to hear this decision. The project was very helpful for
> our company, indexing documents in a centralized NAS.
> I am not a experienced Mono / .Net developer. My major skills are based on
> PHP (I'm also certified on php5). I was thinking on doing a port to this
> language, perhaps now this can be more than just a thought. Maybe php will
> get more people to the project or maybe not.
> Please download and try the new webinterface at the following link. Any
> feedback/comment is incredible valuable.
>
> http://globalsyons.com/projects/beagle/beagleWI.tar.gz
>
> Kind Regards

--

Hugo Sarti

Ingeniero en Sistemas de Información

Syons

www.syons.com.ar

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: About to declare 'unmaintained'

2009-09-22T17:31:56Z

2009/9/22 Adam Tauno Williams <awilliam@...>

And many of the leading Open Source
projects are in Mono: Monodevelop, F-Spot, Banshee, Tomboy, etc... The
Mono ecosystem is thriving, and will do so with or without Beagle.

Banshee is leading something? when? where?
Monodevelop is a leading IDEs? when? where?
Is your a joke?

You know: RH deleted mono from Fedora. Canonical will not include Banshee in default installation of Ubuntu Karmic.

Garbage. This is a claim of pure unadulterated ignorance. The "patent
deal" has nothing whatsoever at-all to do with Mono. This has been
explained dozens of times.

No. MS-Novell deal covers *all* MS patents. Please read it.
It is true it is not only or mainly for Mono but it covers Mono. Only Novell version of Mono, of course.

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: About to declare 'unmaintained'

2009-09-22T17:10:00Z

2009/9/22 Adam Tauno Williams <awilliam@...>

I haven't paid much attention to Tracker

Today it doesn't work. Period.
I used tracker on tree releases of Ubuntu. After 1 week I purged it to install Beagle.

Claiming he is "stupid" is also absurd. He wrote a good chunk of
Gnumeric; solid evidence against stupidity.

I already wrote MdI is not stupid. What is stupid is to leave unmantained one of the best software developed with Mono, Beagle. Then if MdI is not a studip - and I think he is not a stupid - he can find a solution.

I hope he is not too busy with codeplex@microsoft ... ;-)

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: About to declare 'unmaintained'

2009-09-22T10:50:02Z

> I apologize for "stupid" to Miguel De Icaza, I mentioned him because
> his role in Mono and in Novell. Well, MdI is *not* stupid at all. To
> leave Beagle unmantained is stupid.
> If you are his friend, please say him Beagle is dying. Because he is
> not a stupid, I think MdI will do something.
> I think only Novell could save Beagle: Beagle is written in Mono. No
> one, no company, want to write software in Mono because patent issue.

BOGOSITY = 100%. This is crap - stop spouting this nonsense - many
companies are developing code using Mono from Unity [gaming] to Quantifi
[financial] to Medsphere [medical]. And many of the leading Open Source
projects are in Mono: Monodevelop, F-Spot, Banshee, Tomboy, etc... The
Mono ecosystem is thriving, and will do so with or without Beagle.

> But Novell have a deal with MS on patents, then Novell can.

Garbage. This is a claim of pure unadulterated ignorance. The "patent
deal" has nothing whatsoever at-all to do with Mono. This has been
explained dozens of times.

An in general:
<http://www.jprl.com/Blog/archive/development/mono/2009/Jan-19.html>
<http://jeffreystedfast.blogspot.com/2008/02/lots-of-gnomemono-fud-lately.html>
<http://www2.apebox.org/wordpress/rants/124/>

That is the answer to FUD; I won't dignify any responses along those
line - and spare polluting the list archives with more such foolishness.

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: About to declare 'unmaintained'

2009-09-22T10:39:48Z

> > Can Novell leave unmantained a piece of its desktop? This is a suicide for
> > Suse.
> Exactly what Novell intends to do with Beagle is unclear, but I think
> "suicide" is a bit hyperbolic. From my time at Novell there was a
> love/hate relationship with Beagle among SUSE users. Some people
> loved it and wouldn't live without it, and other people despised it to
> the point where the very first thing they did after installing SUSE
> was remove Beagle.

Ugh, what a bunch of irrational haters. Those goons are still around
unfortunately. But don't worry: they hate KDE4, and they will have
GNOME 3 and Tracker.

I imagine openSUSE will simple include Tracker at some point - hopefully
soon. I haven't paid much attention to Tracker but at a glance it has
much of Beagles functionality and already has some integration into
Zeitgeist. Interesting that much of what Dashboard and the like first
hoped to accomplish is finally coming into being.
<http://seilo.geekyogre.com/2009/09/some-pics-from-the-new-gnome-activity-journal/>

> > Well, I think there are some stupids men in Novell (did someone say
> > "Miguel"?), but I hope not so stupid.
> > Monotouch can't be Novell core business....
> Well, Miguel is a friend of mine, so I don't really appreciate that.

Claiming he is "stupid" is also absurd. He wrote a good chunk of
Gnumeric; solid evidence against stupidity.

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: About to declare 'unmaintained'

2009-09-22T10:10:50Z

2009/9/22 Joe Shaw <joe@...>

Novell's a big company, and Mono is a totally separate entity from
their desktop business. If Novell wants to put resources toward
Beagle, it's going to come from the SUSE organization and not Miguel's
Mono organization.

I agree with you, though, in that I am not really sure what Novell's
aims are with Monotouch, but that's orthogonal to this.

I apologize for "stupid" to Miguel De Icaza, I mentioned him because his role in Mono and in Novell. Well, MdI is *not* stupid at all. To leave Beagle unmantained is stupid.
If you are his friend, please say him Beagle is dying. Because he is not a stupid, I think MdI will do something.

I think only Novell could save Beagle: Beagle is written in Mono. No one, no company, want to write software in Mono because patent issue. You know, this issue is too dangerous for business.

But Novell have a deal with MS on patents, then Novell can. Novell can demostrate the patent deal is useful for users. If not, all FLOSS users will realize the deal is not a serious thing.

Imagine Red Hat men laughing when they see Microsoft is asking for money for patent licenses on Monotouch :)

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: About to declare 'unmaintained'

2009-09-22T08:53:39Z

Hi,

On Tue, Sep 22, 2009 at 11:39 AM, guido iodice <guido.iodice@...> wrote:
> Can Novell leave unmantained a piece of its desktop? This is a suicide for
> Suse.

Exactly what Novell intends to do with Beagle is unclear, but I think
"suicide" is a bit hyperbolic. From my time at Novell there was a
love/hate relationship with Beagle among SUSE users. Some people
loved it and wouldn't live without it, and other people despised it to
the point where the very first thing they did after installing SUSE
was remove Beagle. I think a lot of people would be pretty
disappointed if they stopped shipping Beagle, but would they lose a
lot of business? I'm not so sure.

I don't have any inside knowledge anymore, but it is conceivable that
SUSE would ship Tracker in a future release and replace a chunk of
Beagle's functionality with that.

> Well, I think there are some stupids men in Novell (did someone say
> "Miguel"?), but I hope not so stupid.
> Monotouch can't be Novell core business....

Well, Miguel is a friend of mine, so I don't really appreciate that.

Novell's a big company, and Mono is a totally separate entity from
their desktop business. If Novell wants to put resources toward
Beagle, it's going to come from the SUSE organization and not Miguel's
Mono organization.

I agree with you, though, in that I am not really sure what Novell's
aims are with Monotouch, but that's orthogonal to this.

Joe
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: About to declare 'unmaintained'

2009-09-22T08:39:14Z

2009/9/13 Joe Shaw <joe@...>

Since I left Novell nearly
two years ago, there has been none. I think it's safe to say that
Novell no longer has any dedication to the project. I don't mean that
as a dig -- having worked on Ximian and SUSE distributions you have to
make strategic and tactical decisions where to put your resources,
since you can't hack full time on everything. It appears clear that
desktop search hasn't panned out as they thought and that experimental
projects like Dashboard, Association Browser, etc. aren't feasible.

Can Novell leave unmantained a piece of its desktop? This is a suicide for Suse.
Corporate users need to search in Evolution mail, IM messages, files, visited web pages and more in the same time. Only Beagle can do it, if upgraded and mantained.
Beagle can do the difference on enterprise desktop. To leave it unmantained is stupid.
Well, I think there are some stupids men in Novell (did someone say "Miguel"?), but I hope not so stupid.
Monotouch can't be Novell core business....

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Beagle webinterface

2009-09-20T17:53:14Z

Hi everybody,

I was trying to share the new webinterface that I made when noticed the

decision about moving to Unmanteined State.

I'm really sorry to hear this decision. The project was very helpful for our

company, indexing documents in a centralized NAS.

I am not a experienced Mono / .Net developer. My major skills are based on PHP

(I'm also certified on php5). I was thinking on doing a port to this language,

perhaps now this can be more than just a thought. Maybe php will get more

people to the project or maybe not.

Please download and try the new webinterface at the following link. Any

feedback/comment is incredible valuable.

http://globalsyons.com/projects/beagle/beagleWI.tar.gz

Kind Regards

Hugo Sarti

Ingeniero en Sistemas de Información

Syons

www.syons.com.ar

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: About to declare 'unmaintained'

2009-09-13T10:28:52Z

Hi,

I just wanted to reiterate what Bera said. Unfortunately it's been a
long time coming, and I had the revelation fairly recently that our
meager maintenance efforts were simply not going to keep up with the
positive forward progress of other projects upon which we depend, like
Evolution.

Adam asked about bounties. There doesn't appear to be any official
bounties system, although some are posted informally here:

http://live.gnome.org/Bounties

But there doesn't appear to be a comprehensive system similar to Elance.

A couple people mentioned whether Novell or Canonical (Ubuntu) would
fund Beagle development. I used to work at Novell, and I had the
great fortune of working on Beagle pretty much from the start. For a
couple of years there they paid two full time developers to work on
the project: Jon Trowbridge and myself. When Jon left the company, it
was just me -- although there was occasional part-time help, like Dan
Winship's excellent work on the search UI. Since I left Novell nearly
two years ago, there has been none. I think it's safe to say that
Novell no longer has any dedication to the project. I don't mean that
as a dig -- having worked on Ximian and SUSE distributions you have to
make strategic and tactical decisions where to put your resources,
since you can't hack full time on everything. It appears clear that
desktop search hasn't panned out as they thought and that experimental
projects like Dashboard, Association Browser, etc. aren't feasible.

As for Canonical and Ubuntu, a number of releases ago that community
decided to go with Tracker instead of Beagle, I believe in part due to
a major backlash against Mono following the Microsoft/Novell patent
agreement. Although I think Beagle is still for the moment ahead of
Tracker in terms of core user functionality, Tracker has a vibrant
development community backed by open source companies whereas Beagle's
is completely stagnant and bordering on nonexistent. If I were an
impartial party trying to decide in which to invest development
resources, Beagle is simply a tougher case to make.

Having said all that, please don't let me stop anyone from making
those overtures. Nothing would make me happier than to see the old
dog get a new lease on life. :) As Roger said, maybe it can do so
with a reimagined focus.

Like I said, I've gotten to hack on Beagle from the beginning, which
has been five years (!) now. I am very proud of the work I've done
personally, and that we've done as a community. I have my regrets
too, both technical and non-technical. But I've also moved on with my
life and I hack on other stuff now, and I don't personally have much
interest in returning to full-time Beagle development. I take great
comfort in the fact that we created the first user-centric search
system on Linux, and that it is open source software.

Thanks,
Joe
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: About to declare 'unmaintained'

2009-09-11T05:52:07Z

Il giorno ven, 11/09/2009 alle 10.46 +0200, Enrico Minack ha scritto:

Ubuntu seems
to count on a system called Tracker (wasn't there something in Beagle's
history called tracker?), which never succeeded for me to find ANYTHING.

true, very true.

GUIDO IODICE
tel. 338-9977034
guido.iodice@...
http://guiodic.wordpress.com
http://www.facebook.com/people/Guido_Iodice/1471180388

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: About to declare 'unmaintained'

2009-09-11T01:46:52Z

I also think that it is a pity that this great piece of software is
going to die. Beagle has a great clean architecture, that makes it easy
to understand, extend and improve. It provides a great indexing and
search framework that addresses all issues that you are faced when you
want to build your own desktop search engine: indexers, filters,
scheduler, monitoring consumed resources, and so on.

I like the idea to ask Novel and Ubuntu if they are interested in
further maintaining Beagle. I am using Beagle on my Ubuntu system.
Unfortunately, it is not installed and running by default. Ubuntu seems
to count on a system called Tracker (wasn't there something in Beagle's
history called tracker?), which never succeeded for me to find ANYTHING.
It looks to me like they started a new system from scratch, while Beagle
was sitting there, ready to be used or built upon. However, it would be
good to get there feedback.

I could also imagine that anybody of the search interface developers you
mentioned would be interested in Beagle to live on. Could you also write
to some of them, personally?

Well, I have to finish my encomium on Beagle by admitting that I am also
not capable (time-wise) of maintaining Beagle. But who ever takes it
over has my admiration.

Cheers,
Enrico M.

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: About to declare 'unmaintained'

2009-09-10T16:51:35Z

Like others I find beagle absolutely great, but I have only minor C# skills so it's hard to help.

In my situation, I use mainly beagle on an Ubuntu server for a company-wide document search (I just use the CLI via a home-grown PHP web interface), replacing an installation using Windows and MS Indexing Service. I was unable to find any other straightforward document indexer to run on the new Ubuntu server, but beagle filled the gap beautifully. It could and should be of interest to anyone else migrating from MS to Linux (which is a popular move nowadays). Could it be worth approaching the Ubuntu server people (Canonical) to see if they have any interest?? It might narrow beagle's focus a bit, but still might be better than unmaintained. Just a thought.

Thanks for all your good work!

Cheers, Roger Lainson

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: About to declare 'unmaintained'

2009-09-10T13:00:25Z

I love Beagle. I don't want it die.
But I'm not a c# developer, so I can't help.
But Beagle is part on Suse desktop. Novell CAN'T leave Beagle unmantained.

Can you write to Novell, De Icaza or other "big"?

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: About to declare 'unmaintained'

2009-09-10T08:13:28Z

> You must have seen this coming.

Yep, sadly. Beagle is fantastic but due some peoples myopia it has
never gotten the fame or accolades it deserves [and I've never
understood why more apps didn't just support it rather than just rolling
their own meta-data junk].

> As of now, the evolution backend needs a rewrite because of the new
> Evolution API for indexing.

GNOME doesn't have any official bounty system? I know I'd be willing to
throw up some cash for that to be fixed - it is just too handy to live
without. Again, I just don't understand why *everyone* doesn't use
this.

> There are few other backends that are obsolete due to their move to
> sqlite based storage ... they need a rewrite too.

Maybe in the long run the pervasive use of SQLite will help. Just
trying to find some optimism.

BTW, there is a reimplementation of SQLite in C#
<http://code.google.com/p/csharp-sqlite/> - but I assume everyone here
already knows about that.

> There are lots of challenging improvements or bugfixes in the TODO
> list, of different orders of complexity - so if you want to learn more
> about beagle internals or just get your hands dirty with C# (that is
> how I landed here), I am sure I can make concrete suggestions.

I know I'd love to but am already buried in projects.

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

About to declare 'unmaintained'

2009-09-10T07:56:04Z

Dear friends,
You must have seen this coming. Lack of time of both me and Joe
(personally communicated) has left the beagle project practically
unmaintained. We wanted to do a final release, and Joe even managed to
check-in some patches from the bugzilla. We have been talking about it
among us since the summer and *sigh*... I havn't found the time and
right frame of mind to gather everything, do the testing and roll a
tarball. I am not sure when I will get time to do it. But the trunk is
stable, so feel free to use it.

I am still not completely demotivated, just that a lot is going on
right now, enough to keep me occupied. I try and will try to reply to
emails within a few days ... but please lower your expectations =( If
it helps, there will be one final release before this project is
officially orphaned.

As of now, the evolution backend needs a rewrite because of the new
Evolution API for indexing. I don't know much about its complexity.
There are few other backends that are obsolete due to their move to
sqlite based storage ... they need a rewrite too. There are multiple
query clients ... CLI, gtk, kde, web (the web-interface is broken in
0.3.9 but fixed in trunk) and they seem to be working fine without
major problems. Query can be done remotely and there is an RDF
interface to the indexed data if anyone is interested in data-mining.
We already support a lot of file formats and adding new format is
pretty easy (as simple as writing a script for simple formats).

There are lots of challenging improvements or bugfixes in the TODO
list, of different orders of complexity - so if you want to learn more
about beagle internals or just get your hands dirty with C# (that is
how I landed here), I am sure I can make concrete suggestions.

And once again, any support in any form is most welcome.
Thanks to all of you for your support and help in the previous years,
- dBera

--
-----------------------------------------------------
Debajyoti Bera @ http://dtecht.blogspot.com
beagle / KDE fan
Mandriva / Inspiron-1100 user
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: beagled exception in OpenSuse 11.1

2009-09-09T06:36:24Z

> The whole traceback, as well as the Config-Files can be found in
> attachments.
> I googled the gnome site and the whole web, but could not find
> anything, except that it should be mono-related, but no solution.
> I also installed the lastest versions of Mono and beagle, but no
> change.
> The version info is.:
> /usr/bin/beagled --version
> beagled: The daemon to the Beagle search system.
> Web page: http://www.beagle-project.org/
> Copyright (C) 2004-2008 Novell, Inc. and others
> Beagle: 0.3.9
> Mono: Mono 2.0.1
> Thanks in advance for your help.

I'm running Beagle on openSUSE 11.1; for me it has been quite reliable.

awilliam@linux-m3mt:~> rpm -q beagle
beagle-0.3.8-50.1.i586
awilliam@linux-m3mt:~> rpm -q mono-core
mono-core-2.4.2.3-17.1.i586
awilliam@linux-m3mt:~> uname -a
Linux linux-m3mt 2.6.27.29-0.1-pae #1 SMP 2009-08-15 17:53:59 +0200 i686
i686 i386 GNU/Linux

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: ODT/ODP/ODS

2009-09-09T06:34:21Z

> On Wed, Jul 15, 2009 at 7:50 AM, Adam Tauno
> Williams<awilliam@...> wrote:
> > Does Beagle (0.3.8-46) index the content of OpenOffice files? [It sure
> > seems like I remember it indexing StarOffice files...] But double
> > checking on my system and it only seems to be indexing based on the
> > names of OpenOffice files. In fact, looking at my search results, it
> > doesn't appear to be indexing anything but XML and text (source mostly)
> > files.
> > awilliam@linux-m3mt:~> beagle-info --list-filters | grep -i open
> > FilterOpenOffice - Version 0 (/usr/lib/beagle/Filters/Filters.dll)
> > - MimeType: application/vnd.oasis.opendocument.text
> > - MimeType: application/vnd.oasis.opendocument.text-template
> > - MimeType: application/vnd.oasis.opendocument.spreadsheet
> > - MimeType: application/vnd.oasis.opendocument.spreadsheet-template
> > - MimeType: application/vnd.oasis.opendocument.presentation
> > - MimeType: application/vnd.oasis.opendocument.presentation-template
> > - MimeType: application/vnd.oasis.opendocument.graphics
> > - MimeType: application/vnd.oasis.opendocument.graphics-template
> It should be able to, yes. Try running beagle-extract-content on one
> of the ODF files to see how it is identified.

It started working. For kicks I set BEAGLE_EXERCISE_THE_DOG=1 and let
the service bake overnight - it worked the next morning.

Anyway:
awilliam@linux-m3mt:~/Documents> beagle-extract-content OGo13429612.ods
Filename: file:///home/awilliam/Documents/OGo13429612.ods
Warn: bibparse is not found; bibtex files will not be indexed
Debug: Loaded 64 filters from /usr/lib/beagle/Filters/Filters.dll
Debug: Verifying filter_cache
at /home/awilliam/.beagle/filterver.dat ... cache is dirty ? False
Debug: No filter for file:///home/awilliam/Documents/OGo13429612.ods
(/home/awilliam/Documents/OGo13429612.ods) [application/x-extension-ods]
Filter: (determined in .36s)
MimeType: application/x-extension-ods

Properties:
Timestamp = 2009-08-24 20:48:43 (Utc)

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: How to search .* files?

2009-09-06T17:51:34Z

> Is there a way to tell beagle to search certain plain text dot files,
> like .bash_history and .Rhistory?
>
> I tried to make an external filter but didn't succeed.

Oops... no - dot files and directories are not touched - this is
probably hardcoded in the code and cannot be overriden by any user.

--
-----------------------------------------------------
Debajyoti Bera @ http://dtecht.blogspot.com
beagle / KDE fan
Mandriva / Inspiron-1100 user
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: beagled exception in OpenSuse 11.1

2009-09-03T16:10:39Z

Hi,
Sorry, I missed your email ... you possibly forgot to attach the traceback.
Without any other detailed inforthis looks like mono error to me.

- dBera

On Mon, Aug 24, 2009 at 11:03 AM, Dieter
Woerz<Dieter.Woerz@...> wrote:

> Hello,
>
> I am trying to run beagled in OpenSuse 11.1, but whenever I start the
> daemon, I get the following exception:
>
> 20090824 16:34:42.5156 25290 Beagle ERROR EX: Unhandled exception thrown.
> Exiting immediately.
> 20090824 16:34:42.5156 25290 Beagle ERROR EX:
> System.TypeInitializationException: An exception was thrown by the type
> initializer for Beagle.Util.Conf ---> System.TypeInitializationException: An
> exception was thrown by the type initializer for
> System.Xml.Serialization.XmlSerializer --->
> System.Configuration.ConfigurationException: The `autoflush' attribute must
> be `true' or `false' ---> System.Configuration.ConfigurationException:
> Required attribute 'name' not found.
>
> The whole traceback, as well as the Config-Files can be found in
> attachments.
> I googled the gnome site and the whole web, but could not find anything,
> except that it should be mono-related, but no solution.
> I also installed the lastest versions of Mono and beagle, but no change.
> The version info is.:
>
> /usr/bin/beagled --version
> beagled: The daemon to the Beagle search system.
> Web page: http://www.beagle-project.org/
> Copyright (C) 2004-2008 Novell, Inc. and others
> Beagle: 0.3.9
> Mono: Mono 2.0.1
>
> Thanks in advance for your help.
>
> Best regards,
>
> Dieter
>
> --
>
> Dieter Wörz
>
> _______________________________________________
> Dashboard-hackers mailing list
> Dashboard-hackers@...
> http://mail.gnome.org/mailman/listinfo/dashboard-hackers
>
>

--
-----------------------------------------------------
Debajyoti Bera @ http://dtecht.blogspot.com
beagle / KDE fan
Mandriva / Inspiron-1100 user
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

How to search .* files?

2009-09-01T13:49:00Z

Is there a way to tell beagle to search certain plain text dot files,
like .bash_history and .Rhistory?

I tried to make an external filter but didn't succeed.

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

beagled exception in OpenSuse 11.1

2009-08-24T08:03:46Z

Hello,

I am trying to run beagled in OpenSuse 11.1, but whenever I start the daemon, I get the following exception:

20090824 16:34:42.5156 25290 Beagle ERROR EX: Unhandled exception thrown. Exiting immediately.
20090824 16:34:42.5156 25290 Beagle ERROR EX: System.TypeInitializationException: An exception was thrown by the type initializer for Beagle.Util.Conf ---> System.TypeInitializationException: An exception was thrown by the type initializer for System.Xml.Serialization.XmlSerializer ---> System.Configuration.ConfigurationException: The `autoflush' attribute must be `true' or `false' ---> System.Configuration.ConfigurationException: Required attribute 'name' not found.

The whole traceback, as well as the Config-Files can be found in attachments.
I googled the gnome site and the whole web, but could not find anything, except that it should be mono-related, but no solution.
I also installed the lastest versions of Mono and beagle, but no change.
The version info is.:

/usr/bin/beagled --version
beagled: The daemon to the Beagle search system.
Web page: http://www.beagle-project.org/
Copyright (C) 2004-2008 Novell, Inc. and others
Beagle: 0.3.9
Mono: Mono 2.0.1

Thanks in advance for your help.

Best regards,

Dieter

--

Dieter Wörz

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: [beagle] Remove duplicate 'beagle-part-property.h' from include_HEADERS

2009-07-26T15:07:13Z

Hi,

On Sun, Jul 26, 2009 at 1:46 PM, Arun Raghavan<arunsr@...> wrote:
> commit 95b10dd1dc58068fa09d38fa6bac3763afc9c8f9
> Author: Arun Raghavan <ford_prefect@...>
> Date: Sun Jul 26 23:10:44 2009 +0530
>
> Remove duplicate 'beagle-part-property.h' from include_HEADERS
>
> This was causing breakage with recent versions of 'install'. Thanks to
> Matthias Clasen (mclasen@...) for the patch on bug 588994.

For the future, you can mark the author of the patch by using the
--author command-line flag to "git commit". This will make it more
clear that you're the committer and not the author in git history.

Joe
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: beagle-query configurability

2009-07-20T06:30:24Z

> I see that there has been some discussion in the past regarding the maximum
> number of hits returned by beagle-query. I'd like to throw in my 2c worth
> with the following comments:
>
> The hard-coded limit of 100 hits is the single most annoying thing in the
> whole of beagle, which is otherwise a wonderfully useful tool for my work.
> I regularly get messages like 'Too many matches. Showing latest 6 of total
> 711'. These six hits are often not enough to find what I was looking for.

Which version are you running ? If you are running 0.3.9 (latest),
then I would suggest a complete reindexing of all the files
$ beagle-shutdown
$ rm -rf ~/.beagle/Indexes/FileSystemIndex
$ beagled

There was a bug in the earlier versions which would cause this
meaningless 6 of 711 type of problem. You should get at least 100 hits
if the total is this high.

> First of all, if beagle-search can't return all the matches, then I would
> like to be able to choose whether I get the most relevant, the most recent,
> the oldest, etc. As a suggestion, it could use the same criteria as the
> 'Sort' option.

Frankly, this is a bit complicated. The magic happens in
LuceneCommon.cs and LuceneQueryingDriver.cs - which gets all the
matches back in terms of document ids, and then has extract the
relevant fields for all the documents to sort and top-100 them
correctly. Sorting by most recent is the current strategy but it
should not be hard to extend it.

> Secondly, I would like to be able to get more than 100 matches. Well
> actually 100 would be OK if I could get the 100 most relevant, but (to take
> the case above) 6 is not.

See above.

-dBera

--
-----------------------------------------------------
Debajyoti Bera @ http://dtecht.blogspot.com
beagle / KDE fan
Mandriva / Inspiron-1100 user
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: (resend)patch to beaglefs

2009-07-20T03:21:51Z

2009/7/18 Joe Shaw <joe@...>

Hi Guido,

Looks pretty straightforward. Would you mind filing a bug at
http://bugzilla.gnome.org and attaching a patch? I'm not able to
check it in at the moment, and that will ensure that it doesn't get
lost.

Thanks,
Joe

Done:

http://bugzilla.gnome.org/show_bug.cgi?id=589107

_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

beagle-query configurability

2009-07-19T23:02:10Z

Hello folks,

I see that there has been some discussion in the past regarding the
maximum number of hits returned by beagle-query. I'd like to throw in
my 2c worth with the following comments:

The hard-coded limit of 100 hits is the single most annoying thing in
the whole of beagle, which is otherwise a wonderfully useful tool for my
work. I regularly get messages like 'Too many matches. Showing latest 6
of total 711'. These six hits are often not enough to find what I was
looking for. I can use beagle-search, but as it shows no preview of the
files its results aren't of much use to me either.

First of all, if beagle-search can't return all the matches, then I
would like to be able to choose whether I get the most relevant, the
most recent, the oldest, etc. As a suggestion, it could use the same
criteria as the 'Sort' option.

Secondly, I would like to be able to get more than 100 matches. Well
actually 100 would be OK if I could get the 100 most relevant, but (to
take the case above) 6 is not.

I'm not averse to a bit of code-hacking but I'm no python programmer and
don't have the time to reverse-engineer the project. If someone could
point me in the right direction to make these changes I'd be happy to do
some work on it.

Cheers,
Jonathan
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: (resend)patch to beaglefs

2009-07-18T12:20:27Z

Hi Guido,

On Mon, Jul 6, 2009 at 4:44 AM, guido iodice<guido.iodice@...> wrote:

> Dears, I'm a Beagle fan:
> http://guiodic.wordpress.com/category/gnulinux/guide-pratiche-gnulinux/beagle-guide-pratiche-gnulinux-gnulinux/
>
> I discovered that *beaglefs* has a bug because new beagle syntax.
>
> Sorry, I'm unable to use 'diff' and 'patch' properly.
>
> Changement is simple, in hit.c:
>
> beagle_query_add_text (query, "type:File OR type:IMLog"); /* CHANGHE */
> /* beagle_query_add_text (query, "type:IMLog"); */ /* DELETE OR
> COMMENT THIS LINE*/

Looks pretty straightforward. Would you mind filing a bug at
http://bugzilla.gnome.org and attaching a patch? I'm not able to
check it in at the moment, and that will ensure that it doesn't get
lost.

Thanks,
Joe
_______________________________________________
Dashboard-hackers mailing list
Dashboard-hackers@...
http://mail.gnome.org/mailman/listinfo/dashboard-hackers