From owner-freebsd-ports@FreeBSD.ORG  Wed Mar  5 07:05:11 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 4A4A8E7
 for <freebsd-ports@freebsd.org>; Wed,  5 Mar 2014 07:05:11 +0000 (UTC)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com
 [IPv6:2607:f8b0:4001:c03::232])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 18313E3C
 for <freebsd-ports@freebsd.org>; Wed,  5 Mar 2014 07:05:11 +0000 (UTC)
Received: by mail-ie0-f178.google.com with SMTP id lx4so650121iec.23
 for <freebsd-ports@freebsd.org>; Tue, 04 Mar 2014 23:05:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=a6DkU+lAjSNJQ37BD0Y6xzSBlTOItcFs1nOGzumNPgE=;
 b=EhvrZ1VTb0hbI9c+EpVweKkdoWiD0KyLtJKsx4XymshDEyfT+FWByLqbopUyFGKxtB
 v3M/nr8akGTE5lZKE1F2weFbK5ERSgd7Cfcc7tTwIO2nxHKMDmQh35u5CF6DA/YnBv2x
 tC7yGzQGn5j+z3ie+QNqAzde4vJgh1xm0Ln0gb6pv+67/8+HBhPymherYRiDl+InT3RE
 ggj/RO1b9+Tybz4HEzv3HFm0S3H4lHaQgLi1ALpdypfqEEAWQzT9zpDPjnQfVwfYNmQ2
 47LZRRE2ztVGVoKqb0C1VdFDTrZmgXG0unEm01v3n1zQqs9mIgdUXfCMwWqK4BgUDx1x
 kGPQ==
MIME-Version: 1.0
X-Received: by 10.50.66.180 with SMTP id g20mr33022573igt.44.1394003110648;
 Tue, 04 Mar 2014 23:05:10 -0800 (PST)
Received: by 10.50.164.227 with HTTP; Tue, 4 Mar 2014 23:05:10 -0800 (PST)
In-Reply-To: <6C7E006A-63EF-4A89-8B68-BE8AE10FE84E@odo.in-berlin.de>
References: <201310232003.39787.Mark.Martinec+freebsd@ijs.si>
 <029DD189-E4F7-441D-95A4-08E73327DBDB@odo.in-berlin.de>
 <CACdU+f-jOTO9mpo797Xn6Sx8=94qc=6n3cB-GjCDCxrRAeHymA@mail.gmail.com>
 <F56A09C9-1E17-4D84-8D94-638805D1CE7E@odo.in-berlin.de>
 <CACdU+f_CwUHfhuVA2ANYgidnhfnOXyyrXO4CuGUWtDWRH-aLMA@mail.gmail.com>
 <6C7E006A-63EF-4A89-8B68-BE8AE10FE84E@odo.in-berlin.de>
Date: Wed, 5 Mar 2014 01:05:10 -0600
Message-ID: <CACdU+f_7HVhNVj1w9tDNatB4myaf_Af-J_W1+Oq1B+OHWK8M6w@mail.gmail.com>
Subject: Re: amavis[12345]: (12345-02) (!)file utility failed: exit 1
From: Scot Hetzel <swhetzel@gmail.com>
To: Michael Grimm <trashcan@odo.in-berlin.de>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Mar 2014 07:05:11 -0000

On Tue, Mar 4, 2014 at 12:19 PM, Michael Grimm
<trashcan@odo.in-berlin.de> wrote:
> Hi --
>
> On 04.03.2014, at 14:04, Scot Hetzel <swhetzel@gmail.com> wrote:
>> On Mon, Mar 3, 2014 at 10:39 AM, Michael Grimm <trashcan@odo.in-berlin.de> wrote:
>
>>> amavisd-new requires sysutils/file which throws an error
>
> [...]
>
>> I checked the Magdir/windows file and the bug is still there.  You
>> will need to apply the patch that is in PR 183257 to get rid of the
>> error.
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=183257
>>
>> Could someone commit this patch to the sysutils/file port.
>
> Oh, I see. I was just curious whether I might have missed something obvious.
>
> Regarding amavisd-new there is a workaround, I am using /usr/bin/file for the time beeing.
>
Looks like the file utility programmers fixed it another way by
patching src/softmagic.c to use the C locale when calling regcomp.

See http://bugs.gw.com/view.php?id=292

They had fixed the issue on 2/18/2014, so you will have to wait for
file > 5.17 to be released.

Of apply the patch in that bug report.

-- 
DISCLAIMER:

No electrons were maimed while sending this message. Only slightly bruised.