subject:"anybody working\/supporting beagle\?"

anybody working/supporting beagle?

2010-01-21 Thread Amish Shah

Hi,

How active is this project? I'm doing a comparison between beagle and
tracker trying to decide which meta search engine to use. Beagle seems
great, but kind of inactive especially lately.

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

Re: anybody working/supporting beagle?

2010-01-21 Thread Joe Shaw

Hi,

Beagle isn't in active development.  It is getting some occasional
maintenance done by Novell.

Joe

On Thu, Jan 21, 2010 at 5:23 PM, Amish Shah  wrote:
> Hi,
>
> How active is this project? I'm doing a comparison between beagle and
> tracker trying to decide which meta search engine to use. Beagle seems
> great, but kind of inactive especially lately.
>
> thanks
> Amish
>
> ___
> Dashboard-hackers mailing list
> Dashboard-hackers@gnome.org
> http://mail.gnome.org/mailman/listinfo/dashboard-hackers
>
>
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: anybody working/supporting beagle?

2010-01-21 Thread Amish Shah

If I have questions about how to do things, above and beyond the pretty good
documentation, am I likely to get answers on this forum? How responsive has
Novell been about bug fixes?

Or am I better of with tracker which seems like its actively supported, even
though probably a bit less mature than beagle?

thanks
Amish

On Thu, Jan 21, 2010 at 2:53 PM, Joe Shaw  wrote:

> Hi,
>
> Beagle isn't in active development.  It is getting some occasional
> maintenance done by Novell.
>
> Joe
>
> On Thu, Jan 21, 2010 at 5:23 PM, Amish Shah  wrote:
> > Hi,
> >
> > How active is this project? I'm doing a comparison between beagle and
> > tracker trying to decide which meta search engine to use. Beagle seems
> > great, but kind of inactive especially lately.
> >
> > thanks
> > Amish
> >
> > ___
> > Dashboard-hackers mailing list
> > Dashboard-hackers@gnome.org
> > http://mail.gnome.org/mailman/listinfo/dashboard-hackers
> >
> >
>
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: anybody working/supporting beagle?

2010-01-22 Thread Adam Tauno Williams

On Thu, 2010-01-21 at 16:13 -0800, Amish Shah wrote:
> If I have questions about how to do things, above and beyond the
> pretty good documentation, am I likely to get answers on this forum?
> How responsive has Novell been about bug fixes? 
> Or am I better of with tracker which seems like its actively
> supported, even though probably a bit less mature than beagle? 

It seems to me that the future is Tracker [which is sad, the world
doesn't need any more unmanaged code. Ick!]  Most significantly Tracker
will almost certainly be integrated with the GNOME Activity Journal
 which means, at
some point, it will be included in GNOME [displacing Beagle?]

BTW, I love Beagle - it is a massive improvement over 'managing files'.
But, at least for me, it has stopped working.  Since I last updated Mono
it just churns out a lot of -
---
20100122 06:15:13.6246 10662 Beagle ERROR EX:   at
System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags
invokeAttr, System.Reflection.Binder binder, System.Object[] parameters,
System.Globalization.CultureInfo culture) [0x0] in :0 
20100122 06:15:13.6246 10662 Beagle ERROR EX:   at
System.Reflection.MonoCMethod.Invoke (BindingFlags invokeAttr,
System.Reflection.Binder binder, System.Object[] parameters,
System.Globalization.CultureInfo culture) [0x0] in :0 
20100122 06:15:13.6246 10662 Beagle ERROR EX:   at
System.Reflection.ConstructorInfo.Invoke (System.Object[] parameters)
[0x0] in :0 
20100122 06:15:13.6246 10662 Beagle ERROR EX:   at
System.Activator.CreateInstance (System.Type type, Boolean nonPublic)
[0x0] in :0 
20100122 06:15:13.6246 10662 Beagle ERROR EX:   at
System.Activator.CreateInstance (System.Type type) [0x0] in
:0 
20100122 06:15:13.6246 10662 Beagle ERROR EX:   at
Beagle.Daemon.QueryDriver.ScanAssemblyForQueryables
(System.Reflection.Assembly assembly) [0x0] in :0

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

