Le Friday 06 June 2008 09:08:43 John Andersen, vous avez écrit :

Just kill the dog. Everybody else here has done that long ago. Beagle is a solution looking for a problem. Microsoft had an indexer and people dutifully jumped up and built one for Linux. It was aptly named because it is such a poor performer.

Just shut it down and tell it not to start again.

OK, I followed your suggestion. Since I having light systems (e. g. install only what's needed), what are the relevant packages to uninstall? Niki -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi! Am Freitag, 6. Juni 2008 09:08 schrieb John Andersen:

...

I've been running openSUSE 10.3 for a week, and I'm quite satisfied. This morning I began work and noticed my machine was unusually slow. I launched 'top' and saw that a process called beagled-helper consumed no less than 80% CPU (I'm working on a PIV 2.4 GHz).

Is this some daily indexing process or what? BTW, I left my machine running all night.

Just kill the dog. Everybody else here has done that long ago.

I didn't. Beagle has been working great for me so long. Often been the faster alternative when looking for some data than digging through documents by hand or asking the person that provided the information in the first place again. Especially indexing of chat logs is a neat feature. I have only seen beagle hogging the PC once. And that was when on my Wife old PIII 550 I had installed a new system and restored the 15 or 20 GiB of Documents etc.. Even this inital index would slow down within seconds of touching the computer. Afterwards even on that old system I didn't have problems. I did, however, upgrade beagle to the version in the Buildservice which is supposed to fix one or two problem. Regards, Matthias -- Matthias Bach www.marix.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

http://en.opensuse.org/OpenSUSE_mailing_list_netiquette#Changing_the_subject... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi! Am Freitag, 6. Juni 2008 11:24 schrieb Clayton:

...

I did, however, upgrade beagle to the version in the Buildservice which is supposed to fix one or two problem.

Question to those of you still using Beagle: I haven't used Beagle in a long time now... does Beagle still get bogged down on some *.doc and *.odt documents?

Not for me. However as it scans incremental I fear I hadn't even noticed if it gets bogged down on the 2 or 3 documents that get created per day. Regards, Matthias -- Matthias Bach www.marix.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

I've got 6 GB of RAM on this machine, and...gave beagle another chance.

It didn't take too long to banish it back to the doghouse...

As much as I don't like Beagle either :-) what version did you try? The one from the 10.3 repos or the Beagle repo? There is a significant difference between the two, and the 0.3.2 version does work a lot better. Key points are... make sure you have the latest build, and limit the indexing to what needs to be indexed vs indexing everything. If I let Beagle try to index everything, it took a long time. If I limited the indexing to key directories, the indexing was a lot better... it still barfed on some of the docs and odts though. When 11.0 is released I'll try Beagle again.... C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Friday 06 June 2008 10:54:50 Evans Garde wrote:

Clayton wrote:

...

...

I've been running openSUSE 10.3 for a week, and I'm quite satisfied. This morning I began work and noticed my machine was unusually slow. I launched 'top' and saw that a process called beagled-helper consumed no less than 80% CPU (I'm working on a PIV 2.4 GHz).

Is this some daily indexing process or what? BTW, I left my machine running all night.

<snip happens>

...

Personally, I am one who had the 100% CPU use problems. I found that after upgrading to 0.3.x, and then severely limiting what Beagle was allowed to index (limiting it to a single directory with only a few files), I could get it "under control", and it was... reasonably silent in the background. In the end I removed it. It provided nothing I needed, and the resource consumption... even on an AMD6400+ with 4GB of RAM... was more than I was willing to allow it to have.

I've got 6 GB of RAM on this machine, and...gave beagle another chance.

It didn't take too long to banish it back to the doghouse...

What does this thing do, bubblesort in an interpreted-at-execution-time language?

...

C.

I stuck with it for several days without the machine being turned off listening to my drive clunking all of the time. I didn't notice any problems with cpu utilisation or memory but disc access times went up to the point where they were completely un acceptable. This may have been down to every thing being swapped out of memory. When I searched for something I was amazed to see web pages and all sorts of things come up. I think beagle should throw up a splash screen telling people what it can do and wait for them to set it up as the user wants. As I Ieft it running for so long and it didn't stop clunking I assume that it doesn't build and then maintain an index but continuously looks for changes. That' s not on so I simpley disabled it from the icon. No problems since. There is an option to not enable it at start up available from the icon. John 10.3 86_64bit -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Le Friday 06 June 2008 11:51:49 Evans Garde, vous avez écrit :

The beagle is highly annoying beast.

First, when left alone, like in the back yard, it will howl like an insane child, that is when it isn't trying to dig a hole under the fence to run off to who knows where.

And if one is let onto your computer, it will consume resources as if the whole purpose of your computer is to run beagle and beagled-helper.

If I wanted not only to turn it off, but to completely uninstall it, 1) would that be possible (that is, without wrecking my desktop's integrity), and if yes 2) what packages would I have to uninstall? I understand Beagle is a Mono app, and since I use the KDE spin of SUSE, can I uninstall Mono also? Niki -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 06/06/2008 07:57 PM, Carlos E. R. wrote:

...

2) what packages would I have to uninstall? I understand Beagle is a Mono app, and since I use the KDE spin of SUSE, can I uninstall Mono also?

Nope.

You can try, and you will see several apps that require mono.

If you search for beagle in Yast, you can delete everything it finds EXCEPT libbeagle, which has too many dependencies. You also need to delete Kerry. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Niki Kovacs wrote:

Le Friday 06 June 2008 11:51:49 Evans Garde, vous avez écrit :

...

The beagle is highly annoying beast.

First, when left alone, like in the back yard, it will howl like an insane child, that is when it isn't trying to dig a hole under the fence to run off to who knows where.

And if one is let onto your computer, it will consume resources as if the whole purpose of your computer is to run beagle and beagled-helper.

If I wanted not only to turn it off, but to completely uninstall it, 1) would that be possible (that is, without wrecking my desktop's integrity), and if yes 2) what packages would I have to uninstall? I understand Beagle is a Mono app, and since I use the KDE spin of SUSE, can I uninstall Mono also? I uninstalled all packages with beagle in the name, and also kerry, but for dependency reasons kept these:

libbeagle-python-0.2.18-23 libbeagle-0.2.18-23 Beagle is neutralized, but the beagle dependencies in the rest of the system are satisfied. Like Clayton, I'll give it another shot when 11.0 is released - but if it flunks the quake 3 arena test, it's gone. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Sloan wrote:

Evans Garde wrote:

...

Niki Kovacs wrote:

...

Hi,

I've been running openSUSE 10.3 for a week, and I'm quite satisfied. This morning I began work and noticed my machine was unusually slow. I launched 'top' and saw that a process called beagled-helper consumed no less than 80% CPU (I'm working on a PIV 2.4 GHz). Is this some daily indexing process or what? BTW, I left my machine running all night.

The beagle is highly annoying beast.

First, when left alone, like in the back yard, it will howl like an insane child, that is when it isn't trying to dig a hole under the fence to run off to who knows where.

And if one is let onto your computer, it will consume resources as if the whole purpose of your computer is to run beagle and beagled-helper.

While I wouldn't have phrased it exactly as Mr Garde has, I certainly noticed an overall performance hit due to beagle. The system was sluggish, and subject to longish pauses. Going catatonic for a second or two while playing quake 3 arena online makes for some bitter memories. After I nuked beagle, the system was generally silky smooth and responsive from that point on.

I hate the fact that new users of suse are blindsided by this, not suspecting the presence of the beagle thrashing their system, and come away with the impression that linux is sluggish.

Joe

Not only beagle, but the opensuse Updater applet as well. This starts a zypper refresh at each login to kde unless you uncheck the option that it start on each login. Standard practice on every 10.3 install: (1) remove beagle with: rpm -e $(rpm -qa | grep beagle | sed '/^lib.*/d') kerry && rm -r ~/.beagle (2) on first login to kde or gnome, right-click the openSuSE Updater in the task-bar, uncheck "start on login", click quit, just remember to run updates manually or schedule them automatically at a certain time; DONE - No more slowness, crisp performance from boot-to-"end current-session" -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

I had this problem too. Just go to YaST and remove everything *beagle*. Your CPU will be greatfully! I have a big question about that, why use beagle? Really, there´s a lot of problems and every people which I talk about openSUSE claims about that. Why not use another language than mono? I´m so sorry to *flame* this thread, but it´s horrible. Cheers. On Fri, Jun 6, 2008 at 1:58 PM, Kevin Dupuy wrote:

On Fri, 2008-06-06 at 08:50 +0200, Niki Kovacs wrote:

...

Hi,

I've been running openSUSE 10.3 for a week, and I'm quite satisfied. This morning I began work and noticed my machine was unusually slow. I launched 'top' and saw that a process called beagled-helper consumed no less than 80% CPU (I'm working on a PIV 2.4 GHz).

Is this some daily indexing process or what? BTW, I left my machine running all night.

The fact that it was fine then started slowing your system is a problem... take a look at http://beagle-project.org/Troubleshooting_CPU for more information. There may be a document it's getting hung up on. -- Kevin "Yo" Dupuy Public Mail Yo.media: 225-590-5961

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-- /\ Gabriel Stein gabrielstein@gmail.com MSN: gabrielstein@hotmail.com Administrador de Redes - Network Administrator Linux User #223750 +55 51 9357 3886 Porto Alegre - RS - Brasil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

huahauhauaa.... rofl On Fri, Jun 6, 2008 at 3:26 PM, John Andersen wrote:

On Fri, Jun 6, 2008 at 10:11 AM, Gabriel Stein wrote:

...

Why not use another language than mono?

Because without Beagle mono would have no reason to exist?

-- ----------JSA---------

-- /\ Gabriel Stein gabrielstein@gmail.com MSN: gabrielstein@hotmail.com Administrador de Redes - Network Administrator Linux User #223750 +55 51 9357 3886 Porto Alegre - RS - Brasil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Le Friday 06 June 2008 20:45:31 Larry Stotler, vous avez écrit :

Just my 2 cents, but I also find absolutely no point in Beagle. While it may be convient if you have 1000+ documents, with what little most people do, there's no point in it. I make sure it's not installed on any system I do.

What I don't install:

AppArmour Beagle openoffice Compiz

There are others, but those are the main ones. When you are running on a P3/500 with 384MB RAM, you don't need all that stuff. I'd rip out more crap if there weren't so many dependencies(bluetooth, firewire, pilot, isdn, etc.).

The configuration you describe is called Slackware Linux :oD Cheers, Niki (Slackware user from 7.1 to 12.0) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Larry Stotler wrote:

On Fri, Jun 6, 2008 at 2:55 PM, Niki Kovacs wrote:

...

The configuration you describe is called Slackware Linux :oD

If slackware had YaST, I might switch!

Well, there's slapt-get... Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, Jun 6, 2008 at 11:45 AM, Larry Stotler wrote:

Just my 2 cents, but I also find absolutely no point in Beagle. While it may be convient if you have 1000+ documents, with what little most people do, there's no point in it. I make sure it's not installed on any system I do.

Worse than that Larry, if you have a small amount of documents its not needed, but if you have 20 years of business records on line it will kill you machine. When you need it, it won't work. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, 06 Jun 2008 15:58:52 -0400, Evans Garde wrote:

John Andersen wrote:

...

On Fri, Jun 6, 2008 at 11:45 AM, Larry Stotler wrote:

...

Just my 2 cents, but I also find absolutely no point in Beagle. While it may be convient if you have 1000+ documents, with what little most people do, there's no point in it. I make sure it's not installed on any system I do.

Worse than that Larry, if you have a small amount of documents its not needed, but if you have 20 years of business records on line it will kill you machine.

When you need it, it won't work.

Essentially, if you need beagle, you have to devote a whole server to it. double-plus-ungood.

I don't find this to be the case. I use it occasionally (not regularly), and I do find performance issues resulting from the indexer (and often have to kill many beagle-helper processes that just pile up), but I find with the number of IMs I have (I use pidgin heavily for work) and the sheer number of documents I have, it does the job OK enough for me. When ti really starts to take over the system, I nuke it. Having it not search remote filesystems helps *a lot*. Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, 10 Jun 2008 03:29:09 -0400, Evens Garde wrote:

...

Having it not search remote filesystems helps *a lot*..

I don't have ANY remote filesystems, and it's still a dog.

Just goes to show that different people have different experiences. I don't see it have too many performance issues myself, mostly what I see is memory consumption goes through the roof (but that's a constant for Mono apps, it seems - Simias does the same thing). ZMD kills the processor on my system, but that's the only one now. Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, 10 Jun 2008 15:49:37 -0400, Evens Garde wrote:

Remember that Mono...is an implementation of an MS product. And one of the primary purposes of MS products is to eat up resources so as to cause the owner of a computer to go out and buy a NEW machine, with yet another copy of the same software which chewed up the previous machine.

Heh, you know, I never thought of it that way - but it does explain a few things.... ;-) Jim -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Really people.. I don´t like beagle, and I can´t see a program which works perfectly with mono. So sorry, I always have the same opinion: use native softwares/languages in native OS. Why not leave .NET to MS Operational Systems? Cheers. On Tue, Jun 10, 2008 at 4:50 PM, Jim Henderson wrote:

On Tue, 10 Jun 2008 15:49:37 -0400, Evens Garde wrote:

...

Remember that Mono...is an implementation of an MS product. And one of the primary purposes of MS products is to eat up resources so as to cause the owner of a computer to go out and buy a NEW machine, with yet another copy of the same software which chewed up the previous machine.

Heh, you know, I never thought of it that way - but it does explain a few things.... ;-)

Jim

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-- /\ Gabriel Stein gabrielstein@gmail.com MSN: gabrielstein@hotmail.com Administrador de Redes - Network Administrator Linux User #223750 +55 51 9357 3886 Porto Alegre - RS - Brasil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue, Jun 10, 2008 at 12:49 PM, Evens Garde wrote:

Jim Henderson wrote:

...

On Tue, 10 Jun 2008 03:29:09 -0400, Evens Garde wrote:

...

...

Having it not search remote filesystems helps *a lot*..

I don't have ANY remote filesystems, and it's still a dog.

Just goes to show that different people have different experiences. I don't see it have too many performance issues myself, mostly what I see is memory consumption goes through the roof (but that's a constant for Mono apps, it seems - Simias does the same thing). ZMD kills the processor on my system, but that's the only one now.

