Repository navigation
nullmailer: pull up bugfix into 2017Q4 #78
Description
Activity
I can confirm, that nullmailer is completely broken without this patch.
Would be happy if this would be pulled in soon :)Ups. Why is this ticket being closed? The commit was for py-polib, not nullmailer.
Stupid GitHub bug where it will match any "hash#number" in any changelog that we push to pkgsrc and apply it to this project, they refuse to change it so we just have to keep going back and re-opening tickets that they've incorrectly auto-closed. To make it even worse, I'm not notified of these auto-closes as I'm the committer, so I'm reliant on others to tell me when it happens :(
Backported into 2017Q4, the rebuilds are syncing now across the http mirrors.
Reacted by jfqd- added a commit that references this issue
on Mar 14, 2018 - added 2 commits that reference this issue
on Mar 31, 2018 - added a commit that references this issue
on Jun 25, 2018 - added a commit that references this issue
on Dec 1, 2018 138 remaining items
- added 11 commits that reference this issue
on May 14, 2026 - added 2 commits that reference this issue
on May 22, 2026 - added a commit that references this issue
on Jun 12, 2026
Metadata
Metadata
Assignees
Labels
No labels
There was an issue in our nullmailer patches which resulted in:
sendmail: Could not exec nullmailer-injectUpstream already had the correct fix (but no new release yet) which I commited in NetBSD@6cdbbda - maybe this can be pulled into the 2017Q4 branch.