From owner-freebsd-ports@freebsd.org Tue Mar 6 07:40:18 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61469F3ADBC for ; Tue, 6 Mar 2018 07:40:18 +0000 (UTC) (envelope-from ehaupt@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 00F3287E53 for ; Tue, 6 Mar 2018 07:40:18 +0000 (UTC) (envelope-from ehaupt@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id B3806F3ADB9; Tue, 6 Mar 2018 07:40:17 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A11EBF3ADB8 for ; Tue, 6 Mar 2018 07:40:17 +0000 (UTC) (envelope-from ehaupt@FreeBSD.org) Received: from critical.ch (critical.ch [IPv6:2a01:4f8:c17:de4::1:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "critical.ch", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2998C87E4E; Tue, 6 Mar 2018 07:40:17 +0000 (UTC) (envelope-from ehaupt@FreeBSD.org) Received: from wiggles.local (dynamic.wline.6rd.res.cust.swisscom.ch [IPv6:2a02:1203:ecb4:4390:dad3:85ff:fe79:dd2] (may be forged)) (authenticated bits=0) by critical.ch (8.15.2/8.15.2/critical-1.0) with ESMTPA id w267eA1e015078; Tue, 6 Mar 2018 08:40:14 +0100 (CET) (envelope-from ehaupt@FreeBSD.org) X-Authentication-Warning: milkyway.critical.ch: Host dynamic.wline.6rd.res.cust.swisscom.ch [IPv6:2a02:1203:ecb4:4390:dad3:85ff:fe79:dd2] (may be forged) claimed to be wiggles.local Date: Tue, 6 Mar 2018 08:40:05 +0100 From: Emanuel Haupt To: "Jason E. Hale" Cc: Emanuel Haupt , "ports@freebsd.org" , Yuri Subject: Re: Why some python ports fail with build_fs_violation like this: usr/local/lib/python3.6/site-packages/dbus/__pycache__ ? Message-Id: <20180306084005.6379034c47e40cd89709dacd@FreeBSD.org> In-Reply-To: References: <935dd8c6-18ab-cd7f-1f41-31ff44179719@rawbw.com> <20180305112450.4bf542c1b3f2e0e9e993ad4e@FreeBSD.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 07:40:18 -0000 "Jason E. Hale" wrote: > On Mon, Mar 5, 2018 at 5:24 AM, Emanuel Haupt > wrote: > > Yuri wrote: > >> Examples: > >> > >> http://package21.nyi.freebsd.org/data/111amd64-default-qat/463452/logs/errors/py36-notify2-0.3.1.log > >> > >> http://package21.nyi.freebsd.org/data/111amd64-default-qat/463452/logs/errors/Carla-1.9.8.log > >> > >> > >> Yuri > > > > I run into the same problem trying to update the nagstamon port > > (both poudriere and poudriere-devel). > > > > In my case the port is heavily reliant on python36 flavoured > > dependencies. > > > > Here is my build log: > > http://people.freebsd.org/~ehaupt/misc/7DB621161F-672C5B551B-0F0958D74F-E60E451E4E/nagstamon-3.0.2.log > > > > In my case the following files are modified during the build stage: > > > > extra: > > usr/local/lib/python3.6/site-packages/dbus/mainloop/__pycache__ > > extra: usr/local/lib/python3.6/site-packages/dbus/__pycache__ > > > > I'm not sure why that happens. > > > > Emanuel > > The problem looks to be in the devel/py-dbus port. It uses a script > called ${WRKSRC}/py-compile to compile the Python bytecode, but it is > not PEP 3147 compliant. I.e., it is writing out .pyc and .pyo files in > Python < 3.2 style. Therefore, whenever the ports you are trying to > build are loading the dbus module, it is creating the bytecode in the > correct location on the fly and touching the filesystem. Thank you for your explanation. Emanuel