FreeBSD ports you maintain which are out of date
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/po...@freebsd.org.html Port| Current version | New version +-+ games/exult | 1.7.0.20210726 | snapshot-v1.7.0.20210728 +-+ net-mgmt/icingaweb2 | 2.8.2 | v2.9.2 +-+ sysutils/google-compute-engine-oslogin | 20191018.00 | 20210728.00 +-+ 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 Reported by:portscout!
Re: New port: math/polymake -- some questions and help needed
On 6/14/21 9:41 PM, Philipp Ost wrote: Hi ports@ I've been working on a port of polymake (polymake.org). Most of the work is done, but there are some questions. Please advise: [...] I appreciate any hints and comments you may have. It's my first port and I hope I didn't miss anything important. ;-) I submitted the port at the end of June: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256861 Apart from koobs@ (CC'd) looking at it two weeks ago, it still awaits some kind committer to take a look at it. Could someone please take a look? Thank you! Philipp
Could a committer please have a look at this dangling pr please?
It's: dns/knot-resolver: the kresd init script won't stop the service at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256221 Thank you in advance for any attention you can give this. --Chris 0xBDE49540.asc Description: application/pgp-keys
OT: Freshports has been unreachable for over 24hrs. Is it just me?
Sorry. I'd have attempted to contact Dan directly. But given I can't reach freshports... My upstream BGP seems to be in order as I have zero trouble with any other destination other than freshports. Here's my experience # traceroute freshports.org traceroute to freshports.org (54.227.255.74), 64 hops max, 40 byte packets ... 6 ae21.cr9-chi1.ip4.gtt.net (141.136.108.245) 79.236 ms 56.609 ms 60.092 ms 7 76.74.1.10 (76.74.1.10) 71.455 ms 69.593 ms 62.251 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 52.93.28.74 (52.93.28.74) 86.625 ms 52.93.28.84 (52.93.28.84) 75.426 ms 52.93.28.82 (52.93.28.82) 86.000 ms 17 * 52.93.28.72 (52.93.28.72) 141.229 ms * 18 * * * 19 * * * 20 * * * 21 * * * 22 ec2-54-227-255-74.compute-1.amazonaws.com (54.227.255.74) 76.154 ms 76.348 ms * ping(8) reveals no difficulties. Yes, I run a firewall. But nothing is set that would block my ability to reach freshports. Thanks! --Chris 0xBDE49540.asc Description: application/pgp-keys
Re: OT: Freshports has been unreachable for over 24hrs. Is it just me?
On 7/29/21 11:15 AM, Chris wrote: Sorry. I'd have attempted to contact Dan directly. But given I can't reach freshports... My upstream BGP seems to be in order as I have zero trouble with any other destination other than freshports. Here's my experience # traceroute freshports.org traceroute to freshports.org (54.227.255.74), 64 hops max, 40 byte packets ... 6 ae21.cr9-chi1.ip4.gtt.net (141.136.108.245) 79.236 ms 56.609 ms 60.092 ms 7 76.74.1.10 (76.74.1.10) 71.455 ms 69.593 ms 62.251 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 52.93.28.74 (52.93.28.74) 86.625 ms 52.93.28.84 (52.93.28.84) 75.426 ms 52.93.28.82 (52.93.28.82) 86.000 ms 17 * 52.93.28.72 (52.93.28.72) 141.229 ms * 18 * * * 19 * * * 20 * * * 21 * * * 22 ec2-54-227-255-74.compute-1.amazonaws.com (54.227.255.74) 76.154 ms 76.348 ms * ping(8) reveals no difficulties. Yes, I run a firewall. But nothing is set that would block my ability to reach freshports. Dan mentioned yesterday that they were getting DDoS'd: https://twitter.com/DLangille/status/1420554141022097412 But I can verify it is loading as expected on my end as of today. hope this helps with your debugging. -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA
Re: OT: Freshports has been unreachable for over 24hrs. Is it just me?
On 2021-07-29 11:34, Pete Wright via ports wrote: On 7/29/21 11:15 AM, Chris wrote: Sorry. I'd have attempted to contact Dan directly. But given I can't reach freshports... My upstream BGP seems to be in order as I have zero trouble with any other destination other than freshports. Here's my experience # traceroute freshports.org traceroute to freshports.org (54.227.255.74), 64 hops max, 40 byte packets ... 6 ae21.cr9-chi1.ip4.gtt.net (141.136.108.245) 79.236 ms 56.609 ms 60.092 ms 7 76.74.1.10 (76.74.1.10) 71.455 ms 69.593 ms 62.251 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 52.93.28.74 (52.93.28.74) 86.625 ms 52.93.28.84 (52.93.28.84) 75.426 ms 52.93.28.82 (52.93.28.82) 86.000 ms 17 * 52.93.28.72 (52.93.28.72) 141.229 ms * 18 * * * 19 * * * 20 * * * 21 * * * 22 ec2-54-227-255-74.compute-1.amazonaws.com (54.227.255.74) 76.154 ms 76.348 ms * ping(8) reveals no difficulties. Yes, I run a firewall. But nothing is set that would block my ability to reach freshports. Dan mentioned yesterday that they were getting DDoS'd: https://twitter.com/DLangille/status/1420554141022097412 Ahh.. that gets it. I kept getting "server timeout/busy" messages from his web server just before the "blackout". Thank you, and everyone else that took the time to respond. --Chris But I can verify it is loading as expected on my end as of today. hope this helps with your debugging. -pete 0xBDE49540.asc Description: application/pgp-keys
OpenSSL 3.0.0 on i386 failing to build
Hi all, The OpenSSL 3.0.0 port (currently beta2) is failing on i386 due to missing atomic on i386 ld: error: undefined symbol: __atomic_is_lock_free Poudriere logs on vanilla FreeBSD https://brnrd.eu/poudriere/data/114i386-git/2021-07-29_17h04m18s/logs/errors/openssl-devel-3.0.0.b2.log https://brnrd.eu/poudriere/data/122i386-git/2021-07-29_17h04m18s/logs/errors/openssl-devel-3.0.0.b2.log This is apparently the last Release Candidate for OpenSSL 3.0.0. Would appreciate anyone to help fix this, preferably without requiring GCC. With kindest regards, Bernard Spil Maintainer of OpenSSL and LibreSSL ports.