Re: anybody working/supporting beagle?

2010-01-22 Thread Joe Shaw

Hi,

On Thu, Jan 21, 2010 at 7:13 PM, Amish Shah  wrote:
> If I have questions about how to do things, above and beyond the pretty good
> documentation, am I likely to get answers on this forum? How responsive has
> Novell been about bug fixes?

I will certainly try to answer any questions you have, but if things
require development, you're on your own for that.  (Although, again, I
can provide some guidance.)

Novell has not been very responsive to bug fixes, although I am sure
that is different if you are a customer of theirs. :)

> Or am I better of with tracker which seems like its actively supported, even
> though probably a bit less mature than beagle?

I would say it depends on what you want to do, and how much time and
effort you are willing to invest in development, if any.  At this
point, Tracker has a lot more development going on it.

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

Re: anybody working/supporting beagle?

2010-01-22 Thread Joe Shaw

Hi,

On Fri, Jan 22, 2010 at 6:19 AM, Adam Tauno Williams
 wrote:
> BTW, I love Beagle - it is a massive improvement over 'managing files'.
> But, at least for me, it has stopped working.  Since I last updated Mono
> it just churns out a lot of -
> ---
> 20100122 06:15:13.6246 10662 Beagle ERROR EX:   at
> System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags
> invokeAttr, System.Reflection.Binder binder, System.Object[] parameters,
> System.Globalization.CultureInfo culture) [0x0] in  unknown>:0

This doesn't look like the complete stack trace.  Or, at least, there
isn't the exception message included.  Can you provide that?
Hopefully it's something simple.

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

Re: anybody working/supporting beagle?

2010-01-22 Thread Amish Shah

To start with:

We will probably be writing a back-end to talk to postgres. Seems like the
current backend for html files doesn't analysis all the content of the html
files. Also, we want to add some more file attributes to the index
repository during indexing.

Eventually, we'd like to implement autosuggest.

I took a look a the code, and it seems very readable, so I'm a bit more
comfortable with beagle.

Regarding Novell, is there a commercial license for Beagle present? Is it
required or it something one can buy for support :)

thanks
Amish

On Fri, Jan 22, 2010 at 7:59 AM, Joe Shaw  wrote:

> Hi,
>
> On Fri, Jan 22, 2010 at 6:19 AM, Adam Tauno Williams
>  wrote:
> > BTW, I love Beagle - it is a massive improvement over 'managing files'.
> > But, at least for me, it has stopped working.  Since I last updated Mono
> > it just churns out a lot of -
> > ---
> > 20100122 06:15:13.6246 10662 Beagle ERROR EX:   at
> > System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags
> > invokeAttr, System.Reflection.Binder binder, System.Object[] parameters,
> > System.Globalization.CultureInfo culture) [0x0] in  > unknown>:0
>
> This doesn't look like the complete stack trace.  Or, at least, there
> isn't the exception message included.  Can you provide that?
> Hopefully it's something simple.
>
> Joe
> ___
> Dashboard-hackers mailing list
> Dashboard-hackers@gnome.org
> http://mail.gnome.org/mailman/listinfo/dashboard-hackers
>
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: anybody working/supporting beagle?

2010-01-22 Thread Joe Shaw

Hi,

On Fri, Jan 22, 2010 at 12:32 PM, Amish Shah  wrote:
> We will probably be writing a back-end to talk to postgres. Seems like the
> current backend for html files doesn't analysis all the content of the html
> files. Also, we want to add some more file attributes to the index
> repository during indexing.