Remember that Mono...is an implementation of an MS product. And one of the primary purposes of MS products is to eat up resources so as to cause the owner of a computer to go out and buy a NEW machine, with yet another copy of the same software which chewed up the previous machine.

You have to ask yourself if Beagle would have had as much teething problems (pun intended) had it been developed in C or C++. To develop this in Mono made no sense, other than the Mono boys and Miguel de Icaza at Novell have somehow gained influence beyond their contributions to the distro, and would have, except of the loud outcry on this list and others, pushed KDE off the desktop two years ago. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 10 June 2008 01:14:35 pm Evens Garde wrote:

...

To develop this in Mono made no sense, other than the Mono boys and Miguel de Icaza at Novell have somehow gained influence beyond their contributions to the distro, and would have, except of the loud outcry on this list and others, pushed KDE off the desktop two years ago.

Somebody needs to move his desk to the janitor's closet -- then maybe he'll take a hint and leave quietly.

Nah, have the desk moved to the basement. Then he'll start a fire in Novell after extorting several millions of dollars and eventually move to a carribian island. :P j/k -- k -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 10 June 2008 01:39:28 pm Evens Garde wrote:

Kai Ponte wrote:

...

On Tuesday 10 June 2008 01:14:35 pm Evens Garde wrote:

...

...

