Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ntfs-3g: update to 2017.3.23 #846

Merged
merged 1 commit into from Oct 2, 2017
Merged

ntfs-3g: update to 2017.3.23 #846

merged 1 commit into from Oct 2, 2017

Conversation

lbschenkel
Copy link
Member

@lbschenkel lbschenkel commented Sep 29, 2017

Description

I upgraded the port to 2017.3.23. The workarounds for mtree violations are no longer necessary.
Closes https://trac.macports.org/ticket/53536

Type(s)
  • security fix
  • enhancement
Tested on

macOS 10.13 17A365
Xcode 9.0 9A235

Verification

Have you

  • checked your Portfile with port lint?
  • tried a full install with sudo port -vst install?

@lbschenkel
Copy link
Member Author

I forgot to check the "security" checkbox when I submitted, now I don't know how to tell the bot to add the label.

@@ -1,9 +1,8 @@
# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why removing this line?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ports I maintain usually don't have that blank line. Force of the habit.

@l2dy
Copy link
Member

l2dy commented Oct 1, 2017

Did you test Read/Write NTFS filesystems with this port?

@lbschenkel
Copy link
Member Author

lbschenkel commented Oct 1, 2017

Yes, but just basic sanity checks. I didn't do extensive check of all the tools. There are no downstream patches in this port, so this has the same quality as upstream. I saw an open ticket on Trac and felt like I could contribute — the intent here was to upgrade the latest upstream version and avoid the security vulnerabilities of the current packaged version. I'm just a very occasional user of this port though, so I'm not taking maintainership as I usually do for other orphaned ports that I happen to use more frequently.

@l2dy
Copy link
Member

l2dy commented Oct 1, 2017

@mf2k You used --enable-mount-helper in the patch you submitted on Trac, what was it for?

@lbschenkel
Copy link
Member Author

It was not my patch.

@l2dy
Copy link
Member

l2dy commented Oct 1, 2017

@lbschenkel I know, and I @-ed the author of that patch.

@l2dy
Copy link
Member

l2dy commented Oct 1, 2017

@lbschenkel You should put Closes https://trac.macports.org/ticket/53536 into the commit message or else the ticket won't be automatically closed.

@lbschenkel
Copy link
Member Author

Sorry, overlooked the @. My mistake.

But I can tell it what's for: it also builds a mount helper that allows mounting filesystems directly from the finder. However, that violates mtree because they must be put on /sbin and since the current port does not install it (as far as I'm aware, but I didn't install it to check), I didn't bother to include it. If somebody else wants to take this PR and improve it, I don't mind at all. It was just a low-hanging fruit for me.

Regarding the commit message, I'll amend it.

@lbschenkel
Copy link
Member Author

I forgot to say that due to SIP in recent macOS versions, you can't install anything to /sbin or /usr/sbin without booting into recovery and manually copying the binaries. I wonder how many users actually do it (if you're advanced enough to do that, you probably know how to mount via the command line too). I suggest dealing with the mount helper in a separate PR, and allow users to upgrade to the newer version in the meantime, but that's your call.

@mf2k
Copy link
Contributor

mf2k commented Oct 1, 2017

I honestly don't remember the reason for adding --enable-mount-helper anymore. I think it made sense when I looked into updating it. I may have gotten that from the build documentation, but I can't find where I saw it right now. I might also have gotten it from playing with ./configure --help.

@l2dy l2dy merged commit 0a4fdfc into macports:master Oct 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 participants