How to get action on a simple fix for dovecot2?

Bill Cole macportsusers-20171215 at
Sat Nov 16 00:31:58 UTC 2019

I fear that I have done something against the etiquette of MacPorts or 
collaborative programming in a broader sense, so PLEASE if anyone has 
suggestions for how I could have done this better and get the last bit 
actually done (by someone who can) speak up.

In August I opened these bugs:

The first includes a simple tested patch to the Portfile to fix a build 
The second is a request for version update to fix a security issue.
These are housekeeping fixes. No coding required.

They both got hijacked into a massive overhaul of dovecot2:

The author of that PR apparently lost interest after a week and while 
his PR got approved, the test build failed. I don't understand why and 
don't have the time to learn whatever I'd need to learn about Travis and 
Github to figure out the problem and offer a fix.

Today I discovered that the update portion has been overtaken by someone 
else making a PR for an update to an even later version than I 
requested. So there's still my one tiny fix to remove a truly pointless 
dependency forest blocked by the abandoned overhaul PR.

I have submitted a new PR to fix the problem with 32-bit builds:

Sorry if I stepped on any toes in the process...

Bill Cole
bill at or billcole at
(AKA @grumpybozo and many * addresses)

More information about the macports-users mailing list