poudriere: net/openldap24-server: stage/runaway , building forever

2021-04-08 Thread Hartmann, O.
Recent CURRENT host (FreeBSD 14.0-CURRENT #26 main-n245806-4d221f59b85: Sat Apr 3 06:43:44 CEST 2021 amd64), poudriere CURRENT jail at 14.0-CURRENT 147 amd64 from 2021-04-08 05:25:38. It seems that the recent CURRENT does have a serious problem when building net/openldap24-server. The

Re: devel/git: Git via Apache 2.4 HTTPS - info/refs not valid: could not determine hash algorithm

2021-03-29 Thread Hartmann, O.
On Mon, 29 Mar 2021 11:42:28 +0200 Michael Gmelin wrote: > On Sun, 28 Mar 2021 13:08:19 +0200 > "Hartmann, O." wrote: > > > What am I missing here? > > > > The man page of git-http-backend has an apache2 example[0]. > Also, the top answer to th

Re: devel/git: Git via Apache 2.4 HTTPS - info/refs not valid: could not determine hash algorithm

2021-03-29 Thread Hartmann, O.
On Mon, 29 Mar 2021 11:42:28 +0200 Michael Gmelin wrote: > On Sun, 28 Mar 2021 13:08:19 +0200 > "Hartmann, O." wrote: > > > What am I missing here? > > > > The man page of git-http-backend has an apache2 example[0]. > Also, the top answer to th

devel/git: Git via Apache 2.4 HTTPS - info/refs not valid: could not determine hash algorithm

2021-03-28 Thread Hartmann, O.
Hello folks, first of all sorry for "misusing" the lis for this question of mine. But maybe someone already has setup devel/git over HTTPS and it is working. I fail for several days for now and I'm unable to find the problem. After realized that the content of the book "Pro Git" by Chacon and

On 14-CURRENT: no ports options anymore?

2021-03-13 Thread Hartmann, O.
Since I moved on to 14-CURRENT, I face a very strange behaviour when trying to set options via "make config" or via poudriere accordingly. I always get "===> Options unchanged" (when options has been already set and I'd expect a dialog menu). This misbehaviour is throughout ALL 14-CURRENT

poudriere/make differences regarding ICONV

2019-10-21 Thread Hartmann, O.
I'm working on an update of a port we maintain here ourselfs and since a couple of months for now, out of the blue this port (textproc/refdb in carnation rev 1.0.2) won't build anymore, always failing due to an error in poudriere's log, stating: [...] ===> refdb-1.0.2 depends on shared

Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

2013-03-11 Thread Hartmann, O.
Am 03/11/13 11:17, schrieb Dimitry Andric: On 2013-03-10 00:39, Steve Kargl wrote: ... If you have a clang built FreeBSD-current, then it is no longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor the upcoming gcc-4.8.0. AFAICT, the problem is related to /usr/bin/cpp. I haven't tried

lang/ruby19: ruby-1.9.3.392,1 is vulnerable: ** [check-vulnerable] Error code 1

2013-03-09 Thread Hartmann, O.
I try to compile port lang/ruby19 and I always get on a FreeBSD 9.1-STABLE box the following error message, which is obviously triggered by some port auditing - but I do not find the knob to switch it off. Can someone give a hint, please? Regards, Oliver === Cleaning for ruby-1.9.3.392,1 ===

Re: lang/ruby19: ruby-1.9.3.392, 1 is vulnerable: ** [check-vulnerable] Error code 1

2013-03-09 Thread Hartmann, O.
Am 03/09/13 10:38, schrieb Chris Rees: On 9 March 2013 09:37, Hartmann, O. ohart...@zedat.fu-berlin.de wrote: I try to compile port lang/ruby19 and I always get on a FreeBSD 9.1-STABLE box the following error message, which is obviously triggered by some port auditing - but I do not find

CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

2013-03-09 Thread Hartmann, O.
I have one specific FreeBSD 10.0-CURRENT box (FreeBSD 10.0-CURRENT #0 r248061: Fri Mar 8 19:44:30 CET 2013 amd64) which rejects to build either lang/gcc or lang/gcc46 with the very same error shown below. The box is compiled with CLANG (buildworld/kernel). It doesn't matter whether I compile

CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

2013-03-09 Thread Hartmann, O.
I rebuild the kernel module for x11/nvidia-driver on a regular basis via /etc/src.conf setting of PORTS_MODULES+=x11/nvidia-driver but this time, the port gets deleted and - fails to compile (tried 310.32 and 313.26, the latter worked for me before very well). The compilation

Re: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

2013-03-09 Thread Hartmann, O.
Am 03/09/13 17:38, schrieb Ruslan Makhmatkhanov: Hartmann, O. wrote on 09.03.2013 20:31: I rebuild the kernel module for x11/nvidia-driver on a regular basis via /etc/src.conf setting of PORTS_MODULES+=x11/nvidia-driver I answered to your pr. Did you tried that? If I

Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found

2013-03-09 Thread Hartmann, O.
Am 03/09/13 17:02, schrieb Dimitry Andric: On Mar 9, 2013, at 16:36 , Hartmann, O. ohart...@zedat.fu-berlin.de wrote: I have one specific FreeBSD 10.0-CURRENT box (FreeBSD 10.0-CURRENT #0 r248061: Fri Mar 8 19:44:30 CET 2013 amd64) which rejects to build either lang/gcc or lang/gcc46

Re: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

2013-03-09 Thread Hartmann, O.
Am 03/09/13 17:46, schrieb Ruslan Makhmatkhanov: Hartmann, O. wrote on 09.03.2013 20:45: Am 03/09/13 17:38, schrieb Ruslan Makhmatkhanov: Hartmann, O. wrote on 09.03.2013 20:31: I rebuild the kernel module for x11/nvidia-driver on a regular basis via /etc/src.conf setting of PORTS_MODULES

Re: CURRENT (r248103): x11/nvidia-driver fails to compile: @/vm/vm_pager.h:127:2: error: use of undeclared identifier 'RA_WLOCKED'

2013-03-09 Thread Hartmann, O.
Am 03/09/13 18:07, schrieb David Wolfskill: On Sat, Mar 09, 2013 at 06:06:05PM +0100, Hartmann, O. wrote: ... No, it isn't. Same error, system is at revision: FreeBSD 10.0-CURRENT #1 r248106: Sat Mar 9 16:44:58 CET 2013 amd64 The error is the same. ... Please see the message I posted

port building in CURRENT (including r247839) BROKEN

2013-03-05 Thread Hartmann, O.
On all FreeBSD boxes with FreeBSD 10.0-CURRENT #1 r247839: Tue Mar 5 12:28:12 CET 2013/amd64 the build of ports - or updating/upgrading ports is BROKEN! Every port which is about to be updated fails with [...] *** [do-extract] Signal 13 This is common on ALL CURRENT systems so I consider this

9.1-PRE: updating of pkg-1.0.3 - pkg-1.0.4 fails

2012-12-28 Thread Hartmann, O.
Last time I update ports on my latop was on Dec 20th. Everything went well. Today I grabbed the laptop again, made an update of the ports tree and try running portmaster. The laptop is running FreeBSD 9.1-PRERELEASE #142 r244377: Tue Dec 18 07:29:18 CET 2012. The update of pkgng is the first in

portmaster and pkgng

2012-07-23 Thread Hartmann, O.
Hello. I'd like to try pkgng with portmaster. I see that pkg2ng is involving the directory /var/db/pkg, so this implies that there may implications also for usage with ports-mgmt/portmaster. portmaster is supposed to be the tool completely dependend on system's toolsets, isn't it? I know that

www/firefox (13.0,1): SIGNAL 10 or SIGNAL 11 (gettimeofday())

2012-06-07 Thread Hartmann, O.
Hello. On one of my boxes I have a persistent problem with Firefox since the last major update/recompilation a week ago due to the massive PNG update. OS is FreeBSD 10.0-CURRENT/amd64, CLANG compiled. First of all, neither firefox 12 nor 13 compile with CLANG. Firefox 12 also rejects compiling

Re: Binary packages for LibreOffice 3.5 or 3.4

2012-05-07 Thread Hartmann, O.
On 05/07/12 11:35, Baptiste Daroussin wrote: On Mon, May 07, 2012 at 09:20:06AM +0300, Andriy Gapon wrote: on 07/05/2012 01:58 Baptiste Daroussin said the following: Well for libreoffice on freebsd clang is the official compiler, because 4.2.1 is just too old for libreoffice, and I never

editors/libreoffice:internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl/prj

2012-05-04 Thread Hartmann, O.
I found myself incapable of rebuilding/updating editors/libreoffice on ALL FreeBSD 9-STABLE and FreeBSD 10-CURRENT (amd64) platforms with the very same error message as shown below. It doesn't matter whether I try to build/update with CLANG or the legacy gcc 4.2.1. GCC 4.6 and 4.7 fail due to

portsnap fetch update: look: tINDEX.new: File too large

2011-10-15 Thread Hartmann, O.
This morning, I get this when trying to update the local portssystem: Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found. Fetching snapshot tag from portsnap6.FreeBSD.org... done. Fetching snapshot metadata... done. look: tINDEX.new: File too large Portsnap metadata appears bogus.

FreeBSD 10.0-CURRENT: messed up the ports and system (gcc46 won't compile) and need to repair - how?

2011-10-09 Thread Hartmann, O.
Since the change of one of my boxes to FreeBSD 10.0 and some accindetally build of ports without the suggested settings for UNAME_r before building ports, I think I've messed up with some ports and need some advice how to fixate the problem. Some develish motivation drove me today building

Re: Thunderbird 6.0.2/7.0: Crashing when using with OpenLDAP backend

2011-09-29 Thread Hartmann, O.
On 09/29/11 18:31, Andrea Venturoli wrote: On 09/28/11 14:29, O. Hartmann wrote: I run in a problem on FreeBSD 9.0-BETA3/10.0-CURRENT using OpenLDAP (Cyrus SASL2 aktivated) and OpenLDAP backend (most recent client and server). Thunderbird 6.0.2 and 7.0 coredumps with signal 11. I hadn't any

Re: HEADS UP: ports/ and 10.0-CURRENT

2011-09-28 Thread Hartmann, O.
On 09/28/11 15:47, per...@pluto.rain.com wrote: Eitan Adler li...@eitanadler.com wrote: 2011/9/27 O. Hartmann ohart...@zedat.fu-berlin.de: Now I understand why some OS vendors have choosen the latin 10 'X' for their tenth version of their operating system ... FreeBSD XP anyone? Are you sure

Re: HEADS UP: ports/ and 10.0-CURRENT

2011-09-28 Thread Hartmann, O.
On 09/28/11 09:26, Hartmann, O. wrote: On 09/28/11 15:47, per...@pluto.rain.com wrote: Eitan Adler li...@eitanadler.com wrote: 2011/9/27 O. Hartmann ohart...@zedat.fu-berlin.de: Now I understand why some OS vendors have choosen the latin 10 'X' for their tenth version of their operating

10.0-CURRENT: gawk fails to install: the gawk/libintl chicken and egg problem again

2011-09-28 Thread Hartmann, O.
On 09/28/11 19:43, Garrett Cooper wrote: On Sep 28, 2011, at 10:29 AM, Hartmann, O. wrote: On 09/28/11 09:26, Hartmann, O. wrote: On 09/28/11 15:47, per...@pluto.rain.com wrote: Eitan Adler li...@eitanadler.com wrote: 2011/9/27 O. Hartmann ohart...@zedat.fu-berlin.de: Now I understand why

Re: HEADS UP: ports/ and 10.0-CURRENT

2011-09-28 Thread Hartmann, O.
On 09/28/11 20:20, h h wrote: Hartmann, O. ohart...@zedat.fu-berlin.de writes: On 09/28/11 09:26, Hartmann, O. wrote: On 09/28/11 15:47, per...@pluto.rain.com wrote: Eitan Adler li...@eitanadler.com wrote: 2011/9/27 O. Hartmann ohart...@zedat.fu-berlin.de: Now I understand why some OS

Re: HEADS UP: ports/ and 10.0-CURRENT

2011-09-28 Thread Hartmann, O.
On 09/28/11 20:41, Garrett Cooper wrote: On Sep 28, 2011, at 11:38 AM, Hartmann, O. wrote: On 09/28/11 20:20, h h wrote: Hartmann, O. ohart...@zedat.fu-berlin.de writes: On 09/28/11 09:26, Hartmann, O. wrote: On 09/28/11 15:47, per...@pluto.rain.com wrote: Eitan Adler li...@eitanadler.com

Re: 10.0-CURRENT: gawk fails to install: the gawk/libintl chicken and egg problem again

2011-09-28 Thread Hartmann, O.
On 09/28/11 20:15, Hartmann, O. wrote: On 09/28/11 19:43, Garrett Cooper wrote: On Sep 28, 2011, at 10:29 AM, Hartmann, O. wrote: On 09/28/11 09:26, Hartmann, O. wrote: On 09/28/11 15:47, per...@pluto.rain.com wrote: Eitan Adler li...@eitanadler.com wrote: 2011/9/27 O. Hartmann ohart

Re: HEADS UP: ports/ and 10.0-CURRENT

2011-09-28 Thread Hartmann, O.
On 09/28/11 20:56, Hartmann, O. wrote: On 09/28/11 20:41, Garrett Cooper wrote: On Sep 28, 2011, at 11:38 AM, Hartmann, O. wrote: On 09/28/11 20:20, h h wrote: Hartmann, O. ohart...@zedat.fu-berlin.de writes: On 09/28/11 09:26, Hartmann, O. wrote: On 09/28/11 15:47, per...@pluto.rain.com

Re: HEADS UP: ports/ and 10.0-CURRENT

2011-09-28 Thread Hartmann, O.
On 09/28/11 21:16, Hartmann, O. wrote: On 09/28/11 20:56, Hartmann, O. wrote: On 09/28/11 20:41, Garrett Cooper wrote: On Sep 28, 2011, at 11:38 AM, Hartmann, O. wrote: On 09/28/11 20:20, h h wrote: Hartmann, O. ohart...@zedat.fu-berlin.de writes: On 09/28/11 09:26, Hartmann, O. wrote

Re: HEADS UP: ports/ and 10.0-CURRENT

2011-09-28 Thread Hartmann, O.
On 09/28/11 21:30, Matt wrote: On 09/28/11 12:16, Hartmann, O. wrote: On 09/28/11 20:56, Hartmann, O. wrote: On 09/28/11 20:41, Garrett Cooper wrote: On Sep 28, 2011, at 11:38 AM, Hartmann, O. wrote: On 09/28/11 20:20, h h wrote: Hartmann, O.ohart...@zedat.fu-berlin.de writes: On 09/28

Re: HEADS UP: ports/ and 10.0-CURRENT

2011-09-28 Thread Hartmann, O.
On 09/28/11 22:18, Doug Barton wrote: On 09/28/2011 12:39, Hartmann, O. wrote: The mess started to happen when I tried to repair a non CLANG compiling port math/gotoblas with portmaster -vf amth/gotoblas. Since this build binutils and even gettext and libiconv, I guess they got broken. Last I

Re: HEADS UP: ports/ and 10.0-CURRENT

2011-09-27 Thread Hartmann, O.
On 09/27/11 16:27, Matthew D. Fuller wrote: On Tue, Sep 27, 2011 at 09:36:17AM -0400 I heard the voice of Robert Huff, and lo! it spake thus: Adrian Chadd writes: Our children will be dealing with Y2038. :-) Statistically, some of us will. Actually, I had to deal with it just last week...

security/cyrus-sasl2 breaks OpenLDAP!!!

2011-09-25 Thread Hartmann, O.
Performing an update of the ports on a regular basis brought us security/cyrus-sasl2 version 2.1.25. After performing the update, OpenLDAP won't start anymore! It is essential, that the openldap-port is recompiled after upgarding cyrus-sasl2! This has not been reflected by ports/UPDATING so far.

sysutils/sge6[012]: Sun Grid Engine - still broklen due to utmpx?

2011-09-23 Thread Hartmann, O.
I was wondering if the SUN Grid Engine, located in port sysutils/sge6[012] is still broken due to utmpx. My department uses this GRID engine on Linux and since a long time I wish to use it also on FreeBSD. Are there alternatives? What are people using on HPC FreeBSD? Greetings, Oliver

Re: sysutils/sge6[012]: Sun Grid Engine - still broklen due to utmpx?

2011-09-23 Thread Hartmann, O.
On 09/23/11 09:04, Hartmann, O. wrote: I was wondering if the SUN Grid Engine, located in port sysutils/sge6[012] is still broken due to utmpx. My department uses this GRID engine on Linux and since a long time I wish to use it also on FreeBSD. Are there alternatives? What are people using

Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.

2011-08-14 Thread Hartmann, O.
On 08/14/11 11:48, Niclas Zeising wrote: On 2011-08-13 12:08, Roland Smith wrote: On Sat, Aug 13, 2011 at 09:51:41AM +0200, Hartmann, O. wrote: On 08/13/11 09:26, Roland Smith wrote: On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote: On 08/12/11 22:54, Roland Smith wrote: On Fri

Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.

2011-08-13 Thread Hartmann, O.
On 08/13/11 09:26, Roland Smith wrote: On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote: On 08/12/11 22:54, Roland Smith wrote: On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz Does this file

files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.

2011-08-12 Thread Hartmann, O.
Since today, I can not update my ports tree due to this error as follows. This happens on all boxes running FreeBSD, the version of the OS (FBSD 8.2/9.0) doesn't matter. What's up with the ports collection? Regards, Oliver Extracting new files: /usr/ports/GIDs /usr/ports/UIDs

Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.

2011-08-12 Thread Hartmann, O.
On 08/12/11 20:21, Roland Smith wrote: On Fri, Aug 12, 2011 at 07:38:06PM +0200, Olivier Smedts wrote: 2011/8/12 Roland Smithrsm...@xs4all.nl: On Fri, Aug 12, 2011 at 05:46:37PM +0200, Hartmann, O. wrote: Since today, I can not update my ports tree due to this error as follows. This happens

Re: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not found -- snapshot corrupt.

2011-08-12 Thread Hartmann, O.
On 08/12/11 22:54, Roland Smith wrote: On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote: files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz This file is relatively recent; When I used portsnap yesterday, it wasn't there, and now it is. I do a postrmaster

/usr/ports/Mk/bsd.qt.mk, line 115: warning: cc --version 2 /dev/null | awk 'NR == 1 { gsub(/[()]/, , ); print }' returned non-zero status

2011-07-01 Thread Hartmann, O.
When performing a portmaster -av after today's update of the ports tree, I receive this error: === virtualbox-ose-4.0.10 awk: syntax error at source line 1 context is NR == 1 { gsub(/[()]/, , ) awk: illegal statement at source line 1 /usr/ports/Mk/bsd.qt.mk, line 115: warning: cc

gcc-4.5 and 4.6 needs to be recompiled due to /usr/src/UPDATE: 20110608:

2011-06-09 Thread Hartmann, O.
Since the notice mentioned in /usr/src/UPDATE (20110608) both gcc-4.5 and 4.6 seems to need to be recompiled. I tried some ports with USE_FORTRAN= yes setand they failed as with gcc-4.6. There was always an error reporting: undefined reference to __cpumask_t or similar. Oliver

Re: editors/libreoffice: can not compile, crash on, FreeBSD 9.0-CUR/amd64 - msg#00540

2011-06-01 Thread Hartmann, O.
On 05/31/11 15:09, Andriy Gapon wrote: on 31/05/2011 15:22 Olivier Smedts said the following: 2011/5/31 Andriy Gapona...@freebsd.org: on 31/05/2011 12:11 Olivier Smedts said the following: Segmentation fault: 11 (core dumped) That core dump should be investigated / debugged. At the very

x11/nvidia-driver: cc1: error: /src: No such file or directory

2011-05-09 Thread Hartmann, O.
Port x11/nvidia-driver fails with the the following error. This error obviously was introduced within the updates of the last few days, since building the specific port was possible before the last weekend. Does anyone has an idea? Regards, Oliver === Vulnerability check disabled,