Re: How to deal with package broken dependencies

2002-12-22 Thread Rob Weir
On Sun, Dec 22, 2002 at 09:45:32AM -0800, Bill Moseley wrote:
> I had also install Aspell 0.50.3 from source -- I have some code that
> depends on the New Aspell.

[snip]

> That on is probably my fault due to installing the New Aspell from source,
> but I'm not sure.

apt-get install equivs and generate a fake package that Provide:'s the
aspell stuff you've installed.

> Is this just a fact of life when using packages that may have conflicting
> dependencies?
> 
> Can the package system tell me more about these packages, like when they
> were installed (or removed) and what caused that to happen?

Neither apt nor dpkg actually logs what it does, unfortunately.
aptitude does, which is one of the reasons I use it for all my package
management needs.

-rob



msg20644/pgp0.pgp
Description: PGP signature


How to deal with package broken dependencies

2002-12-22 Thread Bill Moseley

I installed kdebase-libs today to get Kmail working.  It seems to have
broken a few things, so I'm wonder how best to deal with it.

First, I had gkrellm2 installed.  Now dpkg shows:

rc  gkrellm1.2.12-2   Multiple stacked system monitors: 1 process.
rc  gkrellm2   2.0.3-1Multiple stacked system monitors: 1 process.

I'm not sure what happened here.  I don't ever remember requesting gkrellm
(version 1) and I sure didn't ask either to be removed -- perhaps it was
removed on a installation conflict that I missed?

I had also install Aspell 0.50.3 from source -- I have some code that
depends on the New Aspell.

Now I see this in dpkg

rc  libaspell100.33.7.1-8 The aspell spell checker runtime libraries.
ii  libpspell4 0.12.2-6   Portable spell checker interface library

That on is probably my fault due to installing the New Aspell from source,
but I'm not sure.

Is this just a fact of life when using packages that may have conflicting
dependencies?

Can the package system tell me more about these packages, like when they
were installed (or removed) and what caused that to happen?

Thanks,




-- 
Bill Moseley [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]