On 12/4/19 10:30 PM, Moritz Mühlenhoff wrote: > On Sat, Aug 24, 2019 at 02:07:26AM -0400, Scott Kitterman wrote: >> On Mon, 15 Apr 2019 09:01:29 -0400 Scott Kitterman <deb...@kitterman.com> >> wrote: >>> Package: src:tumgreyspf >>> Version: 1.36-4.1 >>> Severity: important >>> >>> Python2.7 will go out of upstream security support during the Bullseye >>> development cycle. It is not safe to assume it will be included in the >>> next release, so if you want to be sure tumgreyspf can stay in Debian, >> please >>> port it to python3. >>> >>> Alternately, it's close to 8 years without a new release and there are >>> certainly alternatives for SPF checking and greylisting. Removal might be >> in >>> order. >>> >>> Personally, I want to remove some packages I maintain, particularly python- >>> ipaddr, which tumgreyspf depends on (indirectly via python-spf - which I >> will >>> change to python3 only) during the Bullseye cycle, regardless of what >>> happens to python2.7, so please update (python3 includes the ipaddress >> module, >>> which was developed from ipaddr, in the standard library). >> >> Bumping to serious since python2 removals are going on in earnest and this >> will need to be ported or removed soon. > > Thomas, > tumgreyspf seems dead upstream, the last commit on Github is from April 2015, > should we remove it from the archive? > > Cheers, > Moritz
Hi, This is a small codebase, which I am able to maintain by myself. I started the porting to Python 3 already locally. In the mean time, it's very much OK to remove the package from testing (which will be done with autoremove anyway). I'll get in touch with upstream to see if I can take over the maintenance of the code and become upstream. Cheers, Thomas Goirand (zigo)
