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
HexFiend: update to 2.13.1 #9020
Conversation
Notifying maintainers: |
Travis Build #15045 Passed. Lint results
Port HexFiend success on xcode10.3. Log |
2933c49
to
822f0f1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to add the reference to the Trac ticket to the commit message:
Closes: https://trac.macports.org/ticket/57824
Travis Build #15047 Passed. Lint results
Port HexFiend success on xcode10.3. Log |
822f0f1
to
951aaa0
Compare
Done. |
Travis Build #15048 Passed. Lint results
Port HexFiend success on xcode10.3. Log |
The hexfiend-framework subport seems to fail. However, the Hexfiend port seems to install the Framework in |
I think so. I don't see anything depending on the HexFiend framework package. |
Can you push a change that just drops it? I don't think there's a big point in explicitly marking it as obsoleted either. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this passes CI, I'm merging it.
Travis Build #15051 Passed. Lint results
Port HexFiend success on xcode10.3. Log |
This fails on 10.13 with
I'm assuming the versions below that will also not work. Should we modify the block at the bottom to be The Azure 10.14 build fails with what seems to be a permission problem, but according to https://trac.macports.org/ticket/61392 there are currently some problems with that, so I wouldn't consider that blocking. |
If that's the only error we might be able to patch it to work on 10.13 but unfortunately right now I have no way to test locally. On the latest HEAD they are using more new constants that are not available in older SDKs so this is a kind of an ongoing issue. Unfortunately it looks like upstream is too willing to drop older SDKs and Xcode versions. The binary should still work on 10.12 and above. Would need an update from upstream on what macOS versions they intend to support. |
The build on 10.14 passes for me locally with this patch:
Can you apply that and increase the version filter at the bottom? There may be ways to make HexFiend work on 10.13 and lower, but for now it doesn't, so I'd rather have it fail quickly than waste users' time just to end up with a broken build. |
Description
https://trac.macports.org/ticket/57824
Type(s)
Tested on
macOS 10.15.7 19H2
Xcode 12.1 12A7403
Verification
Have you
port lint
?sudo port test
? n/asudo port -vst install
?