Mailinglist Archive: opensuse-factory (757 mails)

< Previous Next >
Re: [opensuse-factory] Bug 177758
  • From: Pascal Bleser <pascal.bleser@xxxxxxxxx>
  • Date: Tue, 23 May 2006 12:33:35 +0200
  • Message-id: <4472E4FF.8080903@xxxxxxxxx>
jdd wrote:
> Frank-Michael Fischer wrote:
>> So: I am well trained in taking comments like yours.
> can't you beleive most users have _not_ the problem you have?

Can't *you* believe *many* users do have that problem ?
Again, come hang around on IRC and witness the havoc.

> I have a default kde install, and had some kind of bugs, but _not_ the
> one you have.

You're part of the lucky ones, I would say.

>> And I found the real problem: it's the way libzypp is architected and
>> implemented. Now what?

Actually I don't think it's libzypp, it's more about ZMD.

Could someone post a few details about what libzypp actually does and
how it interacts with ZMD ?
Is it an abstraction and/or API to ZMD and rug ?

Is libzypp the one capable of handling yast2/ZMD repos and RPM-MD ? Or
is it ZMD/rug ?

When using RPM-MD repos in yast2, does it still go through ZMD ?

> what I try to make you understant is that if _you_ have _several_ non
> working install, this may be because you always make a kind of install
> that gives the problem.

That ridiculous. What would some "kind of install" have to do with ZMD
working properly or not on 3 different boxes and several others he did
from scratch.
And he's not alone with this issue, it's being reported often on IRC.

On IRC we currently recommend using smart, y2pmsh or rug and
disable+remove ZMD packages.

> this don't mean you do anything wrong, only something that not any
> people do. identifying this could be of great help like the rug test you
> where asked to do.

Well, I strongly presume those problems are related to plain ZMD
and/or libzypp bugs, not particularly to his setup.
Those problems are encountered far too often to just be related to
some specifics of his installation or hardware.

> and all this helps fixing the bug.
> and by the way the starting of the 10.1 is specially fast on my two
> years old machine... and I just discovered beagle was running.. I even
> don't know what it is :-)
> to follow this mail, I tryed beagle. clic on the icon, ask for "yast" in
> the search box. Beagle said the daemon was not started, I clic to start
> and answers come is nearly no time.

Yes, the Beagle frontends work well, no problem with that. But the
Beagle daemon is also often a resource hog that causes people on IRC
to complain about 10.1 being so slow.
I suppose there's not all that much to be done about the Beagle
daemon, it's kind of inherent to what it does (it has to do a lot of
I/O and probably actually needs a lot of memory) - document indexers
usually do that, I don't think there's a silver bullet to solve it.

Nevertheless, Beagle is not a critical component to the system. If
it's a resource hog on your system, then just turn it off, SUSE Linux
10.1 will remain an excellent distribution to work with.
The same cannot be said of the package management subsystem. The
latter must work reliably, always, so we really have to identify and
fix bugs there (and not dismiss them).

-o) Pascal Bleser
/\\ <pascal.bleser@xxxxxxxxx> <guru@xxxxxxxxxxx>

< Previous Next >
This Thread