[HEADS UP] Binary packages for FreeBSD 11 to require 11.3 soon
FreeBSD 11.3 was released on 2019-07-09. After adding 3 months support overlap it'd be 2019-10-09 (yesterday). Given 11.2 is EOL the package cluster will upgrade from 11.2 to 11.3 [*] while the ports tree would adjust ALLOW_UNSUPPORTED_SYSTEM knob and drop 11.2-specific workarouds. Once packages for 11.3 are built (from 2 to 4 days + few hours to mirror) /quarterly and /latest won't be usable on 11.2 anymore. /release_2 from 2018-06-05 should still work. So, upgrade to FreeBSD 11.3 or backup 11.2 packages. If you're on FreeBSD 11.3 already beware some packages may disappear due to broken build e.g., from base Clang/libc++ 8 upgrade. -- [*] Look for 113amd64 and 113i386 jails on https://pkg-status.freebsd.org/ May not be visible until build starts e.g., on Tue/Thu/Sat at 01:00 UTC. ___ 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"
INDEX now builds successfully on 11.x
___ 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"
looking for a committer for databases/mongodb* (security)
Hello, I'm looking for a committer for these PRs. First (containing vuxml entries also): https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239717 (mongodb34 security update) And then these two dependencies: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240126 (mongodb36 security update) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241078 (mongodb34 followup update) I've fixed all suggestions in the PRs and verified on #freebsd-ports (irc) that the PRs are in good enough shape now. Regards, Ronald. ___ 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: Can't update qt5-gui on 11.2-RELEASE-p13
On 2019-10-09 10:25, Alexander Leidinger via freebsd-ports wrote: > Quoting George Mitchell (from Wed, 9 Oct 2019 > 10:12:39 -0400): > >> Apparently the definitions of various structures found in >> /usr/local/include/mtdev.h from libmtdev-1.1.5_2 conflict with >> the definitions /usr/include/dev/evdev/input.h from base. >> This is in the middle of a portmaster qt5 upgrade, trying to >> reinstall qt5-gui-5.12.2_1. I didn't see anything in UPDATING >> that seemed relevant. My ports tree is at 514153. -- George > > I've run into the same error just yesterday. As a workaround, deinstall > the devel/evdev-proto port (it's not the libmtdev port which is the > problem) and it will use the base-system evdev includes. > > Bye, > Alexander. > Problem solved! Thanks for your help. -- George signature.asc Description: OpenPGP digital signature
INDEX build failed for 11.x
INDEX build failed with errors: Generating INDEX-11 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- --- describe.astro --- --- describe.audio --- --- describe.benchmarks --- --- describe.biology --- --- describe.cad --- --- describe.chinese --- --- describe.comms --- --- describe.converters --- --- describe.databases --- --- describe.deskutils --- --- describe.devel --- --- describe.dns --- --- describe.editors --- --- describe.emulators --- --- describe.finance --- --- describe.french --- --- describe.ftp --- --- describe.games --- --- describe.german --- --- describe.graphics --- --- describe.devel --- make[5]: "/home/indexbuild/tindex/ports/devel/llvm70/Makefile" line 213: Need an operator make[5]: "/home/indexbuild/tindex/ports/devel/llvm70/Makefile" line 215: if-less endif make[5]: Fatal errors encountered -- cannot continue===> devel/llvm70 failed *** [describe.devel] Error code 1 make[2]: stopped in /home/indexbuild/tindex/ports make[2]: stopped in /home/indexbuild/tindex/ports *** Error code 1 Stop. make[1]: stopped in /home/indexbuild/tindex/ports *** Error code 1 Stop. make: stopped in /home/indexbuild/tindex/ports 1 error Committers on the hook: amdmi3 brooks dmgk jrm ler mandree Most recent SVN update was: Updating '.': Udevel/llvm70/Makefile Uastro/mkgmap/Makefile Uastro/mkgmap/distinfo Umail/fetchmail/Makefile Amail/fetchmail/files/patch-fetchmail.man Amail/fetchmail/files/patch-t.smoke Umail/dovecot/Makefile Umail/dovecot/pkg-plist Usecurity/Makefile Asecurity/aws-vault Asecurity/aws-vault/Makefile Asecurity/aws-vault/distinfo Asecurity/aws-vault/pkg-descr Usecurity/lego/Makefile Usecurity/lego/distinfo Udatabases/pspg/Makefile Udatabases/pspg/distinfo U.gitauthors Updated to revision 514178. ___ 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: dovecot-2.3.8 not building (lua error)
On 10/09/2019 3:28 am, Paul Macdonald via freebsd-ports wrote: Hi, dovecot is not building on FreeBSD 12.0-REL if lua support is not selected, but does build if it is. ===> Registering installation for dovecot-2.3.8 pkg-static: Unable to access file /var/ports/basejail/usr/ports/mail/dovecot/work/stage/usr/local/%%LUA_LIBDIR%%exec/dovecot/health-check.sh:No such file or directory fixed with 2.3.8_2. Sorry for the breakage. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 ___ 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"
[HEADSUP] Re: Is IPV6 option still necessary?
On Wed, Oct 09, 2019 at 12:14:13PM +0200, Baptiste Daroussin wrote: > On Wed, Oct 09, 2019 at 12:05:49PM +0200, Jan Beich wrote: > > Yasuhiro KIMURA writes: > > > > > On October 10, 2012 IPV6 option of all ports was enabled by > > > default. Commit message said "We are in 2012, it is time to activate > > > IPV6 options by default everywhere". > > > > > > And now we are in 2019. IPv6 is more widely used than 2012. So I > > > wonder if IPV6 option is still necessary. > > > > ipv6 in CATEGORIES is also of dubious value nowadays. For one, > > www/firefox has "ipv6" while www/chromium does not. > > This one is even easier to fix ;) > Done. Now we can get back on the ipv6 option. so if we want to proceed further in removing the option to build with or without ipv6 for the ports side. Please speak up in reply to this email, if you are building without ipv6, why are you doing so, what are the real benefit for it. How bad it will impact you if we do remove that option? Best regards, Bapt signature.asc Description: PGP signature
Re: Can't update qt5-gui on 11.2-RELEASE-p13
Quoting George Mitchell (from Wed, 9 Oct 2019 10:12:39 -0400): Apparently the definitions of various structures found in /usr/local/include/mtdev.h from libmtdev-1.1.5_2 conflict with the definitions /usr/include/dev/evdev/input.h from base. This is in the middle of a portmaster qt5 upgrade, trying to reinstall qt5-gui-5.12.2_1. I didn't see anything in UPDATING that seemed relevant. My ports tree is at 514153.-- George I've run into the same error just yesterday. As a workaround, deinstall the devel/evdev-proto port (it's not the libmtdev port which is the problem) and it will use the base-system evdev includes. Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF pgplWneGvTpyv.pgp Description: Digitale PGP-Signatur
Can't update qt5-gui on 11.2-RELEASE-p13
Apparently the definitions of various structures found in
/usr/local/include/mtdev.h from libmtdev-1.1.5_2 conflict with
the definitions /usr/include/dev/evdev/input.h from base.
This is in the middle of a portmaster qt5 upgrade, trying to
reinstall qt5-gui-5.12.2_1. I didn't see anything in UPDATING
that seemed relevant. My ports tree is at 514153.-- George
In file included from evdevtouch/qevdevtouchhandler.cpp:62:
In file included from /usr/local/include/mtdev.h:36:
/usr/local/include/linux/input.h:27:8: error: redefinition of 'input_event'
struct input_event {
^
/usr/include/dev/evdev/input.h:41:8: note: previous definition is here
struct input_event {
^
In file included from evdevtouch/qevdevtouchhandler.cpp:62:
In file included from /usr/local/include/mtdev.h:36:
/usr/local/include/linux/input.h:53:8: error: redefinition of 'input_id'
struct input_id {
^
/usr/include/dev/evdev/input.h:50:8: note: previous definition is here
struct input_id {
^
In file included from evdevtouch/qevdevtouchhandler.cpp:62:
In file included from /usr/local/include/mtdev.h:36:
/usr/local/include/linux/input.h:84:8: error: redefinition of
'input_absinfo'
struct input_absinfo {
^
/usr/include/dev/evdev/input.h:57:8: note: previous definition is here
struct input_absinfo {
^
In file included from evdevtouch/qevdevtouchhandler.cpp:62:
In file included from /usr/local/include/mtdev.h:36:
/usr/local/include/linux/input.h:108:8: error: redefinition of
'input_keymap_entry'
struct input_keymap_entry {
^
/usr/include/dev/evdev/input.h:68:8: note: previous definition is here
struct input_keymap_entry {
^
In file included from evdevtouch/qevdevtouchhandler.cpp:62:
In file included from /usr/local/include/mtdev.h:36:
/usr/local/include/linux/input.h:300:8: error: redefinition of 'ff_replay'
struct ff_replay {
^
/usr/include/dev/evdev/input.h:158:8: note: previous definition is here
struct ff_replay {
^
In file included from evdevtouch/qevdevtouchhandler.cpp:62:
In file included from /usr/local/include/mtdev.h:36:
/usr/local/include/linux/input.h:310:8: error: redefinition of 'ff_trigger'
struct ff_trigger {
^
/usr/include/dev/evdev/input.h:164:8: note: previous definition is here
struct ff_trigger {
^
In file included from evdevtouch/qevdevtouchhandler.cpp:62:
In file included from /usr/local/include/mtdev.h:36:
/usr/local/include/linux/input.h:327:8: error: redefinition of 'ff_envelope'
struct ff_envelope {
^
/usr/include/dev/evdev/input.h:170:8: note: previous definition is here
struct ff_envelope {
^
In file included from evdevtouch/qevdevtouchhandler.cpp:62:
In file included from /usr/local/include/mtdev.h:36:
/usr/local/include/linux/input.h:339:8: error: redefinition of
'ff_constant_effect'
struct ff_constant_effect {
^
/usr/include/dev/evdev/input.h:177:8: note: previous definition is here
struct ff_constant_effect {
^
In file included from evdevtouch/qevdevtouchhandler.cpp:62:
In file included from /usr/local/include/mtdev.h:36:
/usr/local/include/linux/input.h:350:8: error: redefinition of
'ff_ramp_effect'
struct ff_ramp_effect {
^
/usr/include/dev/evdev/input.h:182:8: note: previous definition is here
struct ff_ramp_effect {
^
In file included from evdevtouch/qevdevtouchhandler.cpp:62:
In file included from /usr/local/include/mtdev.h:36:
/usr/local/include/linux/input.h:366:8: error: redefinition of
'ff_condition_effect'
struct ff_condition_effect {
^
/usr/include/dev/evdev/input.h:188:8: note: previous definition is here
struct ff_condition_effect {
^
In file included from evdevtouch/qevdevtouchhandler.cpp:62:
In file included from /usr/local/include/mtdev.h:36:
/usr/local/include/linux/input.h:395:8: error: redefinition of
'ff_periodic_effect'
struct ff_periodic_effect {
^
/usr/include/dev/evdev/input.h:215:8: note: previous definition is here
struct ff_periodic_effect {
^
In file included from evdevtouch/qevdevtouchhandler.cpp:62:
In file included from /usr/local/include/mtdev.h:36:
/usr/local/include/linux/input.h:416:8: error: redefinition of
'ff_rumble_effect'
struct ff_rumble_effect {
^
/usr/include/dev/evdev/input.h:226:8: note: previous definition is here
struct ff_rumble_effect {
^
In file included from evdevtouch/qevdevtouchhandler.cpp:62:
In file included from /usr/local/include/mtdev.h:36:
/usr/local/include/linux/input.h:444:8: error: redefinition of 'ff_effect'
struct ff_effect {
^
/usr/include/dev/evdev/input.h:247:8: note: previous definition is here
struct ff_effect {
^
13 errors generated.
*** [.obj/qevdevtouchhandler.o] Error code 1
make[3]: stopped in
/usr/ports/x11-toolkits/qt5-gui/work/qtbase-everywhere-src-5.13.0/src/platformsupport/input
1 error
make[3]: stopped in
Re: Is IPV6 option still necessary?
On Wed, Oct 09, 2019 at 12:05:49PM +0200, Jan Beich wrote: > Yasuhiro KIMURA writes: > > > On October 10, 2012 IPV6 option of all ports was enabled by > > default. Commit message said "We are in 2012, it is time to activate > > IPV6 options by default everywhere". > > > > And now we are in 2019. IPv6 is more widely used than 2012. So I > > wonder if IPV6 option is still necessary. > > ipv6 in CATEGORIES is also of dubious value nowadays. For one, > www/firefox has "ipv6" while www/chromium does not. This one is even easier to fix ;) Best regards, Bapt signature.asc Description: PGP signature
Re: Is IPV6 option still necessary?
Yasuhiro KIMURA writes: > On October 10, 2012 IPV6 option of all ports was enabled by > default. Commit message said "We are in 2012, it is time to activate > IPV6 options by default everywhere". > > And now we are in 2019. IPv6 is more widely used than 2012. So I > wonder if IPV6 option is still necessary. ipv6 in CATEGORIES is also of dubious value nowadays. For one, www/firefox has "ipv6" while www/chromium does not. ___ 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"
dovecot-2.3.8 not building (lua error)
Hi, dovecot is not building on FreeBSD 12.0-REL if lua support is not selected, but does build if it is. ===> Registering installation for dovecot-2.3.8 pkg-static: Unable to access file /var/ports/basejail/usr/ports/mail/dovecot/work/stage/usr/local/%%LUA_LIBDIR%%exec/dovecot/health-check.sh:No such file or directory Paul. -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07970339546 e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG 40 Maritime Street Edinburgh EH6 6SA High Specification Dedicated Servers from £100.00pm ___ 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: Is IPV6 option still necessary?
On Tue, Oct 08, 2019 at 10:16:08PM +0300, abi via freebsd-ports wrote: > 07.10.2019 09:18, Yasuhiro KIMURA пишет: > > On October 10, 2012 IPV6 option of all ports was enabled by > > default. Commit message said "We are in 2012, it is time to activate > > IPV6 options by default everywhere". > > > > And now we are in 2019. IPv6 is more widely used than 2012. So I > > wonder if IPV6 option is still necessary. > > > > If you use official packages then you always use IPv6-enabled > > binaries. And even if you build packages by yourself you still use > > IPv6-enabled ones unless you disable IPV6 option. So I think at most > > only a few people uses IPv6-disabled packages. > > > > Are there anybody who still disables IPV6 option for some serious > > reason such as working around IPv6-related problem? If there aren't > > then I think it's time to remove IPV6 option from ports framework. > > > I'm writing from 2019 and I build kernel and ports without IPv6. For all > this years I fail to understand why I need it. > > My home devices fit 10.0.0.0/16 nicely, I have faith in NAT and I > encountered no IPv6-only sites. > > But I saw CVEs in IPv6 stack. Plenty of FreeBSD things are ipv6 only in the FreeBSD cluster. In particular if you do look at the build machines in the cluster, no ipv6 will mean no access to the build log in case of failures. I agree I don't see the reason why we should keep that ipv6 option. When off this option does not bring much value to the users as the code for apps to support ipv6 mostly reside in the libc. Actually that was my intent in 2012 to first turn it on by default everywhere and then drop the option entirely. Best regards, Bapt signature.asc Description: PGP signature
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 +-+ lang/opencoarrays | 2.7.1 | 2.8.0 +-+ science/psychopy| 1.90.3 | 3.2.4 +-+ 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! ___ 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"