Ok.  There are two concepts at play here: a "backend", which is
basically a data source.  The file system is an example of a backend,
and it seems like postgres would also be a backend.  There is also a
"filter", which is code that extracts data and metadata from an item
from a backend.  So there is an HTML filter which pulls the data out
of it.  Both backends and filters can add attributes to the document
that is written to the index.

I'm not sure what you mean when you say that HTML files don't analyze
all the content.  There is a limit of the number of tokens indexed.  I
forget what the number is, but it's something like 2,000 or 10,000 or
50,000.  Something like that.  If you think you're going to need more
indexed than that, you'll want to bump that limit.

> Eventually, we'd like to implement autosuggest.

That'd be great!

> Regarding Novell, is there a commercial license for Beagle present? Is it
> required or it something one can buy for support :)

Hopefully someone from Novell on the list can chime in on this. :)

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

Re: anybody working/supporting beagle?

2010-01-22 Thread Gabriel Burt

On Fri, Jan 22, 2010 at 2:00 PM, Joe Shaw  wrote:
> On Fri, Jan 22, 2010 at 12:32 PM, Amish Shah  wrote:
>> Regarding Novell, is there a commercial license for Beagle present? Is it
>> required or it something one can buy for support :)
>
> Hopefully someone from Novell on the list can chime in on this. :)

There is no license or support contract for Beagle directly;  I
believe the way to get Novell to support Beagle for you is by being a
customer of SUSE Linux Enterprise Desktop
(http://www.novell.com/products/desktop/) and filing a Service
Request, or by filing a bug on bugzilla.novell.com.

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

Beagle excepts [Was: anybody working/supporting beagle?]

2010-01-25 Thread Adam Tauno Williams

On Fri, 2010-01-22 at 10:59 -0500, Joe Shaw wrote:
> Hi,
> On Fri, Jan 22, 2010 at 6:19 AM, Adam Tauno Williams
>  wrote:
> > BTW, I love Beagle - it is a massive improvement over 'managing files'.
> > But, at least for me, it has stopped working.  Since I last updated Mono
> > it just churns out a lot of -
> > ---
> > 20100122 06:15:13.6246 10662 Beagle ERROR EX:   at
> > System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags
> > invokeAttr, System.Reflection.Binder binder, System.Object[] parameters,
> > System.Globalization.CultureInfo culture) [0x0] in  > unknown>:
> This doesn't look like the complete stack trace.  Or, at least, there
> isn't the exception message included.  Can you provide that?
> Hopefully it's something simple.

Cleaned out .beagle/Logs, restarted Beagle, and attached logs.

-- 
openSUSE 
Linux for human beings who need to get things done.


Log.tar.gz
Description: application/compressed-tar


signature.asc
Description: This is a digitally signed message part
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: Beagle excepts [Was: anybody working/supporting beagle?]

2010-01-25 Thread Adam Tauno Williams

On Mon, 2010-01-25 at 08:49 -0500, Adam Tauno Williams wrote:
> On Fri, 2010-01-22 at 10:59 -0500, Joe Shaw wrote:
> > Hi,
> > On Fri, Jan 22, 2010 at 6:19 AM, Adam Tauno Williams
> >  wrote:
> > > BTW, I love Beagle - it is a massive improvement over 'managing files'.
> > > But, at least for me, it has stopped working.  Since I last updated Mono
> > > it just churns out a lot of -
> > > ---
> > > 20100122 06:15:13.6246 10662 Beagle ERROR EX:   at
> > > System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags
> > > invokeAttr, System.Reflection.Binder binder, System.Object[] parameters,
> > > System.Globalization.CultureInfo culture) [0x0] in  > > unknown>:
> > This doesn't look like the complete stack trace.  Or, at least, there
> > isn't the exception message included.  Can you provide that?
> > Hopefully it's something simple.
> Cleaned out .beagle/Logs, restarted Beagle, and attached logs.

I'd guess the crux of the issue is all of the:

