On a related note, I cannot make sense of an oddity I discovered in
fink binary distribution management.
I've got an intel-based imac and a macbook pro running the latest
tiger+xcode+finkcryptounstable (and using the very same fink mirrors)
lists of binary packages available for install in the two systems appear
to be different, with more up-to-date packages available on the imac
than on the macbook pro. The available source packages are invariably
the same, though. Any clue why this could be!?
Examples of little differences follow
scilab has got NO binary on the macbook pro but has got 4.1.1001 binary
on the imac, both have got 4.1.2-1002 source, octave has got 2.9.12-4
binary on the imac but none on the macbook pro, and so on
Cheers - Mattia
Martin Costabel wrote:
> Steffen Schmidt wrote:
>> thanks for the hint - now at least I see that all packages prior to
>> the latest one are found on the binary distro server. That's really
>> weird - I tried fink selfupdate on the client several times plus fink
>> scanpackages on the server - still the latest packages are not available.
>> Hmm, it looks like Packages.gz in e.g. unstable/main/binary-darwin- i386
>> hasn't been changed since mid December - there are a lot of
>> Packages.gz.something though but none of them contain the new package
> Run "sudo apt-get update" on the client.
> This used to be run by "fink selfupdate" automatically, but it isn't any
> more on 10.5.
> I am pitching this to fink-core, because it is a bug in the latest fink
> for 10.5. On 10.4, the latest fink-0.27.10-31 still runs apt-get update
> after fink selfupdate, on 10.5 fink-0.27.10-42 doesn't.