Package: apt Version: 0.5.4 Severity: minor If I download a source package, compile it, build a .deb, and install, then run apt-get upgrade, apt decides that the local package is out of date and will download the binary package and install it, overwriting the local work. This happens even if the versions and Debian revisions are the same for the local and downloaded binary packages. I guess this must be happening because the md5sum of the local package doesn't match what apt is expecting, so it thinks that there is something wrong (note that there is no error message, though).
I think that an informative message should be printed in this situation. Also, the behavior should be documented in the apt-get man page or elsewhere (I couldn't find any mention of this anywhere except for some musings on a security page about signing packages in a future security infrastructure). I decided that the actual behavior of the apt-get program is OK, once one realizes what is going on. I'm going to try changing the Debian revision of the local package from 2 to something like 2.1. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux droid 2.2.20 #2 Mon Mar 18 10:44:55 CST 2002 i686 Locale: LANG=C, LC_CTYPE= Versions of packages apt depends on: ii libc6 2.2.5-14 GNU C Library: Shared libraries an ii libstdc++2.10-glibc2.2 1:2.95.4-7 The GNU stdc++ library -- Raj Manandhar ([EMAIL PROTECTED]) (256) 922-1512 x2900