20100125 08:51:14.2123 08249 Beagle ERROR EX:
System.Reflection.TargetInvocationException: Exception has been thrown
by the target of an invocation. ---> System.TypeLoadException: Could not
load type 'Mono.Data.Sqlite.SqliteBusyException' from assembly
'Mono.Data.Sqlite, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=0738eb9f132ed756'


It appears to be having an SQLite issue.  I've disabled all the backends
now except files.

mono-data-sqlite-2.6.1-31.1.i586 is the package installed.

awill...@linux-m3mt:~/.beagle/Log> rpm -ql
mono-data-sqlite-2.6.1-31.1.i586
/usr/lib/mono/1.0/Mono.Data.Sqlite.dll
/usr/lib/mono/1.0/Mono.Data.SqliteClient.dll
/usr/lib/mono/2.0/Mono.Data.Sqlite.dll
/usr/lib/mono/2.0/Mono.Data.SqliteClient.dll
/usr/lib/mono/gac/Mono.Data.Sqlite
/usr/lib/mono/gac/Mono.Data.Sqlite/1.0.5000.0__0738eb9f132ed756
/usr/lib/mono/gac/Mono.Data.Sqlite/1.0.5000.0__0738eb9f132ed756/Mono.Data.Sqlite.dll
/usr/lib/mono/gac/Mono.Data.Sqlite/1.0.5000.0__0738eb9f132ed756/Mono.Data.Sqlite.dll.mdb
/usr/lib/mono/gac/Mono.Data.Sqlite/2.0.0.0__0738eb9f132ed756
/usr/lib/mono/gac/Mono.Data.Sqlite/2.0.0.0__0738eb9f132ed756/Mono.Data.Sqlite.dll
/usr/lib/mono/gac/Mono.Data.Sqlite/2.0.0.0__0738eb9f132ed756/Mono.Data.Sqlite.dll.mdb
/usr/lib/mono/gac/Mono.Data.SqliteClient
/usr/lib/mono/gac/Mono.Data.SqliteClient/1.0.5000.0__0738eb9f132ed756
/usr/lib/mono/gac/Mono.Data.SqliteClient/1.0.5000.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll
/usr/lib/mono/gac/Mono.Data.SqliteClient/1.0.5000.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll.mdb
/usr/lib/mono/gac/Mono.Data.SqliteClient/2.0.0.0__0738eb9f132ed756
/usr/lib/mono/gac/Mono.Data.SqliteClient/2.0.0.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll
/usr/lib/mono/gac/Mono.Data.SqliteClient/2.0.0.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll.mdb

-- 
openSUSE 
Linux for human beings who need to get things done.


signature.asc
Description: This is a digitally signed message part
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: Beagle excepts [Was: anybody working/supporting beagle?]

2010-01-25 Thread Joe Shaw

Hi,

Yep, that class does not exist in Mono.Data.Sqlite.

A fix might be to change the "using" line to be
Mono.Data.SqliteClient, as I believe that is the older code.
Otherwise some sort will be needed to port to the newer
Mono.Data.Sqlite API.

Joe

On Mon, Jan 25, 2010 at 8:53 AM, Adam Tauno Williams
 wrote:
