Date: Wed, 03 Mar 2021 11:03:18 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 253979] mail/opendmarc: update to 1.4.0 Message-ID: <bug-253979-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253979 Bug ID: 253979 Summary: mail/opendmarc: update to 1.4.0 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: freebsd@gushi.org There's a new release (after several years) available on GitHub, but there appear to be some quality issues, as several folks have reported broken tes= ts, and unmerged fixes before this release was cut. Notably, the configure.ac = has a "docs" line in it that breaks the build.=20=20 Yes, we can patch for this, but at the same time, it should have been caugh= t. I can take some of the pull requests people are putting out on Github and p= ut them into individual OS patches, but it may be better to work with the upst= ream maintainers to try and fix these in a release tag and get a 1.4.5 or someth= ing like that. The port-mailer didn't notify me that there was a new package because the o= ld port is on SourceForge, and the new one is on GitHub. I've currently got a port skeleton that builds for 1.4.0. I'm the maintain= er.=20 Any feedback on the "best" way to proceed would be appreciated. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-253979-7788>