hi again, cannot update anything this happened today
E: libxine1-bin: package libxine1-bin is not ready for configuration E: hal-info: package hal-info is not ready for configuration On Tue, Feb 3, 2009 at 8:00 AM, rik kroondijk <rikkroond...@gmail.com>wrote: > > dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry <= 4' > failed. > Aborted > > this was what happened after typing dpkg -- configure -a > > thx again > > > On Tue, Feb 3, 2009 at 7:53 AM, rik kroondijk <rikkroond...@gmail.com>wrote: > >> hi Leann, >> >> thanks very much for help >> >> I have all kinds of things going on, the newer kernel did not install >> other updates do not install either >> >> E: libxine1-bin: package libxine1-bin is not ready for configuration >> >> E: hal-info: package hal-info is not ready for configuration >> >> W: GPG error: http://ppa.launchpad.net intrepid Release: The following >> signatures couldn't be verified because the public key is not available: >> NO_PUBKEY 60D11217247D1CFF >> >> thx again >> >> >> >> >> >> On Tue, Feb 3, 2009 at 1:24 AM, Leann Ogasawara < >> leann.ogasaw...@canonical.com> wrote: >> >>> Hi Rik, >>> >>> Is this still an issue with the newer 2.6.27-11.27 kernel? I notice >>> there is a typo in the symlink: >>> >>> ./usr/src/linux-headers-2.6.27-11-generic/incluue/linux >>> >>> "include" is misspelled as "incluue". >>> >>> ** Changed in: linux (Ubuntu) >>> Status: New => Incomplete >>> >>> -- >>> package linux-headers-2.6.27-11-generic 2.6.27-11.26 failed to >>> install/upgrade: error creating symbolic link >>> `./usr/src/linux-headers-2.6.27-11-generic/incluue/linux': No such file or >>> directory >>> https://bugs.launchpad.net/bugs/324144 >>> You received this bug notification because you are a direct subscriber >>> of the bug. >>> >> >> > -- package linux-headers-2.6.27-11-generic 2.6.27-11.26 failed to install/upgrade: error creating symbolic link `./usr/src/linux-headers-2.6.27-11-generic/incluue/linux': No such file or directory https://bugs.launchpad.net/bugs/324144 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
