[PlanetCCRMA] apt-get dist-upgrade problem

[Jim Ruxton]

Thank you everyone for the suggestions. The approach taken by Chris 
worked for me and hopefully my apt-get database is back in sync. Thanks 
again!
Jim

>>
>>
>>
> I recently had the same problem with the same version of openssl
> installed and marked _as to-be-installed_ by "apt-get dist-upgrade".
> Rebuilding the rpm database did not fix the problem.
> I personally avoid solutions of the type "rpm -e --nodeps ..." which 
> tends
> to corrupt the rpm database. What I have found is that it is better to 
> work
> with the apt "envelope" to rpm.
> A brute-force approach as in "apt-get install openssl" in
> the present circumstances makes clear the deep dependencies that
> openssl has(which in linux is one of the most important crypto packages),
> since about a hundred packages need to be _uninstalled_. However,
> a "apt-get --reinstall install openssl" worked fine and eliminated the
> 'apt-get dist-upgrade' conflict.
>
> I'm sorry to say that I dont understand apt well enough to explain 
> this behavior,
> so I offer this solution with the miraculous caveat "it worked" -- 
> since eliminating
> the irritating 'openssl double bind' messages was more important to me 
> than a deeper
> understanding of apt's database integrity management.
>
> Chris
>
>
>
>
>
>
>
>
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA@ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
>
>