On Aug 5, 2005, at 12:05 AM, Dave Vasilevsky wrote:
Perhaps apt only gets confused if it doesn't see the .deb on your disk at all, for example if you haven't run scanpackages in a while? That would explain why I don't see this error much anymore
Ok, I did some testing and my hunch was right. The bug of apt-get downloading and 'upgrading' to same version as you already have occurs only if: You have a package installed from a .deb you built with Fink, AND that same version/revision is available in the bindist, AND you haven't done a scanpackages lately so apt doesn't know about the .deb on your hard drive.
The good news is that Fink 0.25.x will include much better support for apt. It has support for using apt-ftparchive (if that package is installed) for 'fink scanpackages'. This is *much* faster than the current system, making it actually practical to run scanpackages. So Fink 0.25.x will also include a 'AutoScanpackages' option in fink.conf, which will automatically do a scanpackages/'apt-get update' every time it finishes building some new packages. :-)
Another solution is to use apt "pinning" to tell apt that you prefer installed packages to those available from the bindist. See 'man apt_preferences' for details. Installed packages have a priority of 100, so the following /sw/etc/apt/preferences works for me:
Package: * Pin: release o=Fink Pin-Priority: 99I'm not sure if pinning would have any negative side effects though, someone more familiar with Debian would know more.
We'll have to discuss whether we want one or both of these to become the default, so the bug can go away.
Dave
PGP.sig
Description: This is a digitally signed message part
