The spamcontrol patch is applied through a script, install_spamcontrol.sh. This
script does not return a non-zero status when patch failures are encountered.
So I missed many failures when updating this port.
To fix this, move the spamcontrol patch application to pre-patch so that the
PATCHFILES->DISTFILES (and manual patch application with PATCH) is not needed
for most patches. This ensures that the spamcontrol patch is always applied
before PATCHFILES. Some PATCHFILES were applying before the spamcontrol patch
causing it to fail to patch properly.
Bump revision as the build had been fine but some files were not being
generated in the package.
Also add my mirror as distcache does not have the updated patches yet.
Reported by: Oleg Strizhak
MFH: 2014Q3
Unstaged ports are being reset today. I'll grab this one from the batch
in order to set the expiration date to match the other unmaintained
interactive ports. The port should be converted to a regular port as
well as providing stage support in order to undeprecate it.
Approved by: portmgr (implicit)
The maintainer is not reachable via email although messages don't bounce.
The current and previous PR have both timed out. Reset the maintainer and
set deprecation date for 20 August, the same the other unmaintained
interactive ports. The port is already staged, but a new maintainer
should convert this interactive port to a regular one in order to
undeprecate it.
PR: 191219
While I'm here:
- Reassign maintainership
- Use @fontsdir instead of custom code
- Do not run mkfontdir/mkfontscale while building the package
- Remove mkfontdir/mkfontscale from build depends
PR: 191568
Submitted by: lgfbsd@be-well.ilk.org
Unstaged ports are being reset today. I'll grab this one from the batch
in order to set the expiration date to match the other unmaintained
interactive ports. The port should be converted to a regular port as
well as providing stage support in order to undeprecate it. The listed
maintainer has been non-responsive for almost two weeks as well.
PR: 191212
Approved by: portmgr (implicit)
This port was going to be reset in a couple of days anyway due to lack
of maintainer response, but I moved the timeline up since unstaged ports
started being reset today. Now that it's unmaintained and interactive,
the same expiration date of the other unmaintained interactive port has
been applied.
PR: 191215
Approved by: portmgr (implicit)