Date: Sat, 11 Oct 2014 05:59:02 -0700 (PDT) From: Beeblebrox <zaphod@berentweb.com> To: freebsd-ports@freebsd.org Subject: Re: py-imaging vs. py-pillow Message-ID: <20141011155821.703bb6d2@rsbsd.rsb> In-Reply-To: <CAHtVNLNLjbxj0mD7BrAj76UeqJ-eLzGi4J-zEY45p23BRzDskw@mail.gmail.com> References: <542E677A.7080205@gmx.net> <20141003203057.GA1053@medusa.sysfault.org> <1412607401631-5954805.post@n5.nabble.com> <CAHtVNLNLjbxj0mD7BrAj76UeqJ-eLzGi4J-zEY45p23BRzDskw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Build fails if tiff is enabled (py27-pillow-2.6.0) OPTIONS_FILE_SET+=TIFF Gives: "ValueError: --enable-tiff requested but tiff not found, aborting" Just advising in case you have not been made aware. Regards. ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/py-imaging-vs-py-pillow-tp5954043p5955962.html Sent from the freebsd-ports mailing list archive at Nabble.com. From owner-freebsd-ports@FreeBSD.ORG Sat Oct 11 13:00:16 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C5667BDE for <freebsd-ports@freebsd.org>; Sat, 11 Oct 2014 13:00:16 +0000 (UTC) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id ADDC32ED for <freebsd-ports@freebsd.org>; Sat, 11 Oct 2014 13:00:16 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NDA00D1Q6ZAUT00@hades.sorbs.net> for freebsd-ports@freebsd.org; Sat, 11 Oct 2014 06:04:24 -0700 (PDT) Message-id: <543929DD.7000807@sorbs.net> Date: Sat, 11 Oct 2014 15:00:13 +0200 From: Michelle Sullivan <michelle@sorbs.net> User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Lars Engels <lars.engels@0x20.net> Subject: Re: PKG not quite ready for prime time References: <sl4g3adpms8lkd2rr38n3666et8eptsp9i@4ax.com> <543817AA.8080305@gmx.de> <he6g3apojoln19fd9d8gr2rs0koq3a6940@4ax.com> <54381E16.9070609@FreeBSD.org> <1a8g3athvnun67c4kljhjtsjjlc30116j1@4ax.com> <543837CF.9070607@FreeBSD.org> <1412970941.2397812.177601925.2135B6F5@webmail.messagingengine.com> <54385A9A.8020907@sorbs.net> <20141011120854.GA20243@e-new.0x20.net> In-reply-to: <20141011120854.GA20243@e-new.0x20.net> Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 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: Sat, 11 Oct 2014 13:00:16 -0000 Lars Engels wrote: > On Sat, Oct 11, 2014 at 12:15:54AM +0200, Michelle Sullivan wrote: > >> Mark Felder wrote: >> >>> On Fri, Oct 10, 2014, at 14:47, Bryan Drewery wrote: >>> >>> >>>> On 10/10/2014 1:12 PM, scratch65535@att.net wrote: >>>> >>>> >>>>> On Fri, 10 Oct 2014 12:57:42 -0500, Brian Drewery wrote: >>>>> >>>>> >>>>> >>>>>> find /usr/share/keys/pkg -exec sha256 {} + >>>>>> >>>>>> >>>>> No such file >>>>> >>>>> >>>> That's your problem. You are missing the signature fingerprints to >>>> compare against. As such Pkg is refusing to do anything to prevent MITM >>>> attacks. >>>> >>>> You are missing this: >>>> https://www.freebsd.org/security/advisories/FreeBSD-EN-14:03.pkg.asc >>>> >>>> freebsd-update can provide it. >>>> >>>> >>>> >>>> >>> Ahh, good point. This is better advice. Even if your system was >>> supposedly fully up to date freebsd-update would detect this is missing >>> and repair it as it was part of an SA. This is better advice than my >>> manual creation method :-) >>> >>> >> Didn't on mine, I ran into the same problem - though it wasn't a show >> stopper for me as I was trying to use my own repo - which also failed >> using the docs... and nothing in the debug gave any clues or additional >> information to the problem. Fortunately, I can read/write code, so I >> fixed things myself. >> > > Thanks for creating an PR. > Actually I noticed about 72 hours ago, and I'm still trying to fix everything that was broken by the forced change... so there is no way I'm going to be doing any PRs until that's all done... and 23rd Oct my boss has me flying to SFO to discuss with the Eng & Ops team about changing all my servers over from FreeBSD to Redhat - exactly what I thought they would - been unable to update/patch any of my prod servers against the Bash bug because the entire build system is broken because of the 'End of life = This is the day its all going to break' issue... so not really got any motivation to log any PRs now... or ever again. Regards, -- Michelle Sullivan http://www.mhix.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141011155821.703bb6d2>