Kevin B. McCarty wrote:
Hi Scott, Scott wrote:But seriously folks... What's a "broken pipe"?A pipe is this keyboard symbol: |
That part I knew. :-)
When you want to use the output of one command as the input of another command, you "pipe" it, like this: ls -l | sort
And that part too.. :-)
A broken pipe happens when the command reading input dies unexpectedly, for instance (supposing I was a very fast typist) if I meanwhile ran "killall -9 sort" in another xterm before ls was finished.
Gotcha! Thanks
dpkg: error processing /var/cache/apt/archives/krita_1%3a1.4.90.1-1_i386.deb (--unpack): trying to overwrite `/usr/share/mimelnk/image/x-raw.desktop', which is also in package digikam dpkg-deb: subprocess paste killed by signal ( *Broken pipe* ) Errors were encountered while processing: /var/cache/apt/archives/krita_1%3a1.4.90.1-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1)In this case, the program that dies is dpkg, and the reason it dies is stated on the second line I quoted above: the already-installed "digikam" package and the new "krita" package that you are trying to install contain the same file. This is not supposed to happen, and is therefore a bug in one of the two packages. Since your "krita" package came from experimental, it's probably the one at fault. Please file a bug against it.
Done. :-)
In the meantime, to work around the problem, you can run dpkg -i --force-overwrite /var/cache/apt/archives/krita_*.deb to tell dpkg that you want it to overwrite the common file instead of griping about it.
Thanks! Now I don't have to confuse the plumber. ;-) -- Scott www.angrykeyboarder.com © 2006 angrykeyboarder™ & Elmer Fudd. All Wights Wesewved