Re: Fwd: FreeBSD ports you maintain which are out of date
On Sun, Mar 17, 2019 at 10:48:12AM +, Dima Pasechnik wrote: > > I just got an email from portscout about > www/squidclamav/ port. Indeed, it has no maintainer: > https://www.freshports.org/www/squidclamav/ > > but the point of this email is a total mystery, probably just an > error, no? I never touched this port, for sure... > > I think it's OK if once upon a time an email listing all the > un-maintained ports is sent around, > but otherwise it's merely spam. > You're subscribed to po...@freebsd.org mailing list, so you also receive portscout's mails to this address. Unmaintained ports have it as MAINTAINER address. Portscout only sents out a single mail when it finds a new upstream version, so it's no spam. Many ports unmaintained ports have received updates and some even got a new maintainer because of portscount's mails to this mailing list. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Fwd: FreeBSD ports you maintain which are out of date
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 + > From: portsc...@freebsd.org > To: alf...@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/alf...@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@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@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@freebsd.org listing the ports you'ld like returned to the pool. Cheers, Matthew signature.asc Description: OpenPGP digital signature
Re: Fwd: FreeBSD ports you maintain which are out of date
On Sun, Mar 17, 2019 at 10:21 AM Lorenzo Salvadore via freebsd-ports wrote: > > On Sunday 17 March 2019 10:48, Lorenzo Salvadore via freebsd-ports > wrote: > > > ‐‐‐ Original Message ‐‐‐ > > On Saturday 16 March 2019 22:08, Alfred Perlstein alf...@freebsd.org 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 + > > > From: portsc...@freebsd.org > > > To: alf...@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/alf...@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. > > > > These e-mails are not send to committers, but to port maintainers. > > Apparently, > > you are py-djangorestframework-filters maintainer: ask to drop > > maintainership > > for your ports (I think you can do it either on this mailing list or on > > bugzilla) > > and you won't receive any e-mail of this kind any more. > > > > Lorenzo Salvadore. > > I forgot to add that e-mails for ports without maintainers are sent to this > mailing list > (I am almost sure, but not completely). I just got an email from portscout about www/squidclamav/ port. Indeed, it has no maintainer: https://www.freshports.org/www/squidclamav/ but the point of this email is a total mystery, probably just an error, no? I never touched this port, for sure... I think it's OK if once upon a time an email listing all the un-maintained ports is sent around, but otherwise it's merely spam. Dima > Thus, to get rid of them, you have to unsubscribe from it. > > Lorenzo Salvadore. > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Fwd: FreeBSD ports you maintain which are out of date
On Sunday 17 March 2019 10:48, Lorenzo Salvadore via freebsd-ports wrote: > ‐‐‐ Original Message ‐‐‐ > On Saturday 16 March 2019 22:08, Alfred Perlstein alf...@freebsd.org 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 + > > From: portsc...@freebsd.org > > To: alf...@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/alf...@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. > > These e-mails are not send to committers, but to port maintainers. Apparently, > you are py-djangorestframework-filters maintainer: ask to drop maintainership > for your ports (I think you can do it either on this mailing list or on > bugzilla) > and you won't receive any e-mail of this kind any more. > > Lorenzo Salvadore. I forgot to add that e-mails for ports without maintainers are sent to this mailing list (I am almost sure, but not completely). Thus, to get rid of them, you have to unsubscribe from it. Lorenzo Salvadore. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Fwd: FreeBSD ports you maintain which are out of date
‐‐‐ Original Message ‐‐‐ On Saturday 16 March 2019 22: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 + > From: portsc...@freebsd.org > To: alf...@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/alf...@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. These e-mails are not send to committers, but to port maintainers. Apparently, you are py-djangorestframework-filters maintainer: ask to drop maintainership for your ports (I think you can do it either on this mailing list or on bugzilla) and you won't receive any e-mail of this kind any more. Lorenzo Salvadore. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Fwd: FreeBSD ports you maintain which are out of date
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 + From: portsc...@freebsd.org To: alf...@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/alf...@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@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Fwd: FreeBSD ports you maintain which are out of date
Port| Current version | New version +-+ graphics/geoserver | 2.1.1 | 2.6.0 +-+ www/groupoffice | 3.7.24 | 6.0.27 +-+ I am always a bit annoyed by these severly outdated ports that are constantly sent in portscout mails... Anyone willing to test my patch for www/groupoffice? It builds just fine, but actual functional test would be highly appreciated... The patch is compressed because it was over 200k mailing list limit. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Fwd: FreeBSD ports you maintain which are out of date
I am happy to report that my PR with update and a fix for portscout discarding beta builds as actual updates have been accepted today, so this should not be an issue for a while ;) Regards, BL On Fri, Mar 14, 2014 at 3:48 PM, Philippe Audéoud jada...@freebsd.orgwrote: On Fri, 14 Mar 2014, John Marino wrote: On 3/14/2014 11:47, John Marino wrote: On 3/14/2014 10:30, Philippe Audéoud wrote: On Fri, 14 Mar 2014, John Marino wrote: On 3/14/2014 10:15, portsc...@freebsd.org wrote: Port| Current version | New version +-+ games/doomsday | 1.12.2 | 1.14.0-build1168 +-+ This port squawks constantly. Can we either get the last submitter to take it over or put it on the to-be-killed list? Or tell portscout to ignore it? Too much noise on already high volume channel. John Hello John, games/doomsday is maintained by ports@. Right -- that's why portscout is bombarding the ports@ mail list. If it were maintained we wouldn't see it. games/doomsday is maintained by ports@. Feel free to make it as ignored for portscout. Is this the general understanding? Anytime any committer gets annoyed with high-frequency portscout squawks on ports@ we just disable it without asking? I thought I caught this before it went out. I wanted to suggest that maybe portscout can not send any notice to ports@ by rule if the port is unmaintained. what about that? John It's a good thing we are noticed when ports are outdated for ports@ but I'm fine with your idea to have a remind once a week or a month. Regards, -- Philippe Audéoud ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Fwd: FreeBSD ports you maintain which are out of date
Big Lebowski wrote: I am happy to report that my PR with update and a fix for portscout discarding beta builds as actual updates have been accepted today, so this should not be an issue for a while ;) I think I probably speak for many of us when I say: thanks a fracking lot! AvW -- I'm not completely useless, I can be used as a bad example. pgp9HcQeXaSPj.pgp Description: PGP signature
Fwd: FreeBSD ports you maintain which are out of date
-- Forwarded message -- From: Yanhui Shen shen@gmail.com Date: 2012/12/5 Subject: Re: FreeBSD ports you maintain which are out of date To: portsc...@portscout.freebsd.org Hi, According to this page http://basiccoder.com/openfetion The OpenFetion Project is deprecated, and therefore I do not want to maintain it any more. :-( Actually, there is a 2.2.1 port, but I think the software itself is buggy. The most annonying problem is, it'll be offline when shortmsg arrived. (100%) So, in my opinion what about just remove it from the ports tree? 2012/12/4 portsc...@portscout.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/shen@gmail.com.html Port| Current version | New version +-+ net-im/openfetion | 2.0.7 | 2.2.1 +-+ 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 If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org Thanks. -- Best regards, Yanhui Shen -- Best regards, Yanhui Shen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Fwd: FreeBSD ports you maintain which are out of date
On Wed, Dec 05, 2012 at 01:59:49AM +0800, Yanhui Shen wrote: -- Forwarded message -- From: Yanhui Shen shen@gmail.com Date: 2012/12/5 Subject: Re: FreeBSD ports you maintain which are out of date To: portsc...@portscout.freebsd.org Hi, According to this page http://basiccoder.com/openfetion The OpenFetion Project is deprecated, and therefore I do not want to maintain it any more. :-( Actually, there is a 2.2.1 port, but I think the software itself is buggy. The most annonying problem is, it'll be offline when shortmsg arrived. (100%) So, in my opinion what about just remove it from the ports tree? I will set an expiration date of one month from now and remove the port then. Thanks for bringing this to our attention. -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Fwd: FreeBSD ports you maintain which are out of date
Hi, I finally managed to get portscout back on a stable server. I have removed all mail addresses from the old portscout to cleanup all the unused mail addresses. If you are a maintainer and would like to get a mail notification, please drop me a mail using your maintainer mail address and I'll add to the list. The RSS feature will be back very soon as well. Thanks to Martin Matuska (mm@) for hosting portscout now. Note that portscout.org will be rerouted as soon as possible. As for now, please use http://portscout.cc. - Martin Begin forwarded message: From: m...@freebsd.org Subject: FreeBSD ports you maintain which are out of date Date: July 23, 2011 8:45:17 PM GMT+08:00 To: po...@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.cc/po...@freebsd.org.html Port| Current version | New version +-+ astro/gpsdrive | 2.09| 2.11 +-+ astro/py-astLib | 0.4.0 | 0.17.1 +-+ astro/viking| 1.1 | 1.2.1 +-+ audio/bmp-crossfade | 0.3.12 | 0.3.14 +-+ audio/icecast | 1.3.12 | 2.3.2 +-+ audio/kid3 | 1.5 | 1.6 +-+ audio/libnjb| 2.2.6 | 2.2.7 +-+ audio/lv2core | 3.0 | 4.0 +-+ audio/orpheus | 1.5 | 1.6 +-+ audio/pd| 0.42-6 | 0.43-0 +-+ audio/py-xmms | 2.02| 2.07 +-+ audio/qjackctl | 0.3.7 | 0.3.8 +-+ audio/rio500| 0.7 | 0.8.1 +-+ audio/slv2 | 0.6.1 | 0.6.6 +-+ audio/spiralsynth | 0.1.7 | 2.0.0 +-+ audio/spiralsynthmodular| 0.2.2a | 0.2.2 +-+ biology/rasmol | 2.7.2.1.1 | 2.7.5.2 +-+ cad/atlc| 4.6.0 | 4.6.1 +-+ cad/impact | 0.7.5.3 | 0.7.6.9 +-+ cad/varkon | 1.19D | 1.19C +-+ chinese/qterm | 0.4.1 | 0.5.12 +-+ chinese/scim-chewing| 0.3.3 | 0.3.4 +-+ databases/adstudio | 9.0.13 | 9.0.15 +-+
Re: Fwd: FreeBSD ports you maintain which are out of date
Hello MArtin, please include me on the list. :) Thanks On Sun, Jul 24, 2011 at 02:52:06AM +0800, Martin Wilke wrote: Hi, I finally managed to get portscout back on a stable server. I have removed all mail addresses from the old portscout to cleanup all the unused mail addresses. If you are a maintainer and would like to get a mail notification, please drop me a mail using your maintainer mail address and I'll add to the list. The RSS feature will be back very soon as well. Thanks to Martin Matuska (mm@) for hosting portscout now. Note that portscout.org will be rerouted as soon as possible. As for now, please use http://portscout.cc. - Martin Begin forwarded message: From: m...@freebsd.org Subject: FreeBSD ports you maintain which are out of date Date: July 23, 2011 8:45:17 PM GMT+08:00 To: po...@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.cc/po...@freebsd.org.html Port| Current version | New version +-+ astro/gpsdrive | 2.09| 2.11 +-+ astro/py-astLib | 0.4.0 | 0.17.1 +-+ astro/viking| 1.1 | 1.2.1 +-+ audio/bmp-crossfade | 0.3.12 | 0.3.14 +-+ audio/icecast | 1.3.12 | 2.3.2 +-+ audio/kid3 | 1.5 | 1.6 +-+ audio/libnjb| 2.2.6 | 2.2.7 +-+ audio/lv2core | 3.0 | 4.0 +-+ audio/orpheus | 1.5 | 1.6 +-+ audio/pd| 0.42-6 | 0.43-0 +-+ audio/py-xmms | 2.02| 2.07 +-+ audio/qjackctl | 0.3.7 | 0.3.8 +-+ audio/rio500| 0.7 | 0.8.1 +-+ audio/slv2 | 0.6.1 | 0.6.6 +-+ audio/spiralsynth | 0.1.7 | 2.0.0 +-+ audio/spiralsynthmodular| 0.2.2a | 0.2.2 +-+ biology/rasmol | 2.7.2.1.1 | 2.7.5.2 +-+ cad/atlc| 4.6.0 | 4.6.1 +-+ cad/impact | 0.7.5.3 | 0.7.6.9 +-+ cad/varkon | 1.19D | 1.19C +-+ chinese/qterm | 0.4.1 | 0.5.12 +-+ chinese/scim-chewing| 0.3.3 | 0.3.4
