Tag Archives: rsync

New new hosting outage

You may have noticed that http://www.finkproject.org is unavailable again.  We regret the inconvenience, believe me.

As before, this also affects distribution of updated package descriptions via the rsync mirrors.  The following two workarounds are available:

  1. Use fink selfupdate-cvs to switch to CVS updating, since CVS service is not affected.
  2. Use a different rsync mirror.  The following mirrors update directly from CVS and are not affected by the outage:
    rsync://ber.de.eu.finkmirrors.net/finkinfo/
    rsync://hnd.jp.asi.finkmirrors.net/finkinfo/
    The easiest option to change this is to edit /sw/etc/fink.conf as a super user (e.g. by using sudo nano /sw/etc/fink.conf) and change the Mirror-rsync line directly.

The disruption also affects the mirroring of package sources.  The following two workarounds are suggested:

  1. Use fink configure --mirror and select option 2 at the first prompt, then go through and just hit return to leave everything else unchanged.  This will have fink try to download from the original source first.
  2. Use a different master mirror.  The following mirrors  are not affected by the outage:
    http://distfiles.ber.de.eu.finkmirrors.net/
    http://distfiles.hnd.jp.asi.finkmirrors.net/
    The easiest option to change this is to edit /sw/etc/fink.conf as a super user (e.g. by using sudo nano /sw/etc/fink.conf) and change the Mirror-master line directly.

http://fink.thetis.ig42.org (also redirected from fink.sourceforge.net) has current content, but doesn’t have the package database or RSS feed.

Check back here for updates.

New hosting outage

You may have noticed that http://www.finkproject.org is unavailable again.  We regret the inconvenience, believe me.

As before, this also affects distribution of updated package descriptions via the rsync mirrors.  The following two workarounds are available:

  1. Use fink selfupdate-cvs to switch to CVS updating, since CVS service is not affected.
  2. Use a different rsync mirror.  The following mirrors update directly from CVS and are not affected by the outage:
    rsync://ber.de.eu.finkmirrors.net/finkinfo/
    rsync://hnd.jp.asi.finkmirrors.net/finkinfo/
    The easiest option to change this is to edit /sw/etc/fink.conf as a super user (e.g. by using sudo nano /sw/etc/fink.conf) and change the Mirror-rsync line directly.

The disruption also affects the mirroring of package sources.  The following two workarounds are suggested:

  1. Use fink configure --mirror and select option 2 at the first prompt, then go through and just hit return to leave everything else unchanged.  This will have fink try to download from the original source first.
  2. Use a different master mirror.  The following mirrors  are not affected by the outage:
    http://distfiles.ber.de.eu.finkmirrors.net/
    http://distfiles.hnd.jp.asi.finkmirrors.net/
    The easiest option to change this is to edit /sw/etc/fink.conf as a super user (e.g. by using sudo nano /sw/etc/fink.conf) and change the Mirror-master line directly.

The online documentation is still available through the Sourceforge CVS browser.   

Check back here for updates.

New hosting outage

You may have noticed that http://www.finkproject.org is unavailable again.  We regret the inconvenience, believe me.

As before, this also affects distribution of updated package descriptions via the rsync mirrors.  The following two workarounds are available:

  1. Use fink selfupdate-cvs to switch to CVS updating, since CVS service is not affected.
  2. Use a different rsync mirror.  The following mirrors update directly from CVS and are not affected by the outage:
    rsync://ber.de.eu.finkmirrors.net/finkinfo/
    rsync://hnd.jp.asi.finkmirrors.net/finkinfo/
    The easiest option to change this is to edit /sw/etc/fink.conf as a super user (e.g. by using sudo nano /sw/etc/fink.conf) and change the Mirror-rsync line directly.

The disruption also affects the mirroring of package sources.  The following two workarounds are suggested:

  1. Use fink configure --mirror and select option 2 at the first prompt, then go through and just hit return to leave everything else unchanged.  This will have fink try to download from the original source first.
  2. Use a different master mirror.  The following mirrors  are not affected by the outage:
    http://distfiles.ber.de.eu.finkmirrors.net/
    http://distfiles.hnd.jp.asi.finkmirrors.net/
    The easiest option to change this is to edit /sw/etc/fink.conf as a super user (e.g. by using sudo nano /sw/etc/fink.conf) and change the Mirror-master line directly.

