F11 -> F12 preupgrade problem resulted in odd alsa loaded

[Tony Nelson]

On 10-02-23 19:11:18, Peter J. Stieber wrote:
> On 10-02-23 11:46:51, PS = Pete Stieber wrote:
> PS>> Making another attempt to explain my problem...
> PS>>
> PS>> After the F11 ->  F12 preupgrade process, I have an
> PS>> orphaned ALSA lib package...
> PS>> ...
> PS>> alsa-lib-1.0.22-3.fc11.x86_64
> PS>> ...
> PS>> Package matching alsa-lib-1.0.22-2.fc12.x86_64
> PS>> already installed.
> PS>> ...
> 
> On 2/23/2010 1:46 PM, TN = Tony Nelson wrote:
> TN> Note this is a lower version.
> 
> Thanks Tony.  I completely ignored this and was hung-up on the fc11
> vs. fc12 portion of the version.

That's the least important part of the version scheme.

 ...
> TN> 1) Wait.  You already have a newer version.
> 
> But I was hoping to use the non-orphaned fc12 version.

The difference between alsa-lib-1.0.22-3.fc11.x86_64 and a hypothetical 
alsa-lib-1.0.22-3.fc12.x86_64 is the environment they were compiled in, 
as they start from the same source code.  An update to alsa-lib in F12 
would have a higher version and would replace the one you had.


> TN> 2) Downgrade the package.  See `man yum` for
> TN> caveats.
> 
> This worked.  Thank you.  And fortunately
> 
> yum update
> 
> does *not* update to the higher numbered fc11 version.
 ...

That would only happen if the F11 repos were active, but in that case, 
the package would not have been an orphan.


> BTW, It would be "I Dream of Jeannie freaky" if you were ever a Major
> in the U.S. Air Force, but I'm sure you have heard that before ;-)

I was USNavy Enlisted.

-- 
____________________________________________________________________
TonyN.:'                       <mailto:tonynelson at georgeanelson.com>
      '                              <http://www.georgeanelson.com/>