Were Intrepid updates the reason I lost my sound on the Intrepid partition?

[Derek Broughton]

Gene Heskett wrote:

> On Sunday 22 February 2009, Steven Vollom wrote:
>>> through his messages for the past few days, I see that he may have
>>> borked apt during a Java installation.
>>
>>What does borking apt mean, and is it fixable?  How can I tell that I
>>borked
>>it?  Thanks!
> 
> First off, I wasn't aware that apt used java.  

It doesn't.  However, it is possible to b0rk (please, let's l3rn to spel
rite!) apt any time you have a package that doesn't install properly.  The
most common way this happens is with a package that has a b0rked install
script.  The script exits with a non-zero return code, and then apt can't
do anything more because the first thing it tries whenever you use it is to
finish installing the package that can't be installed.  A less fatal
problem occurs if you do something silly like powering off your computer
before the install finishes.  That will sometimes require you to manually
run "dpkg --configure -a" before apt can work again, but at least can be
resolved without actually editing scripts.

> As for borked, is a 
> bastardization of the work broken, invented by folks like me who can't
> type well at speed. :-)

...but who like to pretend that their atrocious spelling is intentional.