#14435 closed defect (fixed)
ntfs-3g 1.1120 fetch fails; 1.2310 is available
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | kballard (Lily Ballard) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.6.0 |
Keywords: | Cc: | im.not.using.any.numbers@…, Russell.Stringer.Bell.RIP@… | |
Port: |
Description
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.
Attachments (1)
Change History (7)
comment:1 Changed 17 years ago by avsmith@…
comment:2 follow-up: 3 Changed 17 years ago by Russell.Stringer.Bell.RIP@…
Replying to ryandesign@macports.org:
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)?
comment:3 Changed 17 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | Russell.Stringer.Bell.RIP@… added |
---|---|
Summary: | ntfs-3g 1.1120 fetch fails; 1.2216 is available → ntfs-3g 1.1120 fetch fails; 1.2310 is available |
Replying to Russell.Stringer.Bell.RIP@gmail.com:
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?
Nothing is in a corrupt/inconsistent state. Feel free to install any port. Of course, any port that depends on ntfs-3g will not complete because of the unsatisfied dependency.
2) Does fixing the error simply require "port edit" the ntfs-3g portfile to point to the latest source package, checksums, etc.?
Yes, if the build process has not changed between 1.1120 and 1.2310. If the ntfs-3g build process has changed, then the portfile will have to be adapted to the new ntfs-3g build process.
It seems that the software is supposed to install a symlink ${prefix}/sbin/mount.ntfs-3g
which points to ${prefix}/bin/ntfs-3g
, and also a manpage ${prefix}/share/man/man8/mount.ntfs-3g
. But with 1.2310, none of these are being installed. That seems like a problem.
3) Is the port process supposed to return exit-status 0 after an error like this (is that the intended/desired behavior)?
I would expect a nonzero exit status after such an error. I see that this is not the case. This should be filed as a separate bug, if one is not already filed.
Changed 17 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | Portfile.diff added |
---|
incomplete patch to upgrade to 1.2310
comment:5 Changed 17 years ago by kballard (Lily Ballard)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Bumped to v1.2412 in r36277
I can't get 1.2216 to compile now. Fails with an error of:
Some sort of installation error, since I think it compiled fine.