> On Mon, 2010-01-25 at 08:49 -0500, Adam Tauno Williams wrote:
>> On Fri, 2010-01-22 at 10:59 -0500, Joe Shaw wrote:
>> > Hi,
>> > On Fri, Jan 22, 2010 at 6:19 AM, Adam Tauno Williams
>> >  wrote:
>> > > BTW, I love Beagle - it is a massive improvement over 'managing files'.
>> > > But, at least for me, it has stopped working.  Since I last updated Mono
>> > > it just churns out a lot of -
>> > > ---
>> > > 20100122 06:15:13.6246 10662 Beagle ERROR EX:   at
>> > > System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags
>> > > invokeAttr, System.Reflection.Binder binder, System.Object[] parameters,
>> > > System.Globalization.CultureInfo culture) [0x0] in > > > unknown>:
>> > This doesn't look like the complete stack trace.  Or, at least, there
>> > isn't the exception message included.  Can you provide that?
>> > Hopefully it's something simple.
>> Cleaned out .beagle/Logs, restarted Beagle, and attached logs.
>
> I'd guess the crux of the issue is all of the:
> 
> 20100125 08:51:14.2123 08249 Beagle ERROR EX:
> System.Reflection.TargetInvocationException: Exception has been thrown
> by the target of an invocation. ---> System.TypeLoadException: Could not
> load type 'Mono.Data.Sqlite.SqliteBusyException' from assembly
> 'Mono.Data.Sqlite, Version=2.0.0.0, Culture=neutral,
> PublicKeyToken=0738eb9f132ed756'
> 
>
> It appears to be having an SQLite issue.  I've disabled all the backends
> now except files.
>
> mono-data-sqlite-2.6.1-31.1.i586 is the package installed.
>
> awill...@linux-m3mt:~/.beagle/Log> rpm -ql
> mono-data-sqlite-2.6.1-31.1.i586
> /usr/lib/mono/1.0/Mono.Data.Sqlite.dll
> /usr/lib/mono/1.0/Mono.Data.SqliteClient.dll
> /usr/lib/mono/2.0/Mono.Data.Sqlite.dll
> /usr/lib/mono/2.0/Mono.Data.SqliteClient.dll
> /usr/lib/mono/gac/Mono.Data.Sqlite
> /usr/lib/mono/gac/Mono.Data.Sqlite/1.0.5000.0__0738eb9f132ed756
> /usr/lib/mono/gac/Mono.Data.Sqlite/1.0.5000.0__0738eb9f132ed756/Mono.Data.Sqlite.dll
> /usr/lib/mono/gac/Mono.Data.Sqlite/1.0.5000.0__0738eb9f132ed756/Mono.Data.Sqlite.dll.mdb
> /usr/lib/mono/gac/Mono.Data.Sqlite/2.0.0.0__0738eb9f132ed756
> /usr/lib/mono/gac/Mono.Data.Sqlite/2.0.0.0__0738eb9f132ed756/Mono.Data.Sqlite.dll
> /usr/lib/mono/gac/Mono.Data.Sqlite/2.0.0.0__0738eb9f132ed756/Mono.Data.Sqlite.dll.mdb
> /usr/lib/mono/gac/Mono.Data.SqliteClient
> /usr/lib/mono/gac/Mono.Data.SqliteClient/1.0.5000.0__0738eb9f132ed756
> /usr/lib/mono/gac/Mono.Data.SqliteClient/1.0.5000.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll
> /usr/lib/mono/gac/Mono.Data.SqliteClient/1.0.5000.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll.mdb
> /usr/lib/mono/gac/Mono.Data.SqliteClient/2.0.0.0__0738eb9f132ed756
> /usr/lib/mono/gac/Mono.Data.SqliteClient/2.0.0.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll
> /usr/lib/mono/gac/Mono.Data.SqliteClient/2.0.0.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll.mdb
>
> --
> openSUSE 
> Linux for human beings who need to get things done.
>
> ___
> Dashboard-hackers mailing list
> Dashboard-hackers@gnome.org
> http://mail.gnome.org/mailman/listinfo/dashboard-hackers
>
>
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: Beagle excepts [Was: anybody working/supporting beagle?]

2010-01-25 Thread Gabriel Burt

It exists in gac/Mono.Data.Sqlite/1.xxx/ but not the 2.xxx version.
I'm told we can explicitly link against the old one by specifying
-r:path/to/gac/Mono.Data.Sqlite/1.xxx/  I'm also told that the
2.xxx version has been shipped since Mono 1.2.4 (which we already
require), so we should probably just upgrade to it.  I have a patch to
do so that I'll push if nobody objects.

Gabriel

