From owner-freebsd-ports@freebsd.org Sun Mar 20 20:32:47 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C549AD7C5B for ; Sun, 20 Mar 2016 20:32:47 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU004-OMC3S13.hotmail.com (blu004-omc3s13.hotmail.com [65.55.116.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A7D180 for ; Sun, 20 Mar 2016 20:32:46 +0000 (UTC) (envelope-from carmel_ny@outlook.com) Received: from BLU436-SMTP127 ([65.55.116.74]) by BLU004-OMC3S13.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sun, 20 Mar 2016 13:32:39 -0700 X-TMN: [vQE/sv492NoC6hv55cfQCTLvZZkz5KK+] X-Originating-Email: [carmel_ny@outlook.com] Message-ID: X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.99 at scorpio.seibercom.net Date: Sun, 20 Mar 2016 16:32:35 -0400 From: Carmel To: FreeBSD Ports Subject: Re: clamav problem In-Reply-To: <20160320154254.GI35640@home.opsec.eu> References: <56EC3B91.6030303@protected-networks.net> <895F5CC6-9F5D-4A12-A8C3-E004F4157B4A@pozo.com> <20160320114402.GH35640@home.opsec.eu> <20160320154254.GI35640@home.opsec.eu> Organization: Seibercom NET X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.28; i686-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 20 Mar 2016 20:32:39.0663 (UTC) FILETIME=[A58777F0:01D182E7] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2016 20:32:47 -0000 On Sun, 20 Mar 2016 16:42:54 +0100, Kurt Jaeger stated: >Hi! > >> >The make check of clamav exposes some issues, I've reported them >> >upstream: >> > >> >https://bugzilla.clamav.net/show_bug.cgi?id=11542 >> >> For whatever reason, I keep getting this error message when I try an >> access that report: >> >> You are not authorized to access bug #11542. > >Yes. It seems clamav bugzilla is restrictive and I can not change >that, as submitter of that bug. Now that makes about "ZERO" sense. Why would you (meaning clamav) want to hide bug information? Dumbest thing I ever saw (almost). -- Carmel