To develop this in Mono made no sense, other than the Mono boys and Miguel de Icaza at Novell have somehow gained influence beyond their contributions to the distro, and would have, except of the loud outcry on this list and others, pushed KDE off the desktop two years ago.

Somebody needs to move his desk to the janitor's closet -- then maybe he'll take a hint and leave quietly.

Nah, have the desk moved to the basement. Then he'll start a fire in Novell after extorting several millions of dollars and eventually move to a

^ ^ some other guys he moves

...

Caribbean island.

Works for me.

Thanks for the correction. I forgot the red stapler, too! As for Beagle, I just make it non-installable (taboo?) during installation. I never hear from it again. -- kai www.filesite.org || www.4thedadz.com || www.perfectreign.com remember - a turn signal is a statement, not a request -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

John Andersen wrote:

On Fri, Jun 6, 2008 at 10:11 AM, Gabriel Stein wrote:

...

Why not use another language than mono?

Because without Beagle mono would have no reason to exist?

When I was a kid, Mono was something to avoid. ;-) -- Use OpenOffice.org http://www.openoffice.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Fri, 2008-06-06 at 14:11 -0300, Gabriel Stein wrote:

I had this problem too.

Just go to YaST and remove everything *beagle*. Your CPU will be greatfully!

I have a big question about that, why use beagle? Really, there´s a lot of problems and every people which I talk about openSUSE claims about that.