On Mon, Jan 25, 2010 at 6:28 AM, Joe Shaw  wrote:
> Hi,
>
> Yep, that class does not exist in Mono.Data.Sqlite.
>
> A fix might be to change the "using" line to be
> Mono.Data.SqliteClient, as I believe that is the older code.
> Otherwise some sort will be needed to port to the newer
> Mono.Data.Sqlite API.
>
> Joe
>
> On Mon, Jan 25, 2010 at 8:53 AM, Adam Tauno Williams
>  wrote:
>> On Mon, 2010-01-25 at 08:49 -0500, Adam Tauno Williams wrote:
>>> On Fri, 2010-01-22 at 10:59 -0500, Joe Shaw wrote:
>>> > Hi,
>>> > On Fri, Jan 22, 2010 at 6:19 AM, Adam Tauno Williams
>>> >  wrote:
>>> > > BTW, I love Beagle - it is a massive improvement over 'managing files'.
>>> > > But, at least for me, it has stopped working.  Since I last updated Mono
>>> > > it just churns out a lot of -
>>> > > ---
>>> > > 20100122 06:15:13.6246 10662 Beagle ERROR EX:   at
>>> > > System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags
>>> > > invokeAttr, System.Reflection.Binder binder, System.Object[] parameters,
>>> > > System.Globalization.CultureInfo culture) [0x0] in >> > > unknown>:
>>> > This doesn't look like the complete stack trace.  Or, at least, there
>>> > isn't the exception message included.  Can you provide that?
>>> > Hopefully it's something simple.
>>> Cleaned out .beagle/Logs, restarted Beagle, and attached logs.
>>
>> I'd guess the crux of the issue is all of the:
>> 
>> 20100125 08:51:14.2123 08249 Beagle ERROR EX:
>> System.Reflection.TargetInvocationException: Exception has been thrown
>> by the target of an invocation. ---> System.TypeLoadException: Could not
>> load type 'Mono.Data.Sqlite.SqliteBusyException' from assembly
>> 'Mono.Data.Sqlite, Version=2.0.0.0, Culture=neutral,
>> PublicKeyToken=0738eb9f132ed756'
>> 
>>
>> It appears to be having an SQLite issue.  I've disabled all the backends
>> now except files.
>>
>> mono-data-sqlite-2.6.1-31.1.i586 is the package installed.
>>
>> awill...@linux-m3mt:~/.beagle/Log> rpm -ql
>> mono-data-sqlite-2.6.1-31.1.i586
>> /usr/lib/mono/1.0/Mono.Data.Sqlite.dll
>> /usr/lib/mono/1.0/Mono.Data.SqliteClient.dll
>> /usr/lib/mono/2.0/Mono.Data.Sqlite.dll
>> /usr/lib/mono/2.0/Mono.Data.SqliteClient.dll
>> /usr/lib/mono/gac/Mono.Data.Sqlite
>> /usr/lib/mono/gac/Mono.Data.Sqlite/1.0.5000.0__0738eb9f132ed756
>> /usr/lib/mono/gac/Mono.Data.Sqlite/1.0.5000.0__0738eb9f132ed756/Mono.Data.Sqlite.dll
>> /usr/lib/mono/gac/Mono.Data.Sqlite/1.0.5000.0__0738eb9f132ed756/Mono.Data.Sqlite.dll.mdb
>> /usr/lib/mono/gac/Mono.Data.Sqlite/2.0.0.0__0738eb9f132ed756
>> /usr/lib/mono/gac/Mono.Data.Sqlite/2.0.0.0__0738eb9f132ed756/Mono.Data.Sqlite.dll
>> /usr/lib/mono/gac/Mono.Data.Sqlite/2.0.0.0__0738eb9f132ed756/Mono.Data.Sqlite.dll.mdb
>> /usr/lib/mono/gac/Mono.Data.SqliteClient
>> /usr/lib/mono/gac/Mono.Data.SqliteClient/1.0.5000.0__0738eb9f132ed756
>> /usr/lib/mono/gac/Mono.Data.SqliteClient/1.0.5000.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll
>> /usr/lib/mono/gac/Mono.Data.SqliteClient/1.0.5000.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll.mdb
>> /usr/lib/mono/gac/Mono.Data.SqliteClient/2.0.0.0__0738eb9f132ed756
>> /usr/lib/mono/gac/Mono.Data.SqliteClient/2.0.0.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll
>> /usr/lib/mono/gac/Mono.Data.SqliteClient/2.0.0.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll.mdb
>>
>> --
>> openSUSE 
>> Linux for human beings who need to get things done.
>>
>> ___
>> Dashboard-hackers mailing list
>> Dashboard-hackers@gnome.org
>> http://mail.gnome.org/mailman/listinfo/dashboard-hackers
>>
>>
> ___
> Dashboard-hackers mailing list
> Dashboard-hackers@gnome.org
> http://mail.gnome.org/mailman/listinfo/dashboard-hackers
>
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

