On Fri, Jan 24, 2003 at 01:08:44PM +0100, Torsten Schlabach wrote: > I have developed a piece of software and created a .deb package out of > it. I then tried to install my new package onto a system using dpkg. > Unfortunately I discovered that I had a typo in the dependencies of my > new package so it has one dependency it will never be able to resolve > because the misspelled package does not exist. > > Unfortunately apt-get carries this new defective package in its list of > available packages and is resistant to any attempt to make it "forget" > about the faulty package so I can correct and re-install it.
I've never seen that kind of thing happen. However, does 'dpkg --forget-old-unavail' help? > Attempts like dpkg -P or apt-get remove will try to de-install the > package but just report it was not installed. (Which is correct as it > could not be installed because of the defective dependency.) But even > starting dpkg -install with a corrected .deb file failes as it obviously > goes to the package cache, looks up the old, wrong dependency and then > again tells me it cannot install the package because of unmet > dependencies. That's *very* strange, and doesn't match my understanding and experience of dpkg at all. If the above doesn't help, please show the exact error messages. Cheers, -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