Why not use another language than mono? I´m so sorry to *flame* this thread, but it´s horrible.

Cheers.

Let's not get into this again. The bottom line is we've had several really long threads about the usefulness of Beagle, and the end result is always the same: some people like it, some don't. -- Kevin "Yo" Dupuy Public Mail Yo.media: 225-590-5961 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

...

Let's not get into this again. The bottom line is we've had several really long threads about the usefulness of Beagle, and the end result is always the same: some people like it, some don't.

Sorry Kevin, we are already WELL into it, and see no reason to drop it just because you don't want to go there again.

Maybe someone can change the topic to "Beagle eats my CPU in 10.3" for a more accurate description of the thread :-) - dBera -- ----------------------------------------------------- Debajyoti Bera @ http://dtecht.blogspot.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

...

Maybe someone can change the topic to "Beagle eats my CPU in 10.3" for a more accurate description of the thread :-)

Is there a release which doesn't eat the CPU (and disk bandwidth, and I/O buffers, for that matter) ?

Apparently yes (thats what people say).

If not, then the current generic subject is appropriate.

-- ----------------------------------------------------- Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

...

...

Is there a release which doesn't eat the CPU (and disk bandwidth, and I/O buffers, for that matter) ?

Apparently yes (thats what people say).

Not by my experience with the most recent release.

