Skip to content
This repository has been archived by the owner on Jul 4, 2023. It is now read-only.

GNUTLS 3.4.x #46562

Closed
rakkesh opened this issue Dec 2, 2015 · 15 comments
Closed

GNUTLS 3.4.x #46562

rakkesh opened this issue Dec 2, 2015 · 15 comments

Comments

@rakkesh
Copy link
Contributor

rakkesh commented Dec 2, 2015

GnuTLS has a new release, 3.4.7, and 3.4.x is marked as stable. 3.4.x has API/ABI changes from the previous stable releases 3.3.x. So, every formula which is dependent on gnutls needs to be revised.
What is the process of making such an update?

By the way, I have successfully built emacs, wireshark and qemu with gnutls 3.4.7.

@rakkesh
Copy link
Contributor Author

rakkesh commented Dec 2, 2015

Formulae from Homebrew core which depend on GnuTLS

Formula: Dependency type

  • bitlbee: required
  • emacs: optional
  • freediameter: required
  • git-annex: required
  • glib-networking: required
  • gloox: optional
  • gnu-smalltalk: required
  • gst-plugins-bad: optional
  • gwenhywfar: required [failed: build logs - https://gist.github.com/d4c35eb258d81e933a25] [fixed: https://github.com/gwenhywfar: fix build with gnutls 3.4.x #47038]
  • hamsterdb [upscaledb]: required
  • inspircd: optional
  • kbtin: required [failed: build logs - https://gist.github.com/28cf0fe8bebccd5cd3c3]
  • knot: required
  • libav: optional
  • libinfinity: required
  • libsoup: required
  • libvirt: required
  • libxmlsec1: recommended [both openssl and gnutls are :recommended but libxmlsec1 doesn't seem to link with gnutls]
  • loudmouth: required
  • mailutils: required
  • minbif: required
  • ncdc: required
  • net6: required [failed: build logs - https://gist.github.com/4a122c58eb0882c18aef]
  • ntopng: [A new release, v2.2, is available]
  • openconnect: required
  • pianobar: required
  • pianod: required
  • pidgin: required
  • profanity: required
  • qemu: required
  • task: required
  • taskd: required
  • ucommon: required
  • vpnc: required
  • vte3: required
  • weechat: required
  • wireshark: required

Formulae using nettle (excluding gnutls)

  • knot: required
  • lsh: required [failed: build logs - Yosemite, and El Capitan]
  • pike: required
  • rdfind: required
  • rdup: required
  • stoken: required

Note: Check mark indicates the package has been built with gnutls or nettle.

@DomT4
Copy link
Member

DomT4 commented Dec 2, 2015

This could get a bit complicated. To date the new GnuTLS branch has required the new Nettle branch as well, so you'd have to factor in the breaking nettle release as well into the checks here.

@rakkesh
Copy link
Contributor Author

rakkesh commented Dec 3, 2015

Thanks @DomT4. Updated the list.

@rakkesh
Copy link
Contributor Author

rakkesh commented Dec 3, 2015

@DomT4 The check list is complete now.

Bug reports:
lsh: reported bug 1713 on their bugzilla.
net6: gobby/net6#1 [ project on GitHub - no activity since Nov 1, 2011 ]
kbtin: http://sourceforge.net/p/kbtin/bugs/11/ [ reported by @dunn but no progress ]

gwenhywfar: no easy way to report bugs without sending it to a mailing list in Deutsch.

@DomT4
Copy link
Member

DomT4 commented Dec 6, 2015

Thanks for your work here @rakkesh! Appreciate all the checking. I'd be fine with boneyarding net6 given the lack of any commits in 4 years and new build problems, likewise with kbtin for the ignored bug report for 6+ months.

We should try and either backport fixes or wait on lsh since that's still particularly active.

@rakkesh
Copy link
Contributor Author

rakkesh commented Dec 6, 2015

Agreed, net6 and kbtin can be moved to boneyard; what about gwewnhywfar which is used by aqbanking? Should these two formulae be sent to boneyard as well?

When I get time, I'll check on backporting the latest commits to lsh formula.

@DomT4
Copy link
Member

DomT4 commented Dec 6, 2015

what about gwewnhywfar which is used by aqbanking? Should these two formulae be sent to boneyard as well?

Probably not. @UniqMartin may be able to help with reporting things in German, perhaps.

@UniqMartin
Copy link
Contributor

Probably not. @UniqMartin may be able to help with reporting things in German, perhaps.

Regarding gwenhywfar (thanks, copy & paste!): Their mailing list archive is only visible after subscription, so I haven't checked that yet, and their bug tracker looks like a really sad place: Of all the issues created there in the last 12 months, only one was closed and has seen a response from the author. So I wouldn't get my hopes up … But there's probably no harm in creating an issue and linking to the failed build log.

@rakkesh
Copy link
Contributor Author

rakkesh commented Dec 13, 2015

lsh with patch set for nettle3 support builds successfully with nettle3 but not with the existing nettle version 2.7.1. nettle needs to updated before applying the patch set to lsh formula.

@rakkesh
Copy link
Contributor Author

rakkesh commented Dec 15, 2015

@DomT4 How do you suggest we move forward on closing this issue?

@DomT4
Copy link
Member

DomT4 commented Dec 15, 2015

You can always push the lsh change into the same PR as the gnutls and nettle updates, and everything else that needs a revision. Make sure you annotate any patches with "Can be removed on next release" blah. Let me know before you file the PR and I'll kick the timeout in a very upwards direction.

@rakkesh
Copy link
Contributor Author

rakkesh commented Dec 16, 2015

I have made the changes, let me know a time when I can open a PR.
The commits are available here, https://github.com/rakkesh/homebrew/commits/gnutls-3.4.x.

@DomT4
Copy link
Member

DomT4 commented Dec 16, 2015

Bumped the timeout to three hours. File when desired :). Just a wee note that we don't use args blocks unless there are additional opt-in/opt-out arguments to be passed, Thanks!

@rakkesh rakkesh mentioned this issue Dec 16, 2015
@rakkesh
Copy link
Contributor Author

rakkesh commented Dec 16, 2015

Updated the PR as per the above comment. Removed p11-kit from this PR as it fails at make check stage [2 of 27 tests failed]. @dunn has filed a bug report already.

@DomT4
Copy link
Member

DomT4 commented Dec 31, 2015

Closing in favour of the open PR, Thanks!

@DomT4 DomT4 closed this as completed Dec 31, 2015
@Homebrew Homebrew locked and limited conversation to collaborators Jul 10, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants