We do have a current backup online at http://fink.thetis.ig42.org/ .

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 also still available through the Sourceforge CVS browser.   

Check back here for updates.

Reblogged from akh's Fink Blog:

1. In a terminal window, run

   fink scanpackages ; sudo apt-get update

   to bring your local package list up to date.

2. Verify what binary versions (locally built or otherwise) are known by using apt-cache policy, for example:

   $ apt-cache policy gmp5
   gmp5:
     Installed: 5.1.0-1
     Candidate: 5.1.0-1
     Version Table:
    *** 5.1.0-1 0
           100 /sw/var/lib/dpkg/status
        5.0.5-4 0
           500 file: stable/main Packages

   In this case, version 5.0.5-4 is present.

3. If an older version of the package is available, then you can install that. For example, for gmp5, we’d want to downgrade the library packages as well as the main (headers):

   $ sudo apt-get install gmp5=5.0.5-4 gmp5-shlibs=5.0.5-4 
   libgmpxx5-shlibs=5.0.5-4
   Reading Package Lists... Done
   Building Dependency Tree... Done
   The following packages will be DOWNGRADED
   gmp5 gmp5-shlibs libgmpxx5-shlibs
   0 packages upgraded, 0 newly installed, 3 downgraded,
   0 to remove and 9 not upgraded.
   Need to get 0B/1282kB of archives. After unpacking 
   336kB will be freed.
   Do you want to continue? [Y/n]

   Note that when using apt-get the versioned package format is

   package=version-revision

4. If, on the other hand, you only show one version as available, you can download an earlier version of the package description files from the CVS browser.  To help you figure out where to browse, you can use fink dumpinfo -finfofile to show the section where the package you are interested in resides.  For example:

   $ fink dumpinfo -finfofile gmp5
   Information about 6665 packages read in 2 seconds.
   infofile: /sw/fink/dists/stable/main/finkinfo/libs/gmp5.info

5.  Navigate to the appropriate location in the CVS browser.  If you are on 10.5 or 10.6, first go to the 10.4 directory, and  if you are on 10.7 or 10.8, then start in the 10.7 directory.  Then follow the path from item 4 above, e.g. stable/main/finkinfo/libs for gmp5.
6. Pick an appropriate version of the .info file via the browser, i.e. check the Version field, and download it by viewing it with the Download option and saving the text file (make sure to leave the extension as .info).  For example, one can see the various iterations of gmp5.info in the 10.7 tree here.
7. Move the .info file to /sw/fink/dists/local/main/finkinfo. If the package has a .patch file, then depending on whether that was updated after the .info file you downloaded, you will want either to download an appropriate version of from the CVS browser, or copy it from your stable/main/finkinfo directory if it’s new enough. Following the example of gmp5, to install version 5.0.5-4 from source, you would download the .info file and the current .patch file, which still applies, then use e.g.

   mv ~/Downloads/gmp5.* /sw/fink/dists/local/main/finkinfo

   to put the files in your local tree.

8. Use “fink dumpinfo -fallversions” to verify that the version you just moved into your local tree is available. Using gmp5 as the example again, we verify that gmp5-5.0.5-4 is among the known versions:

   $ fink dumpinfo -fallversions gmp5
   Scanning package description files..........
   Information about 6665 packages read in 1 seconds.
   allversions:
   5.0.5-4
   bi 5.1.0-1

9. Downgrade by using “fink install” including the package versions.  Again using gmp5 for the example:

   fink install gmp5-5.0.5-4 gmp5-shlibs-5.0.5-4
   libgmpxx5-5.0.5-4

   Note that when using a fink command, the versioned package format is

   package-version-revision

10. Build anything that needs the older version.  A word of caution: you stand the risk of having link failures in other packages when you downgrade to a library with an older compatibility version.

finkproject.org is still up, but updates will be posted here rather than there since the website source resides in our SourceForge CVS repository, too.

• If you’re using selfupdate-cvs, that won’t work
• selfupdate-rsync will still work, but until sf.net cvs is back online there won’t be any new packages.
• Developers can’t commit packages currently, so users aren’t actually missing out on much.
• The mailing lists and bug tracker are out, so please post bug reports for unmaintained packages here.  If a package has a listed maintainer, contact them, and then post here in a few days (1) if you haven’t gotten a response in a few days, and (2) if the mailing lists aren’t back up.

https://twitter.com/sfnet_ops .

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.

https://twitter.com/sfnet_ops

https://sourceforge.net/blog/various-sourceforge-services-down/

Hopefully it will be fixed soon.  The best recommendation at this point is to apply  workaround #2 from http://finkers.wordpress.com/2012/10/05/hosting-outage/.

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.