This is something the upstream does not know - in fact, the feedback is that the recent releases work much better. I am curious what exact kind of problem(s) you are seeing. * Continous 100% cpu usage for more than a few minutes at a stretch * High average CPU usage even after the initial indexing is over (which might take a day if there are lots of documents/emails etc. - "beagle-info --status" will give some clue if the initial indexing is still in progress) * The CPU usage does not drop when the mouse is moved or other desktop activity happens * Buffer cache is continously increasing due to beagle i.e. if no other I/O intensive application is running then "grep ^Cached: /proc/meminfo" should give an indication - dBera -- ----------------------------------------------------- Debajyoti Bera @ http://dtecht.blogspot.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Does anyone know if it does build an initial index and then adds to it?

When I ran it for a few days I had the impression that it didn't add to an existing index but kept looking at the lot to see if anything had changed.

What do you mean ? beagle-info --index-info or one of the menu entries in beagle-search shows the number of items in the current index. -- ----------------------------------------------------- Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

My impression is that it looks all of the time and never ever stops when an initial index has been built even when there have been no further changes.

That is definitely not the case, at least with the version on 11.0. I am pretty confident about that. After initial indexing is over, there should be no activity. - dBera PS: There was a corner case in the versions in 10.x and earlier which caused endless crawling like you said but that was fixed long ago. -- ----------------------------------------------------- Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE / Mandriva / Inspiron-1100 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

The Tuesday 2008-06-10 at 20:45 -0400, Evens Garde wrote:

Debajyoti Bera wrote:

...

...

My impression is that it looks all of the time and never ever stops when an initial index has been built even when there have been no further changes.

That is definitely not the case, at least with the version on 11.0. I am pretty confident about that. After initial indexing is over, there should be no activity.

Unfortunately, it doesn't seem to be that way.

Recent example -- desktop machine at home. SuSE 10.3

He said 11.0, but you are using 10.3. -- Cheers, Carlos E. R. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

...

...

Recent example -- desktop machine at home. SuSE 10.3

He said 11.0, but you are using 10.3.

The version in the 10.3 update repo is the same as the latest version on the beagle website.

Do you mean the regular opensuse-10.3 update repo or the factory/some other repo ? I am asking since someone in this very thread complained that the newer beagle-0.3.7 versions are not available from the opensuse updates. E.g. to confirm "beagled --version" will tell you which version you are running, in case you somehow also have a stale version installed. - dBera -- ----------------------------------------------------- Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE / Mandriva / Inspiron-1100 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-06-11 at 12:28 -0400, Evens Garde wrote:

The version in the 10.3 update repo is the same as the latest version on the beagle website.

