kanotix.com :: Thema anzeigen - Smart Package Manager strangeness

kanotix.com

Software - Smart Package Manager strangeness

gardyloo - 01.08.2006, 21:08 Uhr
Titel: Smart Package Manager strangeness

Hi, all,

I've been playing with the "smart" package manager. It's kind of neat (I use it more on the research group's SUSE installation because it seems to do a considerably better job than SUSE's native Yast2, and plays well with apt4rpm). However, just recently I've been having troubles with running it on Kanotix.

If I try to open the smart gui directly, it just crashes. If I so a "smart update" from the cli, an "updating cache" is shown in the terminal (seems to work fine), then the lines

Zitat:

Fetching information for './ -' ...
Fatal: failed to acquire the pool lock: Operation not permitted

All of the other methods for updating/downloading (apt-get, aptitude, kpackage, synaptic) seem to work fine.

Any clues? Of course I've tried running this in various "root" ways, like kdesu, sudo, sux, etc.

[Edit:] It seems that smart was broken by a bug in python-pycurl -- bug reports have been trickling in since the time I noticed the br0ken smartpm. So it seems that this will be resolved sometime soonish in the future.

mzilikazi - 01.08.2006, 22:07 Uhr
Titel: RE: Smart Package Manager strangeness

Sorry but I have no idea about Smart package manager but I do know this. Many times people have said "We now have something better than apt" but I'm still waiting for something better than apt. Winken

slh - 01.08.2006, 22:32 Uhr
Titel: RE: Smart Package Manager strangeness

After smart has "successfully" destroyed dpkg's package integrity, there's really not much to do than re- installing.

gardyloo - 02.08.2006, 01:40 Uhr
Titel:

Good points! I don't usually use Smart on my kanotix installation, because the packages immediately available to me as a Kanotix/Debian are much more numerous than those for SUSE 10.0 on a 64-bit machine.

I don't think that Smart has really screwed up the dpkg system (as I think was implied; I might be wrong!), as dpkg, apt, etc. works just fine.

slh - 02.08.2006, 01:53 Uhr
Titel:

It has, because the on-disk state is seriously different from what dpkg expects and acts upon - I call that broken beyond repair.

gardyloo - 02.08.2006, 02:32 Uhr
Titel:

Ah. Perhaps we're talking at cross-purposes here. Are you saying that the error prompting "failed to acquire pool lock" as in my first message is indicative of a screwed up database (or collection of .debs, or something -- I'm not really sure how the package managers keep track of this stuff!) on my computer? I would naively guess that dpkg and apt would ALSO barf if that were the case. They seem to work just fine for me.

gardyloo - 08.08.2006, 18:41 Uhr
Titel: Fixed.

OK, if anyone is interested, downgrading python-pycurl to (at least for me) 7.15.4-1 solves the "pool lock" problem. Apparently it's a bug in that package.

John - 09.08.2006, 07:54 Uhr
Titel: RE: Fixed.

neverthless don*t use smart, it installs packages with --force and so destroys the systems package-integrity

gardyloo - 09.08.2006, 19:06 Uhr
Titel:

Zitat:

neverthless don*t use smart, it installs packages with --force and so destroys the systems package-integrity

Ohhhhh. Now THAT I didn't know. Thank you! I'll leave it alone on my Kanotix system.