Re: sysutils/beats7: fix in head to 2020Q1
Yes, thank you very much Am 25.01.21 um 11:16 schrieb Kurt Jaeger: > Hi! > >> could someone please pull the fix >> https://svnweb.freebsd.org/ports?view=revision=560735 to 2020Q1? > Done. I added this to 2021Q1, which was probably what you asked for... > -- --- punkt.de GmbH Lars Liedtke .infrastructure Kaiserallee 13a 76133 Karlsruhe Tel. +49 721 9109 500 https://infrastructure.punkt.de i...@punkt.de AG Mannheim 108285 Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein ___ 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"
sysutils/beats7: fix in head to 2020Q1
Hello, could someone please pull the fix https://svnweb.freebsd.org/ports?view=revision=560735 to 2020Q1? Cheers Lars -- --- punkt.de GmbH Lars Liedtke .infrastructure Kaiserallee 13a 76133 Karlsruhe Tel. +49 721 9109 500 https://infrastructure.punkt.de i...@punkt.de AG Mannheim 108285 Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein ___ 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"
OpenJDK11 configure failure on 12.1
Hello *, I am building a certain set of ports in poudriere on FreeBSD 12.1. This worked fine until some time ago. Now I get a configure error for OpenJDK11. > [00:00:55] configure: Found potential Boot JDK using configure arguments > [00:00:55] configure: Potential Boot JDK found at /usr/local/bootstrap-openjdk11 is incorrect JDK version (OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00100020, 536870912, 0) failed; error='ENOMEM' (errno=12)); ignoring > [00:00:55] configure: (Your Boot JDK version must be one of: 10 11) > [00:00:55] configure: error: The path given by --with-boot-jdk does not contain a valid Boot JDK > [00:00:55] configure exiting with result code 1 > [00:00:55] ===> Script "configure" failed unexpectedly. > [00:00:55] Please report the problem to j...@freebsd.org [maintainer] and attach the > [00:00:55] "/wrkdirs/usr/ports/java/openjdk11/work/openjdk-jdk11u-jdk-11.0.8-10-1/config.log" > [00:00:55] including the output of the failure of your make command. Also, it might be > [00:00:55] a good idea to provide an overview of all packages installed on your system > [00:00:55] (e.g. a /usr/local/sbin/pkg-static info -g -Ea). > [00:00:55] *** Error code 1 > [00:00:55] > [00:00:55] Stop. > [00:00:55] make: stopped in /usr/ports/java/openjdk11 > [00:01:09] =>> Cleaning up wrkdir > [00:01:10] ===> Cleaning for openjdk11-11.0.8+10.1 > [00:01:11] build of java/openjdk11 | openjdk11-11.0.8+10.1 ended at Tue Oct 6 08:49:21 CEST 2020 > [00:01:11] build time: 00:01:11 > [00:01:11] !!! build failure encountered !!! Full log can be found here https://gist.github.com/Corvan/8acdeb451fc3aeec3904845c9093ea6c Can someone help me make sense of that, or should I send this to j...@freebsd.org as stated in the error? Cheers Lars -- --- punkt.de GmbH Lars Liedtke .infrastructure Kaiserallee 13a 76133 Karlsruhe Tel. +49 721 9109 500 https://infrastructure.punkt.de i...@punkt.de AG Mannheim 108285 Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein signature.asc Description: OpenPGP digital signature
Re: Silent stoppage building www/chromium
We have been seing this behaviour of poudriere with other Ports as well (tomcat, jni). If it runs out of memory, e.g. swap limits of the jail we're running poudriere in are too small, then it just fails silently. We have been able to prevent this by increasing the limits, to twice the memory limit, but of course I am well aware that not everyone is able to do that. Am 30.08.20 um 23:40 schrieb Marcel Bischoff: > Firefox has Rust as a dependency. In the past I have found that the build > process for the latter easily overwhelms lean systems with little physical > RAM. Regardless of swap space, quite unlike most other ports. > > Marcel > > On 30 Aug 2020, at 17:49, bob prohaska wrote: > >> Apologies, the port in question is www/firefox, not www/chromium. >> >> Sorry for the write-o, >> >> bob >> >> ___ >> 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" -- --- punkt.de GmbH Lars Liedtke .infrastructure Kaiserallee 13a 76133 Karlsruhe Tel. +49 721 9109 500 https://infrastructure.punkt.de i...@punkt.de AG Mannheim 108285 Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein signature.asc Description: OpenPGP digital signature
Re: Chromium (& derivatives) and Python 2.7
At least in Ubuntu the mongodb 3.6 package does not depend on python2. > Package: mongodb-server-core > Version: 1:3.6.9+really3.6.8+90~g8e540c0b6d-0ubuntu5 > Priority: optional > Section: universe/database > Source: mongodb > Origin: Ubuntu > Maintainer: Ubuntu Developers > Original-Maintainer: Debian MongoDB Maintainers > Bugs: https://bugs.launchpad.net/ubuntu/+filebug > Installed-Size: 77,8 MB > Depends: libboost-filesystem1.71.0, libboost-program-options1.71.0, libc6 (>= 2.29), libgcc-s1 (>= 3.4), libgoogle-perftools4, libpcrecpp0v5 (>= 7.7), libsnappy1v5 (>= 1.1.8), libssl1.1 (>= 1.1.0), libstdc++6 (>= 9), libstemmer0d (>= 0+svn527), libyaml-cpp0.6 (>= 0.6.2), zlib1g (>= 1:1.2.0) > Breaks: mongodb-server (<< 1:3.4.14-3ubuntu1) > Replaces: mongodb-server (<< 1:3.4.14-3ubuntu1) > Homepage: https://www.mongodb.org > Download-Size: 21,6 MB > APT-Sources: http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages [...] I don't know about build dependencies Am 28.07.20 um 11:36 schrieb Ronald Klop: > The same problem is going to happen with mongodb36 I presume. It uses > python2 to build, but does not need it to run. > Would it be possible to remove python2 as a RUN_DEPENDS at the end of > 2020, but keep it as a BUILD_DEPENDS in the ports framework? > > This might save some usefull ports. > > How are other projects (like Debian, etc.) solving this? > > Regards, > Ronald. > > > Van: Adriaan de Groot > Datum: maandag, 27 juli 2020 21:36 > Aan: freebsd-ports@freebsd.org > Onderwerp: Chromium (& derivatives) and Python 2.7 >> >> The Chromium build system -- and as a consequence, also QtWebEngine >> -- still >> uses Python 2.7. This is going to be a real problem about six months >> down the >> line, and I have no idea how upstream is going to deal with it. I've >> heard >> there are patches buried deep within the chocolate factory, but not from >> reliable sources. >> >> QtWebEngine is an even specialer case, since it's an LTS and also the >> last LTS >> in the Qt5 series, and I have real doubts about upstream -- The Qt >> Company -- >> being able or willing to deal with Python 2.7 deprecation there. >> >> Has anyone in FreeBSD tried to port the stuff over? I got about an >> hour or two >> into the porting process (making configure accept Python 3 is easy, but >> there's all these wretched code-generating scripts) and hit a brick >> wall of >> templating engines doing sensible Python 2.7 things. >> >> [ade] >> >> >> >> > ___ > 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" -- --- punkt.de GmbH Lars Liedtke .infrastructure Kaiserallee 13a 76133 Karlsruhe Tel. +49 721 9109 500 https://infrastructure.punkt.de i...@punkt.de AG Mannheim 108285 Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein signature.asc Description: OpenPGP digital signature
Re: Is IPV6 option still necessary?
Am 10.10.19 um 17:17 schrieb LuKreme: > On Oct 9, 2019, at 00:15, Baptiste Daroussin wrote: >> 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. > My isp does not support ipv6, so my services are not set to use it. I did > have to specifically disable it in configuration for something, I forget > what, but I have never felt the need to disable it in builds. > Why not just make building in IPv6 support the default, and introduce a flag if someone really needs or wants to build without that support? Best regards Lars -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 i...@punkt.de https://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ 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"
