[MacPorts] #14435: ntfs-3g 1.1120 fetch fails; 1.2216 is available

[MacPorts]

#14435: ntfs-3g 1.1120 fetch fails; 1.2216 is available
--------------------------------------+-------------------------------------
  Reporter:  ryandesign at macports.org  |       Owner:  eridius at macports.org
      Type:  defect                   |      Status:  new                 
  Priority:  Normal                   |   Milestone:  Port Bugs           
 Component:  ports                    |     Version:  1.6.0               
Resolution:                           |    Keywords:                      
--------------------------------------+-------------------------------------
Comment (by Russell.Stringer.Bell.RIP at gmail.com):

 Replying to [ticket:14435 ryandesign at macports.org]:
 > [http://lists.macosforge.org/pipermail/macports-
 users/2008-February/009119.html Ludwig reported] on macports-users, and I
 can confirm, that the ntfs-3g portfile 1.1120 does not fetch.
 >
 > {{{
 > $ sudo port fetch ntfs-3g
 > Password:
 > --->  Fetching ntfs-3g
 > --->  Attempting to fetch ntfs-3g-1.1120.tgz from http://www.ntfs-
 3g.org/
 > --->  Attempting to fetch ntfs-3g-1.1120.tgz from
 http://svn.macports.org/repository/macports/distfiles/ntfs-3g
 > --->  Attempting to fetch ntfs-3g-1.1120.tgz from
 http://svn.macports.org/repository/macports/distfiles/general/
 > --->  Attempting to fetch ntfs-3g-1.1120.tgz from
 http://svn.macports.org/repository/macports/downloads/ntfs-3g
 > Error: Target org.macports.fetch returned: fetch failed
 > Error: Status 1 encountered during processing.
 > $
 > }}}
 >
 > A newer version 1.2216 is available. Maybe the port should be updated to
 that version.


 This bug in the ntfs-3g portfile seems to be still unfixed.  According to
 ntfs-3g.org:
 "The latest stable version is 1.2310, released on March 10, 2008."

 1) After this "port install" fails due to fetch error, is it ok to proceed
 to "port install" another port?  Or must the error be fixed first,
 otherwise MacPorts stays in a corrupt/inconsistent state?

 2) Does fixing the error simply require "port edit" the ntfs-3g portfile
 to point to the latest source package, checksums, etc.?

 3) Is the port process supposed to return exit-status 0 after an error
 like this (is that the intended/desired behavior)?

-- 
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14435#comment:2>
MacPorts </projects/macports>
Ports system for Mac OS