From: Alexander K. H. <ak...@co...> - 2005-05-26 11:29:41
|
On May 26, 2005, at 4:41 AM, Martin Costabel wrote: > Alexander K. Hansen wrote: > [] >> Clarify that _all_ unstable Tiger updates require "fink reinstall >> fink", >> not just selfupdates from an older version. > > The problem with this is that reinstall does *not work* after a > selfupdate from an older version in 10.3. As has been shown a couple of > times on the lists, what happens is the following: > > - Distribution is 10.3 and fink is at an older version. > - User runs "fink selfupdate" > - New version of fink gets downloaded and installed. At this point, > Distribution is still 10.3, the new fink*.deb gets copied to > /sw/fink/10.3/. At the end of installation, the new fink switches the > Distribution to 10.4-transitional > - User tries "fink reinstall fink". This will fail, because the > fink*.deb corresponding to the installed version is not found since it > is not in /sw/fink/dists (=/sw/fink/10.4-transitional) > > The reinstall not only does not work here, but is also not needed. What > is needed is a second selfupdate. > > I think what would work in most cases (apart from an upgrade from very > old versions of fink) is the sequence > > fink selfupdate > fink rebuild fink > fink selfupdate > > -- > Martin > > > Thanks! I haven't been following this too closely since I haven't adopted Tiger just yet, and based the sequence on a suggestion from somewhere (either IRC or on the lists). -- Alexander K. Hansen Associate Research Scientist, Columbia University visiting MIT Plasma Science and Fusion Center Levitated Dipole Experiment 175 Albany Street, NW17-219 Cambridge, MA 02139-4213 |