Chrony 2.3 was release on February 16, 2016:
Created attachment 170539 [details]
testbuilds are fine, portlint is fine.
@Kurt I was looking at the history of changes for this port:
and it always says "maintainer timeout" next to the maintainer's email (firstname.lastname@example.org).
Does this mean the maintainer isn't responding?
The domain "club.kyutech.ac.jp" doesn't seem to be registered anymore, so he's not getting any bugzilla notifications.
If so, we probably need a new maintainer. I'll volunteer to take over.
Also, it would be good if we had a script that checked to make sure maintainers are still alive.
For example, we could send them an email with a link they would need to click on once every X months.
The only problem might be, it would be an excellent email for a phishing attack if maintainers get used to just clicking the link without thinking.
(In reply to Yonas Yanfa from comment #3)
> Does this mean the maintainer isn't responding?
> The domain "club.kyutech.ac.jp" doesn't seem to be registered anymore,
There are valid MXes:
club.kyutech.ac.jp mail is handled by 20 sunny.club.kyutech.ac.jp.
club.kyutech.ac.jp mail is handled by 10 lapis.club.kyutech.ac.jp.
> If so, we probably need a new maintainer. I'll volunteer to take over.
If this PR times out, I'll change the maintainer to your address.
Please note that the maintainer has other ports:
which are probably stale, as well.
(In reply to Yonas Yanfa from comment #4)
If software would check commit messages for ports and flag those ports
where the commit message has a sequence of three timeouts, that
would probably be sufficient. No need for keep-alive-mails 8-}
(In reply to Kurt Jaeger from comment #5)
Sounds good. I'd be happy to take over for http_get, http_post, and mod_spdy as well.
For the other ports:
- japanese/spamassassin: I can't test it because I don't know Japanese :)
- net/packter-agent: is... just weird. Probably the world's first 3D anime packet analyzer.
- net/reposado: I cant' test it because I don't have a Mac (donations accepted :P)
(In reply to Kurt Jaeger from comment #6)
Very good idea :) I'll see what I can come up with.
Do I need to scrape web pages, or is there a database/files I can scan?
(In reply to Yonas Yanfa from comment #8)
the svn commit log messages are a potential source, no ?
(In reply to Kurt Jaeger from comment #9)
Yup, that'll work, thanks :)
A commit references this bug:
Date: Sun Jun 5 03:35:27 UTC 2016
New revision: 416385
net/chrony: 2.2 -> 2.3
- submitter becomes maintainer after repeated maintainer timeouts
- Add support for NTP and command response rate limiting
- Add support for dropping root privileges on Mac OS X, FreeBSD, Solaris
- Add require and trust options for source selection
- Enable logchange by default (1 second threshold)
- Set RTC on Mac OS X with rtcsync directive
- Allow binding to NTP port after dropping root privileges on NetBSD
- Drop CAP_NET_BIND_SERVICE capability on Linux when NTP port is disabled
- Resolve names in separate process when seccomp filter is enabled
- Replace old records in client log when memory limit is reached
- Don't reveal local time and synchronisation state in client packets
- Don't keep client sockets open for longer than necessary
- Ignore poll in KoD RATE packets as ntpd doesn't always set it correctly
- Warn when using keys shorter than 80 bits
- Add keygen command to generate random keys easily
- Add serverstats command to report NTP and command packet statistics
- Fix clock correction after making step on Mac OS X
- Fix building on Solaris
Submitted by: Yonas Yanfa <email@example.com)
Approved by: firstname.lastname@example.org (maintainer timeout)