Re: Beagle excepts [Was: anybody working/supporting beagle?]

2010-01-25 Thread Joe Shaw

Hi Gabriel,

Sounds good to me.

Joe

On Mon, Jan 25, 2010 at 2:07 PM, Gabriel Burt  wrote:
> It exists in gac/Mono.Data.Sqlite/1.xxx/ but not the 2.xxx version.
> I'm told we can explicitly link against the old one by specifying
> -r:path/to/gac/Mono.Data.Sqlite/1.xxx/  I'm also told that the
> 2.xxx version has been shipped since Mono 1.2.4 (which we already
> require), so we should probably just upgrade to it.  I have a patch to
> do so that I'll push if nobody objects.
>
> Gabriel
>
> On Mon, Jan 25, 2010 at 6:28 AM, Joe Shaw  wrote:
>> Hi,
>>
>> Yep, that class does not exist in Mono.Data.Sqlite.
>>
>> A fix might be to change the "using" line to be
>> Mono.Data.SqliteClient, as I believe that is the older code.
>> Otherwise some sort will be needed to port to the newer
>> Mono.Data.Sqlite API.
>>
>> Joe
>>
>> On Mon, Jan 25, 2010 at 8:53 AM, Adam Tauno Williams
>>  wrote:
>>> On Mon, 2010-01-25 at 08:49 -0500, Adam Tauno Williams wrote:
 On Fri, 2010-01-22 at 10:59 -0500, Joe Shaw wrote:
 > Hi,
 > On Fri, Jan 22, 2010 at 6:19 AM, Adam Tauno Williams
 >  wrote:
 > > BTW, I love Beagle - it is a massive improvement over 'managing files'.
 > > But, at least for me, it has stopped working.  Since I last updated 
 > > Mono
 > > it just churns out a lot of -
 > > ---
 > > 20100122 06:15:13.6246 10662 Beagle ERROR EX:   at
 > > System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags
 > > invokeAttr, System.Reflection.Binder binder, System.Object[] 
 > > parameters,
 > > System.Globalization.CultureInfo culture) [0x0] in >>> > > unknown>:
 > This doesn't look like the complete stack trace.  Or, at least, there
 > isn't the exception message included.  Can you provide that?
 > Hopefully it's something simple.
 Cleaned out .beagle/Logs, restarted Beagle, and attached logs.