The online documentation is still available through the Sourceforge CVS browser.   

Check back here for updates.

Hosting outage

You may have noticed that http://www.finkproject.org is unavailable.  The hosting provider at xs4all, where the machine is located, has been notified.  We regret the inconvenience.

In addition to web services, this also affects distribution of updated package descriptions via the rsync mirrors.  The following two workarounds are available:

  1. Use fink selfupdate-cvs to switch to CVS updating, since CVS service is not affected.
  2. Use a different rsync mirror.  The following mirrors update directly from CVS and are not affected by the outage:
    rsync://ber.de.eu.finkmirrors.net/finkinfo/
    rsync://hnd.jp.asi.finkmirrors.net/finkinfo/
    The easiest option to change this is to edit /sw/etc/fink.conf as a super user (e.g. by using sudo nano /sw/etc/fink.conf) and change the Mirror-rsync line directly.

The disruption also affects the mirroring of package sources.  The following two workarounds are suggested:

  1. Use fink configure --mirror and select option 2 at the first prompt, then go through and just hit return to leave everything else unchanged.  This will have fink try to download from the original source first.
  2. Use a different master mirror.  The following mirrors  are not affected by the outage:
    http://distfiles.ber.de.eu.finkmirrors.net/
    http://distfiles.hnd.jp.asi.finkmirrors.net/
    The easiest option to change this is to edit /sw/etc/fink.conf as a super user (e.g. by using sudo nano /sw/etc/fink.conf) and change the Mirror-master line directly. 

Check back here for updates.

Selfupdate methods: point, rsync, cvs

In Fink parlance, a distribution is a set of available packages which depends, amongst other things, on the trees defined in /sw/etc/fink.conf (local, stable, unstable) and the selfupdate method (point, rsync, cvs).

Fink defaults to the point selfupdate method in a brand new installation. The point distribution is the set of packages available when Fink last released a binary distribution. As these releases are not frequent, having a point distribution usually implies having outdated packages.

There are two alternative selfupdate methods that provide the latest packages: rsync and cvs. In the former method, fink selfupdate uses the rsync command to download packages descriptions from one of the rsync mirrors; in the latter, cvs is used to download package descriptions from SourceForge.net.

Choosing a selfupdate method

You should consider the following when choosing a selfupdate method:

  • whenever possible, use either rsync or cvs. They’ll get you up-to-date packages;
  • up-to-date packages are probably not available as official binaries. You’ll need to install Xcode to compile packages from source. You might want to check some unofficial binary distributions;
  • rsync is faster than cvs;
  • when a maintainer releases a new package it is readily available in the cvs distribution. In normal operation, new packages should reach the rsync mirrors in one hour at the latest;
  • firewalls might block rsync or cvs.

Note that when you switch from point to rsync/cvs your next selfupdate will take a while. Subsequent selfupdates should be significantly faster.

In order to switch to rsync, run

fink selfupdate-rsync

Or, if you want to use cvs, run

fink selfupdate-cvs

You can’t go back to the point distribution once you’ve switched to rsync/cvs.

After having changed the selfupdate method, run

fink update-all

to update your packages to their latest versions.

You only need to run selfupdate-rsync or selfupdate-cvs once. Fink remembers your choice and is going to use it in subsequent selfupdates.

Some Fink versions have a minor glitch that shows up when changing the selfupdate method. Please read this FAQ section.

Identifying which selfupdate method Fink is using

There are two ways to check what selfupdate method is being used in your Fink installation. If you run

fink –version | grep Distribution

and it shows something like

Distribution version: 0.9.0.2 architecture (e.g. i386)

then Fink is using the point distribution. If either rsync or cvs is being used, then the command above outputs

Distribution version: selfupdate-cvs (or -rsync), timestamp of last update, OS X version, architecture.

The other possibility is to check the SelfUpdateMethod entry in /sw/etc/fink.conf.

Distribution version: 0.9.0.2 i386