On Fri, Aug 25, 2006 at 09:53:25AM -0400, Anthony DeRobertis wrote: > Jason Tan Boon Teck wrote: > > > ># apt-get install postgresql-8.1 > >Reading Package Lists... Done > >Building Depencency Tree... Done > >Sorry, postgresql-8.1 is already the newest version. > >You might want to run `apt-get -f install' to correct these: > >Sorry, but the following packages have unmet dependencies: > > postgresql-8.1: Depends: postgresql-common (>= 39) but it is not > >going to be installed. > >E: Unmet dependencies. Try 'apt-get -f install' with no packages (or > >specify a solution). > > Add postgresql-common to your apt preferences file, or try: > > apt-get -t sarge-backports install postgresql-8.1 > > > > >How do I troubleshoot this? > > > >preferences content: > >Package: * > >Pin: release a=stable > >Pin-Priority: 700 > > > >Package: * > >Pin: release a=sarge-backports > >Pin-Priority: 999 > > You don't want to do that. Backports should not be pinned higher than > stable! That is why I like aptitude. It alerts you when an intended installation or removal will result in a broken package. Then you can go look at the one that will cause the breakage, as is the case with postgresql-common in this instance, and then install any particular available version. This allows you to leave backports pinned to a low priority and still get updates for any package that you specifically pull in from backports. Regards, -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto
Attachment:
signature.asc
Description: Digital signature