Fwd: FreeBSD ports you maintain which are out of date

[Matthew Seaman]

On 16/03/2019 21:08, Alfred Perlstein wrote:
> How do I stop these emails?
> 
> I just retired my commit bit and stopped committing to ports after some
> folks yelled at me for committing to ports without signoff even though I
> was doing ports before the src/ports split.
> 
> thanks,
> 
> -Alfred
> 
> 
> 
> -------- Forwarded Message --------
> Subject:     FreeBSD ports you maintain which are out of date
> Date:     Thu, 14 Mar 2019 11:27:00 +0000
> From:     portscout at FreeBSD.org
> To:     alfred at freebsd.org
> 
> 
> 
> Dear port maintainer,
> 
> The portscout new distfile checker has detected that one or more of your
> ports appears to be out of date. Please take the opportunity to check
> each of the ports listed below, and if possible and appropriate,
> submit/commit an update. If any ports have already been updated, you can
> safely ignore the entry.
> 
> You will not be e-mailed again for any of the port/version combinations
> below.
> 
> Full details can be found at the following URL:
> http://portscout.freebsd.org/alfred@freebsd.org.html
> 
> 
> Port | Current version | New version
> ------------------------------------------------+-----------------+------------
> 
> www/py-djangorestframework-filters | 0.10.2 | 0.11.0
> ------------------------------------------------+-----------------+------------
> 
> 
> 
> If any of the above results are invalid, please check the following page
> for details on how to improve portscout's detection and selection of
> distfiles on a per-port basis:
> 
> http://portscout.freebsd.org/info/portscout-portconfig.txt
> 
> Thanks.
> 
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"


Even though you've given up your ports bit, you are still listed as the
maintainer for this port.  There's no requirement for port maintainers
to also be ports committers, although becoming the first is frequently a
step towards becoming the second.

So the distfile checker will poke at you when it thinks there's a
possible update available.

You have three options:

  1) Update the port, and submit a PR via bugzilla or raise a review on
     phabricator.  Either you should get approval from a ports committer
     to commit the update or a ports committer will commit it for you.

  2) If portscout is generating bogus reports, and this is in fact not a
     viable update you could commit, then try setting the PORTSCOUT
     variable as described here:


https://www.freebsd.org/doc/en/books/porters-handbook/makefile-portscout.html

     The have the change committed as above.

  3) Resign as the port maintainer.  Just send an e-mail to
     freebsd-ports at freebsd.org listing the ports you'ld like returned
     to the pool.

	Cheers,

	Matthew

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20190317/fff6d07f/attachment.sig>