Dave Vasilevsky wrote:
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.
I am getting this in another situation, even after scanpackages: for
installed packages where no deb is available. I assume these packages
have been installed from the bindist server (some earlier bindist?). I
am observing this here on 10.3.9 and I suspect that the packages
concerned haven't had revision rises for quite a while, so they were
probably installed from a bindist where fink computed the Installed-Size
differently or not at all.
As an example: gnome-libs-1.4.2-19: Within this same version and
revision over more than 18 months, the maintainer has changed, the
BuildDepends list has been changed, and a CompileScript has been added.
In addition, the earlier (installed) version has no Installed-Size
field. I would say apt-get has a point in proposing an update in this
case and the bug is rather that the revision number was never increased.
The other 42 packages that "apt-get dist-upgrade" wants to install on
this machine despite "fink list -o" not listing anything are probably in
a similar state. So in this situation, it is perhaps a good thing to let
apt-get do what it wants.
This variant of the problem will also be less serious on Tiger, because
the Installed-Size is now calculated in a consistent way, so that
differences between successive bindists or even home-made bindists will
concern fewer packages.
There is no guarantee, however, that the calculated Installed-Size will
be the same on different machines for all packages. There are, for
instance, still quite a few packages that write the build directory path
into lib*.la files, so that their size will depend on the precise name
of the build directory. There exist several other examples of such mild
bugs or instabilities that have an influence on the size of binaries or
helper files. So I guess we will have to live with this behavior after
every appearance of a new bindist.
--
Martin
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
