[ 01:45 Yasuhiro Kimura (yasu)  ]

• f32e5a0b505a1a398b34fc86578c827d4a66a531 UPDATING
• f32e5a0b505a1a398b34fc86578c827d4a66a531 mail/py-spf-engine/Makefile
• f32e5a0b505a1a398b34fc86578c827d4a66a531 mail/py-spf-engine/distinfo
• f32e5a0b505a1a398b34fc86578c827d4a66a531 mail/py-spf-engine/files/patch-data_etc_pyspf-milter_pyspf-milter.conf
• f32e5a0b505a1a398b34fc86578c827d4a66a531 mail/py-spf-engine/files/patch-data_share_doc_python-policyd-spf_README.per__user__whitelisting
• f32e5a0b505a1a398b34fc86578c827d4a66a531 mail/py-spf-engine/files/patch-data_share_man_man1_policyd-spf.1
• f32e5a0b505a1a398b34fc86578c827d4a66a531 mail/py-spf-engine/files/patch-data_share_man_man5_policyd-spf.conf.5
• f32e5a0b505a1a398b34fc86578c827d4a66a531 mail/py-spf-engine/files/patch-data_share_man_man5_policyd-spf.peruser.5
• f32e5a0b505a1a398b34fc86578c827d4a66a531 mail/py-spf-engine/files/patch-policyd-spf.1
• f32e5a0b505a1a398b34fc86578c827d4a66a531 mail/py-spf-engine/files/patch-policyd-spf.conf.5

mail/py-spf-engine: Update to 3.0.3

* Since 3.0.0 spf-engine uses flit-core as build backend. So switch to
  use 'USE_PYTHON=pep517'.
* Add entry to UPDATING as default configuration file path of
  pyspf-milter has changed.

ChangeLog:	https://git.launchpad.net/spf-engine/tree/CHANGES?h=3.0.3

[ 13:49 dbaio  ]

• 537162 GIDs
• 537162 UIDs
• 537162 UPDATING
• 537162 mail/Makefile
• 537162 mail/postfix-policyd-spf-python/Makefile
• 537162 mail/py-spf-engine
• 537162 mail/py-spf-engine/Makefile
• 537162 mail/py-spf-engine/distinfo
• 537162 mail/py-spf-engine/files/patch-setup.py
• 537162 mail/py-spf-engine/files/patch-spf__engine_milter__spf.py

Add mail/py-spf-engine, Deprecate mail/postfix-policyd-spf-python

Give time to users to change their env

The new port is the successor, it supports milter feature and its
config file is in another path.

PR:		244424
Submitted by:	Yasuhiro KIMURA <yasu@utahime.org> (maintainer)