>>>
>>> I'd guess the crux of the issue is all of the:
>>> 
>>> 20100125 08:51:14.2123 08249 Beagle ERROR EX:
>>> System.Reflection.TargetInvocationException: Exception has been thrown
>>> by the target of an invocation. ---> System.TypeLoadException: Could not
>>> load type 'Mono.Data.Sqlite.SqliteBusyException' from assembly
>>> 'Mono.Data.Sqlite, Version=2.0.0.0, Culture=neutral,
>>> PublicKeyToken=0738eb9f132ed756'
>>> 
>>>
>>> It appears to be having an SQLite issue.  I've disabled all the backends
>>> now except files.
>>>
>>> mono-data-sqlite-2.6.1-31.1.i586 is the package installed.
>>>
>>> awill...@linux-m3mt:~/.beagle/Log> rpm -ql
>>> mono-data-sqlite-2.6.1-31.1.i586
>>> /usr/lib/mono/1.0/Mono.Data.Sqlite.dll
>>> /usr/lib/mono/1.0/Mono.Data.SqliteClient.dll
>>> /usr/lib/mono/2.0/Mono.Data.Sqlite.dll
>>> /usr/lib/mono/2.0/Mono.Data.SqliteClient.dll
>>> /usr/lib/mono/gac/Mono.Data.Sqlite
>>> /usr/lib/mono/gac/Mono.Data.Sqlite/1.0.5000.0__0738eb9f132ed756
>>> /usr/lib/mono/gac/Mono.Data.Sqlite/1.0.5000.0__0738eb9f132ed756/Mono.Data.Sqlite.dll
>>> /usr/lib/mono/gac/Mono.Data.Sqlite/1.0.5000.0__0738eb9f132ed756/Mono.Data.Sqlite.dll.mdb
>>> /usr/lib/mono/gac/Mono.Data.Sqlite/2.0.0.0__0738eb9f132ed756
>>> /usr/lib/mono/gac/Mono.Data.Sqlite/2.0.0.0__0738eb9f132ed756/Mono.Data.Sqlite.dll
>>> /usr/lib/mono/gac/Mono.Data.Sqlite/2.0.0.0__0738eb9f132ed756/Mono.Data.Sqlite.dll.mdb
>>> /usr/lib/mono/gac/Mono.Data.SqliteClient
>>> /usr/lib/mono/gac/Mono.Data.SqliteClient/1.0.5000.0__0738eb9f132ed756
>>> /usr/lib/mono/gac/Mono.Data.SqliteClient/1.0.5000.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll
>>> /usr/lib/mono/gac/Mono.Data.SqliteClient/1.0.5000.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll.mdb
>>> /usr/lib/mono/gac/Mono.Data.SqliteClient/2.0.0.0__0738eb9f132ed756
>>> /usr/lib/mono/gac/Mono.Data.SqliteClient/2.0.0.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll
>>> /usr/lib/mono/gac/Mono.Data.SqliteClient/2.0.0.0__0738eb9f132ed756/Mono.Data.SqliteClient.dll.mdb
>>>
>>> --
>>> openSUSE 
>>> Linux for human beings who need to get things done.
>>>
>>> ___
>>> Dashboard-hackers mailing list
>>> Dashboard-hackers@gnome.org
>>> http://mail.gnome.org/mailman/listinfo/dashboard-hackers
>>>
>>>
>> ___
>> Dashboard-hackers mailing list
>> Dashboard-hackers@gnome.org
>> http://mail.gnome.org/mailman/listinfo/dashboard-hackers
>>
>
___
Dashboard-hackers mailing list
Dashboard-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/dashboard-hackers

anybody working/supporting beagle?

Re: anybody working/supporting beagle?

Re: anybody working/supporting beagle?

Re: anybody working/supporting beagle?

Re: anybody working/supporting beagle?

Re: anybody working/supporting beagle?

Re: anybody working/supporting beagle?

Re: anybody working/supporting beagle?

Re: anybody working/supporting beagle?

Beagle excepts [Was: anybody working/supporting beagle?]

Re: Beagle excepts [Was: anybody working/supporting beagle?]

Re: Beagle excepts [Was: anybody working/supporting beagle?]

Re: Beagle excepts [Was: anybody working/supporting beagle?]

Re: Beagle excepts [Was: anybody working/supporting beagle?]

14 matches

Site Navigation

Mail list logo

Footer information