The update repo? That's not the most recent. You should have the _beagle_ repo. For instance: ftp://ftp5.gwdg.de/pub/opensuse/repositories/Beagle/openSUSE_10.3/ it currently has 0.3.3-9.2, whereas with the update repo you get 0.2.18-30. However, it provokes a tremendous depencies conflict list, so it is not possible to update. #### YaST2 conflicts list - generated 2008-06-12 14:57:20 #### anjuta has missing dependencies There are no installable providers of yelp for anjuta-1.2.4a-137.i586 === anjuta-1.2.4a-137.i586 === yelp-2.18.1-52.i586 provides yelp == 2.18.1-52, but is scheduled to be uninstalled. yelp-2.18.1-52.i586[gwdg_OSS] provides yelp == 2.18.1-52, but it is uninstallable. Try installing it on its own for more details. anjuta-1.2.4a-137.i586 depends on yelp anjuta-1.2.4a-137.i586 is lacking the requirement yelp (null) Conflict Resolution: ( ) delete anjuta ( ) Ignore this requirement just here brasero has missing dependencies There are no installable providers of libbeagle.so.0 for brasero-0.6.1-23.i586 === brasero-0.6.1-23.i586 === libbeagle-0.2.18-23.i586 provides libbeagle.so.0, but is scheduled to be uninstalled. libbeagle-0.2.18-23.i586[gwdg_OSS] provides libbeagle.so.0, but it is uninstallable. Try installing it on its own for more details. brasero-0.6.1-23.i586 depends on libbeagle brasero-0.6.1-23.i586 is lacking the requirement libbeagle.so.0 (null) Conflict Resolution: ( ) delete brasero ( ) Ignore this requirement just here control-center2 has missing dependencies There are no installable providers of nautilus for control-center2-2.20.0-7.2.i586 === control-center2-2.20.0-7.2.i586 === nautilus-2.20.0-5.2.i586 provides nautilus == 2.20.0-5.2, but is scheduled to be uninstalled. nautilus-2.20.0-5.i586[gwdg_OSS] provides nautilus == 2.20.0-5, but it is uninstallable. Try installing it on its own for more details. control-center2-2.20.0-7.2.i586 depends on nautilus control-center2-2.20.0-7.2.i586 is lacking the requirement libnautilus-extension.so.1 (null) Conflict Resolution: ( ) delete control-center2 ( ) Ignore this requirement just here eiciel has missing dependencies There are no installable providers of libnautilus-extension.so.1 for eiciel-0.9.4-98.i586 === eiciel-0.9.4-98.i586 === nautilus-2.20.0-5.2.i586 provides libnautilus-extension.so.1, but is scheduled to be uninstalled. nautilus-2.20.0-5.i586[gwdg_OSS] provides libnautilus-extension.so.1, but it is uninstallable. Try installing it on its own for more details. eiciel-0.9.4-98.i586 depends on nautilus eiciel-0.9.4-98.i586 is lacking the requirement libnautilus-extension.so.1 (null) Conflict Resolution: ( ) delete eiciel ( ) Ignore this requirement just here evince has missing dependencies There are no installable providers of libnautilus-extension.so.1 for evince-2.20.0-5.2.i586 === evince-2.20.0-5.2.i586 === nautilus-2.20.0-5.2.i586 provides libnautilus-extension.so.1, but is scheduled to be uninstalled. nautilus-2.20.0-5.i586[gwdg_OSS] provides libnautilus-extension.so.1, but it is uninstallable. Try installing it on its own for more details. evince-2.20.0-5.2.i586 depends on nautilus evince-2.20.0-5.2.i586 is lacking the requirement libnautilus-extension.so.1 (null) Conflict Resolution: ( ) delete evince ( ) Ignore this requirement just here evolution has missing dependencies There are no installable providers of yelp for evolution-2.12.0-5.6.i586 === evolution-2.12.0-5.6.i586 === yelp-2.18.1-52.i586 provides yelp == 2.18.1-52, but is scheduled to be uninstalled. yelp-2.18.1-52.i586[gwdg_OSS] provides yelp == 2.18.1-52, but it is uninstallable. Try installing it on its own for more details. evolution-2.12.0-5.6.i586 depends on yelp evolution-2.12.0-5.6.i586 is lacking the requirement yelp (null) Conflict Resolution: ( ) delete evolution ( ) Ignore this requirement just here file-roller has missing dependencies There are no installable providers of libnautilus-extension.so.1 for file-roller-2.20.0-7.i586 === file-roller-2.20.0-7.i586 === nautilus-2.20.0-5.2.i586 provides libnautilus-extension.so.1, but is scheduled to be uninstalled. nautilus-2.20.0-5.i586[gwdg_OSS] provides libnautilus-extension.so.1, but it is uninstallable. Try installing it on its own for more details. file-roller-2.20.0-7.i586 depends on nautilus file-roller-2.20.0-7.i586 is lacking the requirement libnautilus-extension.so.1 (null) Conflict Resolution: ( ) delete file-roller ( ) Ignore this requirement just here gnome-mount has missing dependencies There are no installable providers of libnautilus-extension.so.1 for gnome-mount-0.6-30.2.i586 === gnome-mount-0.6-30.2.i586 === nautilus-2.20.0-5.2.i586 provides libnautilus-extension.so.1, but is scheduled to be uninstalled. nautilus-2.20.0-5.i586[gwdg_OSS] provides libnautilus-extension.so.1, but it is uninstallable. Try installing it on its own for more details. gnome-mount-0.6-30.2.i586 depends on nautilus gnome-mount-0.6-30.2.i586 is lacking the requirement libnautilus-extension.so.1 (null) Conflict Resolution: ( ) delete gnome-mount ( ) Ignore this requirement just here kdebase3-beagle has missing dependencies There are no installable providers of libbeagle.so.0 for kdebase3-beagle-3.5.7-87.5.i586 === kdebase3-beagle-3.5.7-87.5.i586 === libbeagle-0.2.18-23.i586 provides libbeagle.so.0, but is scheduled to be uninstalled. libbeagle-0.2.18-23.i586[gwdg_OSS] provides libbeagle.so.0, but it is uninstallable. Try installing it on its own for more details. kdebase3-beagle-3.5.7-87.5.i586 depends on libbeagle kdebase3-beagle-3.5.7-87.5.i586 is lacking the requirement libbeagle.so.0 (null) Conflict Resolution: ( ) delete kdebase3-beagle ( ) Ignore this requirement just here nautilus has missing dependencies There are no installable providers of libbeagle.so.0 for nautilus-2.20.0-5.2.i586 === nautilus-2.20.0-5.2.i586 === libbeagle-0.2.18-23.i586 provides libbeagle.so.0, but is scheduled to be uninstalled. libbeagle-0.2.18-23.i586[gwdg_OSS] provides libbeagle.so.0, but it is uninstallable. Try installing it on its own for more details. nautilus-2.20.0-5.2.i586 depends on libbeagle nautilus-2.20.0-5.2.i586 is lacking the requirement libbeagle.so.0 (null) Conflict Resolution: ( ) delete nautilus ( ) Ignore this requirement just here nautilus-cd-burner has missing dependencies There are no installable providers of nautilus for nautilus-cd-burner-2.20.0-5.i586 === nautilus-cd-burner-2.20.0-5.i586 === nautilus-2.20.0-5.2.i586 provides nautilus == 2.20.0-5.2, but is scheduled to be uninstalled. nautilus-2.20.0-5.i586[gwdg_OSS] provides nautilus == 2.20.0-5, but it is uninstallable. Try installing it on its own for more details. nautilus-cd-burner-2.20.0-5.i586 depends on nautilus nautilus-cd-burner-2.20.0-5.i586 is lacking the requirement libnautilus-extension.so.1 (null) Conflict Resolution: ( ) delete nautilus-cd-burner ( ) Ignore this requirement just here nautilus-open-terminal has missing dependencies There are no installable providers of libnautilus-extension.so.1 for nautilus-open-terminal-0.7-120.i586 === nautilus-open-terminal-0.7-120.i586 === nautilus-2.20.0-5.2.i586 provides libnautilus-extension.so.1, but is scheduled to be uninstalled. nautilus-2.20.0-5.i586[gwdg_OSS] provides libnautilus-extension.so.1, but it is uninstallable. Try installing it on its own for more details. nautilus-open-terminal-0.7-120.i586 depends on nautilus nautilus-open-terminal-0.7-120.i586 is lacking the requirement libnautilus-extension.so.1 (null) Conflict Resolution: ( ) delete nautilus-open-terminal ( ) Ignore this requirement just here nautilus-sendto has missing dependencies There are no installable providers of nautilus for nautilus-sendto-0.10-55.i586 === nautilus-sendto-0.10-55.i586 === nautilus-2.20.0-5.2.i586 provides nautilus == 2.20.0-5.2, but is scheduled to be uninstalled. nautilus-2.20.0-5.i586[gwdg_OSS] provides nautilus == 2.20.0-5, but it is uninstallable. Try installing it on its own for more details. nautilus-sendto-0.10-55.i586 depends on nautilus nautilus-sendto-0.10-55.i586 is lacking the requirement libnautilus-extension.so.1 (null) Conflict Resolution: ( ) delete nautilus-sendto ( ) Ignore this requirement just here nautilus-share has missing dependencies There are no installable providers of libnautilus-extension.so.1 for nautilus-share-0.7.0-122.i586 === nautilus-share-0.7.0-122.i586 === nautilus-2.20.0-5.2.i586 provides libnautilus-extension.so.1, but is scheduled to be uninstalled. nautilus-2.20.0-5.i586[gwdg_OSS] provides libnautilus-extension.so.1, but it is uninstallable. Try installing it on its own for more details. nautilus-share-0.7.0-122.i586 depends on nautilus nautilus-share-0.7.0-122.i586 is lacking the requirement libnautilus-extension.so.1 (null) Conflict Resolution: ( ) delete nautilus-share ( ) Ignore this requirement just here seahorse has missing dependencies There are no installable providers of libnautilus-extension.so.1 for seahorse-2.20-7.i586 === seahorse-2.20-7.i586 === nautilus-2.20.0-5.2.i586 provides libnautilus-extension.so.1, but is scheduled to be uninstalled. nautilus-2.20.0-5.i586[gwdg_OSS] provides libnautilus-extension.so.1, but it is uninstallable. Try installing it on its own for more details. seahorse-2.20-7.i586 depends on nautilus seahorse-2.20-7.i586 is lacking the requirement libnautilus-extension.so.1 (null) Conflict Resolution: ( ) delete seahorse ( ) Ignore this requirement just here totem has missing dependencies There are no installable providers of libnautilus-extension.so.1 for totem-2.20.0-6.i586 === totem-2.20.0-6.i586 === nautilus-2.20.0-5.2.i586 provides libnautilus-extension.so.1, but is scheduled to be uninstalled. nautilus-2.20.0-5.i586[gwdg_OSS] provides libnautilus-extension.so.1, but it is uninstallable. Try installing it on its own for more details. totem-2.20.0-6.i586 depends on nautilus totem-2.20.0-6.i586 is lacking the requirement libnautilus-extension.so.1 (null) Conflict Resolution: ( ) delete totem ( ) Ignore this requirement just here yelp has missing dependencies There are no installable providers of libbeagle.so.0 for yelp-2.18.1-52.i586 === yelp-2.18.1-52.i586 === libbeagle-0.2.18-23.i586 provides libbeagle.so.0, but is scheduled to be uninstalled. libbeagle-0.2.18-23.i586[gwdg_OSS] provides libbeagle.so.0, but it is uninstallable. Try installing it on its own for more details. yelp-2.18.1-52.i586 depends on libbeagle yelp-2.18.1-52.i586 is lacking the requirement libbeagle.so.0 (null) Conflict Resolution: ( ) delete yelp ( ) Ignore this requirement just here #### YaST2 conflicts list END ### - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIUR4ytTMYHG2NR9URAuspAJ0SV02PyvYnFSYwqk/ymmwnptn3vACePPhk evaUuenESRgtC/hZu38gDPY= =UXW7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

The version of beagle I used was on the suse 10.3 download. If it's bugged why haven't I been offered an update? If the developers want their code to be used and liked they need to make sure this happens. It just means more space

The newer versions are in the factory, I believe. Developers do want users to use better versions but it is not possible for them to create packages for all the distributions and backport all newer versions for old distribution releases. But I think OpenSUSE factory, Debian testing and Mandriva cooker does a reasonably good job of making sure users who want can use the latest releases. - dBera -- ----------------------------------------------------- Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org