Need committer help updating news/nzbhydra2
Hi all, could someone please commit https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267666 — and close obsolete https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262435 while at it. I'm not sure about the process for unresponsive maintainers. Over the years, I've ran into delayed updates and unanswered email with the current maintainer several times. It's perfectly alright to be busy with other things, that's why I'm offering to take over maintainership if all involved agree. Best Marcel
Re: Need committer help updating news/nzbhydra2
Van: Marcel Bischoff Datum: donderdag, 1 december 2022 11:14 Aan: FreeBSD-ports FreeBSD Onderwerp: Need committer help updating news/nzbhydra2 Hi all, could someone please commit https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267666 â and close obsolete https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262435 while at it. I'm not sure about the process for unresponsive maintainers. Over the years, I've ran into delayed updates and unanswered email with the current maintainer several times. It's perfectly alright to be busy with other things, that's why I'm offering to take over maintainership if all involved agree. Best Marcel  Hi Marcel, I will pick up the commit. As I'm a new committer I will need approval from my mentor. Let's see if the maintainer reacts in the meantime. About changing the maintainer I asked portmgr, because I'm not sure if this fits within the policy already. Regards, Ronald. Â
Re: Need committer help updating news/nzbhydra2
> On 1. Dec 2022, at 11:44, Ronald Klop wrote: > > > Van: Marcel Bischoff > Datum: donderdag, 1 december 2022 11:14 > Aan: FreeBSD-ports FreeBSD > Onderwerp: Need committer help updating news/nzbhydra2 > > Hi all, > > could someone please commit > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267666 â and close > obsolete https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262435 while at it. > > I'm not sure about the process for unresponsive maintainers. Over the years, > I've ran into delayed updates and unanswered email with the current > maintainer several times. It's perfectly alright to be busy with other > things, that's why I'm offering to take over maintainership if all involved > agree. > > Best > Marcel > > Â > > > Hi Marcel, > > I will pick up the commit. As I'm a new committer I will need approval from > my mentor. Let's see if the maintainer reacts in the meantime. > About changing the maintainer I asked portmgr, because I'm not sure if this > fits within the policy already. > > Regards, > Ronald. That's great, thanks! Marcel
Unmaintained FreeBSD ports which are out of date
Dear port maintainers, The portscout new distfile checker has detected that one or more unmaintained 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. Please consider also adopting this port. If any ports have already been updated, you can safely ignore the entry. An e-mail will not be sent 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/p5-Games-Dice | 0.045 | 0.046 +-+ textproc/redisearch | 2.2.10 | v2.6.3 +-+ 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!
Trouble building gcc11 on RPi2
While trying to build lang/gcc11 on an PPi2 (armv7) running -current the process keeps stopping with: ===> Configuring for help2man-1.49.2 configure: loading site script /usr/ports/Templates/config.site checking for perl... perl checking for module Locale::gettext... no checking for msgfmt... /usr/local/bin/msgfmt checking for gcc... cc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C... yes checking whether cc accepts -g... yes checking for cc option to enable C11 features... none needed checking for library containing dlsym... none required checking for library containing bindtextdomain... -lintl configure: error: perl module Locale::gettext required ===> Script "configure" failed unexpectedly. Rebuild lang/perl5.32 and devel/p5-Locale-gettext manually before contacting maintainer. *** Error code 1 Stop. make[4]: stopped in /usr/ports/misc/help2man *** Error code 1 Stop. make[3]: stopped in /usr/ports/print/texinfo *** Error code 1 Stop. make[2]: stopped in /usr/ports/math/gmp *** Error code 1 Stop. make[1]: stopped in /usr/ports/devel/binutils *** Error code 1 Stop. make: stopped in /usr/ports/lang/gcc11 Updating the ports tree, cleaning and trying to (re)build dependencies one at a time always comes to the same end. By contrast, a Pi3 running -current had no such problems, a Pi3 running stable/13 got bogged down with excessive swap use. Neither made complaints such as seen on armv7. In case it matters, the motive is to build sysutils/u-boot-rpi2, Thanks for reading, bob prohaska
