freemont

I ripped some mp3's using KAudioCreator about a month ago. All went well.

So I go to rip a couple tracks off a cd last night, and I get errors that
the encoder is not installed. Sure enough, I get:

[paul@lpt-110206 nzb]$ lame
bash: lame: command not found
[paul@lpt-110206 nzb]$ man lame
No manual entry for lame

Then I get:

[root@lpt-110206 nzb]# urpmq lame
no package named lame
The following packages contain lame:
flamerobin
glame

.... oooooook.

It's late, I'm tired, and I'm not getting into this right now, I said. Off
to bed.

This morning, I come in and get:

[root@lpt-110206 nzb]# urpmq LAME
no package named LAME
The following packages contain LAME:
avifile-lame
flamerobin
glame
glame-lame
gstreamer-lame
gstreamer0.10-lame
lame
lame-mp3x
liblame0
liblame0-devel
liblame0-static-devel
libquicktime-lame
libtwolame0
libtwolame0-devel
toolame
twolame
xmms-out_lame
[root@lpt-110206 nzb]# urpmi lame

ftp://ftp.free.fr/pub/Distributions_Linux/plf/mandriva/2007.0/free/release/binary/i586/lame-3.97-1plf2007.0.i586.rpm
installing lame-3.97-1plf2007.0.i586.rpm from /var/cache/urpmi/rpms
Preparing...
################################################## #########
1/1: lame
################################################## #########

I did not change nor add any sources. I didn't change anything! All this
is straight from my console. The part where I get "lame" directly follows
the part where it wasn't found. (I don't log off at night.) Somehow, my
problem resolved itself overnight. But where the heck was lame to start
with?? It worked fine a few weeks ago, and I'm sure I didn't remove it- no
reason to. Perplexing. :-\

Could it have been an update at some point that fouled lame up? And how
can a package *not* be found at one point, then *be* found several hours
later, with no input from the operator?

--
"Because all you of Earth are idiots!"
¯`·..·¯`·-> freemont© <-·¯`·..·¯

james j. dines

It seems your rpm database *may* be a bit screwed up, but it probably
isn't (see below.) Do as root 'rpm --rebuilddb' to be sure it is
consistent.

Unless you left something out you did not try to install lame until the
morning, and when you did so it installed. Most likely, it would have
installed the night before as well.

The previous evening you did 'urpmq lame' and in the morning you did
'urpmq LAME' ... note the difference in case, and the results it will yield:

[root@machine ~]# urpmq LAME
no package named LAME
The following packages contain LAME:
avifile-lame
flamerobin
glame
glame-lame
gstreamer-lame
gstreamer0.10-lame
lame
lame-mp3x
liblame0
liblame0-devel
liblame0-static-devel
libquicktime-lame
libtwolame0
libtwolame0-devel
toolame
twolame
xmms-out_lame
You have new mail in /var/spool/mail/rhiannon
[root@machine ~]# urpmq lame
lame
[root@machine ~]#

So you didn't have it installed and 'urpmq lame' showed it wasn't
installed. In the morning you switched things up (with 'urpmq LAME')
and got different, but expected, results. Then you installed lame
successfully, as you can verify with 'which lame' and 'urpmq lame' but
*NOT* 'urpmq LAME'.

It's all good in the virtual hood :-)

HTH
--
****** Warning - Highly US-Centric .sig approaching! ******
The only way to differentiate "The War on Terrorism"
from "The War on Drugs" is to measure the amount of piss
on the Founding Fathers graves. - James J. Dines

freemont

On Wed, 13 Dec 2006 15:04:08 +0000, James J. Dines writ:

Right, I did leave that out- last night urpmi lame simply returned that
there was no such package, same as urpmq.

Then this morning, it all worked. Go figure. I used caps (LAME) this
morning just on a whim.

It's still a mystery to me what happened to lame in the first place. As
I said, it _was_ there before...

Thanks for the input.

--
"Because all you of Earth are idiots!"
¯`·..·¯`·-> freemont© <-·¯